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.

I think it's worth mentioning that I just released a massive MSFS Vancouver Island scenery that is purely geared for helicopter pilots (ans seaplane pilots to some degree). It has 4 hospitals with helipads, 6 heliports, including Coast Guard, and some exotic helipads: cruise ship, Coast Guard ship, private yacht and a private mansion with a breathtaking view. It even has 3 car accident scenes to discover, for simulating medevac.

In my case I made my own controllers are a part of the motion rig I built. They convert between several configurations: pendulum yoke + throttles; joystick + HOTAS; cyclic + collective. The yoke/joystick/cyclic part is built with hall sensors so has no friction, is very precise and has large throws. Controls are powered bu Arduino Leonardo cards. You can see my test video of the controls below. I think it's worth mentioning that I just released a massive MSFS Vancouver Island scenery that is purely geared for helicopter pilots (ans seaplane pilots to some degree). It has 4 hospitals with helipads, 6 heliports, including Coast Guard, and some exotic helipads: cruise ship, Coast Guard ship, private yacht and a private mansion with a breathtaking view. It even has 3 car accident scenes to discover, for simulating medevac. The video is shot at my CYOW Ottawa airport BTW. I should do something at my newly released Vancouver Island...

Now also available at ORBX Direct

I’m proud to announce the release of Vancouver Island Heliports and Seaplane Bases Pack! Available at Roman Design website. Coming soon to MSFS Marketplace Coming soon to ORBX Direct Audiobook Giveaway: If you share a link to Vancouver Island scenery at your social media - just send me the link and get a free sci-fi audiobook (written by yours truly) until promo codes run out. First 3 will get the Progress Report novel and the next 15 will get The Little Blue Log Book novelette via free codes redeemable at US/UK Audible. Welcome to helicopter and seaplane heaven! Vancouver Island offers a unique combination of breathtaking remote landscapes and urban photogrammetry areas in a relatively compact area. As your helicopter or seaplane glides over the rugged coastline, you’ll be enchanted by dramatic cliffs plunging into crystalline waters, secluded coves cradling pristine beaches, and ancient rainforests whispering tales of timeless beauty. Vancouver Island Heliports and Seaplane Bases pack provides a unique scenery for creative MSFS pilots. Your imagination is the only limit! Simulate patient transfers between 4 hand-modelled hospitals with medical heliports, perform medevac flights from a cruise ship, or locate and rescue injured victims from 3 car accident scenes along remote roads. Fly Coast Guard, government and private flights between 6 heliports, including the Coast Guard and Port facilities, a working lighthouse at the Race Rocks Ecological Reserve, and a Coast Guard ship you can land on. Fly VIP passengers or imagine yourself piloting your helicopter from your yacht to a sprawling mansion with a helipad, built on the top of the hill overlooking a majestic lake. Plan picturesque flights in your float plane between 4 modelled water aerodromes and seaplane bases. All locations are hand-modelled in intricate detail, including key buildings textured with custom-made PBR materials in up to 4K resolution, parallax interiors, lighting and animation elements, ground signs and textures, night lighting, and hundreds of objects placed throughout the scenery. Compatible with Roman Design CYYJ Victoria International Airport and SamScene3D Vancouver City Times. HOSPITALS CBK8 – Royal Jubilee Hospital Heliport CBW7 – Victoria General Hospital Heliport CAT6 – Campbell River Hospital Heliport CVB8 – Comox Valley Hospital Heliport HELIPORTS AND HELIPADS CBR7 – Tofino Lifeboat Station Heliport CBZ7 – Victoria Harbour Shoal Point Heliport (Coast Guard) CBF7 – Victoria Harbour Camel Point Heliport (HeliJet operations) CDH5 – Nanaimo Harbour Heliport (HeliJet operations) CR03 – Race Rocks Lighthouse Heliport CR05 – Coast Guard Ship Helipad PRIVATE HELIPADS CR01 – Willis Point Mansion (NW of Victoria) CR02 – Cruise Ship Helipad CR04 – Yacht Helipad WATER AERODROMES AND SEAPLANE BASES CAB4 – Tofino Harbour Water Aerodrome CAC8 – Nanaimo Harbour Water Aerodrome CAE9 – Bamfield Seaplane Base CAN3 – Ucluelet Water Aerodrome CAR ACCIDENT SCENES Follow the Trans-Canada Highway (Hwy1) North from Victoria to Mill Bay Follow the Trans-Canada Highway (Hwy1) from Duncan to Nanaimo Follow the local road from Tofino to Ucluele FEATURES Custom PBR materials with up to 4K resolution 4 Hospitals 6 Heliports and multiple Helipads 3 Private Helipads 4 Water Aerodromes and Seaplane Bases 3 car accident scenes Animated lighthouse with rotating beacon and light beams Animated Ambulance flashing lights Parallax windows on all buildings with reflective glass and night lighting, based on multiple custom office, residential and hospital 3D room interior renderings Signs with emulated fluorescent night backlighting, 3D modelled letter-shaped signs, and other custom signage throughout the pack Custom night lighting throughout the scenery Hundreds of objects placed throughout the scenery to create an immersive experience Animated flags that respond to wind direction Here are some screenshots of the various scenery locations:

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?

