Set COM2, NAV2 for SimAttachement AS155A

[vFlyteAir3dArt]

Gentlemen

I have a question about using SimAttachment in MSFS 2024.
I’m trying to integrate the Asobo_comnav_as155 in my airaft, and the device’s screens are working correctly,
but the controls, in both cases, are related to COM1 and NAV1.

Where can I configure the properties of a connected device? and change controls properies?

I need to connect contrlos to COM2-NAV2 screens,

that was easy to set NavCom2_Screen $poly by Index=2 in htmlgauge00

[VCockpit05]
size_mm=512,70
pixel_size=512,70
texture=$NavCom2_Screens
htmlgauge00=Generic/Radios/KX155A/KX155A.html?Index=2,0,0,512,70

​check out the video here:

Please help.

COM-NAV-Mess.mp4

[EzRyder]

Déjà vu

i may have just answered this here

SDK - MSFS 2024 SimAttachement

[tracernz]

This attachment does not appear to have any DynamicParameters so it wouldn’t be possible to configure that as an attachment.

[vFlyteAir3dArt]

Yes! I posted my problem there also, but still have the problem.Thanks for your advice and recommendations. I’m trying to solve the problem.

[vFlyteAir3dArt]

I explaine problem here again for users who don’t read FSDevelopers

I’m trying to use the concept described here

Included Attachments

docs.flightsimulator.com

The instrument with all controls is correctly integrated into the aircraft. I make the screen separately and specify what it will display in the panel. CFG

[VCockpit01]
size_mm = 512.70
pixel_size = 512.70
texture = $NavCom1_Screens
htmlgauge00=Generic/Radios/KX155A/KX155A.html?Index=1, 0, 0, 512, 70

[VCockpit02]
size_mm = 512.70
pixel_size = 512.70
texture = $NavCom2_Screens
htmlgauge00=Generic/Radios/KX155A/KX155A.html?Index=2, 0, 0, 512, 70

and the screens work correctly.

I tried to change properties in behavior_parameter - see pic. All changes stored in attached_objects.cfg

attach_to_node = WatchTimer
attach_offset = -0.000326,-0.002916,-0.000242
attach_scale = 1.05

[SIM_ATTACHMENT.4]
attachment_root = simattachments\instruments\asobo_comnav_as155
attachment_file = model/asobo_comnav_as155.xml
attach_to_model = interior
attach_to_node = KX155A_1
;[REMOVED]attach_offset = 0.001048,0.006441,-0.003874
;behavior_parameter.0 = “1”
behavior_parameter.0=“COM_INDEX,1”
behavior_parameter.1=“NAV_INDEX,1”

[SIM_ATTACHMENT.5]
attachment_root = simattachments\instruments\asobo_comnav_as155
attachment_file = model/asobo_comnav_as155.xml
attach_to_model = interior
attach_to_node = KX155A_2
behavior_parameter.0=“COM_INDEX,2”
behavior_parameter.1=“NAV_INDEX,2”

you can see I tried different ways but have the same problem.

It would be nice to use new conception to attach already exists instruments in the model but how change their behavour?

[EzRyder]

changing the behaviors is only half of it (that looks right though ive not done this in 2024 yet)
did you add that suffix to the model node and anim names in Blender (or 3dsmax) as well?

my example i only have one radio,

these are the names you need
the first radio would be a _1 for that #suffix_id# on each part and animation
the second radio would be a _2 for that #suffix_id# on each part and animation

NavComSystem.xml

[vFlyteAir3dArt]

Thank you for exploration.

In my previous model “The Twin“ I used fool 3d model of the COM/NAV radio and connect all animations:

but for NeXT project I’m trying to use several instruments from Asobo_Library

Included Attachments

so in model I only plase a dummy object and $-poly for the screens

then im dev menu connect selected instrument to selected node:

I guess all additional paramentres using dev interface

and will see all changes in attached_objects.cfg

So it isn’t problem to make 3d model of the instrument and connect all animation manually,

but it would be nice to learn how use a new conception and connect NAV2, COM2 to sim object. COM1, NAV1 - is def setting and it works without problem

[EzRyder]

your right
im confusing myself thinking of 2020

dont those already have a screen? and code? if your using that attachment it should be pretty much self contained afaik

the cpl i added just needed the entry for attached_objects.cfg in the preset, everything merged in automatically

[vFlyteAir3dArt]

Yes, the code is somewhere, but for the basic devices, I only need to set a few parameters for operation and interaction: radio and navigation channels, a power supply fuse line, and a backlight control channel. I seem to be putting them in the right places, but there’s no proper response…

[EzRyder]

i meant it looked like you where adding the screen in a pic above, just kinda thought you might be covering up the one thats there

the code is on the server, you can use the VFS Viewer to browse them, they should have all of those behaviors already
the as155 is here and it is completed coded with the new 2024 format already as far as i can see
VFSProjection\simattachments\instruments\asobo_comnav_as155

you only need a panel.cfg entry maybe (thats not there)?

[JimStewart]

As @tracernz mentioned, the AS155A simattachment has no dynamic parameters configured in it’s model behaviour code, which is a quick giveaway that it’s hard coded to control one set of radios only. If you use the VFS projector and read through the asobo_comnav_as155.behavior.xml file, you can see that it looks to be hard coded to com1 / nav1 only.

Regardless of what the JS gauge is capable of doing, the xml controls in the simattachment have no capability to control com2/nav2. Asobo could, if they so want, add a dynamic parameter and supporting code that could then switch what com & nav the attachment is controlling, or alternatively, provide a second xml file within the attachment that could be referenced that controls com2/nav2.

Until then, you’re stuck using the simattachment for com1/nav1 only, and would have to go back to the older method of using your own mesh and behavior xml for a com2/nav2 solution.

[EzRyder]

so would this work ?

duplicate and rename both attachment xml’s in asobo_comnav_as155\model folder
add these renamed files to your package so they end up beside the originals
edit the custom xml loader’s relativefile line to point to your custom behavior file
and edit that custom behavior file to point to com/nav2 ?

then you just have a dif xml (same base location) to point to in the attached_objects

ive done that kind of ‘file manipulation’ before but not exactly for this

[JimStewart]

To be honest, at that point it’s just easier to do it the normal method using your own mesh and xml.

[vFlyteAir3dArt]

Probably… well I will try to solve this problem couple days… if not I use traditional way!

Thanks you for your advices

[DA40CGDFQ]

Was going to report this as a bug, but found this thread. I think this is a bug and should be put on the list to fix. It is not fair to develop a system of sim attachments, and not allow for a second one. Other simattachments have indexes for a second one. Why not for the AS155 radio. Seems to be a common requirement.

@Boris

Thanks

[Boris]

Hello,

I moved this topic in [MSFS 2024] Bug Reports and I logged a bug in our backlog for the missing DynamicParameters of the SimAttachement AS155A.
I will let you know when I have some update to share about this.

Regards,
Boris