-
Posts
124 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by Rufuz64
-
Exclude the core folder AND the Saved Games\DCS
-
It would certainly be helpful if you could provide some specs. VR glasses, VR programmes & mods There are various techniques that can be used to take screenshots. Which one did you use? DCS function, VR-software, 3rd party (which one)
-
After 250 ktn gear just wait with flaps half until the nose comes down. Same with flaps full. Same with trim up.
-
Dynamic Foveated Rendering - Everything in one page
Rufuz64 replied to mbucchia's topic in Virtual Reality
Uninstall is not enough. I had to reset to dafault and then uninstall! -
Update the DLSS preset used by DCS to remove ghosting
Rufuz64 replied to sleighzy's topic in General Bugs
At first I wondered why everyone thinks DLSS 4 is so great^^ If you use the DLSS swapper to switch to DLSS 4, check the version manually. In my case, the swapper did not find the nvngx_dlss.dll in the /bin directory, but in the /bin-mt directory and swapped it. -
If you use ‘Use DCS System Resolution’ under VR / VR Mirror Options, no additional image is rendered for the mirror. Otherwise this is exactly what happens, and this costs VRAM. If you use ‘Crop To Rectangle’, the mirror is cropped to the resolution set under System.
-
I think DLSSTweaksConfig is not updated yet and you should only use Preset E or F.
-
If I understand this correctly, the result should be that markpoints are offset if they are set from the side. This has been confirmed in a test. - Designated a target with the ATFLIR and set a markpoint MK1 - Undesignated - Designated the Markpoint MK1 with WPDSG Result: The pod immediately jumps away from the target. null
-
Check with OpenXR-API-Layers-GUI if your layers are in the right order https://github.com/fredemmott/OpenXR-API-Layers-GUI
-
For me, the performance is better if I set the Max FPS slightly higher than the refresh rate (72 Hz). We also recommend this in our workshops. AMD Ryzen R7 5800X3D Nvidia RTX 4090 64 GB RAM Pimax Crystal QLED / 72 Hz / QV DFR I have just tested it again: RR 72 Hz / MaxFPS 72: The measurement results show higher deviations in the frametime and therefore poorer values for the low average fps. When I turn my head and look at the instruments, it stutters slightly. RR 72 Hz / MaxFPS 90: (Back to my normal setting) Even frametime, better low average fps values. When I turn my head, there is no stuttering at the instruments.
-
Is it necessary to deactivate OVGME mods before a patch? I thought you only had to enable it on again afterwards?
-
Check your Max FPS in DCS
-
Now that you mention it... I already had 3.7.2. Now I checked, it was 3.7.0 again Will a patch put it back?
-
Eye Tracking wird von der Light nicht unterstützt. Daher gibt's auch nur Fixed FR, kein Dynamic FR. Das bedeutet, dass nur ein feststehender Bereich mit höherer Auflösung gerendert wird. Wenn du also etwas scharf sehen willst, musst du den Kopf dahin drehen. Du kannst mit dem Inside Out Tracking gut klar kommen, musst aber auf Helligkeit und Kontrast in deiner Umgebung achten. Lighthouse ist aber dennoch das bessere Tracking.
-
"Bei der individuellen Fertigung der Gläser ... werden die Werte für die normale Alltagsbrille (Fernbrille) benötigt, NICHT! die Werte Ihrer Lesebrille!" Quelle: https://www.nasenfahrrad24.de/Worauf-sollte-man-bei-Sehstaerke-Einsaetzen-fuer-VR-Headsets-wie-der-Meta-Quest-achten Als ich meine Einsätze bei HonsVR bestellt habe, bekam ich für die Pimax Crystal folgenden Tipp: "..we will suggest adding +1.00 to both SPH values as the Pimax Crystal has a shorter focal distance than other VR headsest." Anstelle von SPH +1.50 habe ich also SPH +2.5 bestellt, das hat funktioniert.
-
You have to enable "Use Quad View", otherwise it will not work. Default is OFF
-
Thank you for the clarification. Strangely enough, the (undocumented) ‘Track the eye position’ button behaves differently. If I switch it off, the eye tracking on my Pimax still works...