THIS FREE ADDON is a VR GAME CHANGER! GOODBYE STUTTERS with Smooth Flight for MSFS - ALL VR HEADSETS 

Thanks for this posting, it clarify the situation. I would be nice that you also describe how you software do better that the 2 others. How do you differentiate?

Thank you for owing up to this, and publicly too. It takes real guts to do that. In response, I am completely satisfied that it was inadvertent and I forgive you. If I can do that being the one most affected, I hope that others can too and continue to use and support your app into the future.

It would make a lot of sense to consolidate this FPS project into one sensible project, It’s messy having two different projects…

@@eaglefirestudioI'm hoping that in the future, the differences in our 2 approaches will begin to separate us a bit more. Now that we have a more open line of communication, I expect a bit more of a difference to emerge. Also, I've already been in contact with 2 people that tell me my version doesn't do anything for them..and I find it's refreshing to be able to point them to ResetXPDR's version as an alternative. I could agree with the messy comment, except that they both use the exact same "mobiflight-event-module" that goes in the Community folder, so running comparisons with them couldn't be easier. It's kind of the opposite of messy.

@somewhereelsestudio6342 While I was quick to criticise you yesterday, I applaud you for coming back publicly and apologising....well done! After thinking about it more, I believe the VR Flight Sim Guy jumped the gun a bit and could have maybe have done a tad of research before posting....he did that once before with an initial Windows11 and G2 being wiped out video he posted then retracted when he realised he had created unfounded panic....anyway, alls well that ends well eh?

Outstanding effort, I’ve tried running both of the apps together, it seemed to work ok, good fps. I’ll give this app a good test tomorrow at some point.

@@goochygoochoutdoors.1913Both together? I hate to break it to you, but you're not actually testing what you think you're testing.

@@goochygoochoutdoors.1913 Definitely don't do this. Both programs will be competing to modify the variables that represent the TLOD and OLOD. One of the other, not both!

Why no admission that you just piggy backed onto the original developers app and the major improvement that Reset XPDR published a few days before you released this...not good to imply its all your work, you should definitely give credit to the 2 guys who were there before you

@@GunPilotI never implied that it was *all* my work. And I have given credit to the 2 guys before me. But you're making accusations you know nothing about. Those 2 guys are Muumimorko and Fragality. With the exception of their code that talks to and from MSFS, this program *is* all mine. My design... my code. Both ResetXPDR and I branched off the same code that was built by Muumimorko (the MobiConnect part) and Fragality (the rest of the proof of concept code known as DynamicLOD) after both of them had abandoned the project and announced there would be no further updates. It was at that point that both of us each created a new fork and began to work on our own ideas. (By the way, I originally asked ResetXPDR to collaborate on the project, but he declined. ) After a short discussion, we agreed that our different approaches were unique enough that it would be difficult to collaborate. At the time, ResetXPDR's version was nearly identical to the latest version of the Fragality code... in that it was all based on AGL with a couple of spreadsheets and hard coded AGL = LOD pairings. The version of the original DynamicLOD that I used as a base for the communication with between the tool and MSFS has none of ResetXPDR's code in in it. So yes, I'm using Muumimorko's very slick communication engine to talk to MSFS. The majority of the remainder of the code I'm assuming belongs to Fragality - and it is pages (and pages) of code to manage the spreadsheets that correlate AGL to LOD settings. And since I was not about to base my idea on AGL, that was entirely discarded. But to claim I piggy-backed off of Reset's code? That has no basis in reality.. You must think I saw Reset's autoFPS tool and then built (and tested) mine in 4 days??? I'm flattered that you think I'm that fast, but no. This took time. It's a design I've had ever since MSFS came out with VR support three and a half years ago. Without Muumimorko's amazing Memory Injection code, it wasn't possible until just recently. While we're on the subject, the original design for this came from a title that Papyrus came out with in 1995 (I think) called Indy Car Racing 2, that would change the number of cars you could see based on FPS. Back then getting 12-14 FPS was considered decent performance.

😂😂

Exactly my thoughts!

3?

What’s the third one? I’ve got the autoFPS, what else is there?

@@JanStrojil DynamicLOD Tool

Yes, Yes, Yes... An explanation of each setting, what it attempts to accomplish, and what reasonable values might be considered for low-end, mid-range, and high-end graphics cards would be helpful. I've been playing with AutoFPS for a few days now with decent results. Now spending time with this new app. Having this capability embedded in the sim would be awesome but KUDOS to the persistence of the author. I will definitely contribute some $$.

