ASOBO_FUEL_Switch_Cutoff_Template only works for engine1 valve

Version: 1.34.16.0

Frequency: Consistently

Severity: High

Bug description: *Adding a second ID does not work. Also I noticed the Engine count does not work right. If you set for 2 the CUR_ID does not just change to 2 but the code doubles up mixing both index 1 and 2.

I believe this did not get noticed since all your default planes that use this template are single engine.*

Repro steps:

Attachments:

Private attachments:

1 Like

I reported this for another dev. So it’s not my project using this template. I wrote him a new template as this one is broken. You can test it with any project.

Simply take a twin and add 2 switches then point to this template and have 1 use the <ID>2</ID> tag as that is what the template uses. And you will see both share the same animation.

Hello @Flysimware

I was not able to reproduce this issue.
I edited the Da62 to replace the ASOBO_FUEL_Switch_Cutoff_Crossfeed_Template and was able to manipulate both levers independently with the expected B:FUEL_Cutoff_1/2 being sent.

If you have a package that demonstrate the issue, we can investigate further.

Regards,
Sylvain

Hi @FlyingRaccoon

Wrong template. Use this. Also it’s a toggle switch when you test.

ASOBO_FUEL_Switch_Cutoff_Template

Hello @Flysimware

That’s what I did, I replaced ASOBO_FUEL_Switch_Cutoff_Crossfeed_Template by ASOBO_FUEL_Switch_Cutoff_Template and had those 2 levers behave like switches.

1 Like

Hi @FlyingRaccoon

Ok that makes sense now. I was helping another dev as I use my own templates most of the time. But I have to agree with this other dev this seems to not work. I repeated your test and it worked. So here are some images showing my setting to match the templates names. If you do this setup it fails. So what are we doing wrong as we normally know how to match animation and node names.

Thanks,


Hello @Flysimware

Can you please send us the package that reproduces the issue?

Regards,
Sylvain

Hi @FlyingRaccoon

What is the new method for sharing a project privately? Although the 2 images gives you the exact info to reproduce the result. Not sure the project itself will make any difference. But not as big deal I used my test project and have no issue uploading it. I just prefer private than public.

Hello @Flysimware

Because that’s exactly how I’ve set up the DA62 for testing.
If you have a package that demonstrate the issue, it will be more efficient for me to investigate it directly than to ping pong suggestions until we identify the culprit.

How to provide private content is explained in section 3 here.

Thank you for your time.

Regards,
Sylvain