Can't launch FSX with FSUIPC

[softreset]

Version installed - 4.968

Client - FSX: Steam Edition
Operating System - Windows 10 Pro 64-bit

Was working fine and I received this error message this morning. Referred to FAQ, trusted modules does not show a negative number and there's no registry key entry as mentioned here -

Clicking No launches FSX:SE with no FSUIPC functionality, Clicking Yes causes this to occur

What I've done:

- Removed FSUIPC from modules
- Reinstalled
- Reset FSX.cfg (deleted it, let it rebuild) and re-trusted FSUIPC

Windows Event Viewer

Log file -

********* FSUIPC4, Version 4.968 (8th June 2017) by Pete Dowson *********
Windows 10 Pro 64 Bit reported as Build 14393, Release ID: 1607 (OS 10.0)
fsx.exe version = 10.0.62615.0
Reading options from "C:\Program Files (x86)\Steam\steamapps\common\FSX\Modules\FSUIPC4.ini"
Running inside FSX Steam Edition on Windows 10
Module base=16530000
User Name="Jason Fearing"
User Addr="softreset@me.com"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
        0 System time = 26/06/2017 11:58:58
        0 FLT path = "C:\Users\softreset\Documents\Flight Simulator X Files\"
        0 ------ Module Version Check ------
        0        acontain.dll: 10.0.62615.0
        0             api.dll: 10.0.62615.0
        0        controls.dll: 10.0.62615.0
        0      fs-traffic.dll: 10.0.62615.0
        0             G3D.dll: 10.0.62615.0
        0        language.dll: 10.0.62615.0
        0            sim1.dll: 10.0.62615.0
        0        visualfx.dll: 10.0.62615.0
       16         weather.dll: 10.0.62615.0
       16          window.dll: 10.0.62615.0
       16 ----------------------------------
       32 Trying to connect to SimConnect Steam ...
       47 FS path = "C:\Program Files (x86)\Steam\steamapps\common\FSX\"
      188 ---------------------- Joystick Device Scan -----------------------
      188 Product= Microsoft Nano Transceiver 1.1
      188    Manufacturer= Microsoft
      188    Vendor=045E, Product=07FD (Version 3.21)
      203 -------------------------------------------------------------------

Install file

Installer for FSUIPC4.DLL version 4.968

Looking in registry for FSX install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0
     Parameter"SetupPath"
... >>>  OK! FOUND FSX!  <<< ...
     SetupPath=C:\Program Files (x86)\Steam\steamapps\common\FSX

Looking in registry for FSX-SE install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\DovetailGames\FSX
     Parameter"Install_Path"
... >>>  OK! FOUND FSX-SE!  <<< ...
     SetupPath=C:\Program Files (x86)\Steam\steamapps\common\FSX

************ BUT this is the same path as for FSX! Will only install for FSX-SE ************

Looking in registry for Prepar3D v1 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\LockheedMartin\Prepar3D
     Parameter"AppPath"
... NOT found! ...

Looking in registry for Prepar3D v2 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v2
     Parameter"AppPath"
... NOT found! ...

Looking in registry for Prepar3D v3 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v3
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v3
     Parameter"AppPath"
... NOT found! ...
===========================================================

INSTALLATION FOR FSX-SE:
SetupPath="C:\Program Files (x86)\Steam\steamapps\common\FSX\"
Checking version of the FSX-SE EXE:
... Version 10.0.62615.0  (Need at least 10.0.62607.0)
Checking compatibility with installed SimConnect:
    Found SimConnect build 60905 (Original)
    Found SimConnect build 62615 (Steam)
    Found SimConnect build 61242 (SP1 May07)
    Found SimConnect build 61259 (Acc/SP2 Oct07)
Checking if there's already a version of FSUIPC4 installed in:
       C:\Program Files (x86)\Steam\steamapps\common\FSX\Modules\FSUIPC4.DLL
... No previous valid version found.
FSX-SE Modules folder already exists.

[Pete Dowson]

7 minutes ago, softreset said:

Was working fine and I received this error message this morning.

Has nothing changed on your system leading to this? Because the software won't have changed -- well, except by possible corruption.

The Log is odd. It finished just after this:

      188 ---------------------- Joystick Device Scan -----------------------
      188 Product= Microsoft Nano Transceiver 1.1
      188    Manufacturer= Microsoft
      188    Vendor=045E, Product=07FD (Version 3.21)
      203 -------------------------------------------------------------------

Now that point is where it tries to Acquire the identified devices so they can have buttons and axes assigned.

Can you tell me what a "Microsoft Nano Transceiver 1.1" is? Is it a joystick type device? i.e. does it have buttons or axes you can use in FS?

My guess is that it's a device which is not amenable to the normal DirectInput calls, and this is the cause of the problem.

There was a similar report a while back, but for a different device. However, I tightended up the criteria for deciding which devices FSUIPC scanned, and released interim updates for 4.968 which proved successful, so my advice would be to download and install the newly released full version, 4.969, and try that. It is linked from the usual Schiratti site (the text there is stil out of date) and it is also available in the Download Links subforum above.

Pete

 

[softreset]

Hi Pete,

Thanks for the quick response. The Microsoft Nano Transceiver 1.1 is a USB dongle for a wireless mouse. It's a mouse I've had (with the dongle connected) for the better part of 2 years. In fact, I don't know if I'm unplugged the dongle since plugging it in. I've been using it with FSX and FSUIPC since late mid 2015.

• I updated to 4.969 and received the same error
• I removed the dongle and received the same error

A restart with the dongle removed was successful on the next launch. If I connect the dongle and launch FSX I receive the error message. If I remove the dongle and launch FSX I do not receive the error message.

So I guess that'll be the work flow moving forward. Odd that this is suddenly happening but that definitely appears to be the issue.

No other hardware/software changes in the last year.

Thanks,

Jason

[Pete Dowson]

It shouldn't happen with 4.969 unless it DOES identify itself as a joystick type device.

So I can see what is going on please add these lines to the General section of the FSUIPC ini file and show me the Log file and the CSV file.

Debug=Please

Logextras=x200000

 

 

Pete