Jump to content

Tygaris

Members
  • Posts

    15
  • Joined

  • Last visited

Everything posted by Tygaris

  1. For the record: My problem hasn't been solved! It's still there, but I'm able to jump through some hoops to make it disappear. There is still an issue with DCS MT + OpenXR (WMR).
  2. Managed to get decent frame rates again, after I set SteamVR as the default OpenXR runtime and not Windows Mixed Reality. 90Hz in main menu and 35-60 on Sinai with nearly everything on "High". Works for me now again.
  3. Thanks for the hint. I tried changing the cpu affinity but sadly the problem still exists. It just moved to the next core and so on and so on. Disabled the first 4 cores but: nope I have this issue only in VR. If I disable it, the main menu is at around 100fps and no core is at 100%, and it's GPU bound.
  4. Hi, 5900X, 32 GB, RX 6800, Reverb G2 here. I always had issues with the MT & OpenXR version, but it worked okay'ish when I set SteamVR as the OpenXR runtime. It's not headset related because other VR games run as expected. Since the 2.9 update it got worse. The main menu launches with around 20fps and then drops down to 15fps. Even worse in game where it drops to single digits. I set the graphics to Low, but the frame rate remains the same. Removed all DCS files (installation and save games) and reinstalled it. Just the base game without any additional modules, still the same problem. I changed the OpenXR runtime to SteamVR and the main menu is at 40fps. But that's still bad compared to previous versions, even before MT support. One thing I noticed is that the first core is at 100% while the GPU is taking a day off. With SteamVR the workload on the cores is much more distributed and the GPU is maxed out. Before anyone asks: yes, I'm launching the EXE from the bin-mt folder. But the huge fps difference between OpenXR and SteamVR happens with the single-threaded one, too. Looking forward to a fix or a hint. Help? (making Puss-in-Boots face) M. dcs.log DxDiag.txt
  5. I had this issue, too, when the MT version first came out. Random flashes every few seconds. Even more when a menu was open. Happened only when using OpenXR directly. When I set SteamVR as the default for OpenXR the problem went away. (HP Reverb G2, 6800).
  6. Not a crash but it freezes when the first loading screen is at 14% dcs_log.zip
  7. SteamVR app is closed shortly after launching DCS.
  8. I have the same. (5900x, 32GB, RX6800, Reverb G2) After launching the DCS MT Version with "--force_enable_VR" the flickering is most prominent in the main menu. Only tried two F-14 instant missions where the flickering was a bit reduced. But it's not playable this way. Had the same issues with the patch where OpenXR was "forced". Steam VR isn't working with MT version for me. It either hangs at 0% loading screen or it crashes at around 10-13%. Edit: Tried the single-threaded DCS.exe (with OpenVR and OpenXR) and everything works fine. No flickering, no stutters - actually a similar performance as with the MT version, so... I'll wait then I guess for a hotfix. Pro- Tip: don't release a patch with major changes on a Friday dcs_log.zip
  9. Thanks for the quick response. Really enjoying the campaign, great atmosphere
  10. Bug #1 As soon as the TILS becomes active (light on the panel) the game doesn't respond to joystick button input anymore. After landing everything is fine again. Repro steps: 1. Instant Action -> AJS37 -> Cold Start 2. Startup plane (manual or auto), takeoff and fly for about 40km 3. Select L1 and set mode to landing nav, turn around to airport 4. Set TILS selector do desired channel 5. As soon as the TILS light comes on, button input is ignored and only joystick axii are working 6. After touchdown observe that buttons are responsive again Bug #2 Game crashes instantly when pressing "Autothrottle disconnect / IR-missile fast select" on joystick/throttle. Crash reports sent. EDIT: Damn, wrong link opened :( Can a moderator please move this to the appropriate sub-forum, I'm sorry.
  11. That error comes up, if you install the "old" shader mod.Please refer to Pac_Man's post above on how to install it. https://forums.eagle.ru/showpost.php?p=4209331&postcount=981 Haven't really checked the numbers, the fix is more like a band aid made out of dirty cloth ;) Hopefully someone more clever than me and with a lot more insight into the DCS rendering process will create a working solution. But I never used the shader mods from this thread, only from the YT link so my fix is based on that. Maybe the mods from here were better in the first place - but not IC compliant. Here is the list of changes I've made. Compose.fx: line 22: + #include "_HMD.hlsl" line 87: + discardHmdMask(i.pos.xy, getBufferSize(StencilMap)); line 136: + discardHmdMaskMSAA(i.pos.xy, getBufferSize(StencilMap)); bloom.fx: line 5: + #include "deferred/luminance.hlsl" line 46: * getAvgLuminance() -> getAvgLuminanceClamped() grass2.fx: line 69: + float TerrainContext_seaLevel; Tonemap.fx: line 78: * getAvgLuminance() -> getAvgLuminanceClamped() water.fx: removed completely and replaced with the one from OB.
  12. I've updated the zip. It now contains the complete Mod that I use here with JSGME. (Original source: ) https://drive.google.com/file/d/1mjBR_ilBbmjacKxH3_2DBBPdYrfBNVqR/view?usp=sharing Please make sure to apply this ONLY to a clean DCS installation.
  13. I have fixed mine, but it's based on the shaders from here: (link in the description) https://drive.google.com/file/d/1mjBR_ilBbmjacKxH3_2DBBPdYrfBNVqR /view?usp=sharing
  14. One of the few useful Combined Arms tutorials out there. Thank you very much for that.
×
×
  • Create New...