Edward Klein Posted January 2, 2022 at 06:55 PM Posted January 2, 2022 at 06:55 PM Help, I had another aircraft on the x-pilot client text a private message to me and I was not able text a private message back using the recommended dot commands. ATC was very busy and there was no way I was going to use voice. I have limited experience using text on x-pilot and I looked up the dot commands in the manual for chat and callsign number, but it didn't work. I felt bad I was unable to reply as it was a friendly message requiring a response. I have used text for weather for airports like KORD. example: .wx kord or .metar. kord and it works fine. I tried .atis kord when it is shown, and nothing happens. I been all through the manual, in this forum and on YouTube for examples but couldn't find anything. I believe I'm typing it incorrectly. If someone could TYPE in the correct examples for atis, and contacting other aircraft or responding I would apricated it. Use DAL1949 for aircraft and KORD for atis. Thank you, Ed Link to comment Share on other sites More sharing options...
Dace Nicmane Posted January 3, 2022 at 12:37 AM Posted January 3, 2022 at 12:37 AM If the other aircraft messaged you first, then it's quite simple. You just open the respective tab and type, don't need any commands! Your screenshot has 3 tabs: Messages, Notes and SWA, the last one looks like an attempted Southwest callsign. So if you wanted to respond to them, you simply click on their tab and type. Other than that, the command should be .msg or .chat Link to comment Share on other sites More sharing options...
Dace Nicmane Posted January 3, 2022 at 12:46 AM Posted January 3, 2022 at 12:46 AM As for ATIS, I believe you can double click KORD_ATIS or right click it and choose "Get controller info" or whatever it says there (sorry, not at the computer at the moment). Link to comment Share on other sites More sharing options...
Robert Shearman Jr Posted January 3, 2022 at 01:53 AM Posted January 3, 2022 at 01:53 AM Type in the bottom: .chat SWA123 ... which opens up a separate tab where you and SWA123 may message each other privately, or... .msg SWA123 what's up ... which does the same and also sends the message "what's up" from you to SWA123 Cheers, -R. Link to comment Share on other sites More sharing options...
Edward Klein Posted January 3, 2022 at 03:06 PM Author Posted January 3, 2022 at 03:06 PM Thank you both for the quick response, Dace, I will try to click on the call tab next time I am contacted by another aircraft online. I am aware that clicking on the atis (if it is available) will bring up the information on screen. Bob, I tried this .chat SWA 123 (with spaces} as well as this .chatSWA123 (without spaces) to reestablish contact with the calling aircraft but didn't work for me Wich one is correct? Thank You in advance, Ed Link to comment Share on other sites More sharing options...
Dustin Rider Posted January 3, 2022 at 08:04 PM Posted January 3, 2022 at 08:04 PM 4 hours ago, Edward Klein said: Bob, I tried this .chat SWA 123 (with spaces} as well as this .chatSWA123 (without spaces) to reestablish contact with the calling aircraft but didn't work for me Wich one is correct? Well, neither. If you want to initiate a chat with another user, you have to type that user's actual callsign. In this case, you would type ".chat SWA123", but only if the user logged in as SWA123. Similarly, when obtaining a text ATIS, you have to request it from the ATIS provider, so you can type ".atis KORD_ATIS", not ".atis KORD". Link to comment Share on other sites More sharing options...
Dace Nicmane Posted January 4, 2022 at 12:10 AM Posted January 4, 2022 at 12:10 AM Please note that you have to follow the command syntax closely, or it's not gonna work. The proper command is .chat 〈callsign〉 (with space between "chat" and "callsign" and callsign as one word). So if you type .chatSWA123 (without the space) it's gonna be interpreted by the software as gibberish since it can't recognize the chat command when it's not followed by space and you're likely to either get an error message or be ignored. If on the other hand you introduce an extra space in the middle of the callsign (SWA 123), only the first part up to space (SWA) will be interpreted as the callsign and the extra characters will be simply ignored, so the program is gonna open a chat tab "SWA" as we see in your screenshot because that's literally what you requested. If you make the same mistake in the .msg command and type .msg SWA 123 hello, it will try to send a message "123 hello" to callsign "SWA" (which hopefully won't be connected) because again, that's what you requested when the syntax is .msg 〈callsign〉 〈message〉. Link to comment Share on other sites More sharing options...
Edward Klein Posted January 4, 2022 at 09:17 PM Author Posted January 4, 2022 at 09:17 PM Thanks Dace, You have explained this very well. I will try your suggestions the next chance I get. I thought I might be as simple as correct spacing or punctuation, but I kept getting errors anyway. I will print a copy of this forum for future reference. Probably would help the newbies or others if there were some examples in the instruction manual. Ed Link to comment Share on other sites More sharing options...
Recommended Posts