Mission Editor Meltdown When it Cannot Find a Resource

[Rex]

I just had the Mission Editor CTD twice, taking all of my unsaved work with it, when I tried to load a Static Unit from a Mod (possibly the VPC Field Equipment Mod).  It feels like you'd just get a "resource cannot be loaded" message while it continues on it's way.

To be clear, it DOES write the "resource cannot be loaded" message in a popup, but it then panics, aborts the app, then tries to write a dump.

In fact, I managed to get a video of the exact moment DCS realizes it cannot find the resource I have specified:

 

 

I can't say for sure, but it might be a slight overreaction?

 

2025-01-10 09:42:46.034 WARNING VISUALIZER (9308): terrainSampleOptions aren't set for DemoScene with terrain rendering
2025-01-10 09:42:46.037 INFO    EDTERRAIN4 (27420): ITerrainContextImpl4::setTrafficDecimation(1)
2025-01-10 09:42:46.037 INFO    EDTERRAIN4 (27420): ITerrainContextImpl4::setDate( day=1, month=10)
2025-01-10 09:42:46.037 INFO    EDTERRAIN4 (27420): ITerrainContextImpl4::setTextureMode(full=1)
2025-01-10 09:42:46.043 INFO    EDTERRAIN4 (29956): ITerrainContextImpl4::setTrafficDecimation(1)
2025-01-10 09:42:46.043 INFO    EDTERRAIN4 (29956): ITerrainContextImpl4::setDate( day=1, month=10)
2025-01-10 09:42:46.043 INFO    EDTERRAIN4 (29956): ITerrainContextImpl4::setTextureMode(full=1)
2025-01-10 09:42:46.399 WARNING VISUALIZER (9308): terrainSampleOptions aren't set for DemoScene with terrain rendering
2025-01-10 09:42:46.403 WARNING SCENE (9308): Scene was removed with 1 alive objects
2025-01-10 09:42:46.408 WARNING VISUALIZER (9308): terrainSampleOptions aren't set for DemoScene with terrain rendering
2025-01-10 09:42:46.524 WARNING SCENE (9308): Scene was removed with 1 alive objects
2025-01-10 09:42:46.526 WARNING VISUALIZER (9308): terrainSampleOptions aren't set for DemoScene with terrain rendering
2025-01-10 09:42:57.532 INFO    DX11BACKEND (4564): Compile shader: model/fake_omni_lights.fx:DIRECTX11=true;USE_DCS_DEFERRED=1;
2025-01-10 09:42:57.532 ERROR   EDCORE (4564): Can't open file: /shaders/model/fake_omni_lights.fx.
2025-01-10 09:42:57.573 INFO    DXGUI_WIN_ADAPTER (Main): resize main window to [0, 0]
2025-01-10 09:43:06.306 ERROR   EDCORE (4564): Can't open file: /shaders/model/fake_omni_lights.fx.
2025-01-10 09:43:06.342 INFO    DXGUI_WIN_ADAPTER (Main): resize main window to [5120, 1440]
2025-01-10 09:43:06.380 INFO    DXGUI_WIN_ADAPTER (Main): resize main window to [0, 0]
2025-01-10 09:43:07.285 ERROR   EDCORE (4564): Can't open file: /shaders/model/fake_omni_lights.fx.
2025-01-10 09:43:07.317 INFO    DXGUI_WIN_ADAPTER (Main): resize main window to [5120, 1440]
2025-01-10 09:43:07.353 INFO    DXGUI_WIN_ADAPTER (Main): resize main window to [0, 0]
2025-01-10 09:43:09.902 INFO    DXGUI_WIN_ADAPTER (Main): resize main window to [5120, 1440]
2025-01-10 09:43:09.965 INFO    EDCORE (Main): try to write dump information

 

Edited January 10 by Rex

[Rudel_chw]

1 hour ago, Rex said:

possibly the VPC Field Equipment Mod

 

yes, this error points to an incorrect mod install

 

Can't open file: /shaders/model/fake_omni_lights.fx.

[rob10]

Was going to suggest that would be the likely error.  If you use any of the lights in VPC it causes a crash in the background.  Fortunately the fix is very easy.  In that folder duplicate the fake_omni_lights2.fx and fake_spot_lights2.fx and rename the copy to take out the 2 and it will work fine.  I think something changed in base DCS over time and maybe the mod hasn't been updated.  Note that because that's in core files, the copied files will likely get deleted at some point (esp. if you do a repair).

[Rex]

Thanks very much!  That seems to have helped!