Version: 1.5.23.0
Bug description: See video. No matter what even if I change the <RPM_THRESHOLD>20</RPM_THRESHOLD> the visibility mesh are not in sync from the <NODE_VISIBLE_AT_LOW_RPM> to or from the <NODE_VISIBLE_AT_HIGH_RPM>
Version: 1.5.23.0
Bug description: See video. No matter what even if I change the <RPM_THRESHOLD>20</RPM_THRESHOLD> the visibility mesh are not in sync from the <NODE_VISIBLE_AT_LOW_RPM> to or from the <NODE_VISIBLE_AT_HIGH_RPM>
Hello @Flysimware
Can you share a version of your package?
I can’t really help without more context.
The template is used by our own aircraft without demonstrating such issues:
<Component ID="PROPELLER_VISIBILITY">
<UseTemplate Name="ASOBO_ET_ENGINE_Propeller_Model_Swap_RPM_Template">
<NODE_VISIBLE_AT_HIGH_RPM>PROPELLER_01_BLUR</NODE_VISIBLE_AT_HIGH_RPM>
<NODE_VISIBLE_AT_LOW_RPM>PROPELLER_01_STATIC</NODE_VISIBLE_AT_LOW_RPM>
<ENG_ID>1</ENG_ID>
<RPM_THRESHOLD>100</RPM_THRESHOLD>
</UseTemplate>
</Component>
Regards,
Sylvain
I too use this template with no issue for our piston engines. Was your own aircraft a jet? Did you test using TURBINEENGINEDATA?
[TURBINEENGINEDATA]
turbine_blades = 30
turbine_node.0 = Nodes:ENGINE_Turbine_Still_1
turbine_node.1 = Nodes:ENGINE_Turbine_Still_2
No, this template is only used on pistons and turboprops.
The documentation is incorrect on this. This template relies on the PROP RPM simvar, which is not written to in the case of jet engines.
As far as I can tell, we don’t have an equivalent template for jets and don’t swap to a lower polycount version of the fan.
We will correct the documentation
Regards,
Sylvain
I was about to tell you this since I inspected the templates a few weeks ago when I was looking into my Jet project to implement low poly and high poly fans and do a swap.
The template can only work with propellers not fans unfortunately, now it would be good to find a solution to do it for fans too? surely there is a performance bost to swap to a low poly version of the fans when using the new shaders?
Best,
Raul
They just need to fix it, there is already an SDK method for TURBINEENGINEDATA and we use the tag called turbine_node.n
It got marked as a bug_logged today. Thanks @FlyingRaccoon
@Flysimware @SimbolFSReborn The documentation will be fixed. I don’t think the template will be modified in the near future.
But that template just relies on subtemplates that you can use yourself to do something similar.
Regards,
Sylvain
Hello everyone
Relevant information was added in SDK 1.5.3 documentation
Regards,
Sylvain