Jump to content

Recommended Posts

Installed 2.1 and it didn't show the two Normandy things available, though the game did launch to the main start screen. So I then did the update trick to force it to install Normandy and the WWII assets. On first launch after that it asked me for a serial number for the assets, so I entered it. The launch screen showed up with a spinner... turns out it was waiting for the second serial number, but nothing I did would put that window on top of the full-screen splash screen for DCS. So I killed DCS. The second serial number window was still there (for the Normandy map), so I entered it there. Then manually re-launched DCS... the same spinner (and the same second serial number entry screen), so I killed it again. Now it just crashes on launch (I get the loading progress bar, then boom).

 

FYI. Re-downloading and re-installing everything now. I'm planning to do Nevada first and launch, then the Normandy pieces one at a time. We'll see... the re-download should only take a couple of days.

System Specs: Origin PC Genisis; Core i7 6950; 64 GB Corsair Dominator Platinum; Windows 10 Pro; 2x NVidia GTX 1080 Ti (SLI); Boot drive Intel 750 1.2 TB PCIe SSD; Game drive 4 TB Samsung 850 Evo SSD; Warthog; Dell UP 3216Q; Liquid Cooling

Link to post
Share on other sites

Have similar issue with Normandy map, it's listed in terrains and ticked OK but map isn't available in Instant Action.

 

Just going to tinker around and see if I can get working,... be back.

 

<edit>

 

The Normandy Map is available in "Fast Mission" in the advanced settings panel but if you select it there is no map preview it will not generate a mission.

 

DCS also lists it and the Asset Pack as installed at the home screen v-strange.


Edited by FragBum
<edit>

Control is an illusion which usually shatters at the least expected moment.

Gazelle Mini-gun version is endorphins with rotors. See above.

 

Currently rolling with a Asus Z390 Prime, 9600K, 32GB RAM, SSD, 2080Ti and Windows 10Pro, Rift CV1. bu0836x and Scratch Built Pedals, Collective and Cyclic.

Link to post
Share on other sites

Same issue, but after I log in after the reinstall, exit, then launch the game again it just crashes with an issue in ed_sound (posted in another thread where someone else is having the same issue). Can't really do anything with the current update, and I've spent a couple of days trying.

System Specs: Origin PC Genisis; Core i7 6950; 64 GB Corsair Dominator Platinum; Windows 10 Pro; 2x NVidia GTX 1080 Ti (SLI); Boot drive Intel 750 1.2 TB PCIe SSD; Game drive 4 TB Samsung 850 Evo SSD; Warthog; Dell UP 3216Q; Liquid Cooling

Link to post
Share on other sites

Have you tried the dcs_updater command line utility?

 

https://forums.eagle.ru/showthread.php?t=114030

Control is an illusion which usually shatters at the least expected moment.

Gazelle Mini-gun version is endorphins with rotors. See above.

 

Currently rolling with a Asus Z390 Prime, 9600K, 32GB RAM, SSD, 2080Ti and Windows 10Pro, Rift CV1. bu0836x and Scratch Built Pedals, Collective and Cyclic.

Link to post
Share on other sites

I've used the updater; I'm on the very latest NVidia drivers (WHQL); I updated my Realtek sound drivers to the latest version as well. The crashes still occur... the worst is that now the game just won't get past the splash screen. I've also zapped my Saved Games folder more times that I can count. Sometimes that let's me launch the game, sometimes (now) no.

 

Logs attached...

 

Thanks for any help!

Logs.zip

System Specs: Origin PC Genisis; Core i7 6950; 64 GB Corsair Dominator Platinum; Windows 10 Pro; 2x NVidia GTX 1080 Ti (SLI); Boot drive Intel 750 1.2 TB PCIe SSD; Game drive 4 TB Samsung 850 Evo SSD; Warthog; Dell UP 3216Q; Liquid Cooling

Link to post
Share on other sites

please run:

DCS_Updater.exe clean

 

then

DCS_Updater.exe repair

 

and try again.

 

00016.876 DEBUG LuaGUI: ERROR: safeDoFile() file not found! can't open 'C:\Users\Roger\Saved Games\DCS.openalpha\MissionEditor/optionsLogin.lua'

Windows 10 Pro, Ryzen 2700X @ 4.6Ghz, 32GB DDR4-3200 GSkill,

X470 Taichi Ultimate, 2x R7970 Lightnings Crossfired @ 1.1/6.0GHz,

3x ASUS VS248HP + Hanns·G HZ201HPB + Oculus HMD,

Thrustmaster Warthog HOTAS + MFDs, CH Fighterstick+Pro Throttle+Pro Pedals

