Jump to content

Qcumber

Members
  • Posts

    2166
  • Joined

  • Last visited

Everything posted by Qcumber

  1. Yes. You can use quad view foveated rendering but only in fixed mode. I've used it with rift s, Pico 4 and Quest Pro. It works best with VD so you are already half way there. https://github.com/mbucchia/Quad-Views-Foveated
  2. I just use a generic config file and adjust it as needed for VD or meta. It keeps it simple. I can post it here if that helps.
  3. This happens quite often with me it's usually resolved with a restart of the headset.
  4. Meta released a patch for this a few days ago so no need to stop the update. Just let the headset update to the latest PTC patch.
  5. A 3060ti is borderline for a Q3. Have you tried using quad views foveated rendering in fixed mode? This will give you a massive performance boost. If you keep the centre to about 0.5 x 0.5 then you will reduce GPU load by about 50-70%. It will be more CPU intensity but a 5600x should deal with that. https://github.com/mbucchia/Quad-Views-Foveated
  6. I only thought of this a few days ago when comparing VD and meta again after the update.
  7. OTT is just an interface to access ODT. You can use both. If you change a setting from OTT it will update in ODT. The advantage of OTT is you can set hotkeys and it gives you a lot more control over ASW. However, OTT does not allow you to select the "quality" sharpening setting. I agree. I am using VD all the time these days. It takes a bit more setting up though with a dedicated router etc. I run VD without any AA and it looks pretty good. Sharp and no blurring. Jaggy is some places but not too bad. Looks better than with meta but this might be due to Meta's built in sharpening.
  8. Try running without any AA and see how it looks. I am using that a lot these days. No ghosting or blurring at all. To minimize ghosting with DLSS you need to start with a high resolution. Try adding 1.3 multiplier into OTT. The other thing to try is update to the latest version of DLSS simply by downloading here and then replacing the one in the bin-mt folder. https://www.google.com/amp/s/www.techpowerup.com/download/nvidia-dlss-dll/%3famp You can also use DLSStweaks to change the preset (I find F is the best) and adjust the scaling. https://github.com/emoose/DLSSTweaks
  9. I think it just allows using VDXR through oculus link. What the OP is referring to is using VD through a cable rather than wifi.
  10. DCS runs on open XR. It changed from open VR last year. It's here for good.
  11. This is related to VD so ggodin is the reference rather than mbucchia. I believe the limitation of VD to WiFi vs link cable is a meta issue.
  12. The easy answer is stop using meta link.
  13. I used to think ASW was better too, but running SSW in auto recently has been pretty good. Try VD again but make sure you are comparing like for like. The difference between VD and meta is very subtle.
  14. The maximum I can get is about 300-350 Mbps. I set h264+ to 200 as this gives me a decide latency of about 10 and the quality still looks good. You could also try HEVC 10 bit at 150. I don't think this is your router as such. It's more likely it is the channel you are using and local "noise". Have you tried using a WiFi scanner app to check if there is any interference on the channel you are using? You can use a tin foil box (Faraday cage) to screen out some interference.
  15. The latest version of v68 PTC fixes the open XR toolkit bug. If it is still something else then I would suggest posting a new topic and supplying full details of your issue.
  16. This is the router I use: Deal: Mercusys AX1800 Dual-Band Wi-Fi 6 Router, WiFi Speed up to 1201Mbps/5GHz+574Mbps/2.4GHz, 3 Gigabit LAN Ports, Ideal for Gaming Xbox/PS4/Steam & 4K (MR70X), Black https://amzn.eu/d/3ViDo7U
  17. Try it and see. It's an open XR layer so should be ok. Other open XR layers are fine, such as QVFR and OXRTK.
  18. It's running fine for me. There have been a couple of updates recently. Which one are you using?
  19. Yes. It works for me. I can now run DCS with OXRTK and QVFR using meta cable link.
  20. I would agree with this. There are plans to integrate QVFR with not VD, although mbucchia reports there are a few barriers to overcome first. Hopefully this will happen as it will mean better optimisation and support for QVFR. This is the biggest reason to choose VD over meta. Shall we ask ggodin to rename it to STD?
  21. VD does not allow cable link due to meta not making this option available to third parties. You need a dedicated wifi 6 router connected to your pc via ethernet. I got mine for about £40 from Amazon. Meta cable allows you to go to 960 Mbps whereas the maximum on VD is 400mbos. However, VD allows you to use better video codecs so the differences are not that big. A lot of people run VD out of the box and think meta is better. This is often because they are not comparing like-for-like. You need to make sure the other verall resolution is the same and that you have the same sharpness settings etc. Meta have a default sharpening setting which is very harsh. I am currently using Godlike with QVFR set at centre 1.3, edges 0.5. h264+ at 200 Mbps. With these settings I can get a steady 72 FPS in most situations with good quality and performance.
  22. Try reducing to 80 or 72 Hz. That should reduce your game latency further.
  23. I don't think this approach is officially recommended but it would be worth asking for advice on the VD discord server.
  24. I use this one with VD and it works fine. Deal: Mercusys AX1800 Dual-Band Wi-Fi 6 Router, WiFi Speed up to 1201Mbps/5GHz+574Mbps/2.4GHz, 3 Gigabit LAN Ports, Ideal for Gaming Xbox/PS4/Steam & 4K (MR70X), Black https://amzn.eu/d/0ciDRfyg It's the router speed that's important here, not your Internet speed.
×
×
  • Create New...