Jump to content

Flyingfish

Members
  • Posts

    113
  • Joined

  • Last visited

Everything posted by Flyingfish

  1. I've eradicated the problem by using airlink which doesn't really make sense to me. My cable works fine when I test it. Maybe there's something wrong with my motherboard?
  2. I also have this issue RTX 4090 5800x3d 32gb 3200mhz Installed on M.2 Quest pro
  3. I've tried reinstalling the oculus software, performed a factory reset of the quest pro but it's not made any difference. I'm also getting a lot more stuttering than before.
  4. Has anyone found a solution to this? It's really bad for me on the 2.9 update
  5. Is this available now or is it coming in the next update? Thanks
  6. I'm even getting worse performance when I fly during the day time. I only fly in VR so maybe the performance drop is only VR related
  7. I'm getting worse performance than I did before the Syria update. Is this a common problem?
  8. Thanks for the quick reply. Verifying on steam has fixed the problem with the purple roads but I'm still getting worse performance than I did before the update. I've made the changes on the nvidia control panel which you suggested, although I couldn't find the shader cache option. The log is attached Thanks again for the help dcs.log
  9. Hi, I'm getting significantly worse performance since the last update, both at nighttime and during the day. Also some of the roads are purple. I'm playing in VR on a quest pro with the latest Nvidia drivers
  10. Yes you can, there's a face mask which costs extra but you can still peak under it. If you don't use the Face mask you can easily peak
  11. Hi Mimemema, I don't seem to be getting any performance increase even though I can see that the foveated rendering is working. I've set the highest resolution in the oculus app, left meta-foveated at default but I'm still limited by GPU in the same way I normally am when not using foveated rendering. Is there something else I should be doing? Thanks
  12. I'm pretty sure I've got it working, I can see the resolution changes in my peripheral vision when I move my eyes, but it doesn't seem to be resulting in any performance improvements. I've been monitoring GPU use using task manager and It's no different than when I run DCS using the non MT option (launch oculus VR in oculus VR mode). I've followed all the steps and as I say I can see the resolution change if I look for it but for some reason it just isn't resulting in improved performance. Any ideas? Thanks
  13. Hi I'm getting worse performance since the latest OB update. I don't have exact numbers but I'm getting stuttering where I didn't used to, caused by the GPU maxing out. Happens in both MT and ST I'm using a Quest Pro, specs in signature
  14. Open VR for me. I use a quest pro and it's smoother using open VR
  15. I think you still need the beta to run MT With the quest 2 you don't need anything extra, you just click play on steam and select the MT version. I use OpenXR toolkit with turbo on, this gives me much less stuttering, that's the only thing I change in the toolkit. I also use ODT but only to change the encode resolution
  16. I've recently moved house and have no internet at the moment. When I load up DCS through steam I get an authorisation error message (code 503). Is there any way of fixing this without internet access?
  17. The quest 2 doesn't have eye tracking, the quest pro does
  18. Not with the OpenXR toolkit I don't think. This is the response on discord from the person who programmes OpenXR toolkit when asked if eye tracking foveated rendering will come to DCS Meta runtime does not support "fovMutable", which would be a lot of work to implement. I will add support for Pimax most likely, but only because they have this "fovMutable". Doing this "fovMutable" on Oculus is a lot of work I don't have intention to do.
  19. It does have eye tracking but unfortunately it doesn't work with DCS
  20. Thanks for doing this Minsky, it's really good and adds so much life
  21. I can't bring the comms menu up. I've rebinded the input to different keys on the keyboard and buttons on the HOTAS but it still won't work. I've also uninstalled the game and reinstalled it but there's still no change. I'm using DCS on Steam Specs 5800X3D RTX4090 M.2 Windows 10 32gb RAM
  22. The wave effect you're seeing might be ASW. You can turn it off by pressing CTRL and numpad 1 but it probably won't be as smooth if you do. CTRL numpad 3 forces it on and CTRL numpad 4 puts it back to auto
  23. Thanks. I was launching dcs by right clicking vd in the task bar so looks like that's where I was going wrong. I'll try launching from the games tab when I next get a chance. Thanks for the help
×
×
  • Create New...