Jump to content

Vitralette

Members
  • Content Count

    18
  • Joined

  • Last visited

About Vitralette

  • Rank
    Junior Member
  • Birthday 12/01/1990

Personal Information

  • Flight Simulators
    DCS World Steam Edition [openbeta]
  • Location
    Germany
  • Interests
    Aviation, Simulation, Mountainbiking

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Don't use Oculus Tray Tool (OTT) because its not being supported any longer by the dev. If you have to then leave all settings to default. Meaning PD = 1.0. Oculus Debug Tool (ODT): Same as OTT. Leave everything at Default. "Pixels Per Display Override" = 0 (same as PD =1.0). DCS - PD = 1.0 The only slider you crank up until your PC melts is the render resolution slider within oculus software. If you can set it to max (5408x2736) your Q2 will run at native resolution without any up or downsampling.
  2. I have extensive experience with the Varjo XR-1 used for flight simulation due to my work. So I can't give you a comparison against the G2 but against the Ferrari of VR/MR (at least it was until the XR-3 came out about a month ago). It still has way higher sweet spot resolution than the G2 (XR-1 60 ppd vs. G2 22ppd). Compared to the eye-wateringly expensive "human eye resolution in sweet-spot" of the XR-1: Has the XR-1 higher resolution? Yes. Much better? No. Is there a "oh my god this is amazing compared to Q2" in the XR-1? No. Price to Performance? Q2 blows ev
  3. Thanks @Waltan, but it didn't do the trick for me. Tried that setting before messing with the ingame settings. @speed-of-heat yeah but many people seem to tick that one on at one point or another. I've seen people mentioning this in a similar context before.
  4. Slider in Oculus Software to max, if your PC can handle it. I would not recommend using OTT anymore since the developer stopped the support. https://www.reddit.com/r/oculus/comments/5okoju/oculus_tray_tool/ Pixel Density in OTT or ODT (Oculus Debug Tool) to 1.0 (in ODT that is just a 0 for default settings). I would also recommend to leave every other setting in OTT or ODT at default because since Link v.23 that stuff is all tuned automatically based on your slider settings, except for forcing ASW of course. Ansonsten auch gerne auf deutsch
  5. Oculus App lets you set the render resolution not pixel density. To achieve native resolution (3664x1920) in the sweetspot you will need to set render resolution to 5408x2736 (due to lense barrel distortion). This is the most confusing part about the Q2 setup because most people think setting the slider to 1.7x at 72Hz or 1.5x at 90Hz (=5408x2736) is a supersampling multiplier, which it isnt. This Tweet by Volga Aksoy explaines this.
  6. I am baffled by how little the impact of the DCS graphics settings are for high resolution HMDs. So here is a list of things that don't make much difference and only use resources for the Q2 set at native resolution (5408x2736 render resolution): Textures - For the Hornet this doesn't make any difference for the cockpit, your aircrafts may vary. Airframe textures, runways etc. are lower res but I don't care about that. Set it on low, saves VRAM. Terrain Texture - Doesn't make a difference on Caucasus. Set it on low, saves VRAM. Visible Range -
  7. @ppokit I might have good news for you. I tried a new set of settings which seem to have removed the gpu firewall of death. Now, I am currently still evaluating, but I did about 5 sessions now over half an hour with no problems (which wasn't possible before). Doesn't mean it can't come back and this was just luck but it looks promising. I wanted to wait for a write up till I figured out which setting exactly change the behavior but I would appreciate if you could test these and post our results. I lowered both textures and clutter in order to conserve VRAM. I dont see any diff
  8. Well yeah I seen some of these posts and people keep bringing up VRAM, but I've jet to see real evidence that VRAM is actually a problem. I've someone got a link to a thread where this gets actually shown I'd really appreciate it. That DCS is using ungodly amounts of VRAM is definitely true (MSFS2020 VR on ultra textures only reserves 7.2GB for example), but that this in turn leads to instant fps break downs once a mysterious threshold is reached isn't obvious to me. Continous performance degredation? Sure.
  9. Could you be so kind and explain how a full VRAM is actually effecting the system? Fom what I "understand" is that once the VRAM is full it starts to copy data into RAM which can lead to FPS drops, ok makes sense. What I do not get tho is why I can fly for 30mins with a full VRAM right from the start and THEN all of a sudden it is a problem (as can be seen in the data provided 3 posts up)? I checked if maybe the shared memory is getting filled up (would then start to copy to pagefile/ssd) but that is not the case, at least it's not getting reported by either TaskManager / GPU-
  10. May I ask what happened to your G2? If this can even be determined at this point Anyway sorry to hear you had a bad experience with it. I also have this feeling that I can provoke it to happen by opening F10, going external etc. But then again, as shown by the example runs in the prior post it will also happen without using F10 at all. After the GPU spike I had another look at background processes and found desktop windows manager (dwm.exe) was using almost 20% of GPU 3D rendering resources! Now this was very variable, switching between 0% and 20% - maybe the reason I didnt
  11. Today I was able to fly for 30 minutes on a MP server with about 10 players. Everything went smooth. After landing I restarted DCS in order to see if I could reproduce the problem or if I would get another clean run. Unfortunately the problem was right back the second time around. Same server same amout of players. After 10min I hit the GPU wall as described in the inital post. Good thing about that is that I can now provide some data. First Run - Solid 45fps for 30min (on MP server with ~10 players) Second Run - Hitting the wall after about 10min (same ser
  12. Yes I get the same behavior but only ~50% of the time this trick actually works for me. Half the time when I tab out and back in I get the frames back, half the time it still is stuck until restart. I was under the impression that if DCS is not the active window I get the little notification onscreen. Maybe this notification is unreliable? I did check if any other processes are robbing resources but not if they are stealing the active windows status. Is there any other way to monitor this? The Quest 2 is my first personal (consumer) HMD but I've extensive experience with the V
  13. This post looks similar to this issue Major, Sudden FPS Drop I never thought about it but yes I was always testing in the Hornet, and of course in MP the amount of missiles in the air is way higher then most SP missions. But then again the framerate seems to return to normal after exiting mission/server which it does not for me
  14. HPET is turned off. Regarding the VR Shader MOD by Kegetys - Initially I used it with great results, as you are also recommending it in your guide I was wondering if there is a version which passes IC which im not aware of, or are you only playing single player or servers without IC ?
  15. Thanks, will try your suggestions and I just figured out how to tag someone . I played around with Nvidia setttings quite a bit but never were able to see any real difference regarding visual quality or performance, not enough at least to rule out placebo. Prior to the 100%GPU wall these settings run perfectly smooth on my system, no lag no stutter no frame drops. I mainly set those based on guides I found online by vr4dcs and Lukas S. / Wolta and then dialed almost all of them back to default for testing. Next I will
×
×
  • Create New...