solved Did a repair and now game crashes

[Double Dutch]

Hi, 

I did a repair yesterday and now my game crashes upon startup: DX11 Rederer error. Shader "/shaders/missioneditor/gui.fx failed to compile

Reason: WARNING x4717 followed by error X3004

If I look in my logs I see several errors:

024-01-15 13:51:30.487 ERROR   Scripting (Main): declare loadout fail, duplicate not allowed: "{LAU_SNEB68G}" from "./CoreMods/aircraft/SA342/SA342_Weapons.lua", original located here "./CoreMods/aircraft/AircraftWeaponPack/rockets.lua"
2024-01-15 13:51:30.487 ERROR   Scripting (Main): declare loadout fail, duplicate not allowed: "{LAU_SNEB68_WP}" from "./CoreMods/aircraft/SA342/SA342_Weapons.lua", original located here "./CoreMods/aircraft/AircraftWeaponPack/rockets.lua"

---

2024-01-15 13:51:34.930 INFO    VISUALIZER (Main): render thread initialization...
2024-01-15 13:51:34.935 INFO    GRAPHICSVISTA (20296): renderer: 'dx11backend.dll'
2024-01-15 13:51:35.055 INFO    DX11BACKEND (20296): DX11Renderer initialization (w:3440 h:1440 fullscrn:0 vsync:0 adapter:0 monitor:0 shaderErrors:1)
2024-01-15 13:51:35.335 INFO    DX11BACKEND (20296): Driver Concurrent Creates - 1
2024-01-15 13:51:35.335 INFO    DX11BACKEND (20296): Driver Command Lists - 1
2024-01-15 13:51:35.558 INFO    DX11BACKEND (20296): NVIDIA API init OK
2024-01-15 13:51:35.559 INFO    DX11BACKEND (20296): NVIDIA Display Driver Version 54633.r545_00
2024-01-15 13:51:35.559 INFO    DX11BACKEND (20296): GPU count:1
2024-01-15 13:51:35.629 INFO    DX11BACKEND (20296): commonPool: 48-128, cbPool: 4-14
2024-01-15 13:51:35.629 INFO    DX11BACKEND (20296): samplerPool: 5-16
2024-01-15 13:51:36.226 INFO    DX11BACKEND (20296): NVIDIA DLSS Minimum driver version was reported as : 445.0
2024-01-15 13:51:36.229 INFO    METASHADER (20296): Init filesystem: D
2024-01-15 13:51:36.254 INFO    DX11BACKEND (20296): DX11ShaderBinaries::loadCache Bazar/shaders/fxo/fxo
2024-01-15 13:51:37.209 ERROR   EDCORE (20296): Can't open file: /shaders/missioneditor/guiprimitives.hlsl.
2024-01-15 13:51:37.641 INFO    DX11BACKEND (20296): DX11ShaderBinaries::loadCache done. Loaded 2438/2439.
2024-01-15 13:51:37.650 INFO    DX11BACKEND (20296): DX11ShaderBinaries::loadCache C:\Users\rober\Saved Games\DCS\fxo
2024-01-15 13:51:37.706 INFO    DX11BACKEND (20296): DX11ShaderBinaries::loadCache done. Loaded 121/121.
2024-01-15 13:51:37.744 ERROR   EDCORE (20296): Can't open file: /shaders/missioneditor/guiprimitives.hlsl.
2024-01-15 13:51:37.744 INFO    DX11BACKEND (20296): Compile shader: missioneditor/gui.fx:DIRECTX11=true;USE_DCS_DEFERRED=1;
2024-01-15 13:51:37.746 ERROR   DX11BACKEND (20296): Can't open include file: /shaders/guiPrimitives.hlsl.
2024-01-15 13:51:37.746 ERROR   DX11BACKEND (20296): Shader "/shaders/MissionEditor/gui.fx" failed to compile. Reason:
warning X4717: Effects deprecated for D3DCompiler_47
D:\shaders\MissionEditor\gui.fx(263,30-62): error X3004: undeclared identifier 'gs_cicle'
2024-01-15 13:52:08.977 ERROR   DX11BACKEND (20296): Can't open include file: /shaders/guiPrimitives.hlsl.
2024-01-15 13:52:08.978 ERROR   DX11BACKEND (20296): Shader "/shaders/MissionEditor/gui.fx" failed to compile. Reason:
warning X4717: Effects deprecated for D3DCompiler_47
D:\shaders\MissionEditor\gui.fx(263,30-62): error X3004: undeclared identifier 'gs_cicle'

