turbomax

you must mean some msfs related forum ...? 😀

my wife loves it, now she doesn't have to bother me any more with household/kitchen/fashion/furniture etc. issues any longer. "don't know much about history..." but I do know that I love you, MSFS. what a wonderful AI world this will be.😁

hasn't happened to me for years. but then, I use Addons-Linker, should be part of the MSFS platform, even P3D had a scenery library manager built in ...😀

nobody said it was. it just got downgraded back to the older v310.4, as usual after each MSFS update. I thought that was clear by now. had to use DLSS swapper to bring it back to latest v310.6

and by now we know what that means to DLSS 😀

there are magnetic lens inserts for the Pimax Dream Air, easy to remove and re-insert. RTX 5080 has only 16 GB VRAM, not much considering: Standard 4K screen = ~8.3 million pixels This headset = ~3.5× a 4K display rendered in real time, ca. 30 million pixel And that’s before distortion correction + super sampling (which can push it even higher internally) ........................ "I reckon a new, modern CPU, a fast motherboard and 64GB of RAM on top of that won’t cost all that much. " "only" some $ 2.000 + $ 2.000 for a modern VR headset

good idea, but as you know you'll have to spend some $/€ 3.000 - 5.000 I would think twice before purchasing the bulky Pimax Ultra Wide, and get the lightweight and newer Pimax DreamAir instead. there are some detailed reviewes by MRTV VR on youtube

only if you told it so, but it doesn't do that magically, behind the scenes without you setting the slider in the NVidia app to OPTIMIZE. it had me confused though since I had forgotten that a while ago I had the usercfg.opt file write protected so that neither the NVidia app nor MSFS 5 beta would touch my settings, which during the beta it did, without NVidia's interfering. you could also keep several versions of usercfg.opt with different names (this is what I am doing now). that should be a feature of the MSFS architecture from day 1, let the user keep and choose between several configurations.

you could also make the usercfg.opt file write protected, then settings couldn't get changed, even if you tried to change them manuallly in the SETTINGS UserInterface, they will stay the same.

that's why I DID install and use Nvidia app to make use of SmoothMotion and other nice to have features, I just don't let it "optimise" which you would have to actively execute, it doesn't do that without user input all by itself.

not without a major CPU upgrade.Think of it like: You bought an 8K cinema camera… but your PC can only edit in 1080p here is what AI had to say, and I would agree (I have a higher spec CPU and lower resolution Pimax than you, getting typically 60-70 fps in VR). you would run out of VR memory at only 16 GB VRAM and 73% higher resolution, meaning you will have to reduce everything which makes the Ultra Wide obsolete. I would prefer the upcoming Steam Frame VR or high end: Pimax Crystal DreamAir --------------------------------------------- What resolution you’re actually trying to run Even though it’s listed as: 3840 × 3840 per eye In practice (VR rendering overhead + distortion correction), your GPU is often pushing something closer to: 👉 ~4500 × 4500 per eye (or more) 👉 That’s ~40–45 million pixels per frame total For comparison: 4K monitor = ~8.3 million pixels Your headset = ~5× heavier than 4K ⚠️ Reality check for your setup (RTX 5080 + i9-900K) ❌ Native / full resolution Not happening in MSFS 2024. Even an RTX 5090 struggles here You will be GPU-limited AND CPU-limited Expect unplayable frame rates if you try full res + high settings ⚠️ CPU bottleneck (this is big) Your i9-900K (likely 9900K) will: choke in airports struggle with glass cockpits limit frame generation effectiveness 👉 In VR, CPU limits hurt more because: frame pacing matters more than raw FPS stutters = very noticeable 🎯 What you can realistically expect ✔️ Playable setup (with tuning) If you optimize properly: Resolution scale: 50–70% DLSS: Performance / Balanced Settings: Medium–High mix Frame Generation: ON 👉 You’ll get: ~30–50 FPS (with reprojection / smoothing) decent clarity, but not “full Pimax potential” ❌ What you won’t get Native resolution clarity Ultra settings everywhere Smooth performance in big airports “Maxed out sim” experience 🧠 The key bottlenecks (ranked) CPU (biggest problem) GPU (still very stressed) VRAM (16GB can get tight in MSFS 2024 VR) 🔧 What would unlock the headset To actually use the Crystal Super Ultra-Wide properly in MSFS: Minimum “serious VR” target: CPU: modern high-end (e.g., X3D Ryzen) GPU: RTX 5080 is OK, but 5090-class ideal Aggressive DLSS + foveated rendering 🧾 Honest verdict 👉 Your system is: ✔️ enough to run MSFS 2024 in this headset ❌ not enough to take advantage of it Think of it like: You bought an 8K cinema camera… but your PC can only edit in 1080p 🧠 Practical advice If you’re sticking with this hardware: Lower resolution scale (this matters most) Use eye-tracked foveated rendering (if available) Reduce: terrain LOD traffic glass cockpit refresh rate

IPD adjustment is not the same as IPD offset adjustment.

