That is incorrect. It is a Windows 8 issue with the joystick drivers. The only even somewhat successful solution is to use FSUIPC to control your joystick. That's why did and I have never lost control of Saitek X-65F ever again.

I would agree.

Windows 10 has solved the issue for me.

Am I the only Windows 8.1 user that doesn't have this issue? I left my CH Products yoke unattended for over 2 hours in P3D and it didn't go into a "sleep" mode. I have the issue in FSX though... weird.

Another working solution (for me, Logitech extreme 3d pro joystick and windows 8.1) is to use the Window's compatibility problem adjustment program and to run P3D (or FSX) in windows 7 mode,

That is incorrect. It is a Windows 8 issue with the joystick drivers. The only even somewhat successful solution is to use FSUIPC to control your joystick. That's why did and I have never lost control of Saitek X-65F ever again.

 

 

You're correct in the sense that the problem does not seem to occur in Win 7 or Win 10.  However, my point is that no other game/program seems to have this problem in Win 8.1. I can use my CH yoke fine in FSX, any Win 8.1 game, etc. Furthermore, I have extensively tested this issue with my Thrustmaster joystick.  P3D has the exact same issue with it (does not recognize it as an active controller) yet every one of the many Win 8.1 programs I have recognizes the joystick fine EXCEPT P3D.  This is clearly a bug in P3D that LM needs to address.

 

Also, I've already stated that FSUIPC does not work to fix the issue because the joystick is unrecognized in P3D and, therefore, is not available in FSUIPC.

Another working solution (for me, Logitech extreme 3d pro joystick and windows 8.1) is to use the Window's compatibility problem adjustment program and to run P3D (or FSX) in windows 7 mode,

Tried that with no success.

I have never ever had joystick issues with fsx or p3d in Win8.

Why do folks insist on blaming Lockheed Martin for all their software/hardware problems?  Go to your software/hardware manufacturer and ask them.  You are their customer so they have to keep you happy.  As far as joysticks go my Logitech Extreme Pro has lasted me for 11 years of everyday (retired) flying without a problem.  Those who jumped on the Windows 8 bandwagon just made Bill Gates richer.  It did nothing for flight sim.

 

Jim

 

+1 and my Logitech Extreme Pro works flawlessly in P3D, although I avoided Windoze 8 like the plague and and stayed with 7. 

 

It’s not joystick specific. I’ve tried a Thustmaster 1600M too, and it also fails to appear in P3D.

 

I use a 1600M.  When I jumped on the P3D bandwagon it was when P3D 2 came out.  I had the disappearing joystick problem

but when 2.1 came out all was solved.  I have never had a problem since.  Yes, I use Win7.

 

That is incorrect. It is a Windows 8 issue with the joystick drivers. The only even somewhat successful solution is to use FSUIPC to control your joystick. That's why did and I have never lost control of Saitek X-65F ever again.

 

 

You're correct in the sense that the problem does not seem to occur in Win 7 or Win 10.  However, my point is that no other game/program seems to have this problem in Win 8.1. I can use my CH yoke fine in FSX, any Win 8.1 game, etc. Furthermore, I have extensively tested this issue with my Thrustmaster joystick.  P3D has the exact same issue with it (does not recognize it as an active controller) yet every one of the many Win 8.1 programs I have recognizes the joystick fine EXCEPT P3D.  This is clearly a bug in P3D that LM needs to address.

 

Also, I've already stated that FSUIPC does not work to fix the issue because the joystick is unrecognized in P3D and, therefore, is not available in FSUIPC.

Tried that with no success.

 

Mark,

 

I misunderstood your problem, as usually  the "disappearing joystick" bug that is commonly reported is one where the joystick is recognized by either FSX or P3d under Win 8, but then stops working. What you are saying is that the joystick is recognized in every other app on your computer, except P3d. When you say that it works with FSX, I assume that you mean the boxed version, correct?

 

First, in the P3d user interface, look at the joystick setup and make sure that the name is correct and that the joystick has the correct number of axes. The axes should also be assigned to the correct aircraft control surface, etc.. P3d very rarely doesn't recognize certain brands and models of joysticks correctly. If the joystick doesn't even show up  in the P3d UI, do the following. You may have an inconsistency within the joystick profile contained in the configuration files standard.xml and standard.xmlx. These files can be viewed with a text editor and are located at:

 

