Jump to content

willymo

Members
  • Posts

    7
  • Joined

  • Last visited

  1. After more extensive testing yesterday, it does seem my issue is resolved. For now, anyway. Did a fresh install and redownloaded all my campaigns/missions. After taking so many steps it's hard to be sure what exactly fixed it - but it very well might've just been the particular mission files I was trying to use somehow became corrupt. Weird that it completely crashes the GPU driver. Perhaps a memory leak or something? Either way, it's working now. Thanks again for the support.
  2. Tonight I was doing a little test and I loaded into an empty Syria map and was able to load in and idle on the ground for several minutes in VR with no crashes. Hmm. So, this gave me the idea to redownload and load in a fresh version of one of the mission files I'd been flying on consistently for the past weeks, and it seems to be working. It seems as if corrupted miz files were possibly the culprit. Can't say 100% but it's a step in the right direction anyway. I'll continue testing with other missions and see if I experience any more issues. Appreciate the support.
  3. Okay, so just to be triple sure, I've: Factory reset my GPU and installed latest driver. Ensured there is no overclocking or any extra AMD options enabled at all. Updated Windows. Ran a DCS slow repair (for the 3rd time). There are zero mods or shaders or anything installed. Also, I made sure Hot Plug was turned off just to be sure. Unfortunately, still same results. Load in, start up, about 5 minutes in, CTD with AMD Driver Crash message. Here's the latest zip: dcs.log-20230509-203813.zip
  4. For whatever reason my Windows Updater did not run automatically as usual, and I found an update. I'll install this update and report back. No overclocking, and turned all the fancy AMD options off. There are no unofficial mods installed whatsoever.
  5. I haven't played any this weekend, but this just started happening today. Load mission, start up, just about to take off and CTD with AMD driver unresponsive error pop-up. No hint of struggle before crash, smooth fps, no stutters. I've been playing for several weeks without a crash up til now. I have updated all my drivers twice, ran DCS Slow Repair twice, backed up my Saved Games folder like 5 times today, and on the final one didn't import anything at all from backup. No mods installed. Same result every time, tested in both MT and ST, in both Steam VR and OpenXR. When I ran the same mission with same graphics in 2D, it ran seemingly fine, no crash, but tbh I didn't fly around for more than about 15 minutes. So possibly VR related? I looked around the log for the usual suspects but I'm at a loss this time. Thanks in Advance dcs.log-20230509-185239.zip
  6. I resolved this by setting Pixel Density to 1.0 in the DCS VR settings. If I used anything below that, it would show as you described with a VR view on my monitor. If I used a higher pixel density it skewed the perspective to be unplayable. Unfortunately PD 1.0 looks pretty bad for me and still a lot of lagginess on my G2.
×
×
  • Create New...