Anyone Having Issues Starting OpenBeta?

When I launch DCS, 3 out of 4 times it brings up the Splash screen, then does nothing. I'll wait for 5-10 minutes sometimes, but nothing happens. DCS shows in task manager but it's not creating any load, and that's it.

So, I'll kill it then try again, and again, and eventually, it starts up.

It's like there's some weird race condition or something that makes launching the game a type of roulette.

Logs are of no help unfortunately. Unless the negative one's are diagnostic.

=== Log opened UTC 2020-07-06 05:41:02

2020-07-06 05:41:02.756 INFO DCS: Command line: "C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe" --force_disable_VR

2020-07-06 05:41:02.756 INFO DCS: DCS/2.5.6.50979 (x86_64; Windows NT 10.0.18363)

2020-07-06 05:41:02.756 INFO DCS: DCS revision: 170977

2020-07-06 05:41:02.756 INFO DCS: Renderer revision: 20606

2020-07-06 05:41:02.756 INFO DCS: Terrain revision: 20611

2020-07-06 05:41:02.756 INFO DCS: CPU cores: 8, threads: 16, System RAM: 65446 MB, Pagefile: 0 MB

2020-07-06 05:41:02.902 INFO EDCORE: (dDispatcher)enterToState_:0

2020-07-06 05:41:02.907 INFO Dispatcher: 2020/7/5 22:41 V1803061700

2020-07-06 05:41:02.924 INFO INPUT: Device [Keyboard] created deviceId = -1

2020-07-06 05:41:02.927 INFO INPUT: Device [F16 MFD 1 {FD68A650-4940-11ea-8001-444553540000}] created deviceId = -1

2020-07-06 05:41:02.927 INFO INPUT: Joystick created[F16 MFD 1 {FD68A650-4940-11ea-8001-444553540000}], ForceFeedBack: no

2020-07-06 05:41:02.933 INFO INPUT: Device [Throttle - HOTAS Warthog {5868FB40-00E4-11ea-8001-444553540000}] created deviceId = -1

2020-07-06 05:41:02.933 INFO INPUT: Joystick created[Throttle - HOTAS Warthog {5868FB40-00E4-11ea-8001-444553540000}], ForceFeedBack: no

2020-07-06 05:41:02.940 INFO INPUT: Device [Joystick - HOTAS Warthog {BC60AE20-FDA3-11e9-8001-444553540000}] created deviceId = -1

2020-07-06 05:41:02.940 INFO INPUT: Joystick created[Joystick - HOTAS Warthog {BC60AE20-FDA3-11e9-8001-444553540000}], ForceFeedBack: no

2020-07-06 05:41:02.941 INFO INPUT: Device [F16 MFD 2 {08B20DD0-4941-11ea-8002-444553540000}] created deviceId = -1

2020-07-06 05:41:02.941 INFO INPUT: Joystick created[F16 MFD 2 {08B20DD0-4941-11ea-8002-444553540000}], ForceFeedBack: no

2020-07-06 05:41:03.078 INFO INPUT: Device [Thrustmaster T300RS Racing Wheel {A78D6780-FCF5-11e9-8001-444553540000}] created deviceId = -1

2020-07-06 05:41:03.082 INFO INPUT: Joystick created[Thrustmaster T300RS Racing Wheel {A78D6780-FCF5-11e9-8001-444553540000}], ForceFeedBack: yes, guidFFDriver: {7EC33D90-19CE-434e-8061-E2F879E204DE}

2020-07-06 05:41:03.083 INFO INPUT: Device [TPR T.Pendular Rudder {7A6B9B10-12E3-11ea-8001-444553540000}] created deviceId = -1

2020-07-06 05:41:03.083 INFO INPUT: Joystick created[TPR T.Pendular Rudder {7A6B9B10-12E3-11ea-8001-444553540000}], ForceFeedBack: no

2020-07-06 05:41:03.093 INFO INPUT: Device [Mouse] created deviceId = -1

2020-07-06 05:41:03.131 INFO SOUND: Using driver: wasapi

(just waits here forever)

