sean laser

问题小结：此次更新2.9.14.8222,导致部分的第三方模组中的武器代码会触发此bug，导致地面单位和船舰在任务加载时被忽略，从而在任务中“消失”，所有在航母上出生的飞机也同样会“消失”或者初始化时坠海。 已知不会影响的飞机模组：A-4E-C,A-29B-community,Dark_sword,F-15CGE,F-15EX,F-22A,FH-97A,H-20,J-10A,J-10C,J-11B,J-15D,J-20A,J-35A,VSN_F35_103_Release,WZ-7A,YF-23A 已知影响的飞机模组：VSN F-4，FlankerEx by Codename Flanker（Su-30系列），SU-57 Felon by CUBANACE SIMULATIONS ，J-16A. 已知开发者发布修复的飞机模组：VSN F-4 https://e.pcloud.link/publink/show?code=kZxLInZSIVSBK9EJFy8f2fDW7pxQfvz2tU7%2F 已知已定位可手工修改文件绕过bug的飞机模组：FlankerEx by Codename Flanker（Su-30系列），SU-57 Felon by CUBANACE SIMULATIONS ，J-16A FlankerEx by Codename Flanker（Su-30系列）去下面链接下载Weapons_AS.lua替换。这个文件注释掉了会触发问题的个别武器定义并不会影响其他。 SU-57 Felon 去下面下面链接下载Weapons.lua替换。这个文件注释掉了会触发问题的Kh-59mk2，因此损失了这个武器。可用Su-30的Kh-59mk2代替。 J-16A 下载本贴的Weapons.lua替换。这个文件注释掉了会触发问题的YJ-91。 Bug追踪页： 快速绕过bug方案楼： Weapons.lua

Well, my point is ED should not just mark "remove unoffical mods" as solution for this bug. The reason link back is not everyone can see the quick helpful solution. Also, I updated it with follow-ups perticularly point out the causing and no longer break the land units or ships and with mininal impacts. Mod users should know there is something they can do, while wait for more perfect fix no matter from ED or mod creators. Since there are mods that owner no longer update for years still can work before this update, and people love their mods. And yes I follow the link you provided.

Btw, I think users deserve a better answer than just roughly mark "disable unofficial mods" as "answers", it is just an approach to isolate the boundaries, which really disappointed both users and mod makers. If ED changed some backend logics to some weapons , ED should have make it publicly, such as : XXX old way are unsupported from this version, please use below new way from now on, and explain the new way clearly. even better should say why the new way is so important/great/perform better to replace the old way . And much better is publish a backend tech road-map from time-to-time , let mod community understand this.

Please refer to this ,I have a workaround to let you flight Su-30 and Su-57 again, and maybe you can refer the way and make F-4 flightable again yourself. Follow up:VSN launched F-4 hotfix may address this VSN_F4 - pCloud

I found a quick work around to this "bug", so that you can still fly the mission without part of customized weapons before mod owner publish formal fix or update . For those mod impacted, please open the entry.lua, comment out weapon.lua call out line and save. For example, SU-57, you many want to comment out this line with -- dofile(current_mod_path.."/Scripts/Weapons.lua")--Calling Weapon Types Since not all customized weapons are the cause, I just give out some clues for those who want "quick solution". If I narrow down further, may get back and let you know. So far, with this work around , I managed to revive several mods I have such as : Su-57 follow up: further debug shows the root cause is in Weapons.lua in Kh_59MK2 definition. Just comment out it with --[[]] will make Su-57 back. Note: my installed mod version is 4.3 may different from yours. If you are using the same version as I do , you can download the attached file Weapons.lua to replace. Su-30 follow up: further debug shows the root cause is in Weapons_AA.lua in function __counter_wpn(). Comment out it(first 5 lines) and replace all "__counter_wpn()" with "WSTYPE_PLACEHOLDER" Weapons_AS.lua in KH_38MAE and RudraM1 . For those already downloaded my Weapons_AA.lua, please restore the Mod default , and then download Weapons_AS.lua replace. This will give back the most AS weapons. Note: my installed version is EFM V2.7.98b with CWS 3.6.4. If you are using the same version as I do , you can download the attached file Weapons_AS.lua to replace. J-16A follow up: further debug shows the root cause is in Weapons.lua in YJ-91 definition. Just comment out it with --[[]] Weapons.lua Weapons_AS.lua

I solved it by searching mod folder in saved game for yj12.edm , and then rename it to other name.

May I ask how do you solved this? I have the same issue.