fanda

Hello Pete It seems the fsuipc beta 4.935a for P3D 2.3 does not longer allowes writing the Fuel Flow values. 0x0918 and 0x09B0. We are getting OK after write, but checking the values afterwords via FSUIPC logging results in the P3D values. This behavior was different in the older versions of FSUIPC, allowing us to overwrite the values. We have used overwrite in order to supply 3rd party software with correct Fuel Flow values, as our Q400 addon does not use the FSX/P2D flight dynamics engine. Would it be possible to restore this behavior? Thank you for taking your time to read this With best regards, Oleksiy Frolov Majestic Software

Hello Pete Thank you for the answer. It seems that the change in the timing due to the new simconnect interface in the latest fsuipc has caused the autopilot to react differently than before. We've simply re-tuned the time constants to compensate, so it works.. >Also, versions 4.2xx use the SP2/Accel version of SimConnect, if installed, whereas 4.1xx used at most the SP1 version. Are >you using SP2/Accel or just SP1 with FSX? Yes, I do. I have tested both 4.20 and 4.15 with FSX SP2. Actually the fact that the autopilot was working (far) less stable with the SP2 Simconnect (FSUIPC 4.20) could suggest that the FSX data, in the newer simconnect version is being accessed slower, than before. With best regards, Oleksiy Frolov Majestic Software

Hello Pete I can now definitely confirm that FSUIPC 4.20 causes the trouble in the Dash-8 autopilot operation, and 4.15 not. Will it be possible to get a version 4.16 for testing, to see which version is the first one, affected by this problem ? Thank you very much regards, Oleksiy Frolov Majestic Software

Hello Pete In the recent week I have suddenly got numerous reports of the erratic autopilot behavior of our Dash8Q300 addon, when used with FSUIPC 4.2. When replaced with FSUIPC 4.152 problem disappears. Usually this would indicate that the acceleration data differs between the versions. Do you have an idea what might have been changed between 4.152 and 4.2 that might be causing this trouble ? Thank you, With best regards, Oleksiy Frolov Majestic Software

Hello Pete, * One of my customers, who is trying to use our Dash 8 addon with FSUIPC for FSX, came with the following FSUIPC log: (FSX SP1, firewall off) Any idea what might be the cause for this failure ? Thank you With best regards, Oleksiy ********* FSUIPC4, Version 4.20 by Pete Dowson ********* User Name="" User Addr="" FSUIPC4 not user registered WIDEFS7 not user registered, or expired Running inside FSX (SimConnect SP1 May07) Module base=61000000 DebugStatus=0 110 System time = 17:37:53 110 FLT UNC path = "C:\Documents and Settings\Dimitri\Мои документы\Flight Simulator X-Dateien\" 110 FS UNC path = "K:\FS X\" 1360 LogOptions=00000001 1360 SimConnect_Open succeeded: waiting to check version okay 64063 **** No SimConnect events or states being received! Re-connecting now ... **** 64172 Now running with SimConnect Original 64172 SimConnect_Open succeeded: waiting to check version okay 94954 **** No SimConnect events or states being received! Re-connecting now ... **** 95063 Could not link to all needed SimConnect facilities 110141 **** Retrying SimConnect connection**** 110141 Could not link to all needed SimConnect facilities [code 0] 125188 **** Retrying SimConnect connection**** 125188 Could not link to all needed SimConnect facilities [code 0] 135766 System time = 17:40:09 135766 *** FSUIPC log file being closed Memory managed: 2 Allocs, 2 Freed ********* FSUIPC Log file closed ***********

Hello Pete, * One of my customers, who is trying to use our Dash 8 addon with FSUIPC for FSX, came with the following FSUIPC log: (FSX SP1, firewall off) Any idea what might be the cause for this failure ? Thank you With best regards, Oleksiy ********* FSUIPC4, Version 4.20 by Pete Dowson ********* User Name="" User Addr="" FSUIPC4 not user registered WIDEFS7 not user registered, or expired Running inside FSX (SimConnect SP1 May07) Module base=61000000 DebugStatus=0 110 System time = 17:37:53 110 FLT UNC path = "C:\Documents and Settings\Dimitri\Мои документы\Flight Simulator X-Dateien\" 110 FS UNC path = "K:\FS X\" 1360 LogOptions=00000001 1360 SimConnect_Open succeeded: waiting to check version okay 64063 **** No SimConnect events or states being received! Re-connecting now ... **** 64172 Now running with SimConnect Original 64172 SimConnect_Open succeeded: waiting to check version okay 94954 **** No SimConnect events or states being received! Re-connecting now ... **** 95063 Could not link to all needed SimConnect facilities 110141 **** Retrying SimConnect connection**** 110141 Could not link to all needed SimConnect facilities [code 0] 125188 **** Retrying SimConnect connection**** 125188 Could not link to all needed SimConnect facilities [code 0] 135766 System time = 17:40:09 135766 *** FSUIPC log file being closed Memory managed: 2 Allocs, 2 Freed ********* FSUIPC Log file closed ***********

Hello For some reason engine starter does not operate under SP1, although it could still be my fault somewhere, but I thought to check if there is a possible cause due to the fact that FSUIPC 4.09 was not meant for SP1 I will give you an email regards, Oleksiy

Hello Pete I am testing my Dash 8Q300 FSX patch with SP1 beta 3, and it seems that FSUIPC 4.09 does not run very stable.. It there an FSUIPC beta available, which would support the SP1 beta 3? If so, can I test it ? Thank you With best regards, Oleksiy

actually it is a brilliant idea. One can use the non-null air file path as an indication that FSUIPC has began receiving the data. Thanks regards, Oleksiy

Found the problem, sorry for the trouble I was not waiting for FSUIPC to initialize. Somehow it worked in FS9, but no longer did in FSX. So I added a check for 0xFFFF in 0x4D2 and it works . Thank you With best regards, Oleksiy

Hello Everyone It seems that the new FSUIPC 4.09 no longer returns the air file name in the offset 0x3c00. The result is always empty (no errors reported). Replacing dll with 4.01 solves the problem. Any idea ? Thank you With best regards, Oleksiy Frolov

Hello Pete I would put the remark as follows: The name in 3C00 will not contain the correct aircraft path, untill MSFX loads the gauges completelly and begin the update sequence PANEL_SERVICE_PRE_UPDATE... PANEL_SERVICE_POST_UPDATE >Do you think there are likely to be many gauges actually using FSUIPC4 >when they can get this stuff direct from SimConnect? I am adapting our Dash 8 Q300 to MSFX, and it is using your fsuipc. Not sure how many gauges will do the same, but some will obviously do . rgds, Oleksiy

Hello Pete I figured out the problem. The name in 3C00 is not yet correct when gauges are passed PANEL_SERVICE_POST_INSTALL. However in the PANEL_SERVICE_PRE_UPDATE it is already set properly May be need to be noted in the SDK word file. With best regards, Oleksiy

Hello Pete 0x3C00 (aircraft path) still reflects a previous aircraft, if a new aircraft has been selected due to the situation load, instead of the "aircraft selection" menu in FSX With best regards, Oleksiy

Hello Pete In the FSUIPC 3.7.0.0 the offsets 11D4 and 3364 always return 0 (even when FS is flying) I could confirm that by both using my own code, and your FSInterrogate2std.exe appication Is it possible to fix it ? We use these offsets to see the simulator state. Thanks. Best Regards, Oleksiy Frolov