reported Steam DCS will not launch after latest update

[Clark88]

1 hour ago, BIGNEWY said:

Update to DCS open beta public version on steam as a work around

 

it seems steam have pushed the steam beta client to steam normal client creating problems for DCS stable users. 

 

Having same issue. Will test this workaround. Thanks

 

EDIT: Workaround worked.

Edited November 20, 2021 by Clark88

[BIGNEWY]

So to keep everyone up to date this is the situation.

Steam beta client was creating problems for DCS open beta.
We fixed open beta to work correctly with steam beta client.

today steam pushed the steam beta client to normal steam client,
this has created problems for DCS stable version.

Work around currently is to update to DCS open beta.
(the one in the betas tab that says public open beta with no numbers)

[Cutter]

So, first of all I'm glad I found this topic as I've had this issue appear last night; same as above - the "Can't run, Important files are damaged: Please, repair. Check dcs.log for details."

=== Log opened UTC 2021-11-21 15:10:34
2021-11-21 15:10:34.112 ALERT   SECURITYCONTROL: Can't run Steam!
2021-11-21 15:10:34.116 INFO    APP: Command line: G:\SteamLibrary\steamapps\common\DCSWorld\bin\DCS.exe
2021-11-21 15:10:34.116 INFO    APP: DCS/2.7.7.15038 (x86_64; Windows NT 10.0.19042)
2021-11-21 15:10:34.116 INFO    APP: Application revision: 195037
2021-11-21 15:10:34.116 INFO    APP: Renderer revision: 22490
2021-11-21 15:10:34.116 INFO    APP: Terrain revision: 22438
2021-11-21 15:10:34.116 INFO    APP: Build number: 687
2021-11-21 15:10:34.116 INFO    APP: CPU cores: 6, threads: 12, System RAM: 32694 MB, Pagefile: 8704 MB
=== Log closed.

Before reading this post I uninstalled DCS (except the Mods folder with it's 200GB of dlcs which would take me a day to download - I moved it before uninstalling via steam, then replaced it). I then re-installed with steam, which took several hours overnight. Trying to run DCS just now has given the same error messages.

Having read this post I was a bit confused, as I opted into the DCS Open Beta ages ago. But checking it again I find it is not selected - when did that happen? Is it automatically de-selected when the Stable release catches up with the Beta?

Well the 2GB of Beta has just downloaded... and it works!

Thank you ED.

[djjerryd]

Update to DCS open beta public version on steam as a work around

 

it seems steam have pushed the steam beta client to steam normal client creating problems for DCS stable users. 

 

I did that and it did not work for me. This is an issue that's giving me a headache. I'm putting in a ticket. 

[Treker]

Today's DCS update  fixed this issue.. at least for me  

Latest stable.

[Dodge]

I've noticed this happening to me since the introduction of MT (or thereabouts, but definitely since February)).
My workaround to date has been to 'reverify' the DCS files within the Steam client (Note: DCS = Open-Beta / Steam Client = Regular, but latest steam client (not beta).

However, I'm having to do this 'regularly' where it's becoming a frustration. I've copied the logs from the latest session below

=== Log opened UTC 2023-04-01 21:17:05
2023-04-01 21:17:04.905 ALERT   SECURITYCONTROL (Main): Can't run Steam!
2023-04-01 21:17:04.912 INFO    EDCORE (Main): system  affinity mask: 1111111111111111
2023-04-01 21:17:04.912 INFO    EDCORE (Main): process affinity mask: 1111111111111111
2023-04-01 21:17:04.912 INFO    EDCORE (Main): all CPU cores have the same efficiency class 0
2023-04-01 21:17:04.912 INFO    EDCORE (Main): common cores: {8, 9, 10, 11, 12, 13, 14, 15}
2023-04-01 21:17:04.912 INFO    EDCORE (Main): render cores: {0, 1, 2, 3, 4, 5, 6, 7}
2023-04-01 21:17:04.912 INFO    EDCORE (Main): IO cores: {}
2023-04-01 21:17:06.343 INFO    EDCORE (Main): Create boot pool.
2023-04-01 21:17:06.344 INFO    EDCORE (Main): Created boot pool: n:16
2023-04-01 21:17:06.344 INFO    APP (Main): Command line: "D:\Steam\steamapps\common\DCSWorld\bin-mt\DCS.exe" --force_OpenXR
2023-04-01 21:17:06.344 INFO    APP (Main): DCS/2.8.3.38090 (x86_64; MT; Windows NT 10.0.22621)
2023-04-01 21:17:06.344 INFO    APP (Main): Application revision: 218090
2023-04-01 21:17:06.344 INFO    APP (Main): Renderer revision: 23977
2023-04-01 21:17:06.344 INFO    APP (Main): Terrain revision: 23938
2023-04-01 21:17:06.344 INFO    APP (Main): Build number: 329
2023-04-01 21:17:06.344 INFO    APP (Main): CPU cores: 8, threads: 16, System RAM: 65450 MB, Pagefile: 4096 MB
=== Log closed.

 

[Added after posting]

Things to note, tested since posting....

1) I have a shortcut on the desktop for DCS (MT) (and non-MT)

2) If I run the shortcut without starting the Steam client the above issue 'can' occur. (Note: This is how I generally run DCS). As the error popped up, this time I then closed the error notification and started the Steam client. Once Steam started, I then ran DCS from the Desktop, however, the mouse in the menu wasn't working (also note: VR user, Reverb G2)

