grim_reaper68

New version out yet https://www.digitalcombatsimulator.com/fr/files/3332173/

Corrected link in the post above. Thanks for the information

New version 1.5 for DCS 2.9.10.4160 https://www.digitalcombatsimulator.com/fr/files/3332173/

Sorry, but I don't see your signature.

On which channel can i find you? Youtube?

Hi it's in the payloads.lua, line 126 and 132. Use visual code studio in admin to make the changes. Otherwise, it could be that you couldn't save them.

Take a look at the new doc, it' explains the taxiing logic to the cat.

Hi I just made a test flight in the evening, and saw that the light of the Carrier made terrible aliased shadows on the F18 (not tested other aircraft yet). At day, everything is normal. I first thought it came from the setup, no.

Hi I made a test flight, with an E2D and an S3B on cat 1 and 2, instead of leading me to the cat 3 or 4 that are available, the first yellow shirt guides me to the right and when arriving to the second one, I get "taxiing prohibited". As 2 cat (3 and4) were free, why didn't the yellow shirt leads me to them? I even tried with Cat 1 occupied, but instead of leading me to the cat 2, I got the same message as told above. In my mind it would be great to have the choice on which cat I would be launched.

Hi just clic on skip, it doesn't matter. same for the P4_CAB.

Hi Just a feedback for the RX7900XTX, I have it now since one month, and the FPS gain is very good. But now, I have strange ghosting effect in the external flyby view, and when I'm at some distance from the aircraft. I tried many settings in the Adrenaline soft and in DCS, but nothing helps. I also roll back on the AMD driver to see if it helps, but no result. If someone could help me, I would be glad.

Hi, no it's working fine now. Thanks

Maybe you were locked by an IR misille, so only the flare fires. I will make some test to see if I can reproduce it.

Don't fogret to turn on the ATIRCM/CMWS on, on the power page. If you don't, you have to select Bypass to use chaff and flares.

If you look for some helis, you can find some here

In fact the TACAN itself is working, but you can't switch to the T/R mode, so you only have the bearing, and not the distance.

Make sure you have the line add_ECM_pod(Pylons_CE_BE_EE, id_PHIMAT, 2, 6) in the Payloads.lua file at line 513. The entire file structure has been reworked. All payloads configurations are now in the Payloads.lua file. Hope that helps.

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 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.

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,

Hi since the 2.9.9 updute, the T/R mode for the TACAN is no more avaible.

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?

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

V1.4.1 out now, https://www.digitalcombatsimulator.com/fr/files/3332173/

Hi I will make an update ASAP as the file structure of the F1 has been modified.