-
Posts
735 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by winghunter
-
This looks great, any idea on the price ?
-
Did you see any difference with hyperthreading enabled ? I noticed less stutters when its disabled on my 10750 but its hard to measure stutters objectively.
-
Some CPU BIOS settings are pretty bad for DCS VR...
winghunter replied to RealDCSpilot's topic in Virtual Reality
I can reach 70 fps now with my 3ß70 while with hyperthreading i couldnt due to cpu limit. Also there seem to be less of the DCS stutters. Im on windows 10 though and DCS 2.7 -
Some CPU BIOS settings are pretty bad for DCS VR...
winghunter replied to RealDCSpilot's topic in Virtual Reality
Anyone knows what to do with those other settings ? I just disabled Hyperthreading it was causing my core utilisation to go down due to DCS single thread. -
sry, 125% as in 25% upscaling. I was going for more resolution but i havent considerd this may also cost VRAM. When I drop NIS upscaling from 125% to 80%, i can run High textures and MR. There is a slight 5 fps drop on mission reload, but i can get it back to standard fps by alt-tabbing and waiting for 10-30 seconds. VRAM usage is now at 5.5Gb / 76%. I only tried to reload one mission, it may get worse the more often you restart the mission. But given my limited system i think this is the best compromise. Thanks for the help
-
I have used following workaround: enable fullscreen optimisations in shortcut use DCS system resolution (smallest possible) Set PC monitor resolution to DCS system resolution This seems to give me the same framerates as with alt+enter, while also allowing the mouse to click anywhere
-
The colors are not related to the WMR overlay, i simply mean: green: my regular fps for this mission red: significant drop in fps 10% or more Im using 90hz 100% for the G2 in DevTools, with 25% NIS upscaling in Toolkit. 0% sharpness. MSAA 2x. No other tookit settings used.
-
I have de- and re-installed OpenXR runtime, OpenXR devtools, OpenXR Toolkit, but the problem remains. ( Disabled HAGS again, made no difference to enable it for the mission reload problem and most people get more stutters with HAGS on. ) I figured out its a combination of things relating to VRAM on my 3070 (8gb) edit: green: my regular fps for this mission red: significant drop in fps 10% or more Terrain textures high, MR off: First mission: framerate green Mission reload: framerate green Terrain textures low, MR off: First mission: framerate green Mission reload: framerate green Terrain textures low, MR on: First mission: framerate green Mission reload: framerate green Terrain textures high, MR on: First mission: framerate green Mission reload: framerate red So it seems that having both: terrain textures HIGH and MR enabled is too much for the VRAM to handle, which then gets worse every time a mission loads. This is possibly due to VRAM being outsourced to RAM. From what i read there is no way to disable shared memory, so the GPU will always offload to RAM if VRAM is full.
-
You are right, MR was disabled. It just felt so smooth after testing with low frame rates for hours that i thought it was still enabled. Im almost back to square one, with MR enabled i still get the framerate tanks after repeatedly starting a mission. At least disabling the OpenXR toolkit FPS overlay improved the framerates overall. And now i know its related to MR and not DCS or HAGS
-
I have toolkit v1.2.3 and still got this issue. I was pretty sure MR is still enabled ingame hmm let me check
-
I've filed a bug with OpenXR toolkit. The developer says the frame drop is expected, there is no way around it. Just something to be aware of when using the OpenXR Toolkit overlay.
-
Ok finally resolved it: Turned HAGS on - no effect cleared WMR environment - no effect but probably good idea regardless Turned OpenXR MR from ON to AUTO - no effect but probably good idea regardless Turned OpenXR Toolkit framecounter off : There you go this thing cost me like 30% in frames. I was actually laughing hard when i realised this. I use the fps counter open from OpenXR DevTools now. Now i can open the same mission 3 times in a row with consistent frame rates without having to restart DCS
-
I still have this issue with WMR 112.2211.2002 and 2.7 or 2.8
-
These specs are for Snapdragon mobile processors. DCS wont even run on these so these numbers are meaningless. DCS is certainly not very well optimised, but 3 million triangles is no problem for 20 or 30 let alone 40 series GTX cards, they can push 100 millions of trinagles per frame. The optimisations have to be done at deeper levels. There may be only marginal gains from improving LODs even though its probably still worth doing.
-
Clouds look perfect in VR now! (edit: not all clouds)
winghunter replied to dmatt76's topic in Clouds & Weather System
uhm whats your graphics settings ? -
Head position randomly self-resets to an arbitrary incorrect position
winghunter replied to Aquorys's topic in VR Bugs
I have bound "recenter VR headset" from UI to a joystick combo just in case it looses tracking. Anothering issue i found is that if you sit in front of the monitor like me, the headset is confusing its tracking information from the VR mirror on flatscreen. Since the position tracking of most headsets is also camera based, having the in game view in front of its cameras could confuse the software. I noticed this tracking offset happens much more frequently when i turn my head slowly. Which is why i have to blacken my PC monitor once i start DCS to get a stable tracking performance. Another reason why i wish we could simply disable the VR mirror via options like in other VR games. -
Its especially annoying in VR Disabling reflections via the F16 special menu wont help either
-
If your system isnt GPU limited you may not see a performance difference. But if it is, then there could be some gains see Another reason is to improve headset tracking, as DOF cameras of headsets can be confused by the mirror image
-
DCS looses internect connection on restart if WMR is not closed
winghunter posted a topic in VR Bugs
If WMR is started before DCS, or if DCS is restarted from the menu via i.e. fullscreen change, then DCS cannot access the internet on startup, the authentication fails and modules are not available. WMR needs to be closed and DCS manually restarted. Not sure if its a bug with WMR, DCS or OpenXR -