Sign in to follow this  
jjjallen

Windows 8 Controller Dropout Topic

Recommended Posts

That could be awhile 

Every indication online from FSX users is that Win 8.1 is a further step backwards. Most have quickly uninstalled it, because of CTDs or FSX not even being able to start up. Microsoft is trying its hardest to drive everyone to Android.

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Its Beta, that's why you cannot rely nor expect Beta to run anything properly including FSX; Microsoft is trying very hard to be a *********** and this is the #1 reason why I have never trusted Microsoft; so once again they have lost my trust even more; I am sorely considering switching to Mac; but Macs don't run windows stuff including FSX (not in its native form it doesn't) 

Share this post


Link to post
Share on other sites

Here are a few observations that we have made at SkyPilot while testing our controller dropoput fix on Windows 8:

 

1) An FSX task switch with will cause an exception with an immediate controller disconnect.

2) A simmconnect standalone utility will never process correctly due to the FSX task switch.

3) EZDOK is a factor and will cause any addon simmconnect controller app utility to fail whether FSX is task switched or not.

 

With those results we have no alternative than to wait for Windows 8.1 for some positive results although we are not 100% hopeful at this point.

 

The best thing we can recommend at this point when running Windows 8 is to avoid any task switching.  

 

At this stage FSXASSist can only detect a controller dropout but has no ability to reconnect a lost controller due to limitations in simmconnect.  

 

Stay tuned however because we may happen upon a fix at any time.

 

Regards

Jim Allen

SkyPilot Software 

 

 

 

 

Share this post


Link to post
Share on other sites

The following method works for me:

 

I open fsgrw for weather and minimize,

i open pro-atc, prepare but do no conncect,

I open Fsx (I'm a EZDOK user), load the 737ngx.

Then, I click on the fsgrw icon in the taskbar, transfer the weather to fsx and minimize.

I click on the pro-atc icon in the taskbar and activate my flight, slew the moving map to a second screen and don't touch it after that,

I click somewhere on my fsx screen to regain focus (I always fly in windowed mode) and don't change the focus from there.

Up until now, I can perform any flight without losing my joystick. However, the moment I change focus once more, my joystick control within fsx is gone.

I'll have a flight without EZDOK as I seems to be a factor.

I hope a solution will be found. As it stands now, Completing a flight in fsx is like running a steeplechase :-)

 

Jos

Share this post


Link to post
Share on other sites

I uninstalled EZDOK and replaced it by Opusfsx, using the live view camera option. First impression is that changing focus now doesn't result in losing joystick in FSX. Just a first test of course.

 

Jos

Share this post


Link to post
Share on other sites

Thanks for your info Jos.

 

I forgot to add that we almost never have stick dropouts if we don't task switch.  This is counter to some users who experience persistent dropouts.  

 

All of our USB ports have the 'NoSleep' option set per other thread recommendations.

 

Regards

Jim Allen

Share this post


Link to post
Share on other sites

The most curious thing about the issue is not that FSUIPC4 seems to fix the problem (which it does), when everything else has failed, but rather that Pete Dowson has never commented (as best I can tell) as to why configuring the joystick with FSUIPC4 is a good workaround in Win 8. FSUIPC4 uses SimConnect to control the joystick, but the details are not that straightforward:

 

http://www.fsdeveloper.com/forum/showpost.php?p=55041&postcount=2

 

http://forum.simflight.com/topic/73807-fsuipc-and-joystick-calibration/?p=452788

Share this post


Link to post
Share on other sites

I've read in the w8 forum that even after configuring the axes via fsuipc, the dropout still exists for some people.

The only task switches I perform, are activating my weather engine en pro-atc after loading fsx. For some reason (?) this never causes fsx to loose my joystick. After that, I never switch tasks and I always have a successful flight. When I finally swop focus for testing after the flight, fsx looses the joystick immediately.

All my usb ports have the "no sleep" option too.

 

Jos

Share this post


Link to post
Share on other sites

My  personal view of this is that the various "solutions" to the problem including FSUIPC4, just cut down on the probability of losing your joystick. After going back and looking at a lot of the older posts, I did notice one thing about the FSUIPC4 "trick". Some people just used it and some people used it and also in FSUIPC4.ini, set:

 

JoystickTimeout=<some large number like 60 or 120>

 

I have no idea whether this matters or not.

Share this post


Link to post
Share on other sites

The FSUIPC solution works fine. Assign all controller axes and buttons with it instead of within FSX and you should not lose the controller(s), PROVIDING you do not access the FSUIPC interface during your flight. Since I stuck to those rules I have had no more W8 disconnects.

Share this post


Link to post
Share on other sites

 

 


I forgot to add that we almost never have stick dropouts if we don't task switch.  This is counter to some users who experience persistent dropouts.  

 

How about when you open the ATC Window and switch focus to and from the main FSX/P3D Window?  I think that was mentioned somewhere is this megathread.

Share this post


Link to post
Share on other sites

Well I can tell you all that this drop out still occurs with hair pulling regularity in Win 81. :mad:

Share this post


Link to post
Share on other sites

The FSUIPC solution works fine. Assign all controller axes and buttons with it instead of within FSX and you should not lose the controller(s), PROVIDING you do not access the FSUIPC interface during your flight. Since I stuck to those rules I have had no more W8 disconnects.

Paying 10$ for the solution of a broken function should not be the answer. it's the same as buying a coffeemachine see a crack and buy a new one. No you force the person who sold a broken product to fix it for free and otherwise you throw the broken machine through the window in their face and buy a new one.

Share this post


Link to post
Share on other sites

Paying 10$ for the solution of a broken function should not be the answer. it's the same as buying a coffeemachine see a crack and buy a new one. No you force the person who sold a broken product to fix it for free and otherwise you throw the broken machine through the window in their face and buy a new one.

+100

Share this post


Link to post
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
Sign in to follow this