Jump to content

enjOy

Members
  • Posts

    9
  • Joined

  • Last visited

Everything posted by enjOy

  1. Yes, the issues started with 2.9. I was looking to upgrade to a 6650XT, I'll see if I can borrow a different card. If the issue is lack of video memory, maybe I'll have to reach for something bigger
  2. Yup, I was doing some config work to figure out if there was any combination of settings that would make multiplayer playable for me, so I launched the game several times. And like clockwork, if the shaders folder has anything on it, the game freezes and/or crashes at the same spot.
  3. Nah, if I dont clean fxo and metashaders before launching the game crashes. One more info regarding the solution. It fixes the single thread client. MT still has the same isssue. And multiplayer performance is down the tubes
  4. Yup. That does it. I'll figure out a way to automate clearing the fxo and metashaders folder before launching the game
  5. Interesting, probably the ram issue could be from me overclocking it? No other games show any kind of fault. Repair install didnt help, but I'll follow along the RAM issue track. I'll update this post once i have test results. edit: Memtest86 says my RAM is all good, no errors. Slow repair to installation still no good. Researching for further clues on the DLL crashing.
  6. As the title says, on a fresh install and with official modules only, the game crashes to desktop or freezes on loading, specifically when the loading bar says "Visualizer Start Simulation". Specs: AMD Ryzen 5 5500 @ 4.5Ghz 32gb Ram @ 3200Mhz Nvidia 2060 6Gb 64gb swap file Game installed on an M.2 drive (Corsair MP600 pro) Running on MT client. dcs.log-20231224-185434.zip dcs.log-20231224-185417.zip dcs.log-20231224-185438.zip dcs.20231224-185438.dmp dcs.log-20231224-185436.zip dcs.20231224-185438.crash dcs.log dcs.log.old
  7. Bumping as I found a solution for my particular problem: It had to do with fiddling with UDP burst rates and UDP connection timeouts in my firewall.
  8. Yes, no effect. All services are allowed outbound on my firewall. Also tried install repairs and full reinstalls to no effect. Will try to update Windows 10. As mentioned, last open beta version worked fine.
  9. I have a similar issue, except the client just hangs in the "loading..." screen (the one before displaying the loading bar) for a while then the screen gets black. The only lines in the log that smell of anything are the following: 2023-06-17 23:41:40.818 INFO ASYNCNET (Main): disconnected: 5 Server ping timeout 2023-06-17 23:41:40.821 INFO ASYNCNET (Main): disconnected from server 2023-06-17 23:41:40.875 INFO ASYNCNET (Main): client has stopped I have all services greenlit outbound in my firewall. This has been an issue since the last open beta update (2.8.6.41066) dcs.log
×
×
  • Create New...