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.

Prior to starting MSFS I opened AAO and I was able to select Enable Saitek, everything worked fine when I started MSFS. Thank you,

I was assuming the same, that AAO is just not seeing it. I will check the drivers tonight and see if the log shows anything. Thanks,

I recently upgraded my MOBO, CPU, and Ram which necessitated an upgrade from Win10 to Win11. After re-installing all of MSFS2020 and AAO (Newest version on Simmarket) on Win11 24H2 I was able to select the Enable Saitek in AAO and it worked fine. I then had to re-install Win11 to downgrade from 24H2 to 24H3 to resolve an audio stutter issue, but I have not been able to select the Enable Saitek since it is greyed out. I have tried unplugging the panel from the USB hub and plugging it in to a direct USB on the I/O panel, then restarting both MSFS and AAO but no joy. I have also tried starting both MSFS and AAO as Admin but no joy. Are there any other tips that you may have for me to try? Thanks,

Are you using Smoothtrack or are you using a webcam? If it is a webcam I am not sure. If using Smoothtrack are you using the USB connection or wireless. If it is Wireless you may be getting latency from that, I would suggest trying to use the USB plug. You also may not have enough light on your face or it is too far away from your face which could be causing the jerky motion. I normally have the phone no more than about 24 inches from my face so that it can easily see and recognize my face. If it is too far away it can pick up other movements such as other people or ceiling fans. I simply have my phone in an auto phone holder suction cupped to the desk immediately next to my Yoke. As for the tilting, I actually go into Mapping on Opentrack and set the curve for tilting to all zero so that I do not get any tilting, I just personally don't like it. Also go into Options and bind the center to either an unused joystick button or set a key combo, do the same for Toggle which simply toggles Opentrack on and off allowing you to freeze the view where you want it.

Spend some time adjusting the curves in opentrack I normally setup Dual curves for X and Y axis so it is to my liking, I also set a dead zone so I can have some slight head movement without it translating to the screen. Also make sure to set the reset position button and freeze buttons in opentrack, this will allow you to quickly go back to zero position and if you are programing the FMC or EFB you can push the freeze button to hold it where you are looking.

All I do is Tubeliner flights. I am not sure on the webcam side, as far as I know smoothtrack only works with a mobile device either IPhone or android. I know there are some programs that work with a webcam though I just can't vouch for them. I am sure that both will use opentrack which does work very well though. My son has used smoothtrack on DCS and he has been very happy with it there also. If you have an old phone laying around it will probably work, you just hook it up via WIFI and download the app. I have used it both through the WIFI and the USB, USB works the best.

I have/Use both. I originally came across this a few years ago and have used it ever since. I do recommend it and I can't fly without it. The only down side is that it uses video so you need to have some light for it to work, I just turn on a desk lamp and that is enough for it to work properly. Setup is easy, I actually use an old Iphone for it and have not had any issues. Make sure you follow the setup instructions on https://smoothtrack.app/ .

The 9800X3D is able to be overclocked but the 7800 is not. Below is a post from Reddit, it is literally this easy on the 9800X3D. This can be done either through the BIOS or through Ryzen Master. I continue to test both with the overclock and without. “Enable expo, enable pbo, set frequency override to +200, and then curve optimizer to -30. If it crashes do -25 and so on”

I had to go the route of creating a 23h2 image, but I did it last night and reinstalled windows using the image. So far it seems to have cured it for me. I have only done two short flights but I am optimistic.

So after watching Noel’s thread I spent the time to downgrade from 24h2 to 23h2. So far so good, two flights and not getting the issues I was getting before, I am optimistic that it is fixed for me, I plan to do some more testing tonight.