reported log errors corrupt damage models

[Damned - Gh0st]

Since 2.8 I am seeing errors in the logs relating to "Corrupt Damage Model", "No Property Record For Cell", and "No Property Record For Segment" in the DCS Logs.

The Errors appear in relation to many aircraft in the logs, in multiplayer and singleplayer.

Is this a remnant from updated/unused systems? Should we be concerned about this? Am I the only one experiencing this?

Example:

2022-10-29 22:40:23.149 ERROR   WORLDGENERAL (Main): Error: Unit [F-14B]: No property record for cell "WHEEL_F".
2022-10-29 22:40:23.149 ERROR   WORLDGENERAL (Main): Error: Unit [F-14B]: No property record for cell "collision_belly".
2022-10-29 22:40:23.149 ERROR   WORLDGENERAL (Main): Error: Unit [F-14B]: No property record for cell "WHEEL_R".
2022-10-29 22:40:23.149 ERROR   WORLDGENERAL (Main): Error: Unit [F-14B]: No property record for cell "WHEEL_L".
2022-10-29 22:40:23.149 ERROR   WORLDGENERAL (Main): Error: Unit [F-14B]: No property record for segment "FRONT_WHEEL".
2022-10-29 22:40:23.149 ERROR   WORLDGENERAL (Main): Error: Unit [F-14B]: No property record for segment "WING_L_OUT".
2022-10-29 22:40:23.149 ERROR   WORLDGENERAL (Main): Error: Unit [F-14B]: No property record for segment "NOSE_CENTR".
2022-10-29 22:40:23.149 ERROR   WORLDGENERAL (Main): Error: Unit [F-14B]: No property record for segment "RIGHT_WHEEL".
2022-10-29 22:40:23.149 ERROR   WORLDGENERAL (Main): Error: Unit [F-14B]: No property record for segment "LEFT_WHEEL".
2022-10-29 22:40:23.150 ERROR   WORLDGENERAL (Main): Error: Unit [F-14B]: No cell for property records CELL#146 CELL#149 CELL#163 CELL#165 CELL#168 CELL#169 CELL#177 CELL#178 CELL#179 CELL#183 CELL#184.
2022-10-29 22:40:23.150 ERROR   APP (Main): Error: Unit [F-14B]: Corrupt damage model.

Test Miz and TRK attached.

 

Thanks

Test.miz test.trk

[Azaezzel]

Our server is showing the same thing in the logs. Its not just you.

[CaptHawk]

5 hours ago, Azaezzel said:

Our server is showing the same thing in the logs. Its not just you.

Same here. Sifting through it to check errors for scripts is tough when every asset reports error, corrupt damage model. 

[Damned - Gh0st]

On 10/30/2022 at 4:56 AM, Azaezzel said:

Our server is showing the same thing in the logs. Its not just you.

 

On 10/30/2022 at 10:21 AM, CaptHawk said:

Same here. Sifting through it to check errors for scripts is tough when every asset reports error, corrupt damage model. 

Thank you for the confirmation.

 

@CaptHawk That's actually when I first noticed it, when debugging while developing scripts   Luckily we have the WorldGeneral, App, etc. tags on the errors now so it's not too big a deal to filter them out

[Lineaxe]

yup I am getting it too. I guess I don't have to repair anything and  it's maybe a bug they will fix up?

 

[Six Gun]

Same here

[Flappie]

This Tomcat issue has been reported internally.

[Bucic]

As well as various other errors. It's the IA mission for the F-5E, takeoff from Batumi.

