bennyboy9800

Keep 'em coming @Easy-P !!

Sweet! I will troubleshoot other mods causing the issue and see if I get the same result. EDIT: CONFIRMED!! Removing these two lines from the super hornet mod's entry lua fixes the issue as well! I have not seen the removal of them cause any issues with the mod itself, yet.

I agree too, no one can expect devs to test everything, especially mods that are less available even for the community, let alone devs. I certainly hear that. I would hope that this forum topic could encourage both sides to support each other, to try to troubleshoot the issue.

Creason the issue is that this has never been a problem until you released your F-14A. None of the modders have any idea what is causing it, because it doesn't affect any other module out there. It doesn't even affect the B for christ sake so why is the A so sensitive. Plus the fact that these affects are happening as a result of mods placed in savegames, which by nature isn't suppose to be changing core game files, and haven't had a single negative affect until now.;

Golo your presence is useless here. The fact that you think you have the ultimate opinion, that, because you don't use mods - this problem doesn't exist, is essentially the proof in the pudding that you have no concept of this issue, so leave it to the people who do. Your participation here does nothing but gum up the process of problem solving.

Literally every aircraft mod that uses default-game assets causes this.

Yeah re install didn't work for me either. Seemingly the only solution for those who enjoy modded planes is removing them from savegames, but thats honestly a deal breaker for me. Id rather have them than this A. So other than that its gotta be on Heatblur to fix, and since they never affected the F-14B this shouldn't be too much to ask for. And the mods in question use hornet files, so I'm lost on how this could possibly affect a heatblur module so significantly...

Okay copy that, I was seeing the same issue in the mission editor.

Do you have similar mods located in savegames too? If so then your fix would probably be the best route.

It has something to do with a private super hornet mod. Only crashes when the mod is installed, and I've noticed when it is going to crash the Heatblu F-14A 3d model is replaced by the old ED model. However this shouldn't be the mods fault, because these mods located in savegames haven't ever impacted other modules until now. dcs.log-20201118-181226.zip

Happening to me too, however I fixed it when removing mods located in savegames/mods/aircrafts. This is odd because these mods have nothing to do with Heatblur F-14 files, as they are standalone aircraft mods

No lol I'm definitely talking about this one.

The community stopped paying interest in a mod that will never see the light of day.

+1 Yeah its super annoying

+1

+1

Could you explain how you were able to get the mod to work on the newest version of DCS by using a SFM?

JSOWs get picked out of the sky like flies by SA-15s and SA-10s. Your point is incredibly invalid

The issue hasn't been fixed in the most recent OB. Furthermore the VVSLV push button option disappeared on the right side of the screen, so the only way to cage is to turn the pod to standby? This makes using the pod so frustrating.

+1 happened to me as well

All of your skins are absolutely incredible Reflected!

I completely agree. I'd really like to hear what ED has to say about this idea. Wags said most information was classified but that was over 2 years ago.

That would be the only thing I would ever fly!

Any updates to the progress? Looking forward to seeing the F model in game!