Explanations for various errors in dcs.log file

[dixtrian]

Hi everyone,

 

I saw that some errors in my dcs.log file.

Some about christen eagle is missng are ok because I don't own this plane.

But others for mig29 or mirage2000c are more curious for me.

 

I tried to delete folders containing *.edm files then repair DCS.

Worked in past, I was unable to join multiplayer because of a bad texture file that was not saw with the repair tool but worked after deleting file. But not in the present case.

 

If someone in the DCS community can explain how to fix this:

 

2019-01-27 09:43:50.308 INFO    DCS: DCS/2.5.4.26552 (x86_64; Windows NT 10.0.17134)
2019-01-27 09:43:50.383 INFO    DCS: DCS revision: 146545
2019-01-27 09:43:50.383 INFO    DCS: Renderer revision: 18383
2019-01-27 09:43:50.383 INFO    DCS: Terrain revision: 18529
2019-01-27 09:43:50.383 INFO    DCS: CPU cores: 4, threads: 8, System RAM: 16346 MB, Pagefile: 36826 MB
2019-01-27 09:43:56.208 ERROR   EDCORE: Can't mount coremods/aircraft/christen eagle ii/textures2. Drivers errors: 
2019-01-27 09:43:56.208 ERROR   EDCORE:     EDCDriver: there is no directory coremods/aircraft/christen eagle ii/textures2.edc
2019-01-27 09:43:56.208 ERROR   EDCORE:     FSDriver: there is no directory coremods/aircraft/christen eagle ii/textures2
2019-01-27 09:43:56.208 ERROR   EDCORE:     ZipDriver: Can't open zip archive coremods/aircraft/christen eagle ii/textures2.zip.
2019-01-27 09:43:58.936 ERROR   EDCORE: LoadLibrary failed for ./CoreMods/aircraft/Christen Eagle II/bin/CE2_AI.dll: (127) La procédure spécifiée est introuvable.
2019-01-27 09:43:58.936 ERROR   SECURITYCONTROL: Failed to load ./CoreMods/aircraft/Christen Eagle II/bin/CE2_AI.dll: La procédure spécifiée est introuvable.
2019-01-27 09:43:58.936 ERROR   WorldPlugIns: Can't load plugin module CE2_AI.dll
2019-01-27 09:44:04.811 ERROR   EDOBJECTS: Destruction shape not found AVIASHTAB_CRASH
2019-01-27 09:45:14.732 ERROR   EDCORE: Cant open file: /textures/liveries/mig-29a/33th iap wittstock ab (germany)/description.lua.
2019-01-27 09:45:14.737 ERROR   EDCORE: Cant open file: /textures/liveries/mig-29a/russia/description.lua.
2019-01-27 09:45:14.741 ERROR   EDCORE: Cant open file: /textures/liveries/mig-29a/standard/description.lua.
2019-01-27 09:45:15.258 ERROR   EDCORE: Cant open file: /models/m-2000c-cpt.edm.ilv.
2019-01-27 09:45:15.258 ERROR   VISUALIZER: ILV for cockpit 'M-2000C-CPT' not found
2019-01-27 09:45:15.386 ERROR_ONCE DX11BACKEND: Can't load 'Fonts/font_general_RU.dds' in texture array ''.
2019-01-27 09:45:15.697 ERROR   COCKPITBASE: indicators_keeper::link_all: unable to find link source 'FM_proxy' for indicator 12
2019-01-27 09:45:15.976 ERROR   SOUND: source_add(host:COCKPIT_2D, proto:MagicSeek, alt_proto:): can't find proto
2019-01-27 09:53:25.374 ERROR_ONCE DX11BACKEND: texture 'mig-29_tex03_spec' not found. Asked from 'NGMODEL'
2019-01-27 10:30:17.060 ERROR   EDCORE: Cant open file: /models/m-2000c-cpt.edm.ilv.
2019-01-27 10:30:17.060 ERROR   VISUALIZER: ILV for cockpit 'M-2000C-CPT' not found
2019-01-27 10:30:17.195 ERROR   COCKPITBASE: indicators_keeper::link_all: unable to find link source 'FM_proxy' for indicator 12
2019-01-27 10:30:17.223 ERROR   SOUND: source_add(host:COCKPIT_2D, proto:MagicSeek, alt_proto:): can't find proto
2019-01-27 10:34:12.646 ERROR_ONCE DX11BACKEND: texture 'mig-29_metal_spec' not found. Asked from 'NGMODEL'
2019-01-27 10:34:12.650 ERROR_ONCE DX11BACKEND: texture 'mig-29_nose_spec' not found. Asked from 'NGMODEL'
2019-01-27 10:34:12.654 ERROR_ONCE DX11BACKEND: texture 'mig-29_tex04_spec' not found. Asked from 'NGMODEL'
2019-01-27 10:59:22.980 ERROR   GRAPHICSVISTA: Can't open model M2KC-fragment-nose.

Regards

[Pikey]

There's always been many errors in the dcs.log, ever since I started to read it, many years ago. Errors in a log are common, the word error in normal language implies something wrong, however in developer language it only means something was written to log file and does not always suggest something is wrong.

 

You wont find an explanation of the type of errors written here because the answer will be complex for most of them, some even legacy reasons. It's quite easy to generate errors without causing a problem, I've done it.

 

 

You are far wiser to spend your time tackling a symptom before you get to an error. The devs are not open to discussing the code, at least in the English language forums.

[dixtrian]

Haha, OK, I'm in IT but not as a developper, I'm a Linux Integrator. For me, an error must be understand and it's why I'm posting here :-) but a warning is just something to check if we need or if something work not as expected.

 

 

As I said, an error with texture makes that I was unable to play in multiplayer (it was a light_house). This error make just blackscreen or, in worst case, DCS crash. This is why I'm investigating on the lasts errors messages.

 

 

At this time DCS works fine in solo or multi with the remaining errors.