Link to post
Share on other sites

I get a dialog on the clean command that says "Unknown command: clean"

 

The repair works fine (from the bin directory).

 

Here's a new log set. I rebooted, started with no DCS.openalpha directory, successfully launched, logged in, exited, then tried to re-launch and it dies as in these logs...

 

Thanks!

 

... also, for what it's worth, I never had trouble launching before the 2.1 update, and 1.5.6 works fine all the time. I did have the intermittent crash-on-mission-end on 2.0.x, which I still have when I can manage to launch 2.1

 

Update: I did run clean from the DCS Updater Utility, followed by a repair. Still crashing on launch (same as previous crashes).

Logs.zip


Edited by hedrums

System Specs: Origin PC Genisis; Core i7 6950; 64 GB Corsair Dominator Platinum; Windows 10 Pro; 2x NVidia GTX 1080 Ti (SLI); Boot drive Intel 750 1.2 TB PCIe SSD; Game drive 4 TB Samsung 850 Evo SSD; Warthog; Dell UP 3216Q; Liquid Cooling

Link to post
Share on other sites

Ran with cleanup and then repair, and it ran once and crashed on mission exit (same crash). Then it wouldn't launch again. The error is intermittent. I can't pin down what "resets" it to get it work (launch) again. Even blowing away save games doesn't help every time.

 

I agree it's weird. I've run several stability (CPU & memory) tests and they all pass with flying colors. I also do 3D rendering on this system using VRay (the longest ran something like 35 hours), pinning all CPUs at 100% for the entire time with no issues and using lots of RAM. All other games are happy as clams, including 1.5.6 of DCS. In searching the forums, I note that I'm not the only one that's ever reported this issue. I'm going to guess it's not my hardware, but it's tough to prove.

 

And the offset in ed_sound.dll is 100% consistent -- which one would not necessarily expect in a CPU/RAM instability case.

 

Any, I know it's Alpha (I'm a SW engineer), so let me know what I can do to help diagnose it.

 

Cheers.


Edited by hedrums

System Specs: Origin PC Genisis; Core i7 6950; 64 GB Corsair Dominator Platinum; Windows 10 Pro; 2x NVidia GTX 1080 Ti (SLI); Boot drive Intel 750 1.2 TB PCIe SSD; Game drive 4 TB Samsung 850 Evo SSD; Warthog; Dell UP 3216Q; Liquid Cooling

Link to post
Share on other sites

Crashes with Debug ed_sound.dll

 

Attached are logs from a debug version of ed_sound.dll

 

Cheers!

Logs.zip

System Specs: Origin PC Genisis; Core i7 6950; 64 GB Corsair Dominator Platinum; Windows 10 Pro; 2x NVidia GTX 1080 Ti (SLI); Boot drive Intel 750 1.2 TB PCIe SSD; Game drive 4 TB Samsung 850 Evo SSD; Warthog; Dell UP 3216Q; Liquid Cooling

Link to post
Share on other sites

It's the on-board Asus ROG V 10th Anniversary edition sound. Realtek makes the drivers, which I've tried updates for (no difference among versions). Pretty standard stuff -- there's a digital out and an analog out (I use the latter).

 