022-12-29 21:19:31.715 ERROR   APP (Main): Error: Unit [C-130]: Corrupt damage model.
2022-12-29 21:19:31.716 INFO    APP (Main): MissionSpawn:spawnPlanes 2
2022-12-29 21:19:31.716 ERROR   APP (Main): Error: Unit [F-5E-3]: Corrupt damage model.
2022-12-29 21:19:31.725 WARNING LOG (11288): 1 duplicate message(s) skipped.
2022-12-29 21:19:31.725 ERROR   APP (Main): Error: Unit [E-2C]: Corrupt damage model.
2022-12-29 21:19:31.727 INFO    APP (Main): MissionSpawn:spawnLocalPlayer 1,F-5E-3
2022-12-29 21:19:31.728 ERROR   APP (Main): Error: Unit [F-5E-3]: Corrupt damage model.
2022-12-29 21:19:31.742 WARNING EDCORE (Main): Source mods/aircraft/f-5e/cockpit/shape is already mounted to the same mount /models/.
2022-12-29 21:19:31.749 INFO    VISUALIZER (Main): cockpit ILV loaded
2022-12-29 21:19:31.769 INFO    COCKPITBASE (Main): WebRTC VOIP init: registered radio receiver/transmitter "UHF_RADIO" with id - 0
2022-12-29 21:19:31.769 INFO    COCKPITBASE (Main): WebRTC VOIP init: enabled VOIP capability for radio UHF_RADIO
2022-12-29 21:19:31.769 INFO    COCKPITBASE (Main): WebRTC VOIP init: registered radio receiver "UHF_RADIO_guard" with id - 1
2022-12-29 21:19:31.769 INFO    COCKPITBASE (Main): WebRTC VOIP init: added guard receiver - UHF_RADIO_guard
2022-12-29 21:19:31.853 INFO    COCKPITBASE (Main): lua state still active UHF_RADIO, 23
2022-12-29 21:19:31.853 INFO    COCKPITBASE (Main): lua state still active INTERCOM, 24 (status undefined)
2022-12-29 21:19:31.853 INFO    COCKPITBASE (Main): WebRTC VOIP init: registered radio receiver "Base TACAN receiver" with id - 2
2022-12-29 21:19:31.853 INFO    COCKPITBASE (Main): lua state still active MACROS, 37 (status undefined)
2022-12-29 21:19:31.872 INFO    WORLDGENERAL (Main): loaded from mission Scripts/World/birds.lua
2022-12-29 21:19:33.580 ERROR_ONCE DX11BACKEND (11280): Can't load 'Fonts/font_general_RU.dds' in texture array ''.
2022-12-29 21:19:33.586 INFO    VISUALIZER (Main): Preload() camera=-356393.525250, 12.410247, 618201.437452 radius=100.000000
2022-12-29 21:19:33.586 INFO    EDTERRAINGRAPHICS41 (Main): ITerrainGraphicsImpl4::forceLoading(): pos=(-356394, 12.4102, 618201), radius=100
2022-12-29 21:19:33.596 INFO    EDTERRAINGRAPHICS41 (Main): surface5 clean up LOD 0: left 1  released 10
2022-12-29 21:19:33.596 INFO    EDTERRAINGRAPHICS41 (Main): surface5 clean up LOD 1: left 1  released 14
2022-12-29 21:19:33.596 INFO    EDTERRAINGRAPHICS41 (Main): surface5 clean up 0.468400 ms
2022-12-29 21:19:34.751 ERROR_ONCE DX11BACKEND (11280): texture 'f-5e3_cockpit_normal.bmp' not found. Asked from ''
2022-12-29 21:19:34.751 ERROR_ONCE DX11BACKEND (11280): texture 'f-5e3_cockpit_spec.bmp' not found. Asked from ''

 

dcs.log F-5 - IA TO - bug TACAN bearing pointer stuck.trk

[Flappie]

F-5E was reported earlier. C-130 and E-2 reported.

[Bucic]

On 12/30/2022 at 10:34 PM, Flappie said:

F-5E was reported earlier. C-130 and E-2 reported.

Out of curiosity. Do such errors affect the actual gameplay in any way?

[Flappie]

I don't think so, otherwise we would be seeing "invincible AI aircraft" threads everywhere in the forum.

[Colmillo]

Not only F-14:

7:08:13 PM.411  ERROR  APP  Error: Unit [F-16C_50]: Corrupt damage model. 

Cheers

[Flappie]

On 2/27/2023 at 11:13 PM, Colmillo said:

Not only F-14:

7:08:13 PM.411  ERROR  APP  Error: Unit [F-16C_50]: Corrupt damage model.

A lot of aicraft are affected and most of them were reported earlier. The F-16C was not. Tanks for the heads up.

[SPAS79]

I had this today on Hoggit PGAW, loading the Huey. It loaded in the end but it hanged there for a while. 

[Turbine 205]

We are experiencing a similar issue on our vCSG-3 servers.  Server runs, but after people disconnect the server crashes.

2023-03-26 21:54:28.173 ERROR   APP (3340): Error: Unit [KC130]: Corrupt damage model.
2023-03-26 21:54:28.427 ERROR   APP (3340): Error: Unit [E-3A]: Corrupt damage model.
2023-03-26 21:54:28.719 ERROR   APP (3340): Error: Unit [KC135MPRS]: Corrupt damage model.
2023-03-26 21:54:57.327 ERROR   APP (3340): Error: Unit [S-3B]: Corrupt damage model.
2023-03-26 21:54:57.338 ERROR   APP (3340): Error: Unit [E-3A]: Corrupt damage model.
2023-03-26 21:54:57.350 ERROR   APP (3340): Error: Unit [RC135RJ]: Corrupt damage model.
2023-03-26 21:54:57.369 ERROR   APP (3340): Error: Unit [KC135MPRS]: Corrupt damage model.
2023-03-26 21:55:27.332 ERROR   APP (3340): Error: Unit [S-3B]: Corrupt damage model.
2023-03-26 21:55:27.344 ERROR   APP (3340): Error: Unit [KC135MPRS]: Corrupt damage model.
2023-03-26 21:55:27.369 ERROR   APP (3340): Error: Unit [E-3A]: Corrupt damage model.
2023-03-26 21:55:57.332 ERROR   APP (3340): Error: Unit [E-2C]: Corrupt damage model.
2023-03-26 21:55:57.342 ERROR   APP (3340): Error: Unit [KC135MPRS]: Corrupt damage model.
2023-03-26 21:56:27.330 ERROR   APP (3340): Error: Unit [KC135MPRS]: Corrupt damage model.
2023-03-26 21:56:57.331 ERROR   APP (3340): Error: Unit [EC130]: Corrupt damage model.