Could this be related to some form of DCS + Steam interaction not working well if calling DCS from the shortcut (exe) without the Steam client being loaded before? (Again, I've never encountered this issue before this year - after early January 2023).

3) Re-verified the integrity of the game files again, which will resolve the issue  (but once I try again at a later time the issue will reoccur)

 

 

Edited April 1, 2023 by Dodge

[Dodge]

 

It's reproduceable for me in that if I do the following then I have to re-validate my files

0) Start my HP Reverb G2 headset and any associated software that I plan on using (G2 headset and then VoiceAttack)
1) (Forget to start Steam (stable))
2) Start my 'shortcut' of DCS (MT)
3) Error appears that files are corrupted.
(Image of the message is included below)

==Log==

=== Log opened UTC 2023-04-10 17:04:57
2023-04-10 17:04:57.137 ALERT   SECURITYCONTROL (Main): Can't run Steam!
2023-04-10 17:04:57.143 INFO    EDCORE (Main): system  affinity mask: 1111111111111111
2023-04-10 17:04:57.143 INFO    EDCORE (Main): process affinity mask: 1111111111111111
2023-04-10 17:04:57.152 INFO    EDCORE (Main): all CPU cores have the same efficiency class 0
2023-04-10 17:04:57.152 INFO    EDCORE (Main): common cores: {8, 9, 10, 11, 12, 13, 14, 15}
2023-04-10 17:04:57.152 INFO    EDCORE (Main): render cores: {0, 1, 2, 3, 4, 5, 6, 7}
2023-04-10 17:04:57.152 INFO    EDCORE (Main): IO cores: {}
2023-04-10 17:04:58.603 INFO    EDCORE (Main): Create boot pool.
2023-04-10 17:04:58.603 INFO    EDCORE (Main): Created boot pool: n:16
2023-04-10 17:04:58.604 INFO    APP (Main): Command line: "D:\Steam\steamapps\common\DCSWorld\bin-mt\DCS.exe" --force_OpenXR
2023-04-10 17:04:58.604 INFO    APP (Main): DCS/2.8.3.38090 (x86_64; MT; Windows NT 10.0.22621)
2023-04-10 17:04:58.604 INFO    APP (Main): Application revision: 218090
2023-04-10 17:04:58.604 INFO    APP (Main): Renderer revision: 23977
2023-04-10 17:04:58.604 INFO    APP (Main): Terrain revision: 23938
2023-04-10 17:04:58.604 INFO    APP (Main): Build number: 329
2023-04-10 17:04:58.604 INFO    APP (Main): CPU cores: 8, threads: 16, System RAM: 65450 MB, Pagefile: 4096 MB
=== Log closed. 

 

Workaround/Or perhaps the way it should be done

0) Start my HP Reverb G2 headset and any associated software that I plan on using (G2 headset and then VoiceAttack)
1) Start the steam client (stable)
2) Start my 'shortcut' of DCS (MT)
3) DCS loads correctly

 

For me, its frustration; As I become older my memory doesn't always remind me to start the 'Steam' client before I run the 'DCS (MT)' shortcut, thus I run into the 'important files are damaged' message  - I then have to wait approximately 15mintes each time for the re-validation to complete.

 

@BIGNEWY - If there's anything else needed to have the team take a look at this (again) then let me know and I'll see if I can assist

Edited April 10, 2023 by Dodge

[BIGNEWY]

Thank you Paul for the post and for the discord DM.