No sound issues anywhere else (I've had the system about eight months now). The NVidia cards have HD audio, but I disabled that thinking it might be confusing DCS.

 

Hope that helps!

System Specs: Origin PC Genisis; Core i7 6950; 64 GB Corsair Dominator Platinum; Windows 10 Pro; 2x NVidia GTX 1080 Ti (SLI); Boot drive Intel 750 1.2 TB PCIe SSD; Game drive 4 TB Samsung 850 Evo SSD; Warthog; Dell UP 3216Q; Liquid Cooling

Link to post
Share on other sites

By the way, I suspect the device identifiers are odd because the current drivers are directly from Realtek (their latest), rather than the ones from Asus where they often customize such things. The previous drivers (from Asus) showed exactly the same crash.

System Specs: Origin PC Genisis; Core i7 6950; 64 GB Corsair Dominator Platinum; Windows 10 Pro; 2x NVidia GTX 1080 Ti (SLI); Boot drive Intel 750 1.2 TB PCIe SSD; Game drive 4 TB Samsung 850 Evo SSD; Warthog; Dell UP 3216Q; Liquid Cooling

Link to post
Share on other sites

One more interesting (to me) data point: if I "Uninstall" all audio devices, I can exit missions, restart the app, etc., with apparently no issues/crashes. Of course Windows doesn't like devices to be in the uninstalled state, so it helpfully reinstalls them when I reboot (which is kind of okay, since I like sound to work, generally).

 

There sure seems to be some weird interaction between DCS and the Realtek audio drivers. FYI.

System Specs: Origin PC Genisis; Core i7 6950; 64 GB Corsair Dominator Platinum; Windows 10 Pro; 2x NVidia GTX 1080 Ti (SLI); Boot drive Intel 750 1.2 TB PCIe SSD; Game drive 4 TB Samsung 850 Evo SSD; Warthog; Dell UP 3216Q; Liquid Cooling

Link to post
Share on other sites
  • 1 month later...

Update...

 

I got back to trying to see if there was a way to make it not crash, and I found threads on setting processor affinity (a couple of which specifically mention this same stack), so I gave it a try. No more crashes! I'll run for a few more days and see if I stay crash-free and report.

System Specs: Origin PC Genisis; Core i7 6950; 64 GB Corsair Dominator Platinum; Windows 10 Pro; 2x NVidia GTX 1080 Ti (SLI); Boot drive Intel 750 1.2 TB PCIe SSD; Game drive 4 TB Samsung 850 Evo SSD; Warthog; Dell UP 3216Q; Liquid Cooling

Link to post
Share on other sites
  • 3 weeks later...

Well, I'm surprised. Until I disabled Intel Turbo Boost Max 3.0, constant game crash after initial succesful game (2.1.1) start existed.

 

Always the same error

 

# -------------- 20170724-110853 --------------

# C0000005 ACCESS_VIOLATION at 00000000 00:00000000

00000000 00000000 0000:00000000

00000000 0014EF80 0000:00000000

1957E3E3 0014EFB0 0000:00000000 C:\Program Files\DCS World 2 OpenAlpha\bin\ed_sound.dll SND_del_wave_path()+3EA3

1957C1BE 0014F000 0000:00000000 C:\Program Files\DCS World 2 OpenAlpha\bin\ed_sound.dll SND_del_wave_path()+1C7E

1957C37D 0014F060 0000:00000000 C:\Program Files\DCS World 2 OpenAlpha\bin\ed_sound.dll SND_del_wave_path()+1E3D

195728D9 0014F0A0 0000:00000000 C:\Program Files\DCS World 2 OpenAlpha\bin\ed_sound.dll SND_context_qtree()+D9

19572AF3 0014F0F0 0000:00000000 C:\Program Files\DCS World 2 OpenAlpha\bin\ed_sound.dll SND_context_qtree()+2F3

19572BAC 0014F170 0000:00000000 C:\Program Files\DCS World 2 OpenAlpha\bin\ed_sound.dll SND_context_qtree()+3AC

19573077 0014F220 0000:00000000 C:\Program Files\DCS World 2 OpenAlpha\bin\ed_sound.dll SND_process()+447

0B6DC2F0 0014F280 0000:00000000 C:\Program Files\DCS World 2 OpenAlpha\bin\DCS.exe

0B382EED 0014F2B0 0000:00000000 C:\Program Files\DCS World 2 OpenAlpha\bin\DCS.exe

0B384759 0014F980 0000:00000000 C:\Program Files\DCS World 2 OpenAlpha\bin\DCS.exe

0B815DFF 0014F9C0 0000:00000000 C:\Program Files\DCS World 2 OpenAlpha\bin\DCS.exe

4F508364 0014F9F0 0000:00000000 C:\WINDOWS\System32\KERNEL32.DLL BaseThreadInitThunk()+14

4F8770D1 0014FA40 0000:00000000 C:\WINDOWS\SYSTEM32\ntdll.dll RtlUserThreadStart()+21

 

 

But now all that is gone and I can start and exit the DCS as I want.

 

Thanks hedrums, ED should give you free Hornet and make this fix into the front page.

 

 

-alt10k

 

Asus X99 Deluxe II|Intel i7 6850K @4.2GHz|G.Skill 64GB Trident Z DDR4 3200MHz|Noctua NH-D15 and 4x NF-A14 PWM|Corsair HX850i

Win10 Pro 64 @M.2 512GB 950 PRO|DCS @M.2 250GB 960 EVO

ASUS GTX 1070 STRIX OC 8GB GDDR5|ASUS PG348Q - LG 25UM58 @3440x2520

Corsair Strafe RGB MX Silent|TM Hotas Warthog 7.5cm ext & 3x MFD Cougars|MFG Crosswind|TrackIR 5

A-10C|AJS-37|AV-8B|BS2|F/A-18C|FC3|Mi-8MTV2|PG NE NO SY maps|Tacview.

 

Link to post
Share on other sites
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...