Any idea how to fix this?

[BIGNEWY]

please attach the full log as an attachment it will have more clues. 

but remove all unofficial mods.

run a slow repair

delete metashader2 and fxo folders in saved games dcs

ensure windows and dispaly drivers are up to date. 

thank you 

[Double Dutch]

26 minutes ago, BIGNEWY said:

please attach the full log as an attachment it will have more clues. 

but remove all unofficial mods.

run a slow repair

delete metashader2 and fxo folders in saved games dcs

ensure windows and dispaly drivers are up to date. 

thank you 

dcs.log.old

I added the files. I have no mods concerning planes or similar, I do have Reshade running, is that a mod too? Vaicom?

I have already run a slow repair 2 x.

Windows 11 and Nvidia Strix ROG RTX3080 drivers are up to date.

dcs.log-20240114-154048.zip dcs.log-20240114-154440.zip dcs.log-20240115-142043.zip

[BIGNEWY]

Thanks 

Errors
The Integrity Check failed
Delete all unofficial mods and do a slow repair of DCS.

There is a GPU-related error
(Re-)install the latest GPU drivers. Don't overclock your GPU or RAM.

The crash occurred inside GraphicsCore.dll.
Try a slow repair.
Delete Saved Games\DCS\fxo and metashaders2 and try again.
Next, delete %LOCALAPPDATA%\TEMP\DCS and try again.
Next, try renaming Saved Games\DCS to DCS.old ( keep as a backup ) and try again.
 

Stacktrace
(GraphicsCore):
render::RenderGraph::~RenderGraph + 0x4D8D
(GraphicsCore):
render::RenderGraph::bakeGraph + 0x2012
(GraphicsCore):
render::RenderGraph::bakeGraph + 0x18FE
(SceneRenderer):
DCSSceneRenderer::bakeRenderGraph + 0x3F
(Visualizer):
smCamera_Implement::getClipRegion + 0x1AA77
[...]

 

[Double Dutch]

1 hour ago, BIGNEWY said:

Thanks 

Errors
The Integrity Check failed
Delete all unofficial mods and do a slow repair of DCS.

There is a GPU-related error
(Re-)install the latest GPU drivers. Don't overclock your GPU or RAM.

The crash occurred inside GraphicsCore.dll.
Try a slow repair.
Delete Saved Games\DCS\fxo and metashaders2 and try again.
Next, delete %LOCALAPPDATA%\TEMP\DCS and try again.
Next, try renaming Saved Games\DCS to DCS.old ( keep as a backup ) and try again.
 

Stacktrace
(GraphicsCore):
render::RenderGraph::~RenderGraph + 0x4D8D
(GraphicsCore):
render::RenderGraph::bakeGraph + 0x2012
(GraphicsCore):
render::RenderGraph::bakeGraph + 0x18FE
(SceneRenderer):
DCSSceneRenderer::bakeRenderGraph + 0x3F
(Visualizer):
smCamera_Implement::getClipRegion + 0x1AA77
[...]

 

You know what is really, really strange? If I start a training and my Vaicom pro is on... crash, tested it yesterday 4 times, 2 times with Vaicom, 2 times without.

Today I tested again, without Vaicom, finished the training, all OK. Started with Vaicom on, DCS crashes. Start the training without Vaicom, turn Vaicom on 5 min into the training, crash.

 

