activex

I'd like to answer my own question. I discovered that the cause of the problem was the fact that I was using "int" instead of "uint" for 0x0580, same goes for the 0x02A0 dataref, I was using short instead of ushort. I wish the documentation would tell me whether the dataref is signed or not. Yuck, you have to figure this out for yourself. Consider this issue solved.

Hi, When I read (using current version of FSUIPC7) aircraft heading values using offsets (0x0580 {32-bit int}, 0x02A0 {16-bit, short}) I get wrong values. I know the values are wrong because I can compare them with the values displayed in the interrogate tool. Interestingly, in the interrogate tool, the values are correct. I am using C# and FSUIPCClient SDK which is a wrapper around FSUIPC. Reading other offsets works btw. Ex of code snippet I am using: FSUIPCConnection.Open(); var aircrafthdg = new Offset<int>(0x0580); FSUIPCConnection.Process(); var aircrafthdgVal = aircrafthdg.Value; FSUIPCConnection.Close(); What am I doing wrong? Thanks in advance.

Ah, OK. The value only changes from 0 to 90 when you hit toga but it never changes after that. I thought it was coming from the simulator.

Thanks Pete for the reply. In the default 737 for example when you hit TOGA you will notice in the engine display the value of '0' in green (preset climb power) changes to '90.0'. So I figured, flight sim must have this value available. Anyway, I tried the suggested offset and it did not work (the value never changed). Regardless, I realize that I don't need to read this value anymore. It is sufficient to read the RPM hold value to determine if N1 is depressed for my TQ interface software. Therefore, don't worry about it. Thanks again for your pompt response. It is greately appreciated and helpful. Luke

Hi Pete, Sorry to bother you. I did much searching but could not find an offset in FSUIPC (for FSX) for climb power before take-off, ie. N1 preset power (in %) which will be used on take off when TOGA is active or N1 is depressed, also know as target N1 power. Is there an offset for this? Thanks. Luke

Hi Peter, Thanks for the lightning fast response. I will try to keep this response short. Yes, I agree with your statement: "FSUIPC4 and FSX are both 32-bit programs. There's absolutely no difference is what they do between the 32-bit and 64-bit platforms. There can't be." I thought exactly like you have stated but wanted to verify that FSUIPC is 32-bit. After performing suggested logging in conclusion there's nothing wrong with my software, FSUIPC, nor FSX. The data is written correctly via SimConnect and the SimConnect version is the same across both installations. So what gives? I am not sureonly thing that I can think of is this: The 64-bit installations had REX installed which uses older SimConnect. I actually had to install older version of SimConnect since I never applied SP1 since I updated my sim with FSX: Acceleration which has SP2 on and apparently it never installs the older version of SimConnect since I was getting errors running REX. Instead of trying to continue the investigation and uninstall the mega lengthy installation of REX I chose the easier route and used the 16-bit offsets (which I totally was not aware they existed and that's why I did not use them). Using the 16-bit offsets works like a charm across the board. Thanks for your help. Luke

Hi there, I am writting a throttle quadrant software in .net 2.0/C#. All but the following functions don't work with FSUIPC and FSX on 64-bit platform whether it is VISTA or XP but works fine on 32-bit platforms: - Mixture lever position offsets that I am using don't work on 64-bit platform (3AF0, 3A30). They are mapped in my application to a double which is under CLR 64-bit floating point which is what it should be according to the FSUIPC SDK. So what happens when you set these offsets: In FSUIPC interogate the values change correctly but FSX just ignores them, absolutely nothing happens in the simulator - it's like FSX is ignoring the changed values. I need further assistance. Thanks, Luke