Jump to content

noknees

Members
  • Posts

    3
  • Joined

  • Last visited

About noknees

  • Birthday 04/13/1971

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Do you know what. That worked!! I had dcs and my saved games folder excluded from the anti virus, but I use a shadow save games folder which points to the system drive, but is re-located to F:. Only the f drive location was excluded. Once I excluded both locations, bingo, normal load times. Many thanks
  2. I dont recall It being discussed as a major issue but I was wondering if anybody else out there suffers from extremely long shader compilation waits when loading into missions? I have a very fast system ( ryzen 7900x3d, 64gn ram, 4090 ) and when I load a mission or scenario for the first time the loading screen will freeze often for 5 minutes or so, before eventually starting the mission, then often it will take several more minutes for all of the correct textures to draw in before becoming playable. Next time I load that mission, it loads and starts quickly in 20 seconds or so. If I change anything, or even reboot my pc it seems, I'm back to square one and I have to recompile next time I play. None of this would be so awful, if while it happened you were given some information on the process but instead it just looks like a crash with a frozen view in the headset until its done. Also, sometimes it just doesn't come back and genuinely has crashed. I'm using a quest pro via Virtual Desktop or over the link cable and get the same issue with both. Just wondering if its unique to me - and maybe something I can fix, or if its a common thing that we all just have to live with?
  3. Just in case anybody hasnt found it, 'Sandboxcode' has been kind enough to compile a replacement DLL that points to the renamed DCS https://drive.google.com/file/d/1KgQfV73_xPjVoVZMW9nwzrNT3fKcDAyu/view Haven't tested it yet but folks are reporting it works
×
×
  • Create New...