And when I look at the log or crash files, they all point to graphics and as far as I know, Vaicom does nothing with graphics.

 

Edited January 15, 2024 by Double Dutch

[BIGNEWY]

is your vaicom up to date? 

 

[Double Dutch]

Yes, Downloaded, installed and configured it together with BionicRaven last week.

Maybe I should do a remove and reinstall of DCS, is there an instruction for that? What to save (saved games) so all setting, controls config, liveries, created missions stay intact?

About a year ago I did a complete new PC install due to new hardware and I just 'moved' the DCS folder back to the new SSD D drive and am playing it. Even though I can play, it might be better to start again from scratch (except for the settings).

Edited January 15, 2024 by Double Dutch

[MAXsenna]

Yes, Downloaded, installed and configured it together with BionicRaven last week.
Maybe I should do a remove and reinstall of DCS, is there an instruction for that? What to save (saved games) so all setting, controls config, liveries, created missions stay intact?
About a year ago I did a complete new PC install due to new hardware and I just 'moved' the DCS folder back to the new SSD D drive and am playing it. Even though I can play, it might be better to start again from scratch (except for the settings).

Rename your DCS folder under Saved Games to backup all settings. Then do a full slow repair of DCS. That's the same as a complete new install.
When you type that you "start" VAICOM, I assume you mean VoiceAttack, which then invokes the VAICOM plugin, but as you say. VAICOM shouldn't affect anything graphics related apart from the kneeboard and Jester wheel, which has been changed recently.

Sent from my SM-A536B using Tapatalk

[Double Dutch]

16 hours ago, MAXsenna said:

Rename your DCS folder under Saved Games to backup all settings. Then do a full slow repair of DCS. That's the same as a complete new install.
When you type that you "start" VAICOM, I assume you mean VoiceAttack, which then invokes the VAICOM plugin, but as you say. VAICOM shouldn't affect anything graphics related apart from the kneeboard and Jester wheel, which has been changed recently.

Sent from my SM-A536B using Tapatalk
 

The

 

22 hours ago, BIGNEWY said:

Thanks 

Errors
The Integrity Check failed
Delete all unofficial mods and do a slow repair of DCS.

There is a GPU-related error
(Re-)install the latest GPU drivers. Don't overclock your GPU or RAM.

The crash occurred inside GraphicsCore.dll.
Try a slow repair.
Delete Saved Games\DCS\fxo and metashaders2 and try again.
Next, delete %LOCALAPPDATA%\TEMP\DCS and try again.
Next, try renaming Saved Games\DCS to DCS.old ( keep as a backup ) and try again.
 

Stacktrace
(GraphicsCore):
render::RenderGraph::~RenderGraph + 0x4D8D
(GraphicsCore):
render::RenderGraph::bakeGraph + 0x2012
(GraphicsCore):
render::RenderGraph::bakeGraph + 0x18FE
(SceneRenderer):
DCSSceneRenderer::bakeRenderGraph + 0x3F
(Visualizer):
smCamera_Implement::getClipRegion + 0x1AA77
[...]

 

I do a slow repair and even though I don't play the open Beta, when he is done, the repair says Successfully repaired version 2.9.2.49940@openbeta.

Is repair repairing the right thing here?

[MAXsenna]

I do a slow repair and even though I don't play the open Beta, when he is done, the repair says Successfully repaired version 2.9.2.49940@openbeta.
Is repair repairing the right thing here?

Misplaced my spectacles, so can't read your log. Your log should tell you which version you have. Did you by chance upgrade Stable to OB at one point? If you use Skatezilla's tool, which I highly recommend, it will tell you what version, and you can easily swap between them.

Sent from my SM-A536B using Tapatalk

[Double Dutch]

9 minutes ago, MAXsenna said:

