Roman Design

New demo video that includes the temp monitor: And a full flight video:

Thank you, much appreciated! And thank you for a great app. I don't know what expectations people have - you're not a magician, you can't do miracles. However, this app immensely improved my experience in MSFS2020 because it was the final push I needed for smooth performance. It will do the same job in MSFS2024, I'm already seeing it working. Will it be enough? It seems to be enough for early career mode, but we'll see if the performance will hold in an acceptable range in an airliner at a busy custom airport. The only stutters I see are occasional freezes of the sim that happen with or without your app - so they aren't performance related but maybe scenery loading or network glitches. But whatever happens - your app helps and does exactly what is expected of it, and what MSFS should have been doing natively but doesn't.

Hi, I'm configuring my system again with MSFS2024. I used AutoFPS before in MSFS202 but the settings have changed since, both in the app and on my side. So what are the recommended settings now for Quest3 + Virtual Display + ASW "always on" @80Hz? I'm not sure what to use with motion projection to maintain solid 40fps but still have AutoFPS reduce LOD when needed, and clouds too. I'd appreciate some advise.

UPDATE: The detailed 6DOF Motion Simulator Design and Build Plans for my 6DOF Motion Simulator are now available on my website. Having a Full Motion VR Cockpit for under $1000 is not a dream - it's a (virtual) reality and it feels amazing!

You'd just have to construct a cat-proof cover for the motors. Similar to what DOFReality has as an option.

After enjoying my ultra-low-budget 2DOF Motion Simulator for 3 years I decided to build a budget 6DOF Motion Simulator. The jump from a static VR cockpit to a moving motion rig was as much of an immersion leap as from flatscreen to VR, if not more. Upgrading from 2DOF to 6DOF is even more awesome! As a matter of fact, It’s an absolutely mind-blowing level of awesome! The immersion is complete. There are some minor issues to iron out and tweak, but I can say that it’s so worth it. I was worried about cogging, but I couldn’t even feel it during the flight because there was so much motion going on all the time. The motors heat up to ~46C max with new settings (lower PWMmax, added some derivative, slightly increased dead zone), then I adjusted the settings to yet lower PWMmax and they got even cooler. So I’m cautiously optimistic. Hopefully, they will hold on for longer flights. More testing is needed, but it really felt nice! I will adjust the FlyPT profile to near perfection and I’m set. Then I will proceed with a Joystick/HOTAS configuration and a racing configuration with a force feedback steering wheel and custom-made pedals and shifter. I’ve also reworked the encoder/button/switch boxes, custom pendular yoke and throttle quadrant. The build is an ultra-low budget, just like my 2DOF. The cheapest available off-the-shelf 6DOF motion platform costs around $8000 with shipping and some necessary options, and that is too much. I’ve built one for the cost of under $1000 in parts. I’m happy with how the 2DOF wooden frame held on, so I built the 6DOF frame from wood as well. The top platform is cut from a thick plywood I had lying around. The wood has its downsides, obviously, but it also has its upsides: it’s cheap, easy to work with and its natural flex makes the rig less jarring and clunky, which is a problem with many metal motion rigs, while still precise and fast enough.

Sorry, I don't know why it posted 3 times... I don't see the "delete post" option anywhere...

accidental multipost

Likewise! Correct, MR (SSW or ASW) is unavoidable to get 72Hz or 80Hz. I aim for 80Hz. I couldn't make link work well, maybe it's my cable. But VD works amazingly well for me. AV1 codec (Quest 3) with 130mbps bitrate gives me no noticeable latency (reported latency is in the 60s but I don't feel it). I see no compression artifacts whatsoever, the image is perfect. SSW was not impressive when the PC struggled, but now I don'e see the artifacts, none at all, though I hadn'e tried blue skyes for any length of time. I run RTSS locked at 41. Turbo = ON in OXRTK seems to be important for reducing stutters. Despite the warning of breaking MR, SSW still works fine. When I had Reverb G2 it did break MR. Can you share your AutoFPS settings, maybe a screenshot? I wonder what works for you and how it compares with mine (shared earlier)...

I literally have the top-of-the-line CPU: 7950X3D. However stuttering was always the largest problem for me, even with Reverb G2, and now Quest 3. Though Quest 3 is much smoother and the only problem I see is cockpit judder when looking side to side, but AutoFPS seems to help a lot here. It seems it needs some headrom to be smooth, even with solid FPS. I could always see great smooth FPS in between the stutters, and TLOD is clearly exacerbating stutters. And taxiing in busy airports was always iffy. So I though I'd set very low TLOD ont he ground (where it doesn't really matter) and put a reasonably good looking but as low as possible top limit, to create some breathing room for smooth flights. Stutterless flights are the top priority for me, and I'm very sensivie to stutters and judders. In VR the images is not as crisp as on a 4K monitor, so visuals still look very nice. Ultra clouds add much more to the visuals - but they do have a large CPU impact. Compared to Ultra, High clouds seem like detailless cotton balls. Anyway, the results are already great, thank you again for the app, it really makes it possible to have a steady and smooth flight. It's a shame we can't have it out of the box, and this would have been so easy to implement in MSFS natively, it's such a simple and effective concept! But I'm sure even if it's implemented natively, there won't be so many options to tune it, they would have to dumb it down.

I tried latest test version of AutoFPS with the following settings. Seems to be working, the flight was mostly smooth, but I had some slight stuttering @15,000 entering secont cloud layer, and it looked like the cloud level wasn't dropping from Ultra to High like it should. The visual difference betweek Ultra and High clouds is very noticeable. I couldn't easily check the app status, because I was in my motion rig in VR, and the app is on the screen to far to read without pausing everything, taking off VR and climbing out of the rig. Do these settings make sense for MR @40FPS, RTSS locked to 41?

I must have missed something... So does it mean AutoFPS should now be working properly in VR with MR on? I.e. if I set target FPS to 39 and lock at 40 will the logic work?

What exactly are your setting so the motion repro works with this software? I got the sister app working, but I'm curious if this one has any advantages, though the exact settings should be pretty important for it to operate well around the fixed FPS of MR without letting it go down to break MR.

Hold on, 80Hz with SSW ON means you're running on 40FPS. 120Hz would be 60HZ with SSW ON. I just asked in Discord and confirmed that VD can only do 1/2 divider, meaining there are no 1/3 or 1/4 locked motion reprojection. So both RTSS @80 and AutoFPS target of 76 are meaningless, it never gets there, not should it. Also, I never could run MSFS even at 60 stable in any airliner and vusy area anyway. VD displays 80 because that's it's streaming 40FPS and SSW is creating another 40 frames. It's confusing but it always shows the same FPS with SSW on or off, despite it halving the framerate. Try limiting RTSS to 40 or 41 FPS - in the AutoFPS app it should show 40, but VD would still show 80. If I understand correctly how things work, because of your target is not remotely achievable, AutoFPS would just nail down all settings to minimums, never raising LOD etc. above minimums. It would give you good performance, but it should be the same if you manually fix LOD to your min value etc. Maybe I'm not getting something, let me know if I'm wrong.

Ah, OK, thanks for the clear answer. The next question is, should the sister app work with MR? It would involve more quesswork, but should still help with FPS, right? If the LOD is at the minimum on the ground and gradually goes up, and cloud level changes if FPS dip below MR level, it sounds plausible, right? Or I shouldn't switch on anything related to FPS there are all, just the altitude-dependent changes?