Benrb7

Ditto! https://ibb.co/W4xK1Tm9

The cost for the crystal OG with the headphones and an extra face gasket in very good condition off eBay was £500. The super was going to be another £700 on top of that plus getting it delivered would take some time. They've also just released the OLED panel super which adds more cost and something slightly better but I try and get the best bang for buck. Obviously the crystal light doesn't have eye tracking, very happy with the setup now as it is runs well and gives the decent clarity.

I've found you’re always balancing GPU processing power against the sheer number of pixels you’re pushing depending on the VR headset and after a while it can get very costly. I’ve been through a similar upgrade path: 3080 → 4090 → now 5090, and on the headset side Quest 2 → Reverb G2 (which sadly died) → Quest 3, and I’ve now settled on the Pimax Crystal OG. Headset Per-Eye Resolution Total Resolution (Both Eyes) Quest 2 1832 × 1920 ~7.0 million pixels Quest 3 2064 × 2208 ~9.1 million pixels Reverb G2 2160 × 2160 ~9.3 million pixels Crystal OG 2880 × 2880 ~16.5 million pixels Crystal Super 3840 × 3840 ~29.5 million pixels Coupled with a 14700k z790 MSI board and luckily got 96gb DDR5 Ram in Sept for £170, it's now over £700.. I’ve still got the Quest 3 and a 3S, but they mostly come out when family are round for games like virtual golf. The eye tracking and foveated rendering on the Crystal really help in MSFS 2020, which is still a bit heavier on the PC overall, and it also works very well in MSFS 2024. It does have the odd moment where I need to restart services, but generally it’s been very solid. I've got used to the weight and size of it now. 🤣 I did think about the new super, but you need a new card for that to run at full capacity (going from 16.5 to 29.5 million pixels, or reduce quality), again playing the costly upgrade path. Kind of settled with this now. I don't take anything too seriously though, here's me smashing a 737 down into EGLC on the Pimax. For flying though, the Crystal OG has set a new bar for me.

I'll be following this thread Even the SU4 - Public Beta 2 release is a no go at night the sky goes really weird. Waiting for the fix. :)

I still have a copy of the latest for 2020 which works fine Zip can be downloaded here if anyone wants to use it 🙂 Alternative link here.

Fair comment, but at only marginal steps it's going to be less obvious, I've adjusted with fewer steps to give that a go: Code adjusted is <add key="tlodPairs0" value="0:50|250:75|750:100|1250:125|1750:150|2250:175|2750:200" /> <add key="olodPairs0" value="0:100|500:90|1000:80|1500:70|2000:60|2500:50" />

Ok noted thanks, I didn't notice and stutters or issues in my first flight. As with most things FS related I will trial and error, changing levels drastically also likely to mean it's more obvious with the visible changes around you popping in and out. I am sure there is a compromise that could be reached, I am also thinking of alternating the height at which TLOD and OLOD happens to avoid stuff happening at the same time, i.e. TLOD OLOD 250ft 500ft 750ft 1000ft 1250ft 1500ft

Got it set up and working in VR with a reverb G2 and 14700k/4090. Using these settings from a post I found someone else made. First flight in Cessna out of EGLC very smooth. The config is in the following location if you wanted to back it up to edit change the extension to a text file; C:\Users\YOURUSERNAME\AppData\Roaming\DynamicLOD Once done you can quickly change the above adding the below two lines highlighted, which saves some time manually adding each one: <add key="tlodPairs0" value="0:50|200:55|400:60|600:63|800:65|1000:70|1200:75|1400:80|1600:85|1800:90|2000:95|2200:100|2400:105|2600:110|2800:115|3000:120|3200:125|3400:130|3600:135" /> <add key="olodPairs0" value="0:100|150:70|250:65|350:60|450:55|550:50|650:45|850:40|1050:35|1250:30|1550:25|1750:20|1950:15|2150:10" />