I recorded another video showing the problem on external view. The stick's deflection remains the same (joystick), say around 30 degrees, and quite slowly. It's clear that the Vulcan reacts somewhat slowly and slowly to the left, which is a good thing. However, if the deflection is the same, or even smaller (sometimes just a slight movement of the joystick to the right is enough), the Vulcan immediately starts moving strongly to the right (too sensitive to the right). The roll rate for both directions isn't the same. https://youtu.be/suhUSuICFGw

Nothing is wrong with your install. I experience the same when using the KLN90B autopilot. The display shows nothing, even though the autopilot appears to function, although with no annunciations. As soon as I hot-swap the KLN90B to, for example, the GNS530 suite, all of a sudden, all annunciations come back.

Nick, please, a little update or beta test opportunity ,-)

Agree, would be great to be able to have the speeds in km/h!

@SteveKane Very interesting results!! I will eagerly await more testing! This could explain why I have never seen this, since I don't use any 3rd party hardware applications that might be polling the variables or causing whatever hiccup is related to this in MSFS 2024.

@asnamara Wonderful! I'm glad I could make the improvements you were looking for. I never promise that it's perfect, but with every piece of feedback, hopefully it gets a little better

Hey. Yeah, having the same issue. Can't read the labels in VR during daylight. And I am running a Meganex8K with a 4090, so there are a lot of pixels rendered, but this still isn't enough. Luckily there aren't that many switches, so I just memorized them. But I also have the problem with very bright sunlight making the gauges a bit dim. This seems to be a sim problem. Had that in other planes too. In MSFS 2020 you could mitigate that effect by turning on the gauge lighting, but in MSFS 2024 it doesn't work until it gets darker outside. Made a bug report about that ages ago, but didn't got enough votes to be looked at.

Yup, managed to get to 279 KTAS at FL 280. [image: 0a9dae00-779a-4877-ac7f-c8a7b84094a6.png]

thx for confirming. BTW I am currently in Honduras on my way to Belize

The one on flightsim seems to have been taken down. A2a has one that came with the Aerostar but it doesn't seem to work any more either. I'm guessing Asobo broke it with SU4.

@Black-Square Sorry Nick, I had to crop the screenshots because 1440 is apparently too big for the forums to handle, and I thought I did a better job describing. And yes, I am in MSFS 2024, which I'm sure I missed saying in the OP. Yes, I have been starting with the propeller feathered, only for the last screenshot with the battery charging and positive instrument air had the propeller out of feather and in the high pitch position. Incidentally, I noticed with the propeller feathered that instrument air and fuel pressure reached nominal levels during startup, and then fell off again. I thought I had been keeping abreast of the propeller RPM issue, but apparently I missed how pervasive it is. Sorry about that. This is the same issue as the generator not being tied to the Ng, and therefore not putting out enough power at lower RPMs?

Hey guys, I don't know exactly how the throttle axis is configured on your TQ6s, but I had good results with my Velocity One quadrant using the MSFS 2024 sensitivity settings. I posted the results here if anyone would be interested in taking a look. This gives me the entire range of forward and reverse travel on one axis and roughly matches the virtual detents with the proper positions on my physical axis, though I don't have physical detents. If you guys have physical detents, this same method should, if I'm understanding it right, allow you to tweak it such that you can match the physical detents to the virtual ones, it might just require a different neutral and Sensitivity+/- settings.

@Mark Appreciate it as always.

For Axis And Ohs I managed it, changing the Interior.xml a bit. At the component ELECTRICAL_Switch_Alternator_1 I added this code: <OVERRIDE_ANIM_CODE> (L:var_GeneratorSwitch, number) 1 == if{ 0 } (L:var_GeneratorSwitch, number) 0 == if{ 100 } (L:var_GeneratorSwitch, number) 2 == if{ 200 } </OVERRIDE_ANIM_CODE> Afterwards I used the "Layout Generator" from fs.to to recalculate the layout.json. Now I'm able to control the Switch using something like 1 (>L:var_GeneratorSwitch, number). @Black-Square It would be great if you could add this to one of the next updates. This was already missing in the 2020 version and drove me nuts.

Thank you very much for your advice - greatly appreciated.

Agreed and the OAT gauge top left. The deg C does not match. Dunno about F.