Seems it must be in a queue behind other newer projects saldy, but hopefully some news on it soon. Been quite a while since any update on progess at all. Probably not many people in the market for it with the RJ being available so not very hopeful it will be any time soon

+1 for dual 750s as well although a 650 would also be a welcome option.

Solved! @jmarkows said in Pop-out Panel Power Problem: I don't have any solutions other than it's not a universal problem. That in itself is important information too, because it meant that the solution was to be found on my PC, and not a problem for Black Square to correct. I uninstalled MSFS and reinstalled a fresh copy of it. That did nothing. I then moved the Packages folder from my system drive to a second drive. No joy. Then I noticed that the controller profile for my Honeycomb Bravo was not empty. I use Spad.neXt to control all functions of the Bravo, and the associated profile in MSFS should be empty. Why didn't I check that first? I deleted all bindings that were there, except two for the battery and alternator, which were bound to one of the rocker switches of the Bravo. With those two bindings in place the problem persisted. When I deleted those two last remaining bindings I had no more unwanted power switching. Succes! Apparently MSFS not just sends events when I throw a switch on the Bravo. All events associated with a controller are sent also when the mouse pointer leaves a popped out window, in my case triggering unwanted switching of the electric circuits. @jmarkows Thanks again for your help!

Ok folks, I will post my final finding here for anyone else having similar issues: After some more research, I re-installed all my Navigraph data, and then deleted my Content.xml file and let FS2024 rebuild another one next time it started. Resulted in all VOR's being available etc. This file has also moved from the main Microsoft Flight Simulator 2024 file location (although the old file is still actually there - moved as of SU3 I believe?), to inside a sub folder named your FS2024 username. Finger crossed this is the end of that issue lol. Now off to buy myself the Piston Duke! @Black-Square, you have now left me with quite a conundrum! Just getting into the Starship...but now will want to fly the Duke as well...which to choose!

i think the problem is within my Quadrant.. but i don't know how to fix it. i tried to recalibrate https://youtu.be/iX-kqtOXUSk?si=AecSRsflbJP3MevS here is a video what happens. it straight jumps to the middle and then only starts to go linear

@Zwoop68 said in ILS approaches / Aircraft settings: @SirPilot Your MS Store screenshot is from MSFS 2020 (SU16). But you are correct, latest MSFS 2024 SU4 beta version is 1.6.5.0. What's your MSFS 2024 page say? You were right, I was looking at the 2020 version. Scrolled down and found MSFS2024, which indeed, I was enrolled into the BETA program. Went back to SU3 and everything is working as advertised

Traffic 360 is no longer sold. It was replaced by Traffic Global. The PlusPaks were updates to Traffic X - which was replaced by Traffic 360, which was, in turn, replaced by Global. Traffic Global doesn't contain any military aircraft, so, in theory, you could get the Military PlusPak if you want military aircraft in FSX. I don't think there would be any point in buying the Civil PlusPak if you own Global or 360.

@Black-Square when you say it can fly RNAV approaches that arent RNP, do you mean it will actually get vertical guidance info? So far I havent had any issue loading RNAV approaches but I do not expect, and do not get vertical guidance and just use advisory VNAV. I guess there are probably some RNAV approaches that wont show up in the list of available approaches but im ignorant of that thus far.

@Zwoop68 Thanks for the link. I had seen that thread, but given the title, I skipped it. I confirm that's the problem, and now I've solved it. Thanks.

Hmmm, I ended up changing the potmeter to an encoder in my physical Cabin alt controller, but it gave me other problems. It can actually move the control in the sim, but it can not be synced, so it is not so usable. If I set my control to the same setting as the one in the sim, it works, but if it is not the same, my values are different from the Sims.

@Black-Square About the old fashion navigation lights that they are harder to see in clear weather, yes I can understand. I think the lights are very nicely done at dawn, dusk, and night. If the navigation lights in the sim are like the Dukes' real-life counterparts, then they can stay that way, but you should be able to clearly see the beacon light during daytime even from a small distance. Now this is not the case. And strobes.. during daytime, standing next to the aircraft you expect a bright flash not ? The most I would love to see a bit better in fact is the beacon light during daytime. This is my opinion, but I am certainly open to hearing what others and real Duke pilots think about the Dukes external lights in the sim.

Seeing the same. SU3.

Hm…. I have done all my sun visors exactly the same way, to the best of my recollection, but I will look at the model files and see what might be up with the TBM as soon as I get home from a trip.

Unfortunately I still has this issue randomly coming up even after 1.2 . It only happens to Starship and I believe it has to something with custom avionics. Recently I upgraded to RTX5090 thinking may be related video memory issue obviously its not . I tried several long hauls routes without any issue. Then intermittent stutter came back - every second micro stutter. It usually happens enroute and all the way to the landing. I program FMS manually typing each waypoint using keyboard. The only thing come to my mind is something to do with waypoint programing.