Jump to content
The simFlight Network Forums

gassa

Members
  • Posts

    12
  • Joined

  • Last visited

Posts posted by gassa

  1. Hello,

    I can confirm that the problem has something to do with the CH Manager. Yesterday, I uninstalled all my controller drivers and also uninstalled the CH Manager. After that rebootet my system, started FSX and everything was working fine.

    Then I reinstalled my controller devices, using the built in Windows drivers for my CH devices. With these Windows drivers, the Buttons dialogue was working fine. After that I reinstalled the CH Manager and the Buttons dialogue was still working fine. But that changed after a reboot of the system. After this reboot the problem was the same again, the Buttons dialogue was hanging.

    Maybe it has something to do with the CH drivers that come with the CH Manager (as soon as you install the CH Manager, the Windows own drivers get replayed by the drivers that come with the CH Manager).

    By the way...I'm using the CH Manager Version 4.30 for Vista, since I'm running Vista with SP1.

    Kind regards

    martin

  2. I just deleted the previous log file and gave it another try.

    Here's the new one

    FSUIPC4 Key is provided

    WIDEFS7 not user registered, or expired

    Running inside FSX on Windows Vista (SimConnect Acc/SP2 Oct07)

    Module base=61000000

    Wind smoothing fix is fully installed

    DebugStatus=15

    78 System time = 19:08:21

    78 FLT UNC path = "C:\Users\Gassa\Documents\Flight Simulator X-Dateien\"

    78 FS UNC path = "D:\games\Microsoft Flight Simulator X\"

    2418 LogOptions=00000021

    2418 LogExtras=2

    2418 SimConnect_Open succeeded: waiting to check version okay

    6583 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0)

    6583 Initialising SimConnect data requests now

    6583 FSUIPC Menu entry added

    6630 D:\games\Microsoft Flight Simulator X\FLIGHTS\OTHER\FLTSIM.FLT

    6630 D:\games\Microsoft Flight Simulator X\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR

    65115 System time = 19:09:26, FSX time = 12:46:29 (10:46Z)

    65349 Aircraft="Aircreation582SL red"

    70341 *** Entered Buttons option page ***

    70372 ButtonCheck res=1, *pFirst=288 (0.1, 32)

    70372 FirstButtonChange res=00000120 (0.1, 32)

  3. Hi,

    So here is my FSUIPC.log file (without my name and E-Mail adress).

    FSUIPC4 Key is provided

    WIDEFS7 not user registered, or expired

    Running inside FSX on Windows Vista (SimConnect Acc/SP2 Oct07)

    Module base=61000000

    Wind smoothing fix is fully installed

    DebugStatus=15

    110 System time = 18:55:46

    110 FLT UNC path = "C:\Users\Gassa\Documents\Flight Simulator X-Dateien\"

    110 FS UNC path = "D:\games\Microsoft Flight Simulator X\"

    2668 LogOptions=00000021

    2668 LogExtras=2

    2668 SimConnect_Open succeeded: waiting to check version okay

    6865 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0)

    6865 Initialising SimConnect data requests now

    6865 FSUIPC Menu entry added

    6911 D:\games\Microsoft Flight Simulator X\FLIGHTS\OTHER\FLTSIM.FLT

    6911 D:\games\Microsoft Flight Simulator X\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR

    51169 Aircraft="Aircreation582SL red"

    51902 System time = 18:56:38, FSX time = 12:46:30 (10:46Z)

    54273 Advanced Weather Interface Enabled

    56691 *** Entered Buttons option page ***

    56722 ButtonCheck res=1, *pFirst=275 (0.1, 19)

    56722 FirstButtonChange res=00000113 (0.1, 19)

  4. Hi Pete,

    When I press the buttons TAB, the Buttons option dialogue gets drawed as usual, but non of the editable fields reacts. You simply can't edit something on the buttons dialogue. All other dialoges of FSUIPC are working.

    Yesterday the complete right collumn of the Buttons dialogue was completely empty. I mean it was just grey with nothing displayed in it.

    Ill edit the FSUIPC.ini as mentioned and will show you the LOG file, as soon as I'm home from work.

    Kind regards

    martin

  5. Hi Pete,

    I just checked the Control Manager and there are no non present devices listed. All my three input devices seem to work normal.

    All I can remember is that I changed the USB slots where the control devices where plugged in. They where connected via a USB Hub until a few weeks ago. Now, they are connected directly to the mainboard USB connectors.

    Is there a way to do a complete uninstall and reinstall of FSUIPC? I mean a uninstall where no registry entries remain.

    Kind regards

    Martin

  6. Hello Pete,

    Thanks for your reply. The interesting thing is that I havent changed anything on my machine since I first installed FSUIPC a few months ago. I just updated FSUIPC to the latest version and wanted to change some key assignments.

    I also tried to unplug all control devices (CH Yoke, CH Throttle quadrant and a Logitech steering wheel for rudder pedal use), restarted my PC, fired up FSX and nothing changed. The OK and Chancel buttons stay dead. I also tried to completely uninstall FSUIPC, deleted the FSUIPC.ini and the key file. After the reinstall the problem was still there. I'll try your attached program tonight and let you know if I can nail down the problem.

    Kind regards

    Martin

  7. Hello,

    I just installed FSUIPC 4.26 for FSX. Now I wanted to assign my Joystick buttons. So I opened FSUIPC via the "ADDON" menu. And here is my problem: As soon as I enter the "Buttons and Switches" menu my FSUIPC stops responding. I cant neither press OK nor Chancel. All other FSUIPC functions, like "Key Assignments",.. operate normal, but as soon as I enter "Buttons and Switches" I have to shutdown my FSX via the Task Manager.

    Can anybody help?

    Kind regards

    Martin

×
×
  • 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.