Totally agree 💯

100% agree with you @bulversteher. As a creator of some race tracks for MSFS, I find it insane that Asobo can get the X-Y coordinates of those mountain peaks correct from 20 miles away, but is continually adjusting the elevation right up until you get within arms reach. but it's the limitations of the current sim ...and we all deal with them. The only thing you can do to help alleviate that is to set your TLOD setting higher. This will cause the levels of detail to be drawn at a greater distance. (I was able to gather that Asobo has 14 different LOD levels for terrain) But as we all know, if you set that too high, it gets like a slide-show and that's another immersion breaker.

Totally agree. In VR you really notice these changes much more than on a regular monitor.

I think with 2024 they've all but given up on 2020. I have high hopes for the new version built from the ground up with the lessons learned. I think we'll come to view 2020 as a paid beta, with 2024 hopefully being absolutely amazing 🙏Shame we have to pay twice, but worth every penny

​@MichaelBarry-gz9xl "From the ground up," now where have we heard of that phrase before? 😂

Thankyou so much!

Agreed 👍

This would be good. I’ve downloaded it and it doesn’t seem to do much and still got just as much stuttering.

They're coming thick and fast now mate, thanks for the support :)

Darren; the short answer is this: You should know 3 things about your current settings. Your current Terrain LOD, Object LOD, and what FPS you normally hit with those settings. 1. Set the FPS to a value your video card can hit. It won't do you much good if you set it so high that the SmoothFlight tool continually tries to lower your graphics settings to get you above that FPS threshold. That would look ugly. This doesn't give your computer more power. It does however very intelligently adjust your settings to make the best use of what you have.... all without cooking your video card. (check your video card temperature while this is running - you'll be surprised) 2. In the "Limits" section, set the maximum values to roughly the same as what you now use in normal MSFS flight. In other words, DON"T set these to maximum. This is important, unless all you want is the best visuals at all costs. Note: Once SmoothFlight has found how far it can push the TLOD and OLOD settings without your FPS dropping below your FPS threshold... it will have found the optimum settings for that moment in time. The good news is, it's going to keep double-checking to make sure you are *still* using the optimal settings during your entire flight... so yes, you can go from flying over the ocean to flying low over Lower Manhattan with 3,000 x 3000 supersampling in VR and this beast will auto-compensate and keep you smooth. When you leave the city, the higher graphics come back and you never leave too much power on the table. 3. If you have the maximum values set low enough, and SmoothFlight was able to reach those maximums without dropping below the minimum threshold, the remaining power / headroom is not wasted. It will be converted back into higher FPS. It's not uncommon for me to have my minimum set to 40 FPS, TLOD set to 125 (for scenery out as far as I can see anyway), OLOD set to 85 (because if I miss a baggage cart at the airport, I really don't care) and actual FPS is in the 70's. In VR. Don't be suckered into setting a high FPS number. This number won't limit your FPS. It only sets a threshold by which lots of calculations start happening.

@@somewhereelsestudio6342 Excellent! Thanks for this explanation!

@@somewhereelsestudio6342What do you recommend for landing settings? Seeing what Steve set for his landing settings seems a bit low no? Also...for alitude...if I set it to 33 does that mean 3,300 feet is the altitude at which the settings lock in for landing?

@@JM1701ABCDAs mentioned elsewhere, you can disregard the "Landing Mode" and just let it adjust based on performance. but for those who really love tweaking and want a bit more control for landings, the option is there.

It will definitely help you out Sven, especially since the software tries to better match frame timing at lower FPS values.

Hey Jose, I hope you are well :)

Clouds are not yet implemented. Changing cloud detail is VERY noticeable and was therefore not included ... but the more I read about cloud manipulation, the more I'm tempted to add it. I did some performance testing myself with cloud adjustments, and found the results to be rather un-impressive. That might have to do with the fact that I'm using a 4090 card but I saw no more than one FPS difference between Low detailed clouds and Ultra. Yet I read how everyone else thinks that clouds are "da bomb". So back to the test bench for me. Still, some rather impressive results are possible without such visually obvious changes. And I value invisible mods more than the things that reduce immersion. Yes, this can be minimized... or better yet, the "secret" mini-mode. check the upper left hand corner of the app window. There's a tiny silver button up there that will shrink the app to post-it note size. You can "paste" that anywhere in the cockpit in VR - totally out of the way, but still able to read how it's doing.

Unfortunately it didn't work for me.

My pleasure Kam :) Funny enough, I'm about to try it!

