@SnakeDoc said in lights issues, weather radar stopped working: I have v1.1a installed. The lights were affected from the "force winglets feature" in the tablet These two things shouldn't be true at the same time. Are you sure you have v1.1a? How did you learn that? From the installer, or online from Contrail, etc? If you're still having that issue after v1.1a, then I think Contrail's v1.1a might not actually be v1.1a.

@AlphaEcho said in Dynamic registration numbers still not working!: I’ve not gone back and searched, not much point doing so I felt the same way, which is why I simply pointed you to the most recent discussion on the topic that was fresh on my mind. If you think you're frustrated, imagine how I feel to see the aircraft I've spent years developing, where I've cared deeply about each pixel for some minutes or seconds of my life be marred like this for years by a broken simulator, always with the hope that a solution is one, unannounced midnight update away. @AlphaEcho said in Dynamic registration numbers still not working!: I honestly think the time has come to accept that MS have no interest in fixing the cause of this I'm very sorry you have to deal with this on XBOX, but when the problem was addressed on PC, I could only assume that a solution for XBOX would be forthcoming in weeks, not months. Please don't take offense to this, but I heard the same suggestions since MSFS 2024 was released, but all registration issues on PC were fixed in SU3. It just took some waiting for the proper solution. @AlphaEcho said in Dynamic registration numbers still not working!: please may I ask you to investigate if there are any reasonably “quick” alternate implementations/workarounds that would fix When we had this issue on PC, I created the default-on switch in the tablet to disable the registration as an alternative. Unfortunately, permanently removing them, rendering new textures with registrations, and maintaining two versions for PC and XBOX would take probably two weeks of work for all my aircraft. However, I would do it if I thought the update could be released for XBOX users in less than several months. We still have products and updates that have been waiting for marketplace approval since last September. @AlphaEcho said in Dynamic registration numbers still not working!: If these issues are raised with MS, we are told it’s a developer issue. It’s quite frustrating. Can you share with me when you've been told this? This is 100%, undeniably, an XBOX problem. We do have Asobo's ear for the most part, and things do slowly get addressed and fixed. Like I said, I will do my best to get a response out of Asobo again on this subject as soon as possible. It seems they have a lot of things to fix in SU5, so hopefully this could be one of them.

Confirming that pms50 fixed this from release 2.2.60 of GTN 750.

The issue persisted across all turboprop aircraft that have a condition lever. Re-installing Flight Simulator 2024 resolved the issue. I can only assume it was a faulty package upon installing SU5.

@iflygary Well I do not find it difficult but need to admit that I switched from the in-sim bindings to Axis-and-Ohs a long time ago (several years). This way I can avoid the flaws of the sim with the addition benefit of being able to control much more than the ingame binding allows you. Most important in this case would be to use input repetition for the switch, otherwise it will snap back. I can provide you all the scripts you might need for controlling the Baron in case you would like to go this route. Just to give you a few examples, I can control the sunshades, every air ventil, and most of the other knobs and switches with hardware. It was a game changer for me switching to an external tool to control everything. No more lost bindings, no more missing bindings. Easy switching out hardware. Initial setup takes a bit longer sometimes but this is more due to find the right variables than to bind them. Sorry that I cannot supply more support within the Std.

Okay, so I had a few minutes to test a couple things out. Primarily, the issue I noted earlier with not being able to get close enough to the pitot covers to remove, IS a VR issue. The issue is not there in 2D mode. The same applies with the menu and tablet size changes. These two are not really issues, as they don't negatively effect their use. I didn't test the instrument lighting, but should be able to later this evening.

@Black-Square said in KingAir 350 - brightness of the AP panel: If so, then have you tried adjusting the "ANN BRT" knob on the radio panel (right of the altitude selector)? I didn't know about that "ANN BRT" knob! Everything's fine work now.

That's correct. Data logging from the ETM is not implemented, mainly do to the limitations of JavaScript in MSFS. The button is connected to the unit in software for future use, but it has no functionality.

Can you share a screenshot, please? All the main instruments occupy the same amount of texture space, so there shouldn't be any noticeable difference between them.

Glad I finally tested this. I had forgotten that the indicated airspeed must be below 145kts for the warning horn to activate. That should do the trick

I got the update via Marketplace but for me the module is light years behind the competition we now have the luxury of enjoying. The latest update was underwhelming IMO and the module will remain unused, sadly.

Can anyone explain exactly what needs to be typed to get the Fuel Selector to work? I saw Nick's reply, but the spaces, commas, and "enum" command don't seem to work. I'm struggling with this hardware controller stuff.

Marty and I have this sorted out. The uppercase characters from the Star Trek BT font are acceptable for the registration number.

@Tadeus72 Do not get me started on this. It is a mess and not only with BSQ Planes. It is a Sim issue in my mind. The only way I get this somehow consistently working is the following: Spawn at your departure location Restart the flight before you move the plane. When I do spawn cold & dark I usually hop into the plane and do the restart from inside. After shutdown on the destination airport I do restart the flight, in case of C&D I hop into the plane and push than “end flight”. If I follow these steps it does more or less consistently save the flight in the logbook and also does the state save.

Thanks for sharing. That always makes my day to hear. You know where to find me, so let me know if there is ever anything I can do for you!

Hi Mark, I have uninstalled, re-installed the RJ several times - all to no avail... In response to a support ticket, all that JF Support had to say was: "When trying to import a flightplan into the FMS, have you populated the "CO ROUTE" In the co route box, if you enter your route as YBBNYMML, this will import the flight plan." Manually entering the co route does work but that was not previously required - and is an unnecessary nuisance... Even with a brand new MSFS 2020 installation (a massive download) and only the RJ installed, the problem persists. I have two copies of the RJ. One from the MS online store, and a .exe install file from Justflight. Both versions react the same. This is immensely frustrating - so I have relegated the aircraft onto the back burner.

Here it is in the dark and zoomed in on it with the drone: https://www.youtube.com/watch?v=a-Ak3kpUWEQ