October 9, 201312 yr Well this is what I did to get it to work. Everything was lovely, then I installed 19 updates.. and it all went to pot. Uninstalled the updates and it all works again. Not sure which update it was but don't want to faff around too much. The updates I installed/uninstalled attached as a picture. Edit: Bit of a ninja edit, everything was 100% before I ran these updates and when I installed them I didn't give two thoughts. However after a few tries the joystick kept disconnecting with the same symptoms everyone describes. After mucking around for a while I remembered the updates, uninstalled them and it all works again.
October 9, 201312 yr Yeah, I think some updates we get screw things up from time to time. About a month ago, or so, my FSX was running great. Then, I had a bunch of updates that were applied....I went to run one of my programs, and continued to get unhandled exception errors. Couldn't get rid of the errors, got frustrated, and reinstalled my system back to default, and everything runs perfect. Rod Rod Beck
October 10, 201312 yr I've now been running FSX on my Win 8 build for nearly a month now with all controllers mapped via FSUIPC and disabled via FSX and can confirm I've had absolutely no dropouts since. Previously had issues running it this way and notice that on rare occasions FSUIPC would somehow 'fight' with the FSX-enabled controls even though they've been disabled, or sometimes I would lose the controllers in FSUIPC when accessing the program options from within FSX. I recently upgraded to FSUIPC 4.92 (was previously on 4.80) and this seems to have helped. Unfortunately I have to say that FSXAssist hasn't worked for me and the controllers still drop out when mapped via FSX even with the program running in the background supposedly polling the controllers. Also, when mapping the controllers via FSUIPC I notice there are a several options. -Send direct to FSUIPC calibration -Send to FS as a normal axis I have all of mine set to 'send to FS' at the moment but does anyone use the other 'send direct to FSUIPC' option? Are there any benefits of using that option? Michael R
October 10, 201312 yr I have all of mine set to 'send to FS' at the moment but does anyone use the other 'send direct to FSUIPC' option? Are there any benefits of using that option? Send to FS, simply maps an action via SimConnect directly to the simulator. Send Direct to FSUIPC routes the input through the FSUIPC calibration.
October 10, 201312 yr OK so my 'uninstall updates' solution only worked for that evening. However a German fellow made this program http://va-gae.eu/flightoperations/download/fsx-joystick-tool.html It send all inputs to FSX via simconnect. It's not an ideal solution as you have to re set up all your controls but it works. Any solution with FSUIPC won't work as anything to do with the FSX process looses all connectivity to the joystick.
October 10, 201312 yr Used the fsiupc solution now some month and none single disconnect. Yes its the only way to kill this problem. i have tried everything expect revert back to windows7. Remember to disable all buttons also in FSX Settings. Nicolaus Malmgren
October 10, 201312 yr Also, when mapping the controllers via FSUIPC I notice there are a several options. -Send direct to FSUIPC calibration -Send to FS as a normal axis I have all of mine set to 'send to FS' at the moment but does anyone use the other 'send direct to FSUIPC' option? Are there any benefits of using that option? The second option allows you to use the detailed calibration capabilities of FSUIPC. If you just want to use the Win OS calibration applet, then the first option is fine.
October 10, 201312 yr The second option allows you to use the detailed calibration capabilities of FSUIPC. If you just want to use the Win OS calibration applet, then the first option is fine. Interesting. Might have to experiment a bit then. Currently most of my axes are mapped using the 'send to FS' option but I've noticed that sometimes they seem to get 'buggy'. For example, I sometimes load up an aircraft such as NGX or 777 and would find that the spoiler axis mapped to one of my Saitek throttle controls gets a bit crazy and gets stuck in mid position somewhere. Since then I mapped it using the 'direct to FSUIPC option' and has worked fine since then. Michael R
October 11, 201312 yr I am also losing connection constantly now after a Win8 auto update this week. Mark....are you using FSUIPC for your controls. The reason I ask, I've had WIN 8 for some time now, and I'm always wandering about these updates. I'm using FSUIPC for my controls and I have yet to lose connection. Thanks. Rod Rod Beck
October 11, 201312 yr Hi guys Just one question.... I have a disconnect issue ONLY with the PMDG 747, I have also the 737-800 and I don't have the disc issue, this is totally weird Do you already knew that? Thanks Mauricio
October 11, 201312 yr Mark....are you using FSUIPC for your controls. The reason I ask, I've had WIN 8 for some time now, and I'm always wandering about these updates. I'm using FSUIPC for my controls and I have yet to lose connection. Thanks. Rod I haven't tried that yet. Prior to latest update, I only lost connection when I clicked on a different window and failed to pause FSX first, so I could easily avoid it. Now, after this week's windows update, I lose connection to my CH yoke when, for example, I use the keyboard. Also, I am now losing connection to my CH switch panel, which was never a problem before. I'm using SPAD for that. The problem is, the lost connection persists even outside of FSX. That is, if I try to test the switches in SPAD, they do not respond. The only way I can get the yoke or switch panel back is to unplug and reconnect the USB outside of FSX. Even that does not always work, and I'm forced to reboot windows. Very perplexing. I'm eagerly awaiting P3D v2 and hope they fix this issue eventually. They should, as P3D is DX11, and MS is only updating DX11 for Windows 8 now Does anyone know which of the Win8 updates that occurred earlier this week might have caused this issue? I haven't tried investigating that yet. There were quite a few of them.
October 11, 201312 yr Joystick dropouts are nothing new for Windows 8 users....it's been doing it for most people since the preview releases. I don't think it's anything you did to cause it. MS fail.
October 11, 201312 yr I haven't tried that yet. Prior to latest update, I only lost connection when I clicked on a different window and failed to pause FSX first, so I could easily avoid it. Now, after this week's windows update, I lose connection to my CH yoke when, for example, I use the keyboard. Also, I am now losing connection to my CH switch panel, which was never a problem before. I'm using SPAD for that. The problem is, the lost connection persists even outside of FSX. That is, if I try to test the switches in SPAD, they do not respond. The only way I can get the yoke or switch panel back is to unplug and reconnect the USB outside of FSX. Even that does not always work, and I'm forced to reboot windows. Very perplexing. I'm eagerly awaiting P3D v2 and hope they fix this issue eventually. They should, as P3D is DX11, and MS is only updating DX11 for Windows 8 now Does anyone know which of the Win8 updates that occurred earlier this week might have caused this issue? I haven't tried investigating that yet. There were quite a few of them. I had the same problems, as when I switched to another program with FSX running, I would lose connection. As I said, since using FSUIPC I've not had a problem. I've had three or four, maybe five, different programs running while FSX is running, and I would go to each program and never have disconnect problems. The only other thing I have done is in Device Managers, I've ensured all USB and Human Interface Devices power management is set so computer cannot turn off this device. Without FSUIPC that did not make any difference though. I really think, the only real work around for us WIN 8 users is to use FSUIPC (Payware) with FSX. Hope you get it figured out. Rod Rod Beck
Create an account or sign in to comment