cj43g3r Posted March 24 Posted March 24 @VictorDavion It was not intended as a solution. I am just pointing out my observations with DCS 2.9.14.8222 which did not exist in the previous version. It indicates there is one or more weapons in <SavedGames>\DCS\Mods\aircraft\JAS39\Weapons\Loadout.lua in addition to the previously 3 mentioned that is causing a carrier spawning issue. It's a shortcut to avoid some of the work involved in isolating the problem for those who may be trying to find a solution.
cj43g3r Posted March 25 Posted March 25 For DCS 2.9.14.8222, JAS39C v1.8.5 Beta compatibility with spawning aircraft carriers (A-4e, F/A-18c, T-45 case1 missions) seems to require commenting out (via preceding --) the following weapons from <SavedGames>\DCS\Mods\aircraft\JAS39\Weapons\Loadout.lua: --dofile(current_mod_path .. '/Weapons/Loadouts/jas39_a-darter.lua') --dofile(current_mod_path .. '/Weapons/Loadouts/jas39_mar-1.lua') ... --dofile(current_mod_path .. '/Weapons/Loadouts/jas39_dws39_arm.lua') --dofile(current_mod_path .. '/Weapons/Loadouts/jas39_dws39_tv.lua') Dcs.log doesn't seem to provide any reason why it's affected by jas39_a-darter or jas39_mar-1
VictorDavion Posted March 25 Posted March 25 Unfortunately I dont think this mod is updated anymore so prob dead at this point. 2
Archangel44 Posted March 25 Posted March 25 4 hours ago, VictorDavion said: Unfortunately I dont think this mod is updated anymore so prob dead at this point. That would be a damn shame since this mod was one of the top tier mods not so long ago. F-4E, F-5E-3, F-14, F-15E, F-16C, FA18-C, F-86, A-10C, Spitfire, AJS-37, KA50, MiG-19, L-39, P-51, Flaming Cliffs, All maps, WWII Assets, Combined Arms, Super Carrier.
Gogi12 Posted March 25 Posted March 25 54 minutes ago, Archangel44 said: That would be a damn shame since this mod was one of the top tier mods not so long ago. It is not abandoned, You can join theri Discord channel for more news. 2
Urbi Posted March 25 Posted March 25 all luas in loadouts without which units are not displayed. Loadouts.zip 1 1 Windows 11 Enterprise 64-bit processor AMD Ryzen Threadripper 3970X 32-core processor 3.90 GHz, installed memory 256 GB (256 GB usable), system type 64-bit operating system, x64-based processor 2 x NVIDIA RTX TITAN SLI 48 GB vRAM, 3x 2 TB M2 NVMe WDS200T3XHC Raid, 2x 4 TB M2 NVMe Force MP510 Raid, ERM - 3K3U water cooling, gaming motherboard ROG ZENITH II EXTREME ALPHA Monitor 108 cm ACER PREDATOR CG437K 7680x4320-120Hz, power supply 2000 watts
impreza Posted March 25 Posted March 25 hace 7 horas, Urbi dijo: all luas in loadouts without which units are not displayed. Loadouts.zip 104.27 kB · 3 descargas no conficts with other units??
cj43g3r Posted March 26 Posted March 26 (edited) For DCS 2.9.14.8222, the following JAS39C loadouts has conflicts with the A-4e-c, F/A-18C, T-45 not spawning carriers. It's resolved by commenting out those loadouts with only those mods: --dofile(current_mod_path .. '/Weapons/Loadouts/jas39_a-darter.lua') --dofile(current_mod_path .. '/Weapons/Loadouts/jas39_mar-1.lua') --dofile(current_mod_path .. '/Weapons/Loadouts/jas39_dws39_arm.lua') --dofile(current_mod_path .. '/Weapons/Loadouts/jas39_dws39_tv.lua') But I also see other mods now causing the same symptom A-4e-c, F/A-18C, T-45, UH-60L not spawning carriers: MiG-31K and MiG-31BM RAFALE PACK EVOLUTION II 2.8.7 2023 Seems like all VSN mods The A-4e-c, T-45 and UH-60L all have exceptions in scripts function copyFile where iniFile = nil, caused by scandir not finding any mission file. It does not seem to be the cause of the carrier spawning issue since these exceptions also occur in the case of successful carrier spawning. The carrier spawning issue seems to be related to M61_20_HE_gr and M2_12_7_T. Perhaps a missing core resource ? 2025-03-25 23:27:23.287 INFO APP (Main): MissionSpawn:spawnShips 2 2025-03-25 23:27:23.295 ERROR woShip (Main): Failed to create ship: Descriptor not found weapons.shells.M61_20_HE_gr 2025-03-25 23:27:23.303 ERROR woShip (Main): Failed to create ship: Descriptor not found weapons.shells.M2_12_7_T 2025-03-25 23:27:23.358 WARNING LOG (10036): 1 duplicate message(s) skipped. Seems this can be easily reproduced with only the VSN F-4 mod installed using it's case1 mission: VSN_F4 standalone V2.9.5.206 case1 fails to spawn aircraft carriers. VSN_F4 v2.8.2.102 standalon case1 succeeds spawning aircraft carriers. Edited March 26 by cj43g3r added symptom reproducible with only VSN F-4 1
whisky.actual Posted March 26 Author Posted March 26 ED just released a patch I would suggest testing it, as stated above the mod is still ongoing, our Discord is a better place to follow updates and bugs Regards, Whisky 3
SparrowLT Posted March 27 Posted March 27 yeah i copied the mod folder back to the saved games folder and now i can load MP servers again
SOLIDKREATE Posted April 2 Posted April 2 On 3/25/2025 at 12:36 AM, Gogi12 said: It is not abandoned, You can join theri Discord channel for more news. Discord link invalid. AVIONICS: ASUS BTF TUF MB, INTEL i9 RAPTORLAKE 24 CORE, 48GB PATRIOT VIPER TUF, 16GB ASUS RTX 4070ti SUPER, ASUS TUF 1000w PSU CONTROL: LOGI X-56 RHINO HOTAS, LOGI PRO RUDDER PEDALS, LOGI G733 LIGHTSPEED MAIN BIRDS: AJS37, MB339A, MIRAGE F1, Su-25A
Recommended Posts