Integrity check

[Shug Ninx]

Hello !

I hopefully encountered this issue when joining a multiplayer server only a handful of times, last time I remember VARS Pylons suddenly got rejected whereas it's been laying in my Saved Games\DCS.openbeta\Mods\tech\ for months without issues. I quit DCS, removed the files and everything went back in order.

More recently a friend of mine was joining me on Contention server and was kicked after a few minutes becauseIC failures. What's more puzzling here is the incriminated files where in the core DCS folder (not in savegames), he deleted those, joined again, then was kicked out again after a while with even more core files to delete. He eventually managed to join and remain on the server but some of the deletions led to missing functionalities in the plane he was flying and didn't mod in any way.

Beside the obvious full cleanup and repair, is there a way to manually trigger the IC on one's DCS install to check everything's ok rather than joining a server and being kicked out again and again ?

 

[razo+r]

The only thing you could do is load the mission you plan on joining in singleplayer, fly it for a bit and then check in the MP server selection screen if the IC got triggered or not. 

Sometimes a simple restart of DCS will solve the issue, sometimes not. 

The IC has been not working as designed for an eternity and there does not seem any intentions of solving the issues. You just have to live with it and hope the IC has a good day. 

Edited April 21, 2024 by razo+r

[Shug Ninx]

That's a bit complicated for public servers hosting complex missions such as Enigma's Cold War or Contention, I was hoping for a command line to trigger the IC.

Sad to learn this problem's been around for sol long

[Striker_01]

I'm the friend who is having some problems. I fixed them by cleaning and repairing the DCS and removing the mod file from my saved games. I was able to fly in contention server with a m2000c but when I took the f-16 the IC kicked me out and  incriminated files were also original files from the game. Log behind.

2024-04-26 19:46:09.896 WARNING SECURITYCONTROL (15268): IC fail: /textures/f16c_glass_canopy_refl_roughmet @ mods/aircraft/f-16c/cockpit/textures/f-16c-cpt-textures.zip
2024-04-26 19:46:09.897 ERROR   SECURITYCONTROL (15268): Manifest check failed for resource '/textures/f16c_glass_canopy_refl_roughmet.dds'
2024-04-26 19:46:09.947 WARNING SECURITYCONTROL (15268): IC fail: /textures/f16c_glass_canopy_refl @ mods/aircraft/f-16c/cockpit/textures/f-16c-cpt-textures.zip
2024-04-26 19:46:09.949 ERROR   SECURITYCONTROL (15268): Manifest check failed for resource '/textures/f16c_glass_canopy_refl.dds'
2024-04-26 19:46:09.991 WARNING SECURITYCONTROL (15268): IC fail: /textures/f16c_glass_canopy_gold_refl_roughmet @ mods/aircraft/f-16c/cockpit/textures/f-16c-cpt-textures.zip
2024-04-26 19:46:09.992 ERROR   SECURITYCONTROL (15268): Manifest check failed for resource '/textures/f16c_glass_canopy_gold_refl_roughmet.dds'
2024-04-26 19:46:10.042 WARNING SECURITYCONTROL (15268): IC fail: /textures/f16c_glass_canopy_gold_refl @ mods/aircraft/f-16c/cockpit/textures/f-16c-cpt-textures.zip
2024-04-26 19:46:10.043 ERROR   SECURITYCONTROL (15268): Manifest check failed for resource '/textures/f16c_glass_canopy_gold_refl.dds'

 

[Flappie]

1. Delete this file: .\DCS World\Mods\aircraft\F-16C\Cockpit\Textures\F-16C-CPT-TEXTURES.zip
2. Run a DCS cleanup and repair.
3. Ensure this folder does not exist: "Saved Games\DCS...\Mods\aircraft\F-16C".

Edited May 3, 2024 by Flappie

[carss]

On 4/21/2024 at 2:46 PM, Shug Ninx said:

Hello !

I hopefully encountered this issue when joining a multiplayer server only a handful of times, last time I remember VARS Pylons suddenly got rejected whereas it's been laying in my Saved Games\DCS.openbeta\Mods\tech\ for months without issues. I quit DCS, removed the files and everything went back in order.

More recently a friend of mine was joining me on Contention server and was kicked after a few minutes becauseIC failures. What's more puzzling here is the incriminated files where in the core DCS folder (not in savegames), he deleted those, joined again, then was kicked out again after a while with even more core files to delete. He eventually managed to join and remain on the server but some of the deletions led to missing functionalities in the plane he was flying and didn't mod in any way.

Beside the obvious full cleanup and repair, is there a way to manually trigger the IC on one's DCS install to check everything's ok rather than joining a server and being kicked out again and again ?

 

I have this exact problem! Whenever I join any server, my IC is initially green, but when I'm back in the lobby it's red! I don't necessarily get kicked out except for the Contention server just like your friend! I have never been able to play on that server because of this very issue. In my case it's some UH-1 textures that apparently keep failing the IC.

 

I did grab a screen shot of it too...

[Nimbur]

since the update i often have authentication errors and integrity errors, with F-fE, but also other modules randomly...

i do not use any mods!!!

[Rudel_chw]

1 hour ago, Nimbur said:

i do not use any mods!!!

 

Actually, the log you shared on the other post shows that you at least have the A-4E-C, the Hercules 6.8.2 and the UH-60L

Just as a diagnostic test, try the following:

1) rename the folder "C:\Users\ramon\Saved Games\DCS.openbeta\Mods" to "Mods.bak", to disable your User Mods for a bit.

2) Run a "DCS_updater repair", to ensure that the files you have at the DCS program folder are still original, delete any extraneous files that may appear.

 

now, retry your MP connections ... do you still get IC warnings?