Couldn't agree more!

Thanks to continued updates and optimizations from Asobo, it's true that many of us can run stutter free. However, the settings you use to get stutter free are truthfully only good when flying in the same kind of environment that you created them in. Take those settings to one of the major cities (NYC, Tokyo, Paris, London, etc) and your hard-coded stutter-free existence falls short. Take those same settings to the Alps in nice weather and you're leaving a lot of horsepower on the table and not using to it's full advantage. Do you find yourself wondering if you could add a bit of eye candy?? I know I and many friends do every day. And that's the reason why tools like this exist. So you can be assured you're getting the best performance and/or visuals based on your preference.... no matter where you are. Heavy Rain storm? No problem. Joined a group flight with 30 other planes? Got it covered. :) Myself, I'm very susceptible to low frame-rates, so I set mine to give me blistering FPS numbers in VR. My flying buddy would rather have amazing visuals and happily runs at 10 FPS below me. We use the same tool, different settings, and we are both blissfully happy.

@@somewhereelsestudio6342 Very good point. The feeling of having extra grunt unused can be somewhat annoying sometimes. I am one of those who accepted high 20s in the G2, so for me to be satisfied probably takes less than it does for you. But the settings I use now pretty much allow me to fly a fighter between the skyscrapers in NY with all high/ultra, even clouds. But I know for a fact that I'm missing out on even greater results when in less demanding scenarios. I',m using the Crystal, so that makes up for a lot for it regardless. The clarity is amazing. I will definitely try the software out tomorrow 👍

@@poolhallshark re: "The feeling of having extra grunt unused can be somewhat annoying sometimes." If you had asked me about this in the early days of MSFS2020, I would have denied it. But after tweaking on settings for over 3 years, I suppose the "quest for the perfect setup" is now taking over. It has become a lifestyle.

@@somewhereelsestudio6342 Indeed 😅

I had over 80 this morning with TLOD at 150, 30% supersampling (2500x2100) into a Quest 3 this morning. So we're close. :)

​@@somewhereelsestudio6342which HW do you use? And much more interesting what linking SW do you use? I got a quest 2 and have horrible stutters likely due to linking SW

@@Alexander-hk5keYou lost me. I don't know what HW is ... or what linking SW is.

@@Alexander-hk5ke I replied to this hours ago but it's not showing up. I don't know what you mean by HW and linking SW. Please explain. Could you be referring to HardWare and SoftWare? I have a Quest 3 and use the link cable. If you mean something different.. I'll try to answer once I know what HW and SW mean. Also, It's important to realize that stutters are generated by lots of different things. .. and at no time have I ever claimed that this eliminates stuttering. It's true that almost everyone who uses it (and has reviewed it) reports a dramatic decrease in stutters, but in reality, there are causes for stutters that I have no control over. It's designed to automatically adjust graphics within the limitations of your hardware. So the bottom line is: If you set unreasonable expectations of a tool like this, it's going to disappoint ya. :) For instance if you never got more than 30 FPS on medium settings, but you installed SmoothFlight and cranked up your options to "ultra" and then demanded 65 FPS, it's going to get ugly. That's an extreme example, but I want to reiterate that the best setup advice I can give is this: Leave your system options alone and setting a reasonable FPS that your system can hit - - and you'll probably be in the ballpark.

I do try :D

​@@VRFlightSimGuy Good evening, I just tried this application in VR mode and for me it changes absolutely nothing, I don't see any difference in terms of increase in fps!!!

100%

@@VRFlightSimGuy ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-s8TOeU2vEiw.htmlsi=CM0EbO797QkNIhuf

Thankyou :)

Video coming very soon!

My best advice would be to set some reasonable limits. The worst thing you can do is set FPS to 90 and TLOD maximum to 400. This will NOT give your video card superpowers and magically give you the ability to run everything on Ultra. So, try this as a starting point. Look at what you currently have your Terrain LOD and Object LOD set to. Set the TLOD max limit and OLOD Max limit to the same numbers. Then set FPS to a value that's a bit lower than what you can normally hit. Set Deadzone to 3 or 4 FPS higher than FPS minimum. This will give you a comfortable zone where no changes are necessary. Then go fly. You should have some room to auto-adjust to varying conditions whether that's higher or lower. Edit for clarification: Some are still confused to the real function of the FPS setting. It does not limit your FPS. It''s merely a directive to SmoothFlight that says: "Please don't let FPS fall below THIS". It's very common for me to have my FPS set to 40 and my actual FPS to be fluctuating between 70 and 80. This is where SmoothFlight really shines. Sometimes I'll just head for a large city and dial up a blizzard to watch SmoothFlight handle it. I can hear it faintly say: "Is that all you got? "

