Jump to content

Phantom711

Members
  • Posts

    1268
  • Joined

  • Last visited

Everything posted by Phantom711

  1. @Michel0079 I would call it unlikely, that this is a DCS issue. Remember, that Meta also issues updates to the Meta app and the headset frequently. Could also be something else interfering with your WiFi.
  2. Since you are using a QuestPro, this is absolutely irrelevant. Nothing you set in there has any effect for you because as the name of the app suggests, it is for Windows Mixed Reality and the respective headsets that use it (i.e. HP G2). In the settings of the Meta PC app, make sure that it is set as your OpenXR runtime (Settings>General)! I have a 13700K and for DCS I disabled the 8th core (P-core), which has solved the problem of frequent freezes for me. Disabling all E-cores had a negative effect for me and even though this was propagated by some people, I think it‘s bull<profanity>. But find whatever works for you!
  3. @splash 2.2 is crazy high. Do you really feel that you need that? I have mine set to 1.7…and that is also with a 4090 and using Quad Views on a QuestPro. Maybe rather try the middle ground then…I have mine set to 500. The differences are very subtle and you won‘t notice a difference in all situations. I only noticed, after I tried Virtual Desktop, which simply looked better and I couldn‘t tell why until I tried increasing the bitrate on Quest Link. There is less color banding and I feel like terrain at a distance looks better.
  4. @SgtButsy The game‘s interaction or lack thereoff with an external product like a specific vendor‘s controllers (or virtual hands) might be even more complicated to fix than an internal problem that you mention as examples. And in all fairness, Meta also had a recent record of implementing surprise changes that broke stuff in DCS.
  5. @Hursta1 The update is not even a week old. I don‘t think it‘s a realistic expectation on your part, that this gets fixed that fast.
  6. So wie ich das im NATOPS lese, ist das nur ein Verfahren zur Fehlerbehebung, falls der FCS RESET nicht funktioniert hat.
  7. @MhSucio Do you use OXR toolkit? If so, try disabling it.
  8. @Dogsbd Point is, SteamVR shouldn‘t start at all. At least it has never done that for me with VDXR.
  9. Also try without the —force_enableVR extension. Read somewhere else, that it causes issues since you can now decide in the launcher if you want 2D or VR.
  10. Aus irgendeinem unerfindlichen Grund hat ED den Namen in OXR von „DCS World“ auf „DCS“ geändert. Daher denkt OXR toolkit jetzt „Oh….muss wohl ein neues Programm sein, dann stell mich mal neu ein“. Davon abgesehen sollte sich das Problem des OP wohl, wie schon erwähnt, durch Zentrieren der VR Sicht beheben. Wie man dafür keinen Button belegt haben kann, ist mir aber ohnehin schleierhaft.
  11. Haha...I also just measured. Same!
  12. You don‘t need the —force OpenXR extension. The DCS MT version is OpenXR by default. Are you sure you have VDXR set as the runtime in VD. (It‘s on the PC App of VD)
  13. I can measure tomorrow evening.
  14. But you can extrapolate from that…
  15. Can‘t measure right now…not at home. Have you checked their site? Maybe the dimensions are in some manual…?! it should have pretty much the same dimensions as a warthog base.
  16. The DCS_updater launches the MT-version for a while now.
  17. muchhia has explained this ad nauseum in this thread now. I will try in my own layman‘s terms: QVFR is not „native“ to DCS. But it uses OXR and DCS runs on OXR. But DCS does not adhere to certain OXR standards which is why mbucchia implemented a fix (workaround) specific to DCS in his QVFR app. Since ED now, for no apparent reason, changed the name of „DCS World“ to „DCS“ in OXR, QVFR no longer recognizes, that the workaround needs to be executed. To again fix this in QVFR, mbucchia would need to sign a new license (or something along the lines) which costs money, takes time and then only fixes something which is a fault on EDs side in the first place….
  18. I haven‘t personally tried this, but there is this OpenXR API Layer management tool, so you don‘t have to uninstall/install quad views every time you want to enable/disable it. One can also enable/disable it in the SteamVR options REGARDLESS of if one uses SteamVR or not.
  19. Are you using Quad Views Foveated Rendering in Fixed mode? Because to me it looks like also the resolution is different in the 2 parts.
  20. @Dos I think the OP means, that when you join a mission, that the aircraft parked there on an airfield should not have the wings folded right from the beginning. I think there is an option somewhere in a lua file or something…but I don‘t know exactly.
  21. So despite the title of this thread, I guess anyone using QVFR is affected, no matter which headset? I am asking for a friend... ("He" has a Quest Pro) Jokes aside...I also have some weird flickering...
  22. To whom it may concern: I ended up trying this mod which a guy from my virtual squadron recommended to me. Problem is gone. https://www.digitalcombatsimulator.com/en/files/3332639/
  23. Hello, I don´t want to double-post, but I posted this under the VR subforum, but during my testing it showed, that this issue also happens in 2D. So if any admin would be so kind to actually pull it here and rename it...
  24. @LucShep @TFS Thanks both of you for your answers. I can very well imagine, that things like shadows or textures and objects in general are processed/rendered at a lower quality when further away, but in my given example, I am not changing my distance to that carrier isle. I just turn my head left/right and up/down and can see the quality of the shadows on that structure change from "really nice" to crappy. And all that in a way that makes no sense: nice shadows in my peripheral vision, but crappy in the center and actually the most part of the screen. As if someone reversed the logic there of how on might want to do if one would want to save some processing power and still have nice graphics for the most part. (Kinda like Foveated Rendering...but reversed) What´s the benefit of high quality shadows if I literally have to "side-eye" them? I will check out the mods. Thanks.
  25. !!! I just tested in 2D and the problem appears there as well...so in that regard, my thread is not at the right place, but maybe someone has an idea anyways, what is wrong here. I am more than happy, if it is just a stupid setting on my part somewhere.
×
×
  • Create New...