Mirage F1BE Skins bug (missing roughmet)

[Chess96]

A good part of the Skins for the F1 BE have "missing texture" written all over them. It seems the roughmet is missing. I also noted the french skins use the old light blue color as opose to the new darker color on the F1 B.

Skin impacted: F1 BE

BA 118 Mont de Marsan / Old color

EC 1/30 Alsace BA 132 Colmar Meyenheim / Old color

EC 3/33 Lorraine 60 ans du D-day / Old color

EC 3/33 Lorraine 60 ans des FAFL / Missing texture

EC 3/33 Lorraine BA 112 Reims / Missing texture

All of the IRIAF skins / Missing texture

F1 BD Libya / Missing texture

F1 BQ IRAQ / Missing texture

I also spoted some mismatched drop tanks (color not matching one of the aircraft) on some of the other variants of the F1
Notably the darker F1 CZs, one of them has the tank matching the paint from the aircraft while the other has the tanks in a more generic light grey.

I haven't checked all the drop tanks for all the skins for all the versions but it would be nice if they could be sorted

[Chess96]

Below are the examples with the exact skin name as displayed in the ME

[Chess96]

So it somehow got worse with the latest patch 

[fausete]

Hi, this is fixed internally!

[Chess96]

@fauseteAny ideas what might cause this ? I have asked some friends of mine and everything is fine on their side. I seem to be the only one having this issue.
Also any idea how I might temporarly fix it on my side, while i wait for the next DCS update ?

[Chess96]

Found a new problem with a F1EE IRIAF livery
This one is the 6-6210_2021 Blue (EQ variant)
Wings and fuselage are not the same color

Also the Iraqi livery is missing for the F1EE

[grim_reaper68]

Chess96 do you use the Corail pod mod? I had a similar issue with some liveries. I just released the new version that works. 

[fausete]

For these kind of issues I, especially for modded installs in which it is unknown which mod might be causing the problems, I would recommend a repair. Sorry about my answer, the fix seems to already be public.

[grim_reaper68]

As told, I had the same issue with the F1CT, where the stock liveries made the same missing texture issue. As the entry.lua has been deeply modified, with the new NM zip folder, and the common_wings, tail, and fuse zip folder disappeared, some liveries had some bugs. My mod, before update hadn't the NM.zip. Hope for Chess96 that it's the case. 

@fausete from what fix do you talk?

[fausete]

The fix to the original bug.

[Chess96]

15 hours ago, grim_reaper68 said:

Chess96 do you use the Corail pod mod? I had a similar issue with some liveries. I just released the new version that works. 

Hi !

No, I do not have any mods installed for the F1, I also have no user files liveries.

14 hours ago, fausete said:

For these kind of issues I, especially for modded installs in which it is unknown which mod might be causing the problems, I would recommend a repai. Sorry about my answer, the fix seems to already be public.

I have tried this, I also removed every mod from my install, and even reinstalled the F1 but the problem still persists.

 

[Chess96]

Just now, grim_reaper68 said:

Just test on my side, no problem with them

This is really frustrating because it really feels like I'm the only one experiencing this issue and I have no idea why. 

I have done everything I could think of to investigate this and nothing came back...

Could you maybe point me to the files that would cause my issues ? See if they are corrupted (I don't understand why the repair and reinstall didn't solve this ...)

[grim_reaper68]

First of all, check if your entry.lua file from the F1, contains those lines:

mount_vfs_texture_path (current_mod_path.."/Textures/Mirage-F1_common.zip")
mount_vfs_texture_path (current_mod_path.."/Textures/Mirage-F1_common_fuse.zip")
mount_vfs_texture_path (current_mod_path.."/Textures/Mirage-F1_common_tail.zip")
mount_vfs_texture_path (current_mod_path.."/Textures/Mirage-F1_common_wings.zip")
mount_vfs_texture_path (current_mod_path.."/Textures/Weapons.zip")
mount_vfs_texture_path (current_mod_path.."/Textures/miragef1_pilot.zip")
mount_vfs_texture_path (current_mod_path.."/Textures/Mirage-F1_RoughMet.zip")