Thankyou :) Best to use one or the other, I prefer smooth flight so far as I really like the fps smoothing feature. Best wishes.

There is a checkbox on the left side of the screen for VR. Uncheck that box, and it will change the settings in 2-D mode. It does not have to be started before the sim. You can indeed launch the sim first, fly around for an hour, and then launch it. It doesn't really care. The only limitation is a timer that waits for about 30 seconds to see if it can find MSFS running. So I generally just wait until I have the sim up and running first.

Thankyou for the tip, it used to be the other way around. I'll give this a try now 👍

Use only one. Try them both :)

thanks. Appreciated :) @@VRFlightSimGuy

No need to pause, changes can be made on the fly. The trick is getting to where you can interract with the app while in VR. I manage this by bringing the app into the VR world, and then use the standard Alt-Tab windows shortcut keystroke to bring the app into focus... or some would call it the foreground app. I know this is very klunky, and hopefully a better way will present itself. But functionally there is no reason to pause.

I know I'm not Steve, but locking the frame rate at half native resolution doesn't give Smooth Flight any information to work with. So no, Smooth Flight is designed to run with motion reprojection or ASW turned off. The good news though is that the resulting smoothness can be even better than what you get with a locked frame rate.... Between that and the fact that you have eliminated all of the ASW artifacts, you might just like it better.

I'm still not Steve, and I do hope he replies still but.... if your computer can consistently give you 45 FPS so that lock mode works, then I would set it for 40 in SF. And then I would set the dead zone to three or four, and I would go for a flight. At some point in the future you can go back into settings and turn down your upper limits for the lods to get a higher frame rate..... but for your first test flight you can certainly start with those two settings. This assumes of course that you have shut off ASW or lock mode and are allowing the Sim to report the actual FPS it's able to get

It used to make a difference to performance, but that was pre SU13 - So I'll try it on ultra many thanks.

Absolutely! 😁

Heathrow airport and NYC

But this is no sense because Frame generation brake vsync? No?

It's awfully kludgy - as I don't know how to get a user interface to show up on the in-game ribbon menu... but here's how I've been doing it: First I get all my windows set up and the in-game windows placed where I want them. I don't know how everyone else does it, but I guess we all end up in the same place. But basically, do your normal method to get the SmoothFlight window into the VR space with you. Just before you launch VR, Alt-Tab to the SmoothFlight app by holding the Alt button down and tap Tab until the app is highlighted: then release Alt key. Then one more Alt-tab to go back to MSFS . Because of the default way Microsoft windows works (and has since W95) your most recent 2 windows will always be the default windows to focus. While in VR, you can alt-tab again and it will bring the SmoothFlight app into focus. Alt-tab again to go back to MSFS. I mapped alt-tab to a button on my StreamDeck so I don't have to fumble around to find the keyboard in VR. So yea, it's a bit of a kludgy workaround for now. But it lets me make changes while flying without leaving VR. To be fair though, the main focus of SmoothFlight is that you find your settings and then leave it alone. So hopefully you'll adopt that workflow soon and this will be a non-issue.

@somewhereelsestudio6342 Cool. I will give it a try. To be honest, I was hoping you had some clever way to bring Windows apps into VR. 🙂 I wrote an in-game popup for my app (rsFirstOfficer) but it seems to cause stutters so I don't promote that feature. Thanks for all your efforts on this handy tool.

Nope, they cannot work together. Even though the internal processes are unique, they both modify the exact same parameters in the sim...and as such will just fight against each other with unpredictable results. Umm.. not sure how to answer the next question as DLSS is an upscaling technology and frame generation is another thing entirely. But I think the best way to answer this is that it works just fine with upscaling. It does not work with frame generation... unless the frame generation reports a useful FPS. All of the frame Gen tech I've tried just reports a static number (either half-rate or full rate) and therefore is useless. But if your computer can play the game at half-native rate (36/40/45), just turn it off and see what it looks like. This has the uncanny capability of making 45 FPS look much smoother than the raw numbers indicate.

