Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
Are you using Developer Mode or made changes in it?
No
Have you disabled/removed all your mods and addons?
YES
Brief description of the issue:
Multi-Panel: The HDG/ALT/IAS/VS value knob does not change the associated values in the ATR and the AP controls do not control the AP functions in the plane.
Bravo Throttle: AP controls do not control ATR AP functions and switches do not move light switches in the cockpit.
Provide Screenshot(s)/video(s) of the issue encountered:
Detailed steps to reproduce the issue encountered:
Enter the ATR cockpit
Power up the aircraft by either starting an engine or using GPU
Use the logitech multi-panel or Bravo throttle knob to try to change the heading bug, selected altitude, coarse, vertical speed, or IAS speed
Observe that none of those values will change - this works in all other MSFS 1st party aircraft and most 3rd party
Use the multi-panel or bravo throttle to attempt to select HDG, IAS, NAV, VS or any other AP mode or to turn the AP on.
Observe that the ATR AP does not respond. This works in all other 1st party aircraft and most 3rd party
Use the mapped switches on the Bravo throttle to toggle beacon, landing, strobe, or other extrernal lights.
Observe that the switches on the overhead panel do not change position.
Go to an outside view of the aircraft
Observe that although the switches remain off, the lights are on.
PC specs and/or peripheral set up if relevant:
Honeycomb Bravo Throttle on USB 3.0 port
Logitech Multi-Panel on USB 3.0 port
Build Version # when you first started experiencing this issue:
Upon release of the MS/S&H ATR-72-600
For anyone who wants to contribute on this issue, Click on the button below to use this template:
Do you have the same issue if you follow the OP’s steps to reproduce it?
Provide extra information to complete the original description of the issue:
If relevant, provide additional screenshots/video:
We’ve moved your topic into the Community Support category.
The Bug Reporting category is for posting suspected or confirmed bugs that other users are able to reproduce. Using the template is required in order to provide valuable information, feedback, and replication steps to our test team.
If you are not sure if your issue is a bug or need further input from the community, please use the Community Support category. If the community can replicate your issue, first search the Bug Reporting category to see if there’s an existing topic. If it already exists, contribute to that report. Duplicate bug reports will be closed.
If you believe it is a new report, then create a new bug topic using the provided topic template.
All issues caused by or involving third-party addons/mods should be reported to the third-party developer. Assure that no addons/mods are used when reporting issues in Bug Reports.
I have spent the last day or so configuring Spad.next with my logitech panels.
You need to use LVars. I will try and share my settings on Spad.next.
It does work i can tell you that, the values will all cha ge - the only thing i cant make happen is the animation for the rotation of dials - but still, the values (heading / altitutlde etc all do change).
I was a bit snippy seeing that the forum moderator moved this post from a bug report to “community help.” But yes, please post your configs, I’ll probably have to invest in yet another piece of software to make up for what MS can’t do.
I think it’s more a Logitech thing than MS/Asobo. My Logitech Multipanel and Switch panel have varying results with different aircraft. Some planes play perfectly with them (CJ4, Beech Bonanza, etc.), and some are near useless, some “half work”. Spad.Next or similar seems to be the fixall, but I haven’t made the plunge yet.
I have multiple devices: a Thrustmaster Airbus Stick &Throttle Quadrant, a Turtle Beach Velocity One Stick, a Thrustmaster Hotas One and a Turtle Beach Velocity One Flight controller (the system with the wonderful trim wheel) on my Xbox and to date could not get one of these to work. I have lots of planes but I could get all of them to work decently with at least one of the controls. Not so with the ATR. I have deleted it for the moment as I have spent too much time by now to get it flying. Too bad.
Other than IAS, the Logitech panel has been flawless with every plane I’ve flown - 1st part to add-on. The Bravo Quadrant has actually done even better as it does IAS in the planes that have it.
In the ATR, neither do anything. Even the MSFS bound switches for lights and even for keyboards. Which makes this a bug, not a peripheral issue.
I’ve spent 10 hours so far configuring spad.next for the ATR and got the heading knob/bug working… that’s it. Guessing ALT, IAS, VS and the rest will take the same. All this for a $12 plane. I would have paid 3 times that to have it work like the others in the sim.
I have the heading knob and button working using SPAD.next, but nothing else after a long evening of trying. I spent hours on ALT knob and button and got nowhere.Guessing the other buttons, knobs and switches will take as long.
They could have done better and I would have paid more.
Furthering my comment above: Logitech panels, i.e. the “Switch Panel”, mostly lights, landing gear, etc, and the “Multi Panel”, mostly autopilot and flaps, both use a custom Logitech driver which is loaded with FS2020. Neither panel can be found in FS2020’s Controls configuration page, so you are forced to use whatever control mappings are hard-coded via the driver.
As I mentioned earlier for some planes, the mappings work very well. Here are a few of the issues I have with other planes:
Longitude: Hitting any Switch panel switches seems to cause the Pitot Heat to move from Auto to On, causing a CAS message. I think when you hit any switch on that plane, it sends the state of every switch to the sim, not just the one you just changed, causing interesting issues.
PMDG 737 - similar to above, but it changes the plane exterior lights to some weird states. Even the gear knob does this, so I use the gear knob on my Boeing TCM yoke. I sometimes just unplug the switch panel when flying this, as I’ve gotten adept at mousing most everything.
Aerosoft CRJ - I just got this last week and have only done three flights, but the altitude knob on the Multi Panel doesn’t work (neither does my rocker switch mapping from my Boeing TCM yoke), and I think the same with either heading or speed knob. I have to spin the dials via mouse wheel, which is a pain.
So, it’s a combo of Plane, Saitek/Logitech Drivers, and the sim itself. SPAD was originally freeware invented to allow a simmer to customize mappings for Saitek, and Spad.Next (paid) makes for a fully customizable experience.
I think I explained things correctly, but certainly welcome any corrections or further explanations to the above.
Do you have the same issue if you follow the OP’s steps to reproduce it?
Yes
Provide extra information to complete the original description of the issue:
Honeycomb Throttle Quadrant ALt,VS.HDG,CRS,IAS selector and + minus knob not working on ATR
If relevant, provide additional screenshots/video:
This is unfortunately a common theme. Some functions will work in one plane and wont in others, no matter the peripheral you use.
For example, you can map the fuel pump or fuel tank selector to any controller (or use the Logitech Switch Panel) and it will work in, say, the Cessna 172 but will not work in others such as the Beaver, even though the function is the same.
From what I read in another thread, this is especially true for many functions in the new ATR.
Thats why I wont buy any planes until we have a demo function or return policy in place so that I can test the plane before spending money on it.
Do you have the same issue if you follow the OP’s steps to reproduce it?
Got the same problem using my Bravo Throttle
Provide extra information to complete the original description of the issue:
I noticed that the heading, vertical speed and altitude knob do actually work… Sorta… Whenever I turn the heading knob on the Bravo throttle, the plane will start to turn for instance, but the displayed AP heading in the aircraft will remain “stuck”. Whenever I click the heading dial with my mouse, the plane will turn back to the displayed heading in the sim which hasn’t moved with the Bravo throttle input… Sorta feels like there are two autopilots flying the plane… Bravo controls one, msfs controls the other…
If relevant, provide additional screenshots/video:
Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
For anyone who wants to contribute on this issue, Click on the button below to use this template: