@risa2000 Even 1ms vs 2ms can be enough. The margins can be astonishingly thin for many use cases.
Yes, performance is entirely tied to load factor. Load factor is total rendered pixels rendered, times framerate and such, in proposed config up top, divided by what is put in as a tested config at bottom. Less than 1, fewer pixels are being rendered than you have tested, so PASS/FAIL.
Supersampling, Framerate, Parallel Projections, and anything else I can derive a hard number for, goes into the Load factor.
FOV, due to distortion correction and other possibilities, would require a guesstimated arbitrary penalty to incorporate into the load factor as PASS/FAIL, so it’s just a bit complex to automate for now.
Ideally, test data should be from a Normal FOV headset like the Pimax 5k+. However, when the tested FOV is narrow, the proposed FOV is wide, a 0.5 load factor would theoretically be the PASS/FAIL point (because, half as many pixels). However, I say maybe 0.4 load factor should be considered PASS/FAIL in this case, due to … distortion correction etc.
The stuff below the VR rendering about hardware… all I need was the CPU/GPU. Your GPU is already the same type as mine, about 200MHz lower clock, so 90% on all metrics there. Your CPU is about 90% of mine.
Thanks to that last bit of info, I can confirm you should just be able to use my settings for the Pimax Vision 8kX, minimal tweaking required.
However, you should download the overclocking tool for your GPU. It will probably run at 1925MHz core clock or thereabouts, about 100MHz more than what you have now, and 100Mhz less than mine.
Some wierd stuff also needs more VRAM, like setting textures to max on DCS World so the kneeboard on the pilot is readable.
You should probably NOT upgrade your GPU until more is known about the NVIDIA 3000 series.