xsever

Definitely because the guide below is with a 3080. You you can see the difference for yourself. https://youtu.be/GZY6UzNvdJA

There has been newer methods that significantly lessen the fps drop thanks to frame gen on the pre-rendered lower resolution. More details about it below. Also works on 20- and 30- and 40-seriee cards https://youtu.be/GZY6UzNvdJA

This update seems to be pure bug fixing which should've been done prior to releasing MSFS2024... smh

Thank you for sharing this. It looks very promising. I will give it a try when I have access to my sim rig.

I'm on leave in the mountains and away from my sim rig (which I miss 😭). I will test and revert back next week.

You won't be disappointed. Let us know how it goes.

I'm currently doing my first flight using Glass Out in the Fenix A321 and I must say it's a game changer! I was able to easily create a template to have the PFD+ND on my 2nd monitor and the ENG+ECAM on the 3rd monitor without any performance degradation and without any conflict with the Nexus Mods FG which crashes if a display is popped out the classical way. For my PC and setup, I think I have found the holy grail!

You should submit a ticket with this. IF it's a bug, they will know and they will fix it.

No but shouldn't have to pay neither 🤣 Sure. No one/nothing is perfect but a bug as simple as autobrake being too aggressive even on low should've been spotted on Flight # 01 of beta testing if the QA/QC was being done decently. I'm not asking for an utopian case where planes release with zero bugs, but I also perfectly understand that some bugs are too obvious and easy to spot and hence should be fixed during beta whereas other bugs will not pop their heads until after release, and that's fine, and can be fixed with further updates. Sad but true and wise. I think the problem is that the bar is dropping lower and lower with time and some early adopters are just getting fed up.

I think the early adopters who purchased the plane on day 1 and are reporting bugs through the official channels should be given a discount code that they can use when the -100 version is released. I've been following this thread closely and some of the bugs reported indeed should've been identified and resolved during beta testing. Like how can a proper beta program not identify the overly aggressive autobrake on low? That's a simple one no? In all cases, I'm sure this plane will mature into a very good product and when that happens, more and more will buy it.

One cannot but bow in front of the Concorde. If I had more time at hand to dedicate to simming, I would definitely install P3D just for it but my current time budget is very limited and I spent enough time tweaking MSFS2024 to my liking that I am now dedicating my time to enjoying the various airliners I fly. I will admit though that reading your description of operating the Concorde was a bit overwhelming 😅. Cheers!

Please allow me to sincerely thank you for sharing this video. This is hands-down the best explanation I have seen online of the Microsoft-Asobo sorcery/witchcraft they did with the controls for 2024.

I did more testing about this and I think there's something wrong with dynamic FG in the mod because it's the only constant that is resulting in the "15 FPS" bug. As soon as I disable dynamic FG, the FPS gradually recover to 30 FPS in an almost time linear way: 15 18 20 ..... 30 30. I even tried Manual instead of Fixed and set the FPS target to 57 (0.95 x 60) and the bug still occurred when focus was lost and regained. I went back to Manual FG X2 and 57 and everything worked fine. TLDR: This is not an issue with AutoFPS but with the mod itself I believe. What I discovered reminded me why I didn't use this mod in the past: as soon as you pop out a display from the cockpit, the mod crashes and crashes the sim with it. Could this be your problem as well? I read that this was a limitation of the mod in April 2026 but I had hoped that this was resolved by now. I am now at a crossroads: 1) Nexus mod and no popped-out displays on my two additional monitors or 2) no nexus mod and stick with Lossless Scaling but benefit from popped-out displays. I'm gonna have to do some testing to see which path I can live with more.

Thank you for the timely feedback. The target set in the mod is 60 while the target set in the sim is 30. Man FG X2 and FPS=58 worked wonders so the FPS value definitely needs to be the post-FG value. Regard the weird 15 FPS, @AnkH suggested I turn on two settings inside the mod which I will do tomorrow and revert back. Since him and I are using this mod, maybe we can help you address it in the readme as it is getting more popular amongst simmers with 3000- and 4000-series cards.

I can confirm that using this same logic with the nexus mod gave me the best results. I lock my FPS in the sim to 30 and used the mod to get 2x to achieve 60 which works wonders. Using the logic above, I used Man FG 2x and a manual target of 58 and that worked very well. I wanted to experiment with the mod's dynamic FG option enabled for the odd occasion where I can't achieve 30 FPS and when I did that, I changed the AutoFPS setting to DynFG and kept the target at 58. Things worked well but as soon as I clicked on another window and focus was lost from the sim window and then I refocused the sim's window, the FPS dropped to 15 as reported by AutoFPS FS Source and it was stuck there. The only way to go back to the native 30 FPS was by disabling the mod's dynamic FG. I went back to Man FG 2X and things were back to perfect. Is this a problem with the mod or this due to a misconfigured setting in AutoFPS caused by me when switching to DynFG with the FPS value set to 58? I find the number 15 (30/2) intriguing and you will probably know right away what was happening. Thanks.