100 percent the flaps are inverted. No aircraft goes nose down when the flaps go down. The aircraft in the aim slows down as it should and it feels like it has lift but it is 100 percent not supposed to be pitching nose down to the point you have to fully pull on the yoke to keep it from crashing.

[image: 0f68280a-aa93-4bdf-9527-e502c8fab584.jpeg] I had to take a screenshot from a video I took at USNA while visiting my son there. Across the water from the years, you can see the three remaining VLF towers. Sorry. It was a drizzly day.

@Iconography think i finally solved the issue just in the fenix now same thing don't see anything moving, so instead of using my key board short cut, i used the menu bar to go to external and now i see every thing moving

Hi mark, Thanks for taking the time to reply, I had a search on the forum and see someone say they had the same problem. They solved it by ensuring that both nav radios were tuned to the ils. I have tried this solution and it seems to have solved it. I will keep an eye on it and raise a ticket if I can replicate it again. Thanks again for replying. Ross.

https://www.justflight.com/articles/new-black-square-msfs-aircraft-development-update-feb-2025

Worth trying a reinstall?

I have the most recent version 1.9.1 and there is no 'eng inst' switch or spot to make the pilot visible in the F-15C. Any tips? Looked everywhere on-line

You mean the last SU4 beta update I assume? Did it cause a co-pilot to appear in the Starship?

I've had another AP coupled VOR approach fail. This approach had a standard teardrop intercept, so I set NAV2 on the outbound radial and NAV1 to the inbound radial. As I approached the IAF I activated NAV2 as the source and pressed NAV. She coupled to the outbound radial and flew it beautifully, Using HDG mode at the completion of the outbound I set up a standard 30-degree intercept to the inbound radial, changed the Nav source to VOR1 and pressed NAV. It flew right through the radial without intercepting, so I finished the approach manually.

I have the most recent version 1.9.1 and there is no 'eng inst' switch or spot to make the pilot visible in the F-15C. Any tips? Looked everywhere on-line

I recall this coming up during the testing of the 146 in XP12. It is expected that the TGT will peak out of limits if the throttles are very quickly advanced from idle to full power; however, I do agree that the TGT peak is quite excessive when this occurs (although there isn't any data out there to confirm/deny that). From the discussions I had with the development team, the high TGT peak in this instance is predominantly a side effect of having the engine simulation accurate throughout their normal range. So if the throttles are advanced at a normal rate, the engines will behave accurately and the TGT won't go out of limits. I'm unsure if the needles should be able to rotate 360 degrees, but again, it's one of those things for which there is no data/reference material available for, as no one wants to be overheating the engines on the real aircraft. I will, however, raise this on our internal bug tracker for the development team to take another look at ahead of a future update to the 146 XP12. Mark - Just Flight

It may be worth double-checking that there aren't any outstanding updates for the Thrustmaster software or the device drivers, and also checking if there are any sensitivity curves/deadzones applied within the Thrustmaster software itself. Unfortunately, with it not being our software, we're limited with what support we'd be able to offer for it, but if you contact Thrustmaster support, they should be able to provide some assistance and troubleshooting steps. Mark - Just Flight

Thanks for reporting this. The sunvisor turning invisible is sadly a limitation of the MSFS LOCK interaction system when a clickspot is applied to a transparent object. I know this affects most (if not all) of our aircraft, due to the way we need to set up the animations of the sunvisors. However, we have logged this on our internal bug/feature request tracker, and we'll take a look ahead of the next updates to the PA28s. Mark - Just Flight

It is good practice to allow the aircraft to level off at a preselected altitude before dialling in a new altitude. I don't recall if it's in the 146 or RJ FCOM (or both), but one of them does advise pilots not to adjust the preselected altitude during the altitude acquisition phase. From the input we've had from pilots, as well as various reference videos online, we find that pilots flying these older aircraft types spend more time thinking about passenger comfort than those flying modern airliners. For example, a lot of RJ videos online show pilots descending in V/S mode and slowly increasing/decreasing the VERT SPEED value rather than using LVL CHG mode. Even a relatively 'modern' looking RJ is a lot more involved than a modern airliner! Mark - Just Flight

@Outermarker One has to get the balance right between keeping customers well informed and avoiding too much AWNTY* for the development teams. I am quite sure there will be some more news in due course, but I think it is fair to say that most development date projections are a target first and foremost.

This sounds very similar to I have with an issue with the LVL CHG mode of the autopilot. A fresh WASM folder/install solves the problem temporarily. But over time, it goes back to not working.