These are the Support Forums for FSUIPC and related products.

These forums replace the old support forums which have been running for 20+ years. The old forums contain a wealth of information on all FSUIPC products, but are now no longer available.

Please note that you will need to Register and Login to post for support, and also to download attachments. You can view these forums without registering.

Support is also available via Discord. Please use the following invite link to join the FSUIPC Discord server:
https://discord.gg/zjwUTrxmmE

Controller registry...
 
Notifications
Clear all

[Solved] Controller registry issues after botched firmware update

Posts: 2
Registered
Topic starter
(@c525b)
Joined: 2 days ago

Hello John,

I've dealt with a controller issue due to bad registry entries in the past by following some guidance from this forum, but now I have a brand new PC on Win11 (also new to me).  I've been methodically bringing everything over for my flightsim setup, but I stupidly applied a Virpil firmware update to the wrong controller.  I have a "VPC Mongoos-CM3" throttle and a "VPC Control Panel 3", I applied the firmware for the throttle to the control panel.  I immediately reversed it and there have been no ill-effects as the controllers all look fine in Windows and I can bind them normally...except with FSUIPC7.

When I make bindings in FSUIPC, the only controllers responding are the Control Panel 3 and the T-Pendular Rudder.  My "VPC Mongoos T-50CM3" throttle and my "VKB Gunfighter mk2" joystick are not responding.  I note that the the VKB joystick is also not listed under JoyNames for some reason.

I have so far tried some of the reg. cleaning steps you suggested in the past to other users, to no avail.  Please see logs attached.

 


2 Replies
Posts: 251
Admin
(@fsuipc)
Joined: 9 months ago

Please

1. Disconnect the following devices:

    VPC Control Panel 3

    VKBsim Gunfighter TMW

    VPC MongoosT-50CM3,

2. Download and run the attached .reg script (its a good idea to take a back-up of your registry first, before running this script):

3. Reboot your PC, then re-connect your devices and run FSUIPC7 and check which devices are recognised.

Any issues after that, please re-attach the latest version of those 3 files.

Regards,

John


Reply
Posts: 2
Registered
Topic starter
(@c525b)
Joined: 2 days ago

Fixed.  Thanks!


Reply