Interaction Bug using ASOBO_IT_Switch_Template in nested simattachment

[JimStewart]

Version: 1.5.27.0

Frequency: Consistently

Severity: Blocker

Marketplace package name: if applicable

Context: Modular project using EX1 templates. Base interior is loaded from the attached_objects.cfg file within a preset, secondary panel loaded as a simattachment through an attached_objects.cfg file loaded within the base interior. All other loaded attachments work as intended, other controls (throttle quadrant, instrument animations) on secondary panel work as intended.

Bug description:

Seeing a bug where a two position switch set up with ASOBO_IT_Switch_Template is behaving differently depending on which attachment it is in.

Within the base interior, the switch fully functions as intended - all interactions work properly (click, mousewheel), values are set correctly, and externally setting the value through the behaviour tool updates the switch position correctly.

Within the secondary panel, the switch appears to function normally EXCEPT that it does not receive a click interaction to toggle the switch. It accepts mousewheel interaction where the value will be toggled and the switch animates, and the value may be changed through the behaviour tool whereupon the switch animates correctly.

Looking at the InputEvents tab in the behaviours tool, I can see a difference in that not all the bindings are created for the switch in the nested attachment:

Base interior: AUXILIARY_TEST_SWITCH_1

Panel: AUXILIARY_TEST_SWITCH_2

Both switches are created for test purposes using the same configuration:

It did not make a difference if the nested panel attachment was loaded alongside the base interior in the preset attached_objects.cfg, the behaviour was the same.

[Boris]

Hello,

Can you share with us your project please? (Or at least a minimal sample that reproduce the issue)

See 3) Provide Private Content

Regards,
Boris

[Boris]

Hello,

Tagging this topic as obsolete.
Feel free to ping us here if you are able to reproduce the issue and provide a sample project that demonstrates it.

Regards,
Boris

[JimStewart]

Sure.

I never caught your original request, but without a way around it, I ended up moving away from using an attachment for this, and instead merged the panel in question back into the cockpit. It’s less efficient from the sim’s point of view, since it makes the overall structure less modular, but at least it works as intended.

Unfortunately, it’s kind of a ‘what came first, chicken of the egg?’ scenario, as since I encountered issues in making it work, I’m very unlikely to waste any time in trying again, and instead simply export multiple copies of the cockpit with differing panels in scenarios like this.

[system]

This topic has been automatically closed after 60 days of inactivity since it was marked as obsolete.

If there is important new information about this same report, you can use the “Request reopen” button below to ask the moderation team to review it again.
For other issues or broader discussion, please open a new topic in the appropriate category.