jjeffreys

It is not too late to downgrade, I used this guide:

I never had the issue with Windows 10 and 2020 or MSFS, in December of 24 I upgraded to W11 24H2 and the problem was there in both 2020 and MSFS. I then downgraded to W11 23H2 prior to November of 24 and have paused updates. I have never had the issue since then. I just continue to push the Pause updates out until Microsoft figures out what the problem is. I am 100% that it is an issue that was brought in on Windows around December of 24, something does not play well with 2020 or MSFS.

I will say yes it worked for sure in 2020 with the original V2.1 release, I never tried it in 2024. I will say that this weekend I downloaded the new v2.1.1 (?) release in 2024 and imported my template I use for the CRJ from my AAO in 2020 to the 2024 AAO and it did not work. I did not go in and trouble shoot it though, I just pressed the buttons on the OVHD to make them start and got up in the air. All of the other code seemed to transfer just fine and worked with the import template function so I figured that maybe the code changed with v2.1.1 or it is different in 2024. I will fire up 2020 with the new v2.1.1 and see if the code still works there and if so I will try to trouble shoot it.

I saw on the video by YourSimCFI that with the new FDE update it now has the proper AOA when in approach, did Hans do anything about the HGS layout? On V1 and V2 when on Final approach the HGS is basically unusable since all of the cues go off the bottom of the HGS and are not able to be seen, unfortunately in the video he was in the right seat and not the left with the HGS down. The last post here by "amahran" shows exactly what I am talking about https://forum.aerosoft.com/index.php?/topic/172143-hud-placement/#comment-1087084 Thanks,

I used the following video to do the downgrade, it worked perfectly. I did have to do a complete re-install of windows so make sure you backup all of your info on the C drive.

I had this in both 2020 and 2024 after i built my new rig after Christmas using a fresh install of Windows 11 24H2. Back in January I rolled back to Win11 23H2, I used a version that was prior to December, I can't remember which one. Since I did this I have not had it happen even 1 time since, I fly every weekend at peek times here in the US. It is an issue with MSFS that does not play nice with something in the newer updates in Windows, I have seen in the main MSFS Forum thread that some even experience it on Win 10 and 23H2 with the newer updates. I have had to keep my Windows updates paused to make sure that it does not get corrupted. Edit: Here is the thread I talked about, there are lots of different things people are trying but most of them only work for a short time https://forums.flightsimulator.com/t/audio-stutters-in-menu-globe-and-on-ground-during-flight/718524/512

Actually I had it happening in 2020 and 2024.

I also downgraded to 23H2 back in January and have not had the issue even one time since. I have always been on USB headset and tried removal of the Audio drivers with no permanent change until I rolled back to a pre December 23H2. I was getting it in both 2020 and 2024, I have updates paused and am worried that it will come back if 24H2 is installed again. I watch each of these posts both here and on MSFS forum waiting for the real fix. It is obviously something that was introduced around December by windows that does not play well with MSFS and current hardware.

Thank you, that makes sense that he changed it, I didn't think to look for a change like that.

For the engine start in v1 of the CRJ it used to be: 1 (>L:ASCRJ_ENG_START_L,Number) Now in v2 you have to hold the button for a minimum of 3 seconds, how would I script something like (Hold:3500) to simulate a depression of the button for 3.5 seconds? Thanks in advance,

I also had it rotate early, Trim was set to 6.7 exactly as prescribed and it rotated at or just before V1 automatically. From now on I will just give it a few notches less trim.

Ryan, I am just a desk top pilot, but there is the option in the EFB to add VNAV, I think it is an option on the 1000's. In v1 it was just OK but from my trials last night the VNAV in v2 worked much better, I used SPD for the Climb phase and VNAV for the descent phase. The only down side I have found so far is the DIR function does not play well, I did just read that it sounds like even the real one sometimes has problems so pilots will actually double pump the DIR, to get it to re-draw the path. For example if you want to go direct to SMOKE you would select it and place it at the top LSK then hit EXEC, then select it again and place it in the same LSK again and hit EXEC again, I don't know if this will work in the AS CRJ but I plan to try it tonight. So far after 1 flight I was very happy with the flight dynamics and fixes that they put in. I would like to see the HGS lowered a bit, when using it on Final it still seems that the flight director is too low on the screen, it is not like on v1 where you could not see it, but it still seems too low for use.

No problem, it is one that a lot of folks are having, including me at one time.

It is the NVIDIA App. If you have the app installed you must use MSFS in DX12, the sim will not start in DX11. Go to the User CFG for MSFS and change it to DX12 and it will fire up. If you are not using the app then remove it and it will work. https://forums.flightsimulator.com/t/msfs-crash-before-opening/702654/30

I have a similar issue in that Flaps 5 on the Bravo is actually Flaps 10 in the Max. I have to set it to flaps 2 to get 5. I have the ProDeskSim version for the Bravo. My Spoiler arm seems to work now though, originally it would not arm when moved to the Arm detent, so I think that they made an adjustment to the spoiler. Maybe it is possible for them to make the change on the flaps.