Jump to content
The simFlight Network Forums

Recommended Posts

Posted

(registered FSUIPC 4.05)

When selecting the Buttons + Switches tab in the FSUIPC options and settings dialog, FSUIPC and FSX stop working. Pressing other tabs, OK or Cancel has no effect. The window is not repainted when covered with other windows.

I removed the fsuipc.ini file (that is then regerated when starting fsx) and installed 4.05 (previously was 4.03) but this does not help.

Any idea what can be wrong?

Thanks!

Djeez.

Posted

When selecting the Buttons + Switches tab in the FSUIPC options and settings dialog, FSUIPC and FSX stop working. Pressing other tabs, OK or Cancel has no effect. The window is not repainted when covered with other windows.

...

Any idea what can be wrong?

No. There's nothing peculiar or special in the Buttons menu, especially if there are no buttons defined already.

Can you tell me if you have GoFlight devices? Could it be a bad GFDev.dll file somewhere? Just in case, try installing the copy of GFDev.dll you can find in the download announcment above into the FSX modules folder.

Otherwise, do you have an EPIC?

Regards

Pete

Posted

Thank you very much for your quick reply.

Can you tell me if you have GoFlight devices? Could it be a bad GFDev.dll file somewhere? Just in case, try installing the copy of GFDev.dll you can find in the download announcment above into the FSX modules folder.

I do have GoFlight devices so I followed your suggestion. This does not help. I copied the downloaded file to both the Goflight program folder (were it replaces another version) and to the FSX module folder (where it did not exist). I also tried not to allow the GoFlight Hardware Interface to start when FSX starts and disconnect all GoFlight devices, but no luck either.

All other FSUIPC functions seem to work normally, just the Buttons+Switches tab does not function properly.

Djeez.

Posted

I do have GoFlight devices so I followed your suggestion. This does not help. I copied the downloaded file to both the Goflight program folder (were it replaces another version) and to the FSX module folder (where it did not exist). I also tried not to allow the GoFlight Hardware Interface to start when FSX starts and disconnect all GoFlight devices, but no luck either.

Hmm. Strange. Could you try one more test, then, please. Remove the GFDev.DLL from the Modules folder and rename the other one wherever it was (this is temporarily, for a test). I need to know whether it it to do with the GoFlight driver or not.

I don't have much in the way of GoFlight devices any more, just an RP48, but tomorrow I will try connecting that to my FSX PC (I use it on a WideFS client PC). What devices do you have? When you say you tried without the GF hardware interface running, did you succeed? In other words, was there ANY go flight software at all running at the time?

Assuming it isn't GF, can you also tell me what other add-ons, if any, you have running for FSX. If it isn't some conflict between GFDev.DLL and the new FSX GoFlight drivers, and you don't have an EPIC, I'm essentially running out of things which may possibly be interecting with a plain button scan.

Oh, yes, one other possibility -- any drivers for other game controllers installed, possibly for devices you no longer use? Check the Windows Game Controllers setting. Something at the back of my mind tells me that this has happened before (on FS9, not FSX though) and it turned out to be a rogue game driver.

It just has to be something like this, because what happens uniquely* when you go into the Buttons tab is that it loops around scanning all possible joystick connections waiting for you to press a button. Something, possibly an old driver, is reacting to the query and hanging the process waiting for a device which is probably no longer connected.

Regards

Pete

* P.S. Actually, it isn't quite unique to the Buttons tab -- the Axis Assignments tab would also do this -- only in that case it wouldn't also include the Go Flight driver. So, please see if the Axis Assignments tab hangs in the same way. If so it is defintely a rogue game controller driver in your system. You may be able to find it and uninstall it, or altrernatively plug in whatever it wants.

Posted

I do have GoFlight devices so I followed your suggestion. ...

Further to my last reply, I've now tried connecting GoFlight devices and using the new FSX GoFlight driver software with FSX and FSUIPC4, and this has no adverse affect on the Buttons Tab in the FSUIPC4 options.

So we are most certainly left with the only other possibility -- there is an old possibly long forgotten joystick or game controller driver installed in your system which is hanging when scanned for its status.

I attach a little program, originally from Thrustmaster, which scans joysticks in the same way as FSUIPC. Maybe this will show you the culprit even if Game Controllers does not -- but try Game Controllers first.

Regards

Pete

joyview.zip

Posted
So we are most certainly left with the only other possibility -- there is an old possibly long forgotten joystick or game controller driver installed in your system which is hanging when scanned for its status.

That was it :D

After my visit to the local flightsimclub I forgot to put the CH Pilot connector back in (the old, anologue game port one). Windows Game Controller showed an error and when I plugged it in all was well again.

Thank you very much for the outstanding support. I need the button programming (and GFDisplay) to program around some annoying bugs in the GoFlight software. I wish they were as responsive as you are!

Cheers,

Djeez.

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.