pilotjohn Posted September 8, 2020 Report Posted September 8, 2020 The throttle axes don't start working until I open and close the Axes settings. For some reason the aileron/elevator work fine, but I have no throttle/prop/mixture when first launched into the sim.
John Dowson Posted September 8, 2020 Report Posted September 8, 2020 That is strange. Could you activate logging for Axes Controls in FSUIPC7. Once activated, exit FSUIPC7 and restart (with MSFS running and an aircraft loaded). Then move your throttle. Then open and close the axes assignments dialog and then move the throttle again. Post the log file together with your .ini. Thanks.
pilotjohn Posted September 8, 2020 Author Report Posted September 8, 2020 The logs are attached, and here's the series of events: Start FSUIPC and enable axes logging Exit FSUIPC, delete log Start FSUIPC Start Sim Launch into flight Axis does not move anything Show FSUIPC, go to Axes, check movement/calibration, click Ok (don't have to check, clicking Ok is enough) Axis starts working in sim <end of log> I then also tried to: Exit FSUIPC Start FSUIPC Axis works correctly End flight Launch into flight Axis works correctly It seems this happens when FSUIPC is launched before the simulator. I reproduced it a second time (quit sim, exit FSUIPC, repeat first set of steps). Also, I'm not sure what the AXIS_RUDDER_SET entries are all about, since nothing is assigned to that in FSUIPC (ini attached). Lastly, since playing with FSUIPC, I've been having a few CTDs, primarily (as I remember), during the loading into a flight progress bar (including the first attempt of this test - log also attached). FSUIPC7.ini FSUIPC7-1.log FSUIPC7-2.log FSUIPC7-CTD.log
Pete Dowson Posted September 8, 2020 Report Posted September 8, 2020 9 minutes ago, pilotjohn said: Lastly, since playing with FSUIPC, I've been having a few CTDs, primarily (as I remember), during the loading into a flight progress bar (including the first attempt of this test - log also attached). Crashes in MSFS do need reporting to MS/Asobo (eg on ZenDesk) along with the Event Viewer crash details from Windows. FSUIPC is an entirely separate process and can't crash another process without it having a problem with the facilities being used. The FSUIPC log, as expected, merely shows that MSFS stopped running. the same occurs if you just close it too, though sometimes (not always though, it seems) FSUIPC will receive a QUIT notice. We could try to narrow down the actions leading to such, but if they can occur just when MSFS is loading a flight without any overt action by FSUIPC, that could be fruitless. Better things to work out at present with hopefully more hope of success! Briefly, on this part: 16 minutes ago, pilotjohn said: Also, I'm not sure what the AXIS_RUDDER_SET entries are all about, since nothing is assigned to that in FSUIPC (ini attached). Is nothing at all assigned in MSFS too? The log is reflecting what is detected from MSFS, not what is sent to it. Pete
pilotjohn Posted September 8, 2020 Author Report Posted September 8, 2020 Nothing else is assigned in MSFS (I created FSUIPC or None profiles where applicable). I have two Thustmasters that have a "None" profile, and the VirtualFly axes have an FSUIPC profile which are unset in MSFS. I'll dig more to make sure (at least nothing that would so noisy), unless the "wind" buffeting the rudder would be sent to MSFS. 🙂
pilotjohn Posted September 8, 2020 Author Report Posted September 8, 2020 I filed a CTD and general SimConnect bug, listing: 1. Random crashes to desktop, especially during flight loading screen2. On first flight load SimConnect input is ignored and requires a reconnect/restart (of FSUIPC)3. Random periods where SimConnect inputs are completely ignored and reconnect/restart of the client does not solve the issue (but eventually recovers)
John Dowson Posted September 9, 2020 Report Posted September 9, 2020 Please note that there are known issues with flight loading at the moment, so use this feature at your own risk. I'll take a look at your logs later and get back to you, but could you check your MSFS settings in relation to this, as reported in similar post (FSUIPC7 Control problem): Quote in the options and controls and keyboard hotkeys of FS2020 there is this stupid CO pilot hand off where the sim does pretty much everything for you. thats where the throttle and my keyboard responses were not playing a roll in!. the hotkey was CTRL+ALT+X so i just cleared. John
pilotjohn Posted September 9, 2020 Author Report Posted September 9, 2020 2 hours ago, John Dowson said: Please note that there are known issues with flight loading at the moment, so use this feature at your own risk. I'll take a look at your logs later and get back to you, but could you check your MSFS settings in relation to this, as reported in similar post (FSUIPC7 Control problem): John So to be clear, I'm not loading the flight from FSUIPC. The flight is being selected and loaded through MSFS world view, it's just that the controls don't work on "initial flight of the day" (e.g. first flight after sim launch with FSUIPC open). I have never pressed that key combination in my life 🙂, but will also unset it.
pilotjohn Posted September 9, 2020 Author Report Posted September 9, 2020 A quick report back with the just released version, the first flight of the day issue remains: if FSUIPC is running before MSFS is started, the first flight load does not respect any control inputs until what I assume is a reconnect (forced by going to Axes... and clicking Ok).
John Dowson Posted September 9, 2020 Report Posted September 9, 2020 30 minutes ago, pilotjohn said: A quick report back with the just released version, the first flight of the day issue remains: if FSUIPC is running before MSFS is started, the first flight load does not respect any control inputs until what I assume is a reconnect (forced by going to Axes... and clicking Ok). Ok. Seems strange as I've never encountered this issue, and stop and start MSFS with FSUIPC7 continually running all the time. However, I'll add an additional axes scanning request once MSFS starts, to see if this solves that issue. I'll post an update shortly.
John Dowson Posted September 9, 2020 Report Posted September 9, 2020 @pilotjohn Could you please try the attached version and let me know if that helps/solves your issue, thanks. FSUIPC7.exe
pilotjohn Posted September 9, 2020 Author Report Posted September 9, 2020 45 minutes ago, John Dowson said: @pilotjohn Could you please try the attached version and let me know if that helps/solves your issue, thanks. FSUIPC7.exe 585 kB · 0 downloads Thanks... this appears to fix the problem. I tested it twice through 4 separate sessions (2 each, old version problem, new version no problem).
John Dowson Posted September 9, 2020 Report Posted September 9, 2020 4 hours ago, pilotjohn said: Thanks... this appears to fix the problem Ok, I thought it would, but unfortunately no idea why! Rather worrying.... John
pilotjohn Posted September 20, 2020 Author Report Posted September 20, 2020 On 9/9/2020 at 4:19 PM, John Dowson said: Ok, I thought it would, but unfortunately no idea why! Rather worrying.... John This issue (or maybe different) seems to have returned... On today's debugging session (since like with FSX I'm doing more of that than flying), FSUIPC was running, sim started, flight launched, no response in sim (went to axes) still nothing. FSUIPC exit//restart was required.
Thomas Richter Posted September 20, 2020 Report Posted September 20, 2020 Hi, when you start FSUIPC first and then MSFS and the axes don't work, close FSUIPC and copy the FSUIPC7.log file before you restart to see what's in the file please. Please also update to latest FSUIPC7. Thomas
pilotjohn Posted September 20, 2020 Author Report Posted September 20, 2020 14 minutes ago, Thomas Richter said: Hi, when you start FSUIPC first and then MSFS and the axes don't work, close FSUIPC and copy the FSUIPC7.log file before you restart to see what's in the file please. Please also update to latest FSUIPC7. Thomas This happened with a restart of FSUIPC after a crash as a result of TransmitClientEvent failed. Logs for both session attached (also in other thread). Log 1 leading up to FSUIPC crash, log 2 FSUIPC restart but controls not working until Axes/Ok. logs.zip
Thomas Richter Posted September 21, 2020 Report Posted September 21, 2020 Hi, why posting this in two different threads, that is confusing for no reason ?? As I said already, you might first fix the controller problem in your registry. 109 System time = 20/09/2020 17:22:28 109 FLT path = "C:\Users\janos\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\" 188 ------------------------------------------------------------------- 203 Registered HotKey 'InvokeFSUIPCOptionsKey' (key=0x46, modifier=0x1) 297 FS path = "C:\Users\janos\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\" 313 ---------------------- Joystick Device Scan ----------------------- 313 Product= vJoy - Virtual Joystick 313 Manufacturer= Shaul Eizikovich 313 Serial Number= 2.1.9 313 Vendor=1234, Product=BEAD (Version 2.25) 328 GUIDs returned for product: VID_1234&PID_BEAD: 328 GUID= {675FFD60-DD8E-11EA-8004-444553540000} 328 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767 328 GUID= {67604B80-DD8E-11EA-800A-444553540000} 328 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767 328 GUID= {67602470-DD8E-11EA-8006-444553540000} 328 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767 328 GUID= {67602470-DD8E-11EA-8008-444553540000} 328 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767 328 GUID= {67607290-DD8E-11EA-800C-444553540000} 328 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767 328 GUID= {675FD650-DD8E-11EA-8002-444553540000} 328 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767 328 Product= vJoy - Virtual Joystick 328 Manufacturer= Shaul Eizikovich 328 Serial Number= 2.1.9 328 Vendor=1234, Product=BEAD (Version 2.25) 328 Product= vJoy - Virtual Joystick 328 Manufacturer= Shaul Eizikovich 328 Serial Number= 2.1.9 328 Vendor=1234, Product=BEAD (Version 2.25) 328 Product= VirtualFly - RUDDO+ 328 Manufacturer= 328 Vendor=16D0, Product=0DA3 (Version 0.2) 328 GUIDs returned for product: VID_16D0&PID_0DA3: 328 GUID= {225074A0-E19B-11EA-8001-444553540000} 328 Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U4096,V4096,X4096,Y0,Z0 328 Product= VirtualFly - YOKO+ 328 Manufacturer= 328 Vendor=16D0, Product=0DA0 (Version 0.2) 328 GUIDs returned for product: VID_16D0&PID_0DA0: 328 GUID= {25CD3F50-E19B-11EA-8002-444553540000} 328 Details: Btns=7, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X4096,Y4096,Z0 328 Product= vJoy - Virtual Joystick 328 Manufacturer= Shaul Eizikovich 328 Serial Number= 2.1.9 328 Vendor=1234, Product=BEAD (Version 2.25) 328 Product= vJoy - Virtual Joystick 328 Manufacturer= Shaul Eizikovich 328 Serial Number= 2.1.9 328 Vendor=1234, Product=BEAD (Version 2.25) 328 Product= vJoy - Virtual Joystick 328 Manufacturer= Shaul Eizikovich 328 Serial Number= 2.1.9 328 Vendor=1234, Product=BEAD (Version 2.25) . . . 344 ------------------------------------------------------------------- 344 WARNING: Joystick ID 6 is duplicated in Registry 359 WARNING: Joystick ID 7 is duplicated in Registry 375 WARNING: Joystick ID 8 is duplicated in Registry 484 WARNING: Joystick ID 10 is duplicated in Registry 484 WARNING: Joystick ID 11 is duplicated in Registry 500 Device acquired for use: 500 Joystick ID = 3 (Registry okay) 500 3=vJoy Device 500 3.GUID={675FFD60-DD8E-11EA-8004-444553540000} 500 Device acquired for use: 500 Joystick ID = 4 (Registry okay) 500 4=vJoy Device 500 4.GUID={67604B80-DD8E-11EA-800A-444553540000} 500 Device acquired for use: 500 Joystick ID = 5 (Registry okay) 500 5=vJoy Device 500 5.GUID={67602470-DD8E-11EA-8006-444553540000} 500 Device acquired for use: 500 Joystick ID = 6 (Registry okay) 500 6=vJoy Device 500 6.GUID={67602470-DD8E-11EA-8008-444553540000} 500 Device acquired for use: 500 Joystick ID = 7 (Registry okay) 500 7=vJoy Device 500 7.GUID={67607290-DD8E-11EA-800C-444553540000} 500 Device acquired for use: 500 Joystick ID = 8 (Registry okay) 500 8=vJoy Device 500 8.GUID={675FD650-DD8E-11EA-8002-444553540000} 500 Device acquired for use: 500 Joystick ID = 2 (Registry okay) 500 2=VirtualFly - RUDDO+ 500 2.GUID={225074A0-E19B-11EA-8001-444553540000} 500 Device acquired for use: 500 Joystick ID = 10 (Registry okay) 500 10=VirtualFly - YOKO+ 500 10.GUID={25CD3F50-E19B-11EA-8002-444553540000} 500 Device acquired for use: 500 Joystick ID = 11 (Registry okay) 500 11=VirtualFly - TQ6+ 500 11.GUID={F2A26C20-E19C-11EA-8003-444553540000} Thomas
John Dowson Posted September 21, 2020 Report Posted September 21, 2020 11 hours ago, pilotjohn said: log 2 FSUIPC restart but controls not working until Axes/Ok. You log shows that a PAUSE_SET control was sent (with parameter 1, i.e. on) as soon as you connected to MSFS: Quote ... 8469 C:\Users\janos\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\MISSIONS\Custom\CustomFlight\CustomFlight.FLT 8469 SimObjects\Airplanes\Asobo_E330\aircraft.CFG 8469 Aircraft loaded: running normally now ... 8500 User Aircraft ID 1 supplied, now being used 9172 Aircraft="Extra 330 Asobo" 9172 System time = 20/09/2020 17:22:37, Simulator time = 14:21:04 (21:21Z) 13266 *** EVENT: Cntrl= 66055 (0x00010207), Param= 1 (0x00000001) PAUSE_SET .... Controls (e.g. axes movements) will not be seen by the sim when this pause mode is set. I cant see where you unset this pause mode - maybe in the sim? Its also set later, sometime after you have closed the axes dialog panel: Quote ... 20125 *** Entered Axes option page *** 22875 *** Exiting Axes option page *** 36703 *** EVENT: Cntrl= 66055 (0x00010207), Param= 1 (0x00000001) PAUSE_SET Next time you experience this issue, check that you have not inadvertently paused the sim. John
pilotjohn Posted September 21, 2020 Author Report Posted September 21, 2020 2 hours ago, John Dowson said: You log shows that a PAUSE_SET control was sent (with parameter 1, i.e. on) as soon as you connected to MSFS: The series of events that is probably related to the pause (and how I generally have to recover): 1. Flying with no issues (controls working) 2. Controls stop working (e.g. always at the wrong time - e.g. late landing phase, some maneuvers etc.) 3. I frantically pause (e.g. press ESC; pause with menu) 4. Start FSUIPC (since in this case it crashed) 5. Resume 6. Flying again, still about to crash etc. (no control effectiveness despite FSUIPC now running) 7. Pause again 8. Go to FSUIPC Axes/Ok 9. Unpause 10. Things have recovered 2 hours ago, John Dowson said: Controls (e.g. axes movements) will not be seen by the sim when this pause mode is set. I cant see where you unset this pause mode - maybe in the sim? Its also set later, sometime after you have closed the axes dialog panel: Next time you experience this issue, check that you have not inadvertently paused the sim. John
John Dowson Posted September 21, 2020 Report Posted September 21, 2020 On 9/9/2020 at 5:41 PM, pilotjohn said: Thanks... this appears to fix the problem. I tested it twice through 4 separate sessions (2 each, old version problem, new version no problem). So this is not correct, and the additional axis scanning I added for you to prevent this now makes no difference? If so, I'll remove this, as it shouldn't be needed anyway. On 9/8/2020 at 11:51 PM, pilotjohn said: It seems this happens when FSUIPC is launched before the simulator. And this is also no longer correct. Do you only get this issue when you restart after you have received the TransmitClientEvent errors and FSUIPC later crashes? If so, its that issue (i.e transmit client event failures) that needs to be resolved, and I wouldn't worry about this other problem for now. And as mentioned in the other post, you should clean your registry as it seems to be in quite a mess.
Thomas Richter Posted September 21, 2020 Report Posted September 21, 2020 Hi, those controllers are vJoy - Virtual Joystick, not physical devices. Maybe multiple installations have been done by mistake? Quote 313 Product= vJoy - Virtual Joystick 313 Manufacturer= Shaul Eizikovich 313 Serial Number= 2.1.9 313 Vendor=1234, Product=BEAD (Version 2.25) 328 GUIDs returned for product: VID_1234&PID_BEAD: 328 GUID= {675FFD60-DD8E-11EA-8004-444553540000} 328 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767 328 GUID= {67604B80-DD8E-11EA-800A-444553540000} 328 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767 328 GUID= {67602470-DD8E-11EA-8006-444553540000} 328 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767 328 GUID= {67602470-DD8E-11EA-8008-444553540000} 328 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767 328 GUID= {67607290-DD8E-11EA-800C-444553540000} 328 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767 328 GUID= {675FD650-DD8E-11EA-8002-444553540000} 328 Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767 Thomas
pilotjohn Posted September 21, 2020 Author Report Posted September 21, 2020 Probably, but not sure where to delete these from. I did have an instance of vJoy have to be uninstalled "manually" which probably left these. They are not physical.
pilotjohn Posted September 21, 2020 Author Report Posted September 21, 2020 39 minutes ago, John Dowson said: So this is not correct, and the additional axis scanning I added for you to prevent this now makes no difference? If so, I'll remove this, as it shouldn't be needed anyway. And this is also no longer correct. Do you only get this issue when you restart after you have received the TransmitClientEvent errors and FSUIPC later crashes? If so, its that issue (i.e transmit client event failures) that needs to be resolved, and I wouldn't worry about this other problem for now. And as mentioned in the other post, you should clean your registry as it seems to be in quite a mess. Unknown for some of these. I'll do some more testing.
pilotjohn Posted September 22, 2020 Author Report Posted September 22, 2020 I'll stop posting to this thread. I'm not sure if this was a mis-test on my part. The last few flights with FSUIPC running before the sim, I haven't had the issue of it not functioning as expected.
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now