Jump to content

wheelie

Members
  • Posts

    53
  • Joined

  • Last visited

Posts posted by wheelie

  1. On 2/27/2024 at 4:28 PM, Elphaba said:

    So I'm getting 70 fps in DSC in VR, when I look outside the cockpit and watch the world go by it occasionally skips just a few pixels, like it pauses then catches up. 

    But there is no fluctuation in fps or frame time. 

    However, if I run the game in 2D it's silky smooth. 

    Is this a bug or something that can be tweaked? 

    I updated to NVidia driver 551.46, cleared the DX runtime cache and usual FXO and Metashaders folders and its definately smoother for me.
    This is with the Varjo Aero and RTX4090 so even i can notice a difference.

    • Like 1
  2. A year ago i ran a 3090 with 24gb VRAM.

    Syria missions (multiplayer) and liberation missions would take up 21/23gb of the VRAM, i was a tad shocked to say the least and always wondered how other users would handle this with the plethora of cards out there. I've since switched to a 4090 and again i see high utilisation of VRAM which is kind of what i would expect.

    So a year later i still see the same VRAM behaviour i had seen before MT was a thing. Maybe we're seeing more caching in VRAM for the new eye candy, night lights, shadows, pre-rendered content, 4k textures? I don't know but the VRAM usage for me is the same as it's always been however for cards with 8, 12 and 16gb ram i suspect this may have caused some unexpected issues that could result in shared memory being used which would obviously be far, far slower than the GDDR6 on a lot of GPU's.
    Perhaps the additional shadow options have added to this? I don't know but i see the VRAM as high as it's always been on my system.

    A good troubleshooting exercise would be to have the same mission replay and enable each shadow/texture option to see what, if any increase this causes and and what point it goes above the threshold of a GPU's available VRAM.

    • Like 1
  3. 7 hours ago, daddio007 said:

    Sorry to post continuously but I have an update. 

    I rolled Varjo Base back to the previous 3.9.0.10 version and DCS build 2.8.7.42583 works fine in VR. I then upgraded back to the latest Varjo Base of 3.10.1.14 and it hung and had the message in the log:
    ERROR   VISUALIZER (Main): OpenXR exception: runtime is not available
        Source: Projects\Visualizer\Source\OpenXR\openxr_program.cpp:322

    Subsequent attempts to load DCS defaulted to 2d with the same message, as before.

    Rolled back again to Varjo Base 3.9.0.10 and 3d works again. Loaded consistently at least 6 times.

    At least on my system, the incompatibility is between the latest builds of DCS and Varjo Base. Older build of either will work with the newer of the other (DCS 2.8.6.41066 works with Varjo Base 3.10.1.14 but DCS 2.8.7.42583 only works with Varjo Base 3.9.0.10 (or earlier presumably).

    If anyone else having the issue wants to try this please let me know if it works or not and I will update the ticket I have open with ED and Varjo.

    Thanks!

    Thanks for the update mate much appreciated, so with the VB software rolled back you can use the OpenXRTK within DCS? i.e. NO DFR enabled?

  4. 9 minutes ago, Fizzle said:

    A few days later I have had a single instance where DCS didn't start in VR with this set. So it's not a complete fix, but it's definitely a big improvement. Used to get VR starts about 20% of the time, now it's more like 90%.

    Are you playing with OpenXR enabled and no DFR?
    This seems to be the main issue, since the latest release we cannot use OpenXR toolkit with the wrapper as we could in 41066.1.
    Matt has released the updated version of DFR which allows us to once again use OpenXRTK within DCS but turbo mode crashes DCS and the anti-aliasing is broken somehow, e.g when i look back at the sidewinders on the wingtips they are pixelated.

  5. @BIGNEWY

    Scott can we get some information or clarification as to what changed in the last DCS patch that is not detailed in the change log please?
    It appears something changed around VR that was not documented or detailed that specifically affects Varjo Aero headsets.
    Openbeta v41066.1 doesnt have the issue.

    Any clarification/details would be most appreciated.

  6. 7 minutes ago, zildac said:

    Same here latest OB and Varjo Base and no issue.

    Ok so quick question for those that are saying its ok.
    Currently we cannot use OpenXR tooklit and Varjo Aero like we could previoiusly.
    So within DCS we now don't have the ability to open the XR toolkit menus and amend the VR config with the current MT openbeta.

    If your using DFR you already have OpenXR tooklit disabled and you won't see what we're referring to.

    Does anyone currently use the OpenXR Toolkit enabled with the Aero and are able to open the XR Toolkit menus within DCS MT openbeta?

  7. 13 hours ago, daddio007 said:

    I had to roll back to 2.8.6.41066. That fortunately still works.

     

    Thanks for the suggestion though! Glad it works for you! 🙂

    Where are you getting the previous version of the beta 14066 install? Did you already have it locally?
    i'm at the point where i want to rollback.

  8. 5 hours ago, LOW_Hitman said:

    Using nearly the same settings like you and DCS performs great. One thing that is really strange is vsync, because it shouldn't have any affect in DCS-VR but when i set it to fast there is a noticeable positive impact (no tearing) - strange because vsync isn't working in VR - or should not work in VR 🙂

    Are you using Hyperthreading or SMT or do you keep it off? Iam not sure which setting performs better - some people say keep it off within dcs-mt

     

    Hyperthreading is on mate and works fine for me with an i9 9900k @5ghz all cores.
    The Vsync to FAST is a weird one but i think its more driver/nvidia related than specific to VR. Great when it stops tearing though, i had to disable vsync in DCS and set vsync to fast and have left it that way for about 18 months now.

    Glad you had a positive result with it.

    • Like 1
  9. I can confirm i also have this issue even with the i9 9900k.

    If i have OpenXR toolkit enabled DCS crashes after both the headset and screen goes black.
    If i set OpenXR toolkit to safe mode i see the mirror working properly but black screen in the headset.
    If i disable OpenXR toolkit (no DFR) i can use as normal but with no OpenXR tookit settings or changes possible.

    If i disable OpenXR toolkit and install DFR again i can use as normal.
    Prior to the update i could use OpenXR toolkit without DFR and change all aspects of the headset/OXRTK/instance wrapper settings within game.

    I have literally tried every conceivable combination of drivers, versions of OpenXRTK and various versions of varjo base and GPU drivers all to no avail.

    Common error appears to be the following:

    2023-07-05 00:02:14.599 ERROR   VISUALIZER (Main): OpenXR exception: runtime is not available
        Source: Projects\Visualizer\Source\OpenXR\openxr_program.cpp:322

  10. 12 hours ago, Assamita said:

    Hi. I've been playing DCS in VR for 2 years now without many issues. I'm running a Pico 4 with Virtual Desktop and up until this morning, everything worked as expected.

    This morning, Steam VR updated to version 1.25.7 and the headset connects properly to VD, then connects properly to Steam VR, but when I launch DCS, it launches in windowed mode, not VR. I've tried rebooting the computer, MT, single thread version, everything I can think of.

    Any hint of what could be happening?

    First thing is rollback to the previous version of Steam as thats the latest change that has broken your setup buddy.
    Or perhaps the dcs.exe that you're launching doesnt have the addition arguments after the dcs.exe

    E.g. dcs.exe should normally have --force_enable_VR

    e.g. I use openxr and use the following

    "D:\Programs\Eagle Dynamics\DCS World OpenBeta\bin-mt\DCS.exe" --force_enable_VR --force_OpenXR
    Yours may need the following:  --force_steam_VR

     

  11. I'm seeing a 20/30% increase chaps running MT open beta standalone on a Varjo Aero.

    PC: i9 9900k@5ghz all cores, 4090 GPU, 64gb RAM, M.2 drive dedicated for DCS.

    I used to use opencomposite but now use native OpenXR.

    Ran a DCS repair to start with as below:

    #################

    Go into your \Eagle Dynamics\DCS World [openbeta]\bin folder.

    There, hold Left Shift and right click and click "Open Command window here."

    (Windows 10 creators update now uses Powershell, type cmd in Powershell, press enter and then continue)

    Then, type the following exactly as printed:

    .\DCS_updater.exe cleanup

    this will delete all non official files

    then do a DCS repair

    .\DCS_updater.exe repair

    #################

    i set opencomposite app back to steamvr
    Reinstalled OpenXR toolkit 1.3

    Created shortcut on desktop to the bin-mt folder and amended the properties of the shortcut to:

    "D:\Programs\Eagle Dynamics\DCS World OpenBeta\bin-mt\DCS.exe" --force_enable_VR --force_OpenXR

    no need to replace openvrdll

    NVidia control panel changes: Manage 3d settings - Threaded optimisation = on, VSYNC to FAST

    Run DCS in administrator mode (automatically higher process) and away i go.

    Hope this helps.

×
×
  • Create New...