Jump to content

Recommended Posts

Posted (edited)

Once you select the fuze settings in ME on the GBU-24B/B, they are permanently white on the modified ones, as seen in the pics below. The USAF green coating cannot be re-added. 

Steps to reproduce:

Go to ME, load up an F-45E-45MC

Go to Payload Manager
Set GBU-24B/B
Edit fuzes
Cannot be changed back once set on those pylons, even after deleting aircraft or loading a new mission. This also persists after a restart of DCS.

 

 

image.png?ex=665107e3&is=664fb663&hm=00fimage.png?ex=665107f0&is=664fb670&hm=e94

Edited by HB_Painter
Classification of Bugs and User reports
Posted (edited)

Yeah B/B is the Navy version, so only having the Navy coatings available for that makes sense.

The actual problem here is that the Phantom has the wrong version of GBU-24. It should have the A/B, but instead has the Navy B/B.

The A/B does already exist in DCS World and is available for RAZBAM's F-15E and the F-16CM, so hopefully this should be a fairly trivial fix.

Edited by Northstar98
clarity
  • Like 2

Modules I own: F-14A/B, F-4E, Mi-24P, AJS 37, AV-8B N/A, F-5E-3, MiG-21bis, F-16CM, F/A-18C, Supercarrier, Mi-8MTV2, UH-1H, Mirage 2000C, FC3, MiG-15bis, Ka-50, A-10C (+ A-10C II), P-47D, P-51D, C-101, Yak-52, WWII Assets, CA, NS430, Hawk.

Terrains I own: South Atlantic, Syria, The Channel, SoH/PG, Marianas.

System:

GIGABYTE B650 AORUS ELITE AX, AMD Ryzen 5 7600, Corsair Vengeance DDR5-5200 32 GB, NVIDIA GeForce RTX 4070S FE, Western Digital Black SN850X 1 TB (DCS dedicated) & 2 TB NVMe SSDs, Corsair RM850X 850 W, NZXT H7 Flow, MSI G274CV.

Peripherals: VKB Gunfighter Mk.II w. MCG Pro, MFG Crosswind V3 Graphite, Logitech Extreme 3D Pro.

  • HB_Painter changed the title to [DCS Issue] GBU-24B/B Coatings in Fuze Selection Menu
Posted (edited)
On 5/24/2024 at 1:17 PM, HB_Painter said:

Hey thanks for the report! We will take a look at this together with ED 🙂

Just for reference, on lines 445 and 625 of CoreMods\aircraft\F-4E\Entry\F-4E.lua, if "GBU-24" is replaced with "34759BBC-AF1E-4AEE-A581-498FF7A6EBCE", the GBU-24B/B gets replaced with the GBU-24A/B as is correct for our F-4E.

I'm not sure if that remains so when dropped (while I own the Phantom module, I can't test it) if anyone wants to test it, I've attached a corrected F-4E.lua. Back up the one you have first though, before replacing it with this one (all I've done is changed the 2 CLSID entries as above and added a comment to identify them as being for the GBU-24).

As above, the relevant path is [your main DCS World installation, usually inside Program Files\Eagle Dynamics\DCS World] then CoreMods\aircraft\F-4E\Entry

 

F-4E.lua

Edited by Northstar98
Updated F-4E.lua for 2.9.6.57650, corrected which lines should be changed

Modules I own: F-14A/B, F-4E, Mi-24P, AJS 37, AV-8B N/A, F-5E-3, MiG-21bis, F-16CM, F/A-18C, Supercarrier, Mi-8MTV2, UH-1H, Mirage 2000C, FC3, MiG-15bis, Ka-50, A-10C (+ A-10C II), P-47D, P-51D, C-101, Yak-52, WWII Assets, CA, NS430, Hawk.

Terrains I own: South Atlantic, Syria, The Channel, SoH/PG, Marianas.

System:

GIGABYTE B650 AORUS ELITE AX, AMD Ryzen 5 7600, Corsair Vengeance DDR5-5200 32 GB, NVIDIA GeForce RTX 4070S FE, Western Digital Black SN850X 1 TB (DCS dedicated) & 2 TB NVMe SSDs, Corsair RM850X 850 W, NZXT H7 Flow, MSI G274CV.

Peripherals: VKB Gunfighter Mk.II w. MCG Pro, MFG Crosswind V3 Graphite, Logitech Extreme 3D Pro.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...