@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

Just a wee bit dark over the Indian Ocean, Mauritius to Colombo. [image: 376cb914-6740-46ee-942a-2609ea502045.png]

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.

I know this is not what you guys are looking for, but I highly recommend leaving the internal settings behind and switch to something like Axis-and-Ohs, spad.next, Mobiflight etc. This does not only solve the mysterious loosing of controls sometimes it also opens up a lot more options in terms of what you can control. Just as an example I can even manage my sunshades via hardware, every air intake,aso. Initial setup takes a bit longer for every new plane but it is worth it. Only limitation is the number of buttons and axis available as hardware.

@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.

@MarkS Yes, it would be nice if one could quickly determine reasonable PID values ​​without constant testing. Strangely, this only occurs with the autopilot activated in the Cessna 152 when tracking VORs; everything is fine when tracking the GPS flight path. Therefore, I wondered if MSFS had artificially degraded the signal using a random number generator. But that can't be the case, since the C172 doesn't have this problem. What always works is the cone of confusion and, of course, the maximum range. To avoid triggering an error due to the missing line of sight, I also tested this at higher altitudes in flat terrain. Sometimes the autopilot tracks 50 NM without interruption, and then it cuts out for no apparent reason. There's also a peculiarity with the C152 that I only discovered by constantly monitoring the bus voltage variable. For a few milliseconds, the bus voltage drops to zero. You can't see it on the instruments. But since a missing bus voltage triggers a restart of my autopilot in my LUA script, it keeps restarting. The autopilot in the Cessna remains switched on. In summary, this means to me that clean tracking can only be achieved with correct PID values ​​for navigation, roll, etc.

Additionally, while 80% of the tooltips are displayed from the ceiling, some are displayed in the correct places, but it's obvious that something is wrong. The tooltips seem to be cut off. Perhaps MSFS2024 has a standard that needs to be updated. However, I haven't encountered an MSFS2020 model where tooltips are displayed incorrectly in MSFS2024. Here's an example. Model MSFS2020 in MSFS2024: [image: 1.jpg] Volcan in MSFS2024 (part is cut off): [image: 2.jpg]