Misplaced my spectacles, so can't read your log. Your log should tell you which version you have. Did you by chance upgrade Stable to OB at one point? If you use Skatezilla's tool, which I highly recommend, it will tell you what version, and you can easily swap between them.

Sent from my SM-A536B using Tapatalk
 

Yes I did, a looong time ago. But after the hardware upgrade and moving DCS to it's own SSD drive, I only used the DCS.exe, and recently the DCS.exe in bin-mt

[MAXsenna]

Yes I did, a looong time ago. But after the hardware upgrade and moving DCS to it's own SSD drive, I only used the DCS.exe, and recently the DCS.exe in bin-mt

The name of the exe won't tell you which version it is. Right click it and select details. It seems you have multiple versions. Skatezilla's tool would help you in situations like this.

Sent from my SM-A536B using Tapatalk

[Double Dutch]

I have an open beta folder in my saved games, but I dont think I play the open beta. Where can I see what version I play?

[BIGNEWY]

36 minutes ago, Double Dutch said:

I have an open beta folder in my saved games, but I dont think I play the open beta. Where can I see what version I play?

can you attach your newest DCS log, it will have clues. 

thanks

[Double Dutch]

16 hours ago, BIGNEWY said:

can you attach your newest DCS log, it will have clues. 

thanks

dcs.log

024-01-15 16:56:32.393 INFO    APP (Main): Command line: "D:\DCS World\bin-mt\DCS.exe" 
2024-01-15 16:56:32.393 INFO    APP (Main): DCS/2.9.2.49940 (x86_64; MT; Windows NT 10.0.22621)
2024-01-15 16:56:32.393 INFO    APP (Main): Application revision: 229940
2024-01-15 16:56:32.393 INFO    APP (Main): Renderer revision: 24802
2024-01-15 16:56:32.393 INFO    APP (Main): Terrain revision: 24741
2024-01-15 16:56:32.393 INFO    APP (Main): Build number: 49

I see no reference to open beta other than in my username/saved games folder, there I have DCS and DCS.beta. When I do a slow repair, the end overview also mentions it repaired the open beta version (Successfully repaired version 2.9.2.49940@openbeta).

Edited January 19, 2024 by Double Dutch

[Insonia]

your F-18 files were corrupted.

IC fail
2024-01-15 16:57:42.472 WARNING SECURITYCONTROL (Main): IC fail: mods/aircraft/fa-18c/cockpit/scripts/device_init.lua
Sound file errors
2024-01-15 16:57:43.354 ERROR   SECURITYCONTROL (27804): Can't decompress file /sounds/1/Effects/Explosions/ExplodeHeavyDistant_3.wav.
2024-01-15 16:57:43.354 ERROR   ED_SOUND (27804): sf_open_virtual(/sounds/1/effects/explosions/explodeheavydistant_3.wav) failed: File contains data in an unknown format.
2024-01-15 16:57:43.354 ERROR   ED_SOUND (27804): can't load wave: "effects\explosions\explodeheavydistant_3"
Crashes
2024-01-15 17:06:08.596 ERROR   DX11BACKEND (32148): Failed assert `false && "failed to create texture"` at Projects\render\dx11backend_win8\Source\DX11TextureManager.cpp:696

 

 

Edited January 19, 2024 by Insonia

[Double Dutch]

6 minutes ago, Insonia said:

your F-18 files were corrupted.

IC fail
2024-01-15 16:57:42.472 WARNING SECURITYCONTROL (Main): IC fail: mods/aircraft/fa-18c/cockpit/scripts/device_init.lua
Shadar errors
2024-01-15 16:57:34.040 ERROR   EDTERRAINGRAPHICS41 (7584): metashaders/terrain/varyhouselight.fx
Sound file errors
2024-01-15 16:57:43.354 ERROR   SECURITYCONTROL (27804): Can't decompress file /sounds/1/Effects/Explosions/ExplodeHeavyDistant_3.wav.
2024-01-15 16:57:43.354 ERROR   ED_SOUND (27804): sf_open_virtual(/sounds/1/effects/explosions/explodeheavydistant_3.wav) failed: File contains data in an unknown format.
2024-01-15 16:57:43.354 ERROR   ED_SOUND (27804): can't load wave: "effects\explosions\explodeheavydistant_3"
Crashes
2024-01-15 17:06:08.596 ERROR   DX11BACKEND (32148): Failed assert `false && "failed to create texture"` at Projects\render\dx11backend_win8\Source\DX11TextureManager.cpp:696

 

