nwadc10

I tried writing a number and I kept getting an error when compiling but I'm sure it was a 32bit integer. This must be the problem and will take it from here, thanks.

Sorry for failing to add the versions of everything, they are as follows: FSUIPCClient.dll (the .NET DLL): 1.1.2397.13 I saw on this forum a supposed new version of this DLL which I have downloaded but will not incorporate into this particular program. I am working on a follow up program that I will convert to using the new version of the DLL. FS: Testing FSX FSUIPC (the FS module DLL that we pay for): current versions I am not reading the message, my program writes the message to FS. I don't know all the different ways I tried to tell the process to display for only 5 seconds but they are all variations of "5", "+5", I've tried writing to 32FA, the control offset, before writing to 3380, the message text offset. I've tried many different things where there should be only 1 correct answer which is what I'm trying to figure out. I've tried changing to write "1" (which is intended as display message for one second) to the display text control and FSInterrogate shows the value of 32FA as 48 seconds. Programmatically, this is what my code looks like: DisplayMessage->Value = "Some Text Here To Display On FS Screen"; DisplayMessageControl->Value = "5"; FSUIPCConnection::Process("Display Message"); FSUIPCConnection::Process("Display Control"); It's the DisplayMessageControl->Value = "5"; that is giving me the problem because the message itself appears without issue. In the document that comes in the FSUIPC SDK the description for offset 32FA is as follows: "Text display control word. You can display messages from an external program just like an Adventure. Write the message as a zero-terminating string to offset 3380 (see below), subject tto the maximum of 128 characters including the zero terminator, then write a number to this offset, 32FA, as follows: 0 display till replaced +n display for n seconds, or until replaced [this is what I'm trying to do] -l display and scroll, or until replaced -n display and scroll, or for n seconds, or until replaced ..." So, the real question is, what should the line DisplayMessageControl->Value = "5"; look like (particularly after the =) in order to obtain control of this feature? Thanks again! Justin

I have succesfully added text display to FS from a program using offset 3380. However, I am trying to control the length of time it is displayed using offset 32FA. I would like the message to display for 5 seconds but when I write the string "5" to the offset, FSInterrogate shows a weird number. On last check FSInterrogate showed a value of 53 when I wrote "5". I've tried all kinds of scenarios such as "+5" and I'm not getting results I want. I suspect it's a simple syntax problem. How should I be writing to this offset? I am using the old DLL if that makes a difference for the answer. Thanks! Justin

Thank you for your quick response. I'm not certain of how I am supposed to put parenthesis around the H file. I've tried a few different combinations and it gives me a file not found error. This procedure forces the compiler to view the H file as a C file rather than C++? I'm continuing to do research on it. I may have to ditch the Windows Forms project and create it as a MFC Dialog Application where the FSUIPC files compile correctly through VC++.NET 2003. Justin

Hi Pete, I've already written one program succesfully a couple years ago using your SDK and VC++6. I've upgraded to VC++.NET 2003 and am now having trouble getting the FSUIPC files to compile. I have got the error list down to 21 items, most seem to be hung up on the DWORD data type and class definitions in FSUIPC.h. I've searched MSDN and can't find any reference to DWORD in the documentation. The DWORD data type worked fine in VC++6. Have you any tips or tricks to get past this issue? Additionally, I'm using a Windows Forms project. I tried starting a MFC Application and the files compiled correctly without errors. I've searched this forum for similar issues and found nearly nothing in reference to VC++.NET 2003. Thanks for your help and your product. Justin