@@somewhereelsestudio6342 It seems to interfere with the Turbo mode in the XR Toolkit, whereas sometimes I can see the effects of turbo mode fps increase (in the 60's) for a time and then it drops down to half refresh at 36 for awhile...can you verify if this is normal behavior or not?...Not sure if i should use this with the XR toolkit currently. Also I have no understanding of how to get the UI visible in the cockpit when in VR...any idea? Thank you for this btw, I may be able to come back to msfs because of this!!

I know right! Crazy how these two addons were released so close together. I use TAA as it's the best image quality setting :)

@@VRFlightSimGuy OK thanks I’ll have to do some more comparisons

In this current iteration, the SmoothFlight tool is designed to work without motion reprojection only. With ASW or MR, the sim continually reports that it is always at half-native-framerate. So without accurate FPS data coming from the sim, SmoothFlight cannot accurately assist.

Understood; the plan was to try it with no MR anyways, thanks.@@somewhereelsestudio6342

So you are auto-varying 3 settings based on the UI window= TLOD, OLOD and RA. What is RA? By the way too; I don't know why on my PC but the utility was accurately picking up the correct Motion Reprojection FPS and was adjusting the 3 variable settings as I flew just fine. So also tried in non MR as well, was auto-correcting in the same fashion in both modes just fine.@@somewhereelsestudio6342

@@somewhereelsestudio6342Is that also the case when enabling MR in ToolkitXR and not in FS2020 itself?

@@MrEDETGood question. Because of the way that all reprojection technologies work, I think they'll all be problematic. Because my experience with them is that they either will report 45 FPS or 90. (assuming this is on a headset that's set to 90hz refresh) . The most important part of this is that no matter which one they report, it will never change. And watching that number change is how SmoothFlight works. So if you MUST use reprojection, then maybe a different solution is better for you. But in my testing, as long as I can set the minimum FPS to 38 or higher, I can have a successful result. YMMV of course... and that's why we pre-release these types of tools so we can get a better handle on what works (hopefully the vast majority of it) and what doesn't.

Re-install? That's a bit overly dramatic. The only things that are changed are your Terrain LOD and Object LOD. And it doesn't change it in the files. It only changes the copy of the program while it's in memory and running on your PC. You can easily go back into your settings menu and drag the slider to the desired value. That's the extent of what is changed. I'll make sure this is implemented for my next update. In the meantime, please accept my apology for not including it in this admittedly early access release.

With AutoFPS, you can quickly change your TLOD Min to be higher and even a higher Alt TLOD Base if you want for such flights.

I can hardly keep up mate, not that I'm complaining :D

Give it a try. It costs nothing. And you might find that the equally-spaced frames are actually smoother looking than what you get with motion reprojection technologies.... so it's worth a shot.

I'm going to do that today and will post video

I've yet to try it using ASW, give it a go and let us know 👍

If you run any version of ASW, the sim will report that you're currently getting 45 FPS. (or half of your native refresh rate) If you set the threshold of SmoothFlight lower than that, it will keep turning up your eye candy until you have a slideshow. If you set it higher than 45, it will constantly turn down your graphics until it looks horrible. So no, ASW is assumed to be discarded with this tool. It requires the sim to tell the truth. ASW is not truth. :)

Yes. Higher FPS is not always good for VR. Try and match half of your refresh rate

Yes 👍

You might have been asking Steve directly this question...but in case you're open to a 3rd party opinion, I think a re-install is a bit excessive. Years of tweaking settings don't accumulate or create some sort of pollution. At least I see no evidence of that. If you installed through Steam, you could do the "Verify Integrity of installed files" option which would only update the files that the compare would deem necessary.

@@somewhereelsestudio6342 Hi and thanks for the reply, this reply was open to anyone. I am still considering a re-build, problem is with windows... everytime you install & un-install an app it leaves junk particularly in the registry some apps leave hundreds of unused bits of junk. As the registry gets bigger and bigger it slows the system down a bit. You never know your system is clear until you complete a clean build. And then you start to add apps and the hole thing starts over again PS good point about checking with steam.

It would have been so much easier if they had just implemented it inside the box. It's quite a trick to get this to work using an outside application. Imagine how slick it would be if it was embedded??

DX11 for TAA, DX12 for DLSS 👍

@@VRFlightSimGuyThanks! I don't like DLSS. With TAA I have 40+ fps with my Aero and 3090. Want to try the sim beta if you say there is some performance increase.

​@@VRFlightSimGuy Hello, why don't you use the NVIDIA DLSS anti-aliasing in the VR menu for precisely the NVIDIA RTX graphics cards because I tried it and I always have a constant 45 fps and with OpenXR I increase the resolution of the headset and it works perfectly ! whether it's my hp reverb g2 v 2 headset or the pico 4!