I already ran repair, what else can I do?

dcs.log.old

this is the old log, I see so many errors on that too...

[Insonia]

the old log dont have any IC fail. dont have those specific sound fail loading error. dont have any reason why it fails.

those i mentioned only occur in your new log. you have more errors in new logs.

a lot of those default "error" that everybody has were normal log, ED probably need clean those up. those can be distracting.

Indeed, those did not make much sense.

i may suggest you scaning( chkdsk /F D: ) your file system first. 

after the scan the hard drive then do a slow repair( clean and repair ). 

Edited January 19, 2024 by Insonia

[Double Dutch]

No errors, 

5 minutes ago, Insonia said:

the old log dont have any IC fail. dont have those specific sound fail loading error. 

those i mentioned only occur in your new log. you have more errors in new logs.

a lot of those default "error" that everybody has were normal log, ED probably need clean those up. those can be distracting.

i may suggest you scaning( chkdsk /F D: ) your file system first. 

after the scan the hard drive then do a slow repair( clean and repair ). 

Checked and no issues. 

No report or anything to see what was repaired, can I see that anywhere? Some log somewhere?

[Insonia]

autoupdate_log.txt and autoupdate_log_old.txt in DCS world install folder should contain the update/install/repair info.

how is the hard disk / file system scan result?

normally repair game should fix the issue. But it keeps creating more errors i'm suspicious that you may have file system error as well. 

 

Edited January 19, 2024 by Insonia

[Double Dutch]

17 minutes ago, Insonia said:

autoupdate_log.txt and autoupdate_log_old.txt in DCS world install folder should contain the update/install/repair info.

how is the hard disk / file system scan result?

normally repair game should fix the issue. But it keeps creating more errors i'm suspicious that you may have file system error as well. 

 

 

checkdisk wat good, no issues

In the log it seemed to have fixed some FA18 files?

autoupdate_log.txt

[Insonia]

nope it just keeps reinstalling the same 5 unrelated files over and over and over again since Jan 14.

Quote

I do a slow repair and even though I don't play the open Beta, when he is done, the repair says Successfully repaired version 2.9.2.49940@openbeta.

but you were on openbeta channel. the stable should return 2.9.1.48335

i guess the DCS installation/update data (autoupdate.dat) is totally messed up? so it just cannot pick up the right file to compare? Maybe starting over is the correct choice.. 

Spoiler

here is hack that may work or not who knows. delete "autoupdate.dat". when you click repair again will force the updater to regenerate a new file database.  autoupdate_log.txt can increase to few mb big and every single file will be put back to "_downloads" to be scan and reinstalled.

 

[BIGNEWY]

check your antivirus and security is not creating a problem for DCS 

[Double Dutch]

6 minutes ago, BIGNEWY said:

check your antivirus and security is not creating a problem for DCS 

I have bitdefender, paused it and did another slow repair. See the log.autoupdate_log.txt

[Double Dutch]

15 minutes ago, Insonia said:

you didnt regenerate the "autoupdate.dat"? the updater  shows no file needs repair this time.

 

I didn't do anything other I just supplied the file again after the slow repair was done with bitdefender off.

The time stamp of the file is now 11:26, that is 20 min ago. It is resaved after the last repair.

ps. just to be sure I did a cleanup first and it is also shown in the log right before the repair.

pps. the log shows 10:26 but i think that is because of CET

Edited January 19, 2024 by Double Dutch