Specs:

i9-9900K

64GB DDR4

2080Ti 11GB

ASUS Hero XI Wi-Fi

1TB Samsung EVO Plus NVME Drive + 4TB Spinner (ALL DCS stuff on nvme)

Hotas Warthog + Throttle + TPR Pedals + 2MFD Pack from TM

I buy my stuff directly from ED and not Steam (although Steam is installed)m and don't have Steam running when I use DCS.

If anyone has any idea what might be happening, I'd appreciate any info.

Thanks,

Rex

BTW, it does this whether I use VR or Track IR

When I launch DCS, 3 out of 4 times it brings up the Splash screen, then does nothing. I'll wait for 5-10 minutes sometimes, but nothing happens. DCS shows in task manager but it's not creating any load, and that's it.

 

 

=== Log opened UTC 2020-07-06 05:41:02

2020-07-06 05:41:02.756 INFO DCS: Command line: "C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe" --force_disable_VR

2020-07-06 05:41:02.756 INFO DCS: DCS/2.5.6.50979 (x86_64; Windows NT 10.0.18363)

2020-07-06 05:41:02.756 INFO DCS: DCS revision: 170977

2020-07-06 05:41:02.756 INFO DCS: Renderer revision: 20606

2020-07-06 05:41:02.756 INFO DCS: Terrain revision: 20611

2020-07-06 05:41:02.756 INFO DCS: CPU cores: 8, threads: 16, System RAM: 65446 MB, Pagefile: 0 MB

 

 

Specs:

 

i9-9900K

64GB DDR4

2080Ti 11GB

 

ASUS Hero XI Wi-Fi

 

1TB Samsung EVO Plus NVME Drive + 4TB Spinner (ALL DCS stuff on nvme)

Hotas Warthog + Throttle + TPR Pedals + 2MFD Pack from TM

I know I will probably get my head ripped off for even suggesting this, but try enabling the WINDOWS PAGEFILE, I know you have a lot of ram, but depending on what expert you care to take advice from, running with no PAGEFILE is not considered good practice by some, just increase it and see if it makes any difference to the DCS startup.

Cheers, Ian.

Maybe too obvious, but did you try cleanup/repair?

Thanks guys, will try. I disabled Pagefile on purpose since I have 64GB of RAM and don't like unnecessary write cycles on my SSD (and putting it on the spinner is too slow).

That said, I am a Unix/Linux guy and purchased a Win10 machine 8 months ago solely for playing DCS and a couple of other games/sims (and for running large-ish VMs). In general, I am very much not a fan of the OS, but begrudgingly use it as a necessary evil for certain things. Linux is fine running w/out swap so long as memory is sufficient, so for better or worse, that's my frame of reference.

If there's a chance that it needs a pagefile for whatever reason, I'll give it a shot.

For this trial, I suppose I should "Let Windows Manage" the size? (shudders)

Will also try the other suggestions.

Thanks for the feedback!

Unfortunately, swap was not the problem

I found something in the Windows Application Logs.

What's odd is that this is completely intermittent. This morning, it started 3 times in a row without issue, then failed 2 times, then worked once, then failed 4 times.

I do have a swap file running now.

Fault bucket , type 0

Event Name: APPCRASH

Response: Not available

Cab Id: 0

 

Problem signature:

P1: DCS.exe

P2: 2.5.6.50979

P3: 5ee8ccb3

P4: DCS.exe

P5: 2.5.6.50979

P6: 5ee8ccb3

P7: c0000005

P8: 0000000000791531

P9:

P10:

 

Attached files:

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2E8C.tmp.WERInternalMetadata.xml

 

These files may be available here:

\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_DCS.exe_e2bcec970d8cf9ee268d07bb4f9e2820fc3c3f_a8c78e39_62131301-e970-45c9-a401-b6cef2ae10b8

 

Analysis symbol:

Rechecking for solution: 0

Report Id: a3f54556-1e0d-4588-bcb3-d09f0c68fb4b

Report Status: 100

Hashed bucket:

Cab Guid: 0

I think it's a race for creation of one of the temp files