Jump to content

Invisibull

Members
  • Posts

    599
  • Joined

  • Last visited

2 Followers

Personal Information

  • Location
    NYC

Recent Profile Visitors

21558 profile views
  1. When not caged, my understanding is that the dial should move to reflect the range to a target based on radar returns. I've messed around with this for an hour and have yet to see the dial move off of 1800'. When I cage it, it goes right to 600', but right back to 1800' when uncaged again, regardless of how far away the target is.
  2. Support Ticket #143755 was put in on 8/27 and so far I've been asked to check a bios setting to see if my RAM was being overclocked (it wasn't). Very disappointing to be completely ghosted by ED on this issue.
  3. I'm still getting this crash, but never when using the non-MT .exe. I have reinstalled DCS from scratch am using no scripts or mods, and I have done tests on my memory and it is fine. Could someone please help? I've attached the latest DCS.log and here is the Windows Crash Report from the Event viewer: Faulting application name: DCS.exe, version: 2.8.8.43704, time stamp: 0x64e3b9dd Faulting module name: VCRUNTIME140.dll, version: 14.34.31938.0, time stamp: 0x023b235f Exception code: 0xc0000005 Fault offset: 0x000000000000165e Faulting process id: 0x4e38 Faulting application start time: 0x01d9d62a3dcb6612 Faulting application path: D:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin-mt\DCS.exe Faulting module path: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll Report Id: d8dd710f-9880-4cdb-a0d4-5a185a6ec61c Thx dcs.log-20230824-013901.zip
  4. Thx for your reply. I've come to discover that the crash doesn't happen when I'm not using the MT exe. Further, even while using the MT exe it only seems to happen in that particular mission so far. Incidentally, those script errors have been coming up for years in some cases and have never manifested in any noticeable way in the game environment; I don't think they are involved at all. Thx again.
  5. Aircraft used here is an F-16 in MP. Please find relevant logs attached. Thx. null dcs.log-20230606-193242.zip
  6. Yesterday's update has resolved this issue. Thx for all your help, @c0ff
  7. I've always run all DCS.exe's as admin and there is no Debugging Tools folder, so I'm still feeling the pain over here.
  8. I should add that the server will run, but that it takes 3 or 4 hours of "loading" before it will. This was the case even before the hotfix and before I updated Windows.
  9. Trying that now. Thx. I'll report back here when done.
  10. I guess the fix wasn't so hot. So, we wait until the next update and hope for the best?
  11. @BIGNEWY Today's hotfix had no effect on my issue. The DCS Log is exactly the same and the DCS server is still stuck in the loading screen.
  12. Hi, I started by doing all the things you've suggested plus a system restore and none of it helped. I then did a full uninstall, deleted all folders associated with DCS, including the DCS folder within my saved games folder and then did a reinstall from scratch. None of that changed anything either. As far as a "full" log - I provided the entire log in my first post. I'd imagine its brevity is due to the fact that DCS hangs up before a longer log can be generated. DCS is running fine on my PC, but I haven't been able to host a server using the dedicated executable on my server PC since the update.
×
×
  • Create New...