Read a posted FS Message in FS9

[Vincent T]

I am using Flight Simulator 2004 and wanted to know if there is a way I can capture the text from a posted FS message. Like when the door of the aircraft is closed, the text Door closed is displayed. I want to capture that message.

 

I did read and see that the offset 0x3380 can be used to write a message, but it cannot read the same value.

 

public Offset<string> messageWrite = new Offset<string>(0x3380, 128);

 

I wouldn't mind sharing what I am trying to do. I am using 3rd party software's that display various text messages. For example FSPassengers displays messages of crossing 10000 ft, seats belts off or on, door closed etc. I want to trap these messages into my program. The reason why I want to trap is I don't want to keep the FS9 window open is to reduce the CPU heat by running FS9 onscreen, I would rather keep it minimized. These are some of the examples, I know I could probably check doors, or seat belt etc, but want to know if there is anyway within FSUIPC or any addon that I can read the string message.

 

Thanks in advance

 

Regards,

Vincent. 

 

[Pete Dowson]

 

I am using Flight Simulator 2004 and wanted to know if there is a way I can capture the text from a posted FS message. Like when the door of the aircraft is closed, the text Door closed is displayed. I want to capture that message.

 

I did read and see that the offset 0x3380 can be used to write a message, but it cannot read the same value.

 

Where did you read that? The offsets list for FS2004 (as installed in your FSUIPC Documents folder) actually describes the READING of the messages at 3380 before the additional function of writing messages -- though there are a number of FS messages which can't be seen this way, like "BRAKES", "PAUSE" or "SLEW". Not sure about the door messages, though of course for those you can simply read the door status offset and make your own message.

 

The FSX list, on the other hand, is different. In FSX the messages from FS itself can't be so read, only those from third party software using FSUIPC  Maybe the source for the information you have was about FSX?

 

Pete

[Vincent T]

Hi Pete,

 

Thanks for your response. I worded my request wrongly. When I meant - "I did read and see that the offset 0x3380 can be used to write a message, but it cannot read the same value." I meant that I could use a code snippet to write to FS and it would display it the FS window with the offset of 3380, but I could not read any other messages posted by FS.

 

I haven't specifically tried about FS Passengers, but the default FS messages like door closed, was not read when making a refresh call with offset 3380. Since you have mentioned that I can actually read, let me go back and see what I can get. Thanks for pointing me into some direction.

 

I am using FS9, and hope to trap those messages. 

 

Thanks again!

Vincent

[Pete Dowson]

Hi Pete,

 

Thanks for your response. I worded my request wrongly. When I meant - "I did read and see that the offset 0x3380 can be used to write a message, but it cannot read the same value." I meant that I could use a code snippet to write to FS and it would display it the FS window with the offset of 3380, but I could not read any other messages posted by FS.

 

I haven't specifically tried about FS Passengers, but the default FS messages like door closed, was not read when making a refresh call with offset 3380. Since you have mentioned that I can actually read, let me go back and see what I can get. Thanks for pointing me into some direction.

 

Well, I think it can read the ATIS messages, though I vaguely recall that the main purpose of the facility in the first place was to grab text output from FS Adventures, in FS2000, It's a bit hazy, as this was done many years ago, after all -- with over 14 years of continuous FSUIPC development it is getting difficult to identify how or why things were done. And I am a lot older now which doesn't help.

 

I really don't know about the ones you are interested in -- many are not posted to the function being intercepted.  I know it doesn't get the paused, slew, view names and brakes messages, and perhaps the exit opening and closing messages are in that group. If they don't appear in the same place (actually the "message window") as the ATIS messages, then they aren't sent to that window, and there's no way you will do it with FSUIPC, You'd need to find the correct place in FS's Windows.DLL to hook into (assuming they even go through Windows.DLL).

 

Pete