necr

Hey tobi, thanks for your work. I'm facing somewhat of a bizarre problem - my model is exported, with a wrong rotation and dimensions. I've fixed those by resetting the pivot point to the center of the world, and dimensions in Scene-Units-Unit scale, saved the model as a new file. I've ensured that the new bounding box has correct dimensions in Blender. After export to EDM (runs without errors) I'm getting the old rotation values + old dimensions. This is Blender 3.0.0.0, I tried 1.0.7 and 1.0.8 addon versions. Thanks!

Could there be something wrong with the default collision model? There's no arg. 1, for example What has worked for me was defining a new plane, with a well known name/display name. But it still requires more work. Mig_31M = { Name = 'MiG-31', DisplayName = _('MiG-31'), But then, it's MP incompatible and can't land (see above).

Thanks for sharing the code and keep going! For all we know, it may come out in 2023: "Implementation is expected during 2022."

They're already there, but for some reasons not added to pylons in Su-30MK_SFM\Entry...Should be an easy fix. Awesome models, I hope ED buys them or at least accepts the contribution.

For me it's gone too. Please try incognito mode, you might have special permissions. @f4l0 new version is reported by 2.2.4.0, but OneDrive reports empty/unavailable file. Could you please check?

Thanks for the new experience Andre and f4l0 - just got my SimShaker Sound Module. Just a hint to whoever's using FC3 based mods - they work with the default profile (do not support customization, AFAIU they're not defined in SimShaker internal classes). In the C:\Users\<your user>\Saved Games\DCS\Scripts\SimShaker.lua (L425) adjust the FC3 objects list: elseif obj.Name == "MiG-29A" or obj.Name == "MiG-29G" or obj.Name == "MiG-29S" or obj.Name == "Su-25" or obj.Name == "Su-25T" or obj.Name == "Su-27" or obj.Name == "Su-33" or obj.Name == "F-15C" or obj.Name == "A-10A" or obj.Name == "A-4E-C" or obj.Name == "J-11A" or obj.Name == "An-30M" or obj.Name == "B-1B" or obj.Name == "B-17G" or obj.Name == "B-52H" or obj.Name == "C-17A" or obj.Name == "C-130" or obj.Name == "E-2C" or obj.Name == "E-3A" or obj.Name == "F-4E" or obj.Name == "F-14A" or obj.Name == "F-15E" or obj.Name == "F-16A" or obj.Name == "F-16A MLU" or obj.Name == "F-16C bl.50" or obj.Name == "F-16C bl.52d" or obj.Name == "F-117A" or obj.Name == "FA-18A" or obj.Name == "IL-76MD" or obj.Name == "IL-78M" or obj.Name == "KC130" or obj.Name == "KC-135" or obj.Name == "KC135MPRS" or obj.Name == "MiG-23MLD" or obj.Name == "MiG-23UB" or obj.Name == "MiG-25PD" or obj.Name == "MiG-25RBT" or obj.Name == "MiG-27K" or obj.Name == "MiG-31" or obj.Name == "MQ-1A Predator" or obj.Name == "MQ-9 Reaper" or obj.Name == "S-3B" or obj.Name == "S-3B Tanker" or obj.Name == "Su-17M4" or obj.Name == "Su-24M" or obj.Name == "Su-24MR" or obj.Name == "Su-25TM" or obj.Name == "Su-30" or obj.Name == "Su-34" or obj.Name == "Su-35" or obj.Name == "Tornado GR4" or obj.Name == "Tornado IDS" or obj.Name == "Tu-22M3" or obj.Name == "Tu-95MS" or obj.Name == "Tu-142" or obj.Name == "Tu-160" or obj.Name == "VSN_F35" or obj.Name == "Yak-40" or obj.Name == "A-50" or obj.Name == "An-26B" then and set the file to read-only as SSforA tries to overwrite it with ExportAutoTune. You may have to spawn in a default FC3 plane before jumping in a modded plane. I see why auto-registering a plane would not be a good idea in some cases, but "manual" adding of planes would be a nice feature.