Propellers 3DSMax Material is not working properly for Turbofans

Version: 1.5.1 / SU3

Frequency: Frequently

Severity: Low

Marketplace package name: Any airplane with jet engines using the new animation method.

Context: What package? in flight, cold and dark, at ramp / gate.

Bug description:

When configuring a turbofan engine as per SDK instructions setting the material of the turbofans to “Propeller” and configuring the engine data with the number blades, nodes, etc.

It results on the turbo fan to never stand still, and spin always:

-It spins endesly, despite there is zero wind whatsover.

-It spins even when the covers are set to ON, which should not allow the behavior since there is nothing physically allowing the engine to spin.

I cannot use it at the moment, the entire feedback I got from my internal team is that this very disturbing, unrealistic and I had to revert to the old method from MSFS 2020 with still, blur, etc. and using eng RPMs for animations.

NOTE: The material works fine with propellers engines and rotor crafts.. only turbofan engines are affected

Repro steps:

A) Load the 737 Max, set winds to calm, no wind.. note how the fans spin all the time..

B) Bug 2, put covers on, wait 1 minute, take the covers out, note the fans are spinning.

The fans should be still when powered off, no significant wind and also if the covers are on..

If you test with the CJ4, you will notice how the blades and fans are still when engines are powered off, this is because this aircraft is using the old method, animating the fans based on eng RPMs. The expected behavior with the new material is this.. even more with covers set.

Best,
Raul

1 Like

Weekly bump..

Please guys, it would be lovely to have this working correctly for jet / fans.

Best,
Raul

Hello @SimbolFSReborn

I could not replicate this behavior so far.
Spawning the 737 at a ramp, the engine fans were standing perfectly still.
Let me know if there is additional context I am missing.

Regards,
Sylvain

Hi Sylvain,

I still see the issue, this video shows what I mean, is still happening on my system 1.5.13:

Best,
Raul

I’d like to throw out a idea that since a lot of things are now done by shaders, that there is an issue with not setting the object’s rotation (or move/location) axis properly.

I recently had an issue with windshield rain not going in the correct direction. the issue was the result of not setting the rotation to 0,0,0 of the windshield objects. I use blender so this was not an issue before in 2020 using UV’s for rain. UVs are no longer used in 2024 for rain.

I just had a discussion with another dev that uses 3DS, and he had a rain direction issue also. He had to reset the rotation orientation to -ve y (I think) , anyway the object rotation axis was the issue.

Since ASOBO cannot reproduce the issue in-house, maybe there is an issue with some axis or whatever on your project.

I have no idea if this is the problem, just throwing it out there as something to consider.

Also add the “fix” to the SDK documentation that both Blender and 3DS are affected.

Since a few other things are now dependent on shaders, other features could be affected.

I am seeing this with the Max 737, not only my project.. the video I posted, you can see the blades always spinning.. forever..

R.