C:\Users\<username>\AppData\Roaming\Lockheed Martin\Prepar3D v2\Controls

 

Examine each file and make sure again that the joystick is named correctly and that the assignments look correct. If they appear correct, rename standard.xml and restart P3d. See if the joystick now shows up in the UI. Select the controller and reset everything to default settings.

 

It sounds like to me that if none of of these suggestions  pan out, you have a driver conflict or you have some other joystick utility/app running that is causing issues. I assume that you have tried another joystick to see if P3d recognizes it. If it doesn't recognize that joystick either, then there is something wrong with your P3d installation. If FSUIPC can't see the joystick also, then there is something wrong with the joystick driver installation. With FSUIPC, you also have disable all joysticks from within the P3d UI, else P3d and FSUIPC will "fight" over the control of the joystick. This gives completely erratic joystick behavior.

 

Jay

There are a few different problems at hand here:  I used to have USB devices stop working with windows 8.0 until Lockheed Martin reported that fixed - I think it was P3D 2.4, but I am not sure. If I remember correctly that was an issue with FSX legacy handling of devices, requiring a workaround in P3D and since then my devices have been working without disconnect in P3D. They are, however, frequently not recognized in the P3D internal control setup with only the Mouse Yoke being displayed. That's another variation of 'not recognized' and might contribute to the confusion.

 

I generally just edit the standard.xml directly now. I don't expect this to be fixed within the lifetime of Win 8.

Thanks.  Yes, the issue I have is that P3D does not show the joystick at all (or any other brand joystick) unless one runs the deep sea rescue scenario as described above. This seems to be a not unique issue, as others have reported it too.  (There is a thread on the issue on the LM forum, and I found a couple of others with Google.)  So, I would describe it as P3D usually does not recognize the controller at all, but does under certain conditions (deep sea rescue mission and any flights thereafter) but then that recognition is lost on the next start up.  FSUIPC does not see the controller either but every other Windows program does.  I don't have any other controllers plugged in. Thus, I don't think it has anything to do with the drivers or with Windows.  I play numerous games, and none of them have this problem.

 

This issue started once I upgraded to 2.5 (with a full P3D wipe and install),  Before that, I had the randomly disappearing joystick issue, but it was pretty rare and easily solved by unplugging and replugging the USB.

 

I have tried deleting the controls folder and letting P3D rebuild, but that didn't work.  P3D does rebuild, but again only shows "mouse yoke" as the sole controller option.  I'll take a closer look at the standard.xml file as you suggested once I get home.

 

Thanks for the suggestions.

It's no a bug, it's a bad feature of Windows 8, go to the properties of the joystick in device manager and you will find the solution

It's no a bug, it's a bad feature of Windows 8, go to the properties of the joystick in device manager and you will find the solution

Are you're talking about the USB going to sleep issue?

That is incorrect. It is a Windows 8 issue with the joystick drivers. The only even somewhat successful solution is to use FSUIPC to control your joystick.

 

I haven't had any disconnect issues on Win 8.1 and my G940 FCS (no FSUIPC needed). It might have something to do with the drivers, but initially others had success changing the sleep / power management settings, and switching from USB 3 ports to the native (USB 2 or 1.1). I have a feeling that might also be related to the controller driver.

I haven't had any disconnect issues on Win 8.1 and my G940 FCS (no FSUIPC needed). It might have something to do with the drivers, but initially others had success changing the sleep / power management settings, and switching from USB 3 ports to the native (USB 2 or 1.1). I have a feeling that might also be related to the controller driver.

 

I'm just glad Windows 10 has fixed this for me.

Exact same hardware, same usb ports in use, etc - no issues.  :-)

Thanks everyone for your feedback.  No amount of tweaking the standard.xml file worked for me, but I was able to get FSUIPC working.  I just had not been using it right.  Now P3D still shows "mouse yoke" as the controller, but I can at least calibrate the controls with FSUIPC.