Jump to content

VitS

Members
  • Posts

    151
  • Joined

  • Last visited

Everything posted by VitS

  1. It should be enough to run dcs.exe from where it is installed. WMR and SteamVR will be launched automatically
  2. This is missleading. You can run absolutely lowest settings and still be cpu bound even with 1660. Graphics is not only thing DCS uses your CPU for. It needs to run scripts for all units on the map, it needs to calculate physics for all radars. And so on
  3. Having 32GB or even 64GB is always good thing for DCS and sims in general. Even if game itself doesn't need that much it still good to have lots of memory for file cache.
  4. In perfect world you are correct. In reality most (DX12/Vulkan) games still run better on CPU with less cores but higher singlecore speed
  5. 1) Install hacks which "increase gaming performance" you found on internet even though you have no clue what they do. 2) Update to latest version of Windows. 3) Go cry on forums that upgrade broken your PC ... 5) PROFIT
  6. Isn't it standalone HMD?
  7. What is wrong with this picture? You mean missing planes? Maybe you just out of video memory? Too high PD and only 8gig of vram?
  8. I think he was reffering to running dcs in Virtual Desktop, not Oculus Link
  9. Sluttering you mention can be caused by things: 1) You are running ASW off but don't get stable 72 fps 2) You are running what is called "45 HZ forced" in OTT. This is really lame setting that limits your fps to 36, but does't actually use ASW interpolation! To troubleshoot: 1) Run OTT and set ASW Mode to 45. 2) Run DCS and hit ctrl-pause once. See how much fps you are getting. You should be getting 36 fps stable. 3) Run Oculus Debug Tool (you can find it here "C:\Program Files\Oculus\Support\oculus-diagnostics") and make sure that "Asynchronous Spacewarp" is set to "Force 45fps, AWS enabled" You should not be getting any micro slutters now. If you are still getting them try lowering your settings till you get stable 36fps.
  10. You need to delete "motionReprojectionMode" : "auto" line and then just use Motion Smoothing setting in SteamVR
  11. I think clouds are not renderer as 3d objects, that's what causes the problem.
  12. In VR mode display resolution doesn't do anything.
  13. OTT PD just overrides DCS PD setting. You can easily check it yourself, just use Pixel Density Visual HUD in OTT. Visual HUD is broken in DCS right now, but you can still see it on mission loading screen if you look to the left or to the right.
  14. Do you have any applications running that show their windows on top of other windows? Like OTT or Oculus Debug Tool? If you try to minimize them
  15. Meanwhile for the rest of humankind "native" means "not emulated". I.e. running oculus games on Index using revive is not native. You obviously have no slightest idea how VR pipelines work. That's like blaming ED for using nvidia/ati drivers to work with GPU.
  16. That's just not true. Elite dangerous and dcs night flights looks absolutely amazing in Quest.
  17. Note that for ASW to work properly your GPU should have headroom. If you are having bad exprience with ASW try to lower you settings. As streakeagle said, only downside of ASW in DCS is is ghosting of aircraft in a dogfight.
  18. 2nd. Wear fancy multi colored pants :)
  19. Reverb is really good upgrade from O+ in DCS. Picture clarity is amazing, and there is much less aliasing.
  20. SteamVR has special mode that simply locks your fps to 45. WMR motionvectors reprojection tries to guess what next frame will look like based on previous frames. With motionvectors reprojection enabled game looks much smoother but you can see some artifacts and ghosting. So it works the same as SteamVR Motion Smoothing and Oculus ASW. Long story short on WMR headsets always enable motionvector reprojection if you are not getting stable 90 fps in game (and in DCS you never get 90 fps).
  21. DCS uses Oculus apis, not Steam openvr. Are you saying that changing SteamVR SS somehow works with Oculus Rift S?
×
×
  • Create New...