if yes, the problem comes from that. The new filestructure is at below. Fuse, tail and wings.zip  have disappeared, and now there is the new NM.zip
 

mount_vfs_texture_path (current_mod_path.."/Textures/Mirage-F1_common.zip")
mount_vfs_texture_path (current_mod_path.."/Textures/Weapons.zip")
mount_vfs_texture_path (current_mod_path.."/Textures/miragef1_pilot.zip")
mount_vfs_texture_path (current_mod_path.."/Textures/Mirage-F1_NM.zip")
mount_vfs_texture_path (current_mod_path.."/Textures/Mirage-F1_RoughMet.zip")

If your entry.lua is correct, there could be corrupted files in the texture folder or in the liveries folder.

Try to remove completely the F1 folder, rename your saved games DCS folder so you're sure there is nothing that could interfere with the root folder, then run a repair with check all files (slow) you can also add the search for extra files after repair, to see if something could come from the root folder. Hope that could help you.

It really looks like the bug I had after having replaced the original entry file, with the one I had for the Corail POD. That was the result, 

 

本帖最后于2024年11月4日，由grim_reaper68编辑

[Chess96]

@grim_reaper68I checked and my entry.lua looks fine

I have already run a repair and nothing came out of it

What really confuses me is that the exact same livery looks perfectly fine on the Mirage F1BQ (IA only), but is then corrupted in the BE.

When checking the livery files themselves I find something that could be strange.

The livery .zip in the BE folder contains only a description.lua

nullBut the livery .zip for the BQ has two extra files inside it.null

[grim_reaper68]

I cross checked both, the Iraq BE uses the Iraq BQ texture, and works fine on my side. Tested both in blue and red task force.   

I think, you must have an older version of the BE Iraq livery, as you can see, both of mine has the same color. On your screens, they seem to have 2 different colors.

Check in the Mirage-F1BE folder, what date of modification do you have for the Mirage F1B Iraq Air Force.zip. Mine is at the 31/10/2024 19:58. And the BQ one 31/10/2024 21:00.

If the BE one has a different time and date, delete the entire liveries folder, and start a deep repair. If you have no external liveries, there can't be a conflict. It looks like the bugged one, is the older livery. 

[Chess96]

17 hours ago, grim_reaper68 said:

Mine is at the 31/10/2024 19:58. And the BQ one 31/10/2024 21:00.

18:50 for the BE and 20:13 for the BQ, both on the 31/10/2024 

I deleted the folder and ran a deep repair and it didn't work ... it got reinstalled with the corrupted liveries 

I am running out of ideas ... I have no ideas why it does that on my build 

[grim_reaper68]

Do you use EDM? Try to load the F1B in EDM and select the livery. Then you can see what the name of "missing" texture is.

I just noticed that you're french. Maybe we could try to talk through discord and maybe could find where the bug is. 

[Chess96]

2 hours ago, grim_reaper68 said:

Do you use EDM? Try to load the F1B in EDM and select the livery. Then you can see what the name of "missing" texture is.

I just noticed that you're french. Maybe we could try to talk through discord and maybe could find where the bug is. 

I do not use EDM, but I have managed to fix my problem with a quite extreme solution.

I went across the whole install of DCS and deleted anything I saw that was linked to the mirage F1. And then ran a repair. This finally did it. 

I don't know what file was corrupt in the end but it was one of those. 

Thanks for you patience and help @grim_reaper68! 

Tu peux me trouver sur Discord sous le même nom qu'ici du jamais

[Loukuins]

On 11/5/2024 at 10:14 PM, Chess96 said:

I do not use EDM, but I have managed to fix my problem with a quite extreme solution.

I went across the whole install of DCS and deleted anything I saw that was linked to the mirage F1. And then ran a repair. This finally did it. 

I don't know what file was corrupt in the end but it was one of those. 

Thanks for you patience and help @grim_reaper68! 

Tu peux me trouver sur Discord sous le même nom qu'ici du jamais

I think it's because you ran a quick repair and not the longer one that check exactly each file and their content? (If you are not on steam of course)