Jump to content
The simFlight Network Forums

FSUIPC version 7.4.6 not working right


Cuantreau

Recommended Posts

Hi John, since latest update 7.4.6 I have a couple of issues that did not happen prior to updating from 7.4.5.

First one is key assignments are not working anymore and last when pressing ALT ENTER to make msfs in full screen a weird flash appears for a second, this happens only with this new version. 7.4.5 was working wonderfully. Thanks for your support as always.

FSUIPC7.ini FSUIPC7.log InstallFSUIPC7.log

Link to comment
Share on other sites

12 minutes ago, Cuantreau said:

First one is key assignments are not working anymore

Your log shows that you were trying to control things before everything was ready:

Quote

    90125 C:\Users\Bocha\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\MISSIONS\Custom\CustomFlight\CustomFlight.FLT
    91875  [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '11002 (>K:ROTOR_BRAKE)'
    91875  [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '100 (L:switch_124_73X, number) == if{ 12401 (>K:ROTOR_BRAKE) }'
    91875  [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '100 (L:switch_117_73X, number) == if{ 11701 (>K:ROTOR_BRAKE) }'
    91875  [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '(L:switch_123_73X, number) s0 l0 50 == if{ 12301 (>K:ROTOR_BRAKE) } l0 0 == if{ 12301 (>K:ROTOR_BRAKE) 12301 (>K:ROTOR_BRAKE) }'
    91875  [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '100 (L:switch_115_73X, number) == if{ 11501 (>K:ROTOR_BRAKE) } 100 (L:switch_116_73X, number) == if{ 11601 (>K:ROTOR_BRAKE) }'
    91875  [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '(L:switch_258_73X, number) s0 l0 0 == if{ 25801 (>K:ROTOR_BRAKE) } l0 100 == if{ 25802 (>K:ROTOR_BRAKE) }'
    91875  [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '10 (L:switch_460_73X) - 10 div s0 :1 l0 0 > if{ 46007 (>K:ROTOR_BRAKE) l0 -- s0 g1 } l0 0 < if{ 46008 (>K:ROTOR_BRAKE) l0 ++ s0 g1 }'
    93406 Starting WAPI (out of Parking State)...
    93406   [INFO]: **** Starting FSUIPC7 WASM Interface (WAPI) version 1.0.4 (WASM version 1.0.3) using connection -1
    93406   [INFO]: Connected to MSFS
   110906 -------------------- Starting everything now ----------------------
 

You need to wait until everything is connected and ready, so can you please try again and wait a little longer - it looks like its taking just under 2 minutes to load the PMDG 737 and get everything ready. If that is not the issue, please activate logging for Buttons & Keys and Events, and show me a log file where your key presses are not working, i.e. load the aircraft, wait until everything is loaded, then press a few assigned keys, then exit before attaching your FSUIPC7.log and FSUIPC7.ini files.

18 minutes ago, Cuantreau said:

when pressing ALT ENTER to make msfs in full screen a weird flash appears for a second, this happens only with this new version. 7.4.5 was working wonderfully.

This seems to work ok here...

I have just fired-up MSFS and there was yet another update. I have noticed that key assignments seem to be a bit hit and miss - they work sometimes but the reception of keys seems to get stalled sometimes. No idea what they have done, but it looks to be an issue on MSFS's side. I will look into this further tomorrow.

I also now see a continual spinning circle in the bottom right of MSFS, so it looks to be continually bust for some reason... 

Link to comment
Share on other sites

Do you have FSUIPC auto-started? If so, try exiting FSUIPC7 and restarting it once your aircraft is loaded. This seems to make the key reception a lot more reliable.

It looks like there may be performance issues in the latest update, and having FSUIPC7 started by the sim means that the processor time allowed for FSUIPC7 is restricted by the sim. Starting this manually seems to fix this.

I will investigate further tomorrow.

John

Link to comment
Share on other sites

Hi John, thanks for the quick reply. I've just re-installed 7.4.5 now and want to make a few flights today. The spinning circle started yesterday (or the day before) with a msfs forced update "Dune" something that I did not buy but when you exit the sim and restart the spinning circle and performance drop should go away (at least this happened to me and a few others that I read on avism)

I load FSUIPC from msfs EXE.xml file with this command:

<Launch.Addon>
    <Name>FSUIPC7</Name>
    <Disabled>False</Disabled>
    <Path>C:\FSUIPC7\FSUIPC7.exe</Path>
    <CommandLine>-auto</CommandLine>
  </Launch.Addon>

and have been doing it this way since I can remember with no issues.

I'm on MSFS SU14 (no beta) and FSUIPC 7.4.5 is working great. Will try logging buttons & keys and events tomorrow. Will let you know. Thanks a lot again for the support.

Link to comment
Share on other sites

13 hours ago, Cuantreau said:

The spinning circle started yesterday (or the day before) with a msfs forced update "Dune" something that I did not buy but when you exit the sim and restart the spinning circle and performance drop should go away (at least this happened to me and a few others that I read on avism)

Yes - after a restart, everything is working here, including key assignments.

13 hours ago, Cuantreau said:

I load FSUIPC from msfs EXE.xml file with this command:

<Launch.Addon>
    <Name>FSUIPC7</Name>
    <Disabled>False</Disabled>
    <Path>C:\FSUIPC7\FSUIPC7.exe</Path>
    <CommandLine>-auto</CommandLine>
  </Launch.Addon>

and have been doing it this way since I can remember with no issues.

Yes, that is how the auto-start works.

13 hours ago, Cuantreau said:

I'm on MSFS SU14 (no beta) and FSUIPC 7.4.5 is working great. Will try logging buttons & keys and events tomorrow. Will let you know. Thanks a lot again for the support.

Ok, I will need to see your files to determine what the issue is. Some folks had connection issues with 7.4.5, hence the update. There weren't any changes that could affect key assignments though (apart from a minor correction where key assignments to presets selected from the Find Preset weren't being saved/stored correctly) so I am surprised at your issue....

John

Link to comment
Share on other sites

OK John, today I installed MSFS beta SU15 and re installed FSUIPC v7.4.6 and I should say everything is working as it should, starting FSUIPC automatically. I'll leave you the logs, but all's good now, don't have a clue what fixed it (the beta SU15 may be the answer). The flashing I was talking about only happens with MSFS in Devmode. Thanks a lot for helping out John.

FSUIPC7.ini FSUIPC7.log

Link to comment
Share on other sites

1 hour ago, Cuantreau said:

I'll leave you the logs

No point if its working, but your logs show that you are still trying to control things before everything is ready:

Quote

    66859 System time = 15/02/2024 14:39:17, Simulator time = 16:39:15 (17:39Z)
    66875 Aircraft="PMDG 737-800 Aerolineas Argentinas (LV-GUC)"
    66875 Button changed: bRef=0, Joy=0 (A), Btn=20, Pressed
    66875 [Buttons.PMDG 737-800 Aerolineas Argentinas (LV-GUC)] 5=PA,20,CPPMDG_B737-7_LIGHTS_RETRACTABLE_LANDING_ALL_OFF,0
    66875  [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '11002 (>K:ROTOR_BRAKE)'
    66875 Button changed: bRef=0, Joy=0 (A), Btn=28, Pressed
    66875 [Buttons.PMDG 737-800 Aerolineas Argentinas (LV-GUC)] 7=PA,28,CPPMDG_B737-7_LIGHTS_ANTI_COLLISION_OFF,0
    66875  [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '100 (L:switch_124_73X, number) == if{ 12401 (>K:ROTOR_BRAKE) }'
    66875 Button changed: bRef=0, Joy=0 (A), Btn=24, Pressed
    66875 [Buttons.PMDG 737-800 Aerolineas Argentinas (LV-GUC)] 8=PA,24,CPPMDG_B737-7_LIGHTS_TAXI_OFF,0
    66875  [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '100 (L:switch_117_73X, number) == if{ 11701 (>K:ROTOR_BRAKE) }'
    66875 Button changed: bRef=0, Joy=0 (A), Btn=15, Pressed
    66875 [Buttons.PMDG 737-800 Aerolineas Argentinas (LV-GUC)] 18=PA,15,C66587,37802
    66875 FS Control Sent: Ctrl=66587, Param=37802 ROTOR_BRAKE
    66875 Button changed: bRef=0, Joy=0 (A), Btn=17, Pressed
    66875 [Buttons.PMDG 737-800 Aerolineas Argentinas (LV-GUC)] 19=PA,17,C66587,40702
    66875 FS Control Sent: Ctrl=66587, Param=40702 ROTOR_BRAKE
    66875 Button changed: bRef=0, Joy=0 (A), Btn=13, Pressed
    66875 [Buttons.PMDG 737-800 Aerolineas Argentinas (LV-GUC)] 20=PA,13,C67279,0
    66875 FS Control Sent: Ctrl=67279, Param=0 AUTO_THROTTLE_DISCONNECT
    66875 Button changed: bRef=0, Joy=0 (A), Btn=27, Pressed
    66875 [Buttons.PMDG 737-800 Aerolineas Argentinas (LV-GUC)] 21=PA,27,CPPMDG_B737-7_LIGHTS_POSITION_STEADY,0
    66875  [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '(L:switch_123_73X, number) s0 l0 50 == if{ 12301 (>K:ROTOR_BRAKE) } l0 0 == if{ 12301 (>K:ROTOR_BRAKE) 12301 (>K:ROTOR_BRAKE) }'
    66875 Button changed: bRef=0, Joy=0 (A), Btn=22, Pressed
    66875 [Buttons.PMDG 737-800 Aerolineas Argentinas (LV-GUC)] 22=PA,22,CPPMDG_B737-7_LIGHTS_RUNWAY_BOTH_OFF,0
    66875  [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '100 (L:switch_115_73X, number) == if{ 11501 (>K:ROTOR_BRAKE) } 100 (L:switch_116_73X, number) == if{ 11601 (>K:ROTOR_BRAKE) }'
    66875 Button changed: bRef=0, Joy=0 (A), Btn=19, Pressed
    66875 [Buttons.PMDG 737-800 Aerolineas Argentinas (LV-GUC)] 26=PA,19,CPPMDG_B737-7_LIGHTS_INTERIOR_DOME_WHITE_OFF,0
    66875  [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '(L:switch_258_73X, number) s0 l0 0 == if{ 25801 (>K:ROTOR_BRAKE) } l0 100 == if{ 25802 (>K:ROTOR_BRAKE) }'
    66875 Button changed: bRef=0, Joy=0 (A), Btn=31, Pressed
    66875 [Buttons.PMDG 737-800 Aerolineas Argentinas (LV-GUC)] 28=PA,31,CPPMDG_B737-7_ANTISKID_OFF_POS_SW,0
    66875  [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '10 (L:switch_460_73X) - 10 div s0 :1 l0 0 > if{ 46007 (>K:ROTOR_BRAKE) l0 -- s0 g1 } l0 0 < if{ 46008 (>K:ROTOR_BRAKE) l0 ++ s0 g1 }'
    66875 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37802 (0x000093aa) ROTOR_BRAKE
    66875 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 40702 (0x00009efe) ROTOR_BRAKEI
    66875 *** EVENT: Cntrl= 67279 (0x000106cf), Param= 0 (0x00000000) AUTO_THROTTLE_DISCONNECT
    67734 Run: ""C:\MSFS\Community\fsltl-traffic-injector\fsltl-trafficinjector.exe""
    67734 Run: ""C:\Users\Bocha\AppData\Roaming\DynamicLOD\bin\DynamicLOD.exe""
    68094 Run: ""C:\Users\Bocha\Documents\RealTurb CAT Areas Global for MSFS\RealTurb CAT Areas Global for MSFS.exe""
    95187 C:\Users\Bocha\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\MISSIONS\Custom\CustomFlight\CustomFlight.FLT
    95203 Starting WAPI (out of Parking State)...
    95203   [INFO]: **** Starting FSUIPC7 WASM Interface (WAPI) version 1.0.4 (WASM version 1.0.3) using connection -1
    95203   [INFO]: Connected to MSFS
    96594 c:\msfs\community\pmdg-aircraft-738\simobjects\airplanes\pmdg 737-800\aircraft.cfg
    96594 Aircraft loaded: running normally now ...
   122719 *** EVENT: Cntrl= 66703 (0x0001048f), Param= 2 (0x00000002) EXTERNAL_SYSTEM_TOGGLE
   122750 *** EVENT: Cntrl= 66702 (0x0001048e), Param= 6 (0x00000006) EXTERNAL_SYSTEM_SET
   122844 -------------------- Starting everything now ----------------------
 

You should really wait longer before trying to do anything.

1 hour ago, Cuantreau said:

don't have a clue what fixed it (the beta SU15 may be the answer)

 I don't think so....but, as I said, I need to see your files (generated when you have the issue) to diagnose. I have been testing 7.4.6 most of the day here and cannot find any issues....

1 hour ago, Cuantreau said:

The flashing I was talking about only happens with MSFS in Devmode.

I always run in DevMode and do not see this. Do you still have the same issue? FSUIPC is not involved in this at all, unless you assign alt+enter also in FSUIPC...

John

Link to comment
Share on other sites

On 2/15/2024 at 4:17 PM, John Dowson said:

No point if its working, but your logs show that you are still trying to control things before everything is ready:

You should really wait longer before trying to do anything.

 I don't think so....but, as I said, I need to see your files (generated when you have the issue) to diagnose. I have been testing 7.4.6 most of the day here and cannot find any issues....

I always run in DevMode and do not see this. Do you still have the same issue? FSUIPC is not involved in this at all, unless you assign alt+enter also in FSUIPC...

John

Hi John, as for flashing issue, yes still having it with latest version, but in devmode and within the Virtual cockpit (PMDG 737-800). Thanks

Link to comment
Share on other sites

What do you mean by 'flashing issue'?  Can you please explain what this is. Do you still enter/leave full screen mode?

Alt+Enter is an MSFS hot-key and I can't see how FSUIPC can be involved. If you exit FSUIPC7 and use Alt+Enter, do you see the same?

Link to comment
Share on other sites

like if you would take a picture with those old cameras that had flashes, all my screen goes a bit whitish for less than a second when transitioning from full screen to window mode using ALT ENTER. I will try exiting FSUIPC and let you know, thanks John.

Link to comment
Share on other sites

  • 2 weeks later...

Just an update, with latest v7.4.8, key assignments are working just as they did with 7.4.5., perfectly. Something with v.06, and v.07 where not right in regards of speed with recognizing keys assign.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.