Jump to content

wheelie

Members
  • Posts

    53
  • Joined

  • Last visited

Everything posted by wheelie

  1. 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.
  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.
  3. 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. I have 3 monitors attached for 2d DCS, 1 @4k and 2 @1080p. I only use one for DCS and cannot reproduce this bug unfortunately.
  5. 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.
  6. @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.
  7. Aha apologies chap didnt realise that would actually work, many thanks.
  8. 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?
  9. 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.
  10. 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.
  11. I'm assuming you already have the NVidia control panel optimized but this is mine. Main things for MT is "Threaded Optimisation" should be ON. I also have VSync as FAST as it stops tearing.
  12. Thats weird given the strength of the CPU Gib, is AMD EXPO enabled in the bios?
  13. Setup and setttings look good to me Gib only i can think of is the default resolution on the new crystal's is really high, i watched a Vrflightsimguy video and he had to reduce/override the resolution to get back to reasonable framerates. He overrided the resolution within OpenXR toolkit mate, hope this helps.
  14. Never really understood this spotting issue, played in 4k in 2d and now play exclusively in VR with the Varjo Aero. The 1 to 1 representation within VR especially at high resolution makes spotting pretty easy for me at least.
  15. 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
  16. @BIGNEWY Hey mate are you guys actively aware of this VR issue with the Aero following the last update?
  17. Hi Chuck, I had something similar and it was down to my DCS settings for water, when i set it to low/medium it can sometimes have render issues. I set it to HIGH, restart DCS and set it back to medium. Works for me.
  18. Hey mate i think its this fix you need to install. https://github.com/mbucchia/OpenXR-InstanceExtensionsWrapper/releases
  19. @AssamitaYou should point it to the DCS.exe buddy rather than the updater for the single thread version. You only really need to use the updater when a new release is available.
  20. 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
  21. 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.
  22. Thankfully it's not a BIOS setting Colin i believe its a program called Process Lasso, apparently the program can be used to forbid DCS to use the E-Cores and set DCS to high priority. This essentially forces DCS to have a higher priority of the CPU's time and limits DCS to only use the performance cores. Hope this helps buddy.
  23. Guys apparently if you're running 12/13th GEN CPU's you ned to set DCS to only run on the P cores, lots of discussion around this on various discord groups and tying DCS to P cores fixes quite a few issues around stuttering especially with a 4090 GPU in the system as well. Just a heads-up.
×
×
  • Create New...