me too, they have to be very specific for the Pimax, not the same value as your normal reading glasses. https://vroptician.com/prescription-lens-inserts/pimax-crystal-light "Far distance prescription (from your everyday glasses – we'll adjust your prescription for the headset's focus distance)"

here: or what I usually do: AI On the Pimax Crystal Light, there are two different things people mix up: Physical IPD → moves the lenses IPD offset (software) → shifts the image per eye for fine alignment You’re asking about the offset, which is the software tweak—here’s how to actually adjust it. 🧭 Where to adjust IPD offset You do it inside Pimax Play (or older PiTool): Open Pimax Play Go to Device Settings → IPD / Advanced Find: Horizontal IPD Offset Vertical IPD Offset Adjust sliders (usually per eye: left/right) That’s the only place—there’s no physical “offset” control on the headset. ⚙️ What the offsets actually do Horizontal offset → shifts image left/right per eye Vertical offset → shifts image up/down per eye They don’t move lenses—just the rendered image. This helps if your eyes aren’t perfectly symmetrical or the headset fit isn’t perfect. (Pimax Store) 🎯 How to tune it properly (practical method) Step-by-step: Set your physical IPD first Use the headset dial/wheel until image is sharp (Crystal Light uses a manual dial on the headset) (Pimax Support) Look at a distant object in VR Horizon, stars, UI crosshair—anything far away works best Adjust horizontal offset Move slider slowly Goal: both eyes “merge” perfectly (no double image) Stop when: image feels centered no eye strain Adjust vertical offset (if needed) Fix blur where top/bottom looks off Even tiny changes matter (±0.5 mm can be noticeable) Re-check comfort You should feel: no eye strain stable depth clear center image ⚠️ Important tips (most people miss these) Fit matters as much as settings If the headset sits wrong, offsets won’t fix it (Pimax Store) Use small adjustments Offsets are fine tuning, not big corrections Don’t skip physical IPD first Offset cannot fix badly set lens distance Check during real use (games/sims) Menus can look fine while gameplay still feels off 🧠 Quick rule of thumb Double vision → adjust horizontal offset Blur top/bottom → adjust vertical offset General blur → fix physical IPD or headset position first If you want, tell me what you’re seeing (e.g., “one eye blurry,” “cross-eyed feeling,” “far objects double”), and I can give you exact offset directions (+/- values) to try.

with totally smooth over 70 fps in VR (roughly 5760 × 2880 total rendered pixels, about 17 million), I see no need for a RTX 5090. 73 fps screenshot taken in VR on Pimax Crystal Light:

no more crashes for me switching back and forth between 3D to 2D since the latest beta 5 update: 1.7.22.0, perhaps because of: "Improved the way the game switches in virtual reality to avoid excessive memory usage."

low quality for a low price. you get what you pay for. perhaps for someone totally $$ budget limited. PS5 + VR2 price is similar to current price of 64 GB DRAM for pc alone. 😀

switching back and forth between 2D and VR didn't crash anymore, that's new 😀 perhaps thanks to: "Improved the way the game switches in virtual reality to avoid excessive memory usage." with totally smooth over 70 fps in VR (roughly 5760 × 2880 total rendered pixels, about 17 million), I see no need for a RTX 5090. but still: "Descend and maintain minus 1.000" farewell Beechcraft N6062B

just got MSFS 2024 beta 5 update 1.7.22.0 https://forums.flightsimulator.com/t/sim-update-5-beta-1-7-22-0-release-notes-april-21-2026/763449 RELEASE NOTES Sim Update 5 Beta - 1.7.22.0 Stability & Performance Improved the way the game switches in virtual reality to avoid excessive memory usage. General Bug Fixes Fixed an issue preventing the use of WASM DLC aircraft on Xbox. Career General Bug Fixes Fixed Acknowledge reach altitude step after a skip to descent SDK Fixed Event API regression. ......................................................... nothing much to write home about for me, except this one, I will write home immediately: 😀 Improved the way the game switches in virtual reality to avoid excessive memory usage. .............. at home they just wrote back I had to run DLSS swapper (DLL v310.6), again!

Oops! That page can’t be found. Nothing was found at this location. Try searching, or check out the links below.

that's a known fact and why I always insert only 2 banks of DIMMs. 2 x 32 GB in my case.

in his post? "the more data you have in the fastest possible storage component, the better for performance." "it should however reduce long frame frequency so one's FPS will be a bit more consistent." if that was true, 256 GB would be even better. but it isn't, because the CPU obvioulsy can re-load fast enough in the background from just 32 GB DRAM main memory with no fps penalty. at least that's what Asbobo said. and I have yet to see any benchmark that shows how 64 GB and more has improved performance noticeably.

and where exactly do you show a direct relationship between more RAM results in more fps? the fact that MSFS can use and pre-load stuff into main memory upto 42 GB is not proof that this makes the sim run smoother. especially not when using CPU's that have lots of cache, which is many times faster than main DRAM.

I hope they find ways where we have a lot of coast... 😀

and the single one user who has 96 GB said it was even better 😀 hasn't provided a single benchmark screenhot showing increased fps or more constant frametimes though.