[Wiggo]

With latest OB patch 2.8.xxxx has A LOT of these in my DCS.log. Corrupt model for example Hind. Hornet display buttons graphical feedback does not work, but that have been already reported. It seems there is a lot of graphical bugs for some reason in latest OB, and I have had MANY DCS repairing, renaming missioneditor folder etc, because of jamming pretty much daily on SP campaigns loader at "Sim Poststart". Something really exploded pretty much everything in DCS (coordinates does not add up with models on ground etc. CCIP pipper on hornet is giving false readings. Something weird with ground lvls. Something weird with runways (a lot of Runway / taxiway does not exists) on DCS.log and other very weird stuff. (yes I have reapired it, as administrator, deleted all the 3th party mods, but still buggy as hell. In every plane there is some weid new glitch. That freezing of loading screen happens only with f/a18c but in every map SP Campaign. Dunno if these are related, but somethin did something to latest OB that I really recommend just to back off   What is that loading screen thing? Does it have something to do with muchos corrupt this and corrupt that in dcs log? It has been reported two years ago on persian gulf map, but with MP (though same manouvers helped). Still what is going on? Why everything smashed suddenly?

[Wiggo]

On 4/21/2023 at 5:50 PM, Wiggo said:

With latest OB patch 2.8.xxxx has A LOT of these in my DCS.log. Corrupt model for example Hind. Hornet display buttons graphical feedback does not work, but that have been already reported. It seems there is a lot of graphical bugs for some reason in latest OB, and I have had MANY DCS repairing, renaming missioneditor folder etc, because of jamming pretty much daily on SP campaigns loader at "Sim Poststart". Something really exploded pretty much everything in DCS (coordinates does not add up with models on ground etc. CCIP pipper on hornet is giving false readings. Something weird with ground lvls. Something weird with runways (a lot of Runway / taxiway does not exists) on DCS.log and other very weird stuff. (yes I have reapired it, as administrator, deleted all the 3th party mods, but still buggy as hell. In every plane there is some weid new glitch. That freezing of loading screen happens only with f/a18c but in every map SP Campaign. Dunno if these are related, but somethin did something to latest OB that I really recommend just to back off   What is that loading screen thing? Does it have something to do with muchos corrupt this and corrupt that in dcs log? It has been reported two years ago on persian gulf map, but with MP (though same manouvers helped). Still what is going on? Why everything smashed suddenly?

Hornet display buttons now works again! Thank you! It is really nice to have that feedback, when using buttons fast - like in cold start. 

[Osiris400]

After the recent patch my groups server is having this as well. With basically every unit from Su-24s to the Forrestal to E-2s and F-14s and even the new F-15E.

[Lock-Os]

Second the person up above me. Lots of Corrupt damage models.dcs.log

[Flappie]

The following aircraft won't trigger these messages anymore in the next OB update:

• M-2000C
• AV-8B
• L-39
• Su-25A
• Mi-24V
• Tornado GR4
• Tornado IDS
• MiG-23MLD
• MiG-31
• E-3A
• A-50
• MQ-9
• F-15E

Many reported units still need such a fix. I'll try to update this thread from time to time.

S-3B and S-3B Tanker units had not been reported yet. They are, now. Thank you, @Turbine 205.

[Yazan]

I know this is not the correct place. but I could not create new or reply to the similar thread.

I'm getting this message in logs for A10-CII. I am on latest OpenBeta.

2023-08-07 17:10:24.366 ERROR   APP (Main): Error: Unit [A-10C_2]: Corrupt damage model.

 

Thanks.

[silverdevil]

6 minutes ago, Yazan said:

I know this is not the correct place. but I could not create new or reply to the similar thread.

I'm getting this message in logs for A10-CII. I am on latest OpenBeta.

unfortunately i think this is pretty common. i fly the F-16 and pretty much every log has these lines.

Quote

2023-07-30 19:21:12.610 ERROR   APP (Main): Error: Unit [F-16C_50]: Corrupt damage model.
2023-07-30 19:21:16.100 ERROR   APP (Main): Error: Unit [F-16C_50]: Corrupt damage model.
2023-07-30 19:26:18.861 ERROR   APP (Main): Error: Unit [F-16C_50]: Corrupt damage model.
2023-07-30 19:28:00.550 ERROR   APP (Main): Error: Unit [F-16C_50]: Corrupt damage model.
2023-07-30 19:28:05.683 ERROR   APP (Main): Error: Unit [F-16C_50]: Corrupt damage model.

but your report for the particular plane may be helpful.

[Yazan]

18 hours ago, silverdevil said:

unfortunately i think this is pretty common. i fly the F-16 and pretty much every log has these lines.

but your report for the particular plane may be helpful.

exactly that's my point, because on the other thread I noticed they collected the models that shows this error

I thought I'd report A10 since it's not mentioned there. Thanks!

[Flappie]

The following aircraft won't trigger these messages anymore in the next OB update:

• E-2C/"D"
• F-16C

[BIGNEWY]

threads merged