I'm not criticizing the readme, or you, please don't take it personally. You are doing an amazing job and helping the community a great deal. I'm just trying to figure out if this program can help me and what the correct settings would be for my setup. Yes, I'm acknowledging that "warned that MR can break", it's not like you promised it must work 🙂But it doesn't say that it can't work with MR, so I'm trying to make it work if that is possible. The problem is two-fold: 1. It's a fact that letting FPS go lower than half of the refrash rate brakes MR. The goal is to try and manage the LOD/clouds so it doesn't happen, or catch it the moment it does. Some people seem to be more sensitive to judder than others and while many are fine without MR, many others (like me) can't live without it as it's just not smooth. 5% is something that was mentioned here. I'm aiming for minimal workable reduction. It looks to me that setting a target FPS of 10% less, i.e. 36 wouldn't work, because my system in KJFK in PMDG737 (oribably worst case scenario) is doing 37FPS, so it would be "fine" according to the Auto FPS software, while it's a horrible experience in VR. If it would just keep it at 36 it's not a solution. Ideally I'd set 40FPS, but the readme says that it needs some overhead, and it makes sense. But I want as small an overhead as possible, as even 39FPS is not desireable and should be avoided as soon as it occures. 2. How would it know what level to keep the LOD at, because it won't ever go above 40FPS with MR? MSFS is so fidgety and unreliable that it's very difficult to do a clean test - if MR brakes with Auto FPS it would certainly brake without it. That's why I'm asking questions on what settings would make sense with MR. Is it not supposed to work with MR at all and I shouldn't even try?

I'm trying to understand the app logic. Readme didn't do it for me 🙂 So, suppose I'm in VR with SSW (VD motion reprojection) with Quest 3 running at 80Hz. So the FPS is capped at 40. I set 38 in Auto FPS, which is 5% lower. So, let's say the performance dips momentarily below 38 (which is already bad as it's braking MR), and Auto FPS drops TLOD to my min of 30 from normal setting of 100. FPS recovers to 40, but it's going to stay there as it is a hard cap. So how AutoFPS will know when to bump up the TLOD back? There's no overhead to "shave off" by gradually reducing TLOD. And as soon as it dips - it breaks MR. So will it just constantly try to lower and raise TLOD all the time? I don't think this is what happened when I tried it yesterday. Can it actually stay ahead of it and keep TLOD lower until it's not limiting anymore. But then how does it know when to bump it up again, without doing it too often to cause stutters?

I don't have Varjo, but AFAIK what you're doing is setting a target FPS to 90, but then hard-limiting it to 30. That way AutoFPS can't ever reach the target and should just bump everything to minimums and keep it there. Also, MSFS reprojection is not the same as VR HMD reprojection and to my knowledge doesn't do anything with the framerate on any HMD. So that setup doesn't sound logical. If you hard-limiting FPS to 30 in the Verjo, then the target sould be set to slighly below 30, as far as I understand the concept. Things may be different with Varjo, but should not be that different.

I actually read both readme files for both apps before posting. It's generalized for all FPS caps (FPS about 10% less than cap) and basically says "if it breaks motion reprojection for you - this app is not for you". But I was wondering about people's actual experience with it. In theory, going anywhere below 45 FPS (with 90Hz) will break motion reprojection (I had G2 prior to Quest 3) and create some judder or tearing. But people seem happy with VR and this app, including you I assume. I suspect that the actual setting for the FPS, and chosing the right app from the two can be very important, and a couple of FPS can make or brake the whole thing. So I was wondering what people are using with Quest 3 and VDXR, how close they get (someone mentioned 5% and not 10%) to the cap etc. If would be nice to know what works for VR users, because most seem to use pancake mode.

What should be the settings for VR with Motion Reprojection on? - Is AutoFPS or DynamicLOD_Reset more appropriate for VR with MR on? - What should be the FPS target? In VR, maintaining the target FPS is key, and MR is a must for most users (me included) for smooth experience. But the problem is that it essentially caps framerate at 45 (in case of 90Hz refresh) or 40 (80 Hz) or 36 (72Hz). So how would AutoFPS know that it's time to increase FPS if they would never go above that value? Also, would it be too late correcting the problem when FPS fall below 45 - because when it happens there would already be stutters in VR. This makes it far from clear what target FPS to set. So what are the recommended settings for this? If it matters, I have Quest 3 + Virtual Desktop (god mode, VDXR), RTX 4090, 7950X3D, 64Gb DDR5 RAM.