Jump to content

Recommended Posts

Posted

Hello all,

Sorry to bother you again.

I have the following Saitek controllers

1, yoke and throttle quadrant ... quadrant set up for spoilers, throttle 1 and throttle 2.

2. second quadrant set up for throttle 3, throttle 4, and flaps

3. trim wheel

4. throttle quadrant set up for landing gear, prop and mixture. buttons set up for altimeter increase/decrease, heading increase and decrease and vertical speed increase and decrease.

I have noticed that since my last incredibly bad experience with a hardware update, that every time I turned MSFS on, I had to reset and reallocate all my settings on second throttle and 4th quadrant as listed above.

This proved to be a bit of a pain but was today further complicated by the fact that both of the problem controllers now rename themselves with the same name ie I set up second controller and rename it Flaps, after changing a default setting, Then I apply and save.and then go through the controller configuration. Apply and save again and then I exit MSFS.

Reentering MSFS it go straight to controllers and find that both the second and fourth controllers are both named Flaps and all the settings in the fourth controller are the same as the flaps controller.

The same applies in reverse ie if I delete the fourth controller, rename it Landing gear after changing the one setting in default. I set it all up, applly and save and exit MSFS. Getting back into  MSFS I find that both controllers are now named Landing gear and both have the landing gear settings.

Any ideas on how to retain the individual controllers named as Flaps and Landing gear.  Is it a naming protocol ie should I leave it as quadrant profile name or is that not relevant,

Regards

Tony

 

Tony Chilcott.

 

My System. Motherboard. ASRock Taichi X570 CPU Ryzen 9 3900x (not yet overclocked). RAM 32gb Corsair Vengeance (2x16) 3200mhz. 1 x Gigabyte Aorus GTX1080ti Extreme and a 1200watt PSU.

1 x 1tb SSD 3 x 240BG SSD and 4 x 2TB HDD

OS Win 10 Pro 64bit. Simulators ... FS2004/P3Dv4.5/Xplane.DCS/Aeroflyfs2...MSFS to come for sure.

Posted

I had the same issue with 2 CH quadrants. So, I only use 1 now. When MSFS sees two controllers with identical ID's then strange things happen. I gave up trying to fix this.

5800X3D, RTX4070, 600 Watt, one or two 1440p 32" screens, 64 GB RAM, 4 TB  PCle 3 NVMe, Warthog throttle, VKB NXT EVO stick, Honeycomb Alpha yoke, CH quad, 3 Logitech panels, 2 StreamDecks, Desktop Aviator Trim Panel. Crystal Light VR.

 

Posted

Fielder.

It is resolved.

It is all in the naming protocol ie MSFS does not like Landing Gear or Flaps as controller names.

In the end I deleted all controller names and settings leaving me only with default for all of my controllers, key board and mouse. Then I changed a setting on Keyboard ie adding keystroke B for altimeter reset, After I validated that change it automatically asks to rename the profile, so I elected keyboard profile 1and entered that, I then continued on in the new profile deleting all the settings, applying and saving. Then I started adding the items I wanted, applied and saved, elected to GO back and then reenterring the controller options. Same procedure applied to the mouse, Rudder Pedals and Trim wheel,  The second quadrant (for flaps, throttle 3 and 4) I renamed quadrant profile 2 and the quadrant I am using for landing gear, mixture and propellor settings I renamed as quadrant profile 3 in order to eliminate confusion as I found if I had to change a key mapping I had to go to the controller I thought it was and press a key to see if it highlighted. invariably if I had not changed anything for a while I wound up selecting the wrong quadrant first which proved annoying.

So that sorted it all out for me and I think you would agree that if you are flying the 747 the extra throttle quadrant proves very satisfying.

I also, when initially setting up the key mapping on each quadrant, go through each and every mapping setting on ""äll assignments and delete everything that I do not use. As I fly in VR only, I do not use things like a setting for lights or fuel mappings etc. This may or may not be applicable to you, but I do find it beneficial despite the very long setting up process.

I hope that proves helpful for you.

Regards

Tony

 

  • Upvote 1

Tony Chilcott.

 

My System. Motherboard. ASRock Taichi X570 CPU Ryzen 9 3900x (not yet overclocked). RAM 32gb Corsair Vengeance (2x16) 3200mhz. 1 x Gigabyte Aorus GTX1080ti Extreme and a 1200watt PSU.

1 x 1tb SSD 3 x 240BG SSD and 4 x 2TB HDD

OS Win 10 Pro 64bit. Simulators ... FS2004/P3Dv4.5/Xplane.DCS/Aeroflyfs2...MSFS to come for sure.

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
  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...