Jump to content

Phantom711

Members
  • Posts

    1209
  • Joined

  • Last visited

Everything posted by Phantom711

  1. As someone who flies in a virtual Squadron that puts a lot of emphasis on Carrier ops, I can only recall one instance in the past few month(!) where someone damaged his gear on a trap. Otherwise it‘s really not an observed issue really…
  2. @VR Flight Guy in PJ Pants Well yes, the passthrough of a Q3 is was better than that if the QPro. But how many people have setups with like even just the front section of a cockpit and can make use of those early adoptions of an AR cockpit? You only take that one aspect to call the QPro „rubbish“ while disregarding the performance advantage of eye-tracking/DFR. As far as I can tell my USB-C connection is better than my WiFi6. DP would be superior though.
  3. No. OpenXR is the default. and also that „—force_enable_VR“ extension might cause issues when you use the new DCS launcher.
  4. Do you mean the OpenXR tools for WMR or the OpenXR toolkit companion which lets you make some adjustments while in VR with the blue-ish window popping up. In any case neither of them need to be started prior starting DCS. And you are more than likely running DCS in OpenXR anyways because it us the default, and arguably best way of running DCS in VR. But yes, the ORX toolkit companion is not being updated anymore and might(!!!) cause issues.
  5. @VR Flight Guy in PJ Pants Can you elaborate further on that? Because I don‘t understand your reasoning here.
  6. Trust me, the pancake lenses of a Quest 3 or Quest Pro are just so much better than the fresnel lenses of a G2. You simply can‘t just compare VR headsets by their resolution. The Quest headsets can also be used at refresh rates of 72 or 80Hz without flickering. Indirectly that also helps in performance compared to the 90Hz of the G2. Now since you also look for a headset that your son can use for other standalone games, I out of the 2 I would recommend the Q3. If it was only for DCS, I would argue that the QPro is the overall better choice due to it‘s eye-tracking feature. I‘ll die on that hill.
  7. @Justin1Ntime Be aware that the game will be smoothest when FPS match the refresh rate. So usually 72FPS at 72Hz will appear smoother than 90FPS at 120Hz. And yes…as already stated, in VR your FPS can not exceed the headset‘s refresh rate.
  8. Hey, yeah…same problem here. Started like 3 weeks ago. I also went ahead and turned off hand-tracking. Still need to evaluate if that solved it. But good to know, that it seems to be a common problem. At least that increases chances of it getting fixed.
  9. @BIGNEWY @Nealius Sorry to bring this up again... What I discovered now is, that when I use the "Quit to desktop" option to leave the game (multiplayer), a nicely working replay is created. Same applies to other brute force measures to end the game (i.e. Task manager). If I leave via "Quit" or "Leave server" the replay comes up with "Mission Load Fail". Sounds good, right? Well yes, but unfortunately replays that worked up to like 2 or 3 weeks ago (until September update?) now still load, but no clients spawn. ED...this is sabotage....
  10. 1. OpenXR toolkit might not work properly any more. 2. Turbo Mode is enabled by default in QuadViews and you should not enable it additionally in OXRTK. That might actually also be the source of your problem here.
  11. Ok. I rechecked now. I hope you have a seperate monitor for OBS because that helps a lot, but should work regardless. So start the game you want to capture. In OBS select "Game capture". In the dropdown now select "capture specific window" and then select the respective game (window) in the next dropdown. That should be it. (You don´t need to repeat those steps next time you want to capture). At least that´s how it works for me with DCS, I don´t know, how IL-2 behaves. But this is a DCS Forum.
  12. Try „Game capture“ or something like that. Can‘t recall the exact name right now.
  13. @Lord Vader Thanks for taking the time to answer. As I said, I don‘t claim that it is definitely(!) wrong. I just felt it might have been overlooked or misinterpreted. But if that‘s what you research came up with, I believe you.
  14. @Cali Sounds like you have it assigned as buttons. You must assign it as an axis in the DCS controls options. There is a dropdown menu on top where you can select all available axis commands.
  15. @NineLine Are those maps not just GeoTIFFs? Where would they need to go?
  16. The keyword is „scan volume“ here! I do not question the fact, that EXP3 requires the scan volume to be limited to 90deg. This has probably to do with providing a higher update rate. What I do question is if or why the radar is not „willing“ to slew those 90deg of scan volume all the way to the left or right. In the above case, scanning from 70deg right to 20deg left would still be the 90deg of azimuth scan that you are referring to. I don‘t have anything to prove my case, I am just deducting that from how the radar behaves in A/A (i.e. TWS AUTO). It simply doesn‘t appear plausible to me, that the azimuth scan in A/G needs to stay centered around the nose.
  17. @BIGNEWY But this would still be within the physical gimbal limits of the radar. Wouldn‘t it make sense that the radar adjusts its scan pattern to the right if the selected target is there? I mean it took a while until ED implemented A/A radar slewing to the left and right…maybe this feature should also exist in A/G…? I really don‘t know and hence don‘t have any publicly available evidence.
  18. What does the scaling actually do?
  19. @oboe All that you are saying is correct, but due to the fresnel lenses, the option to have DFR might be pretty pointless.
  20. Depending on which preset you are using (i.e. Ultra, Godlike etc), of course VD is supersampling. As long as you know it, you can then adjust the respective settings in QV.
  21. OXRTK does not need to be started up. It is active in the background unless you actively disable it. You might actually try to disable it via the respective checkmark as suggested above in order to check if it is the source of your problem. If you are in fact using Virtual Desktop, then Oculus Tray Tool has absolutely zero effect on your PCVR experience. I would suggest to also leave that alone. Have you used QuadViews Foveated Rendering? In that case you now also need to activate that in the DCS VR settings.
  22. @Vox Those notes/warnings/cautions do not imply that one is not supposed to flare. The NATOPS also states a maximum landing weight of 39000lbs for a FLARED landing as opposed to the 34000lbs limit one has for landings/traps on the boat.
  23. @hannibal Yeah I‘m also running the QPro with a 4090… I still run into ASW occasionally, but definitely less so with QV enabled.
  24. OpenXR toolkit has a build-in check box to disable it if you want to check if it‘s interfering with something. So no need to uninstall right away. What „built-in support for foveated rendering“? DCS now has a checkbox (or toggle switch in the launcher) to activate/deactivate QuadViews. You still need to have QuadViews installed as before if you want to make use of it. It is just a convenient feature now for testing or quickly turning it on/off to your preference for different modules. So…if you had used QV before and now you uninstalled it, OFC you have worse performance. Also check out this VR subforum where you might find better advice then whereever you were told to uninstall OXRTK and QV.
×
×
  • Create New...