Adding two [SIM_ATTACHMENT.n] for interior causes flap handle to break

[MSFS 2024] Bug Reports Aircraft
1

Sim: Beta 1
Version: 1.3.10.0
Severe: and need to know now what method to use!

Bug description: I found that my flaps handle was acting strange and going full max or full retracted even if i were to use the F6 and F7 keys to rule out any hardware issues or code.

After a long time locating the reason, my findings I find are odd.

I created several SIM_ATTACHMENT to the interior. If I remove all but one the flaps handle works normal. If I remove all but two the flaps handle for a 4-position flaps will move to 3-positions. Only when I leave only a single interior attachment will it act normal. No other issues in the some but the flaps so far are behaving oddly.

Here is my attached_objects.cfg
attached_objects.cfg (1.6 KB)

You can see this is very standard. Are we not allowed to have more than 1 [SIM_ATTACHMENT.0] for the interior???

I did notice the DA62 has two exterior but only 1 interior. And they used a ModelMerge instead for the interior. I tried to copy this method but it never works for me. But I should be able to use the method I am using now as it’s working perfect except the flaps handle bug.

P.S. The mouse moving the flaps works normal. It’s only hardware and the keyboard F6 and F7 that behave strange. Hope to see this fixed or let us know if there is a limit for [SIM_ATTACHMENT.0] for the interior.

1 Like
2

Hi @FlyingRaccoon

I wanted to add some images showing the two methods and what these do differently. And hope you guys can confirm if this is a bug or you need to ModelMerge if you plan to use more than 1 interior function call.

This is when the preset has one [SIM_ATTACHMENT.n]. This is a ModelMerge and the flaps handle behaves normal when using the F6 and F7 keys. The two far left functions.

Screenshot_234
Screenshot_234578Ă—741 21.9 KB

This is when the preset has two [SIM_ATTACHMENT.n] for the interior functions. For every extra interior [SIM_ATTACHMENT.n] the flaps handle to skips 1 flap position in each direction. If you have three interior [SIM_ATTACHMENT.n] the flaps handle skips 2 positions in each direction.

Screenshot_235
Screenshot_235758Ă—755 35.7 KB

3

What behavior code are you using in your two function interior attachments? You could be having a conflict with the input event that controls flaps. If both attachments have a flap control, it could be firing both on the same event and incrementing the flap position twice. And if you add a third attachment with a flaps input event, you get three increments. Just a thought.

5

I also thought of that too. I have two Functions.
Function_Interior = calls to my modelbehaviordef asset for code.
Function_Interior_Cabin = calls to the Function_Interior to borrow that call.

<Behaviors version="1">
    <IncludeBase RelativeFile="..\..\Function_Interior\model\Cockpit.xml"/>
</Behaviors>

I have tested with no code or RelativeFile as as i thought the same thing. And it does not matter. Just adding more than one [SIM_ATTACHMENT.n] seems to be the issue. And the DA62 use the ModelMerge method.

But I was thinking since you brought this up I will remove all calls to code from any exterior and interior that is not the main function. This way we can rule that out. I am curious and I never tried removing the extra exterior calls.

6

It shouldn’t take too much time to comment out some behavior code so you can try to isolate the issue. Also, make sure you don’t mix 2020 behaviors with 2024 behaviors in the same modelbehaviors file. I was having all kinds of issues when I did that.

In fact, this post caught my attention because I had a somewhat similar problem with flaps but in my case, incrementing or decrementing flaps made it jump to full or retracted and never stopped in the right notch.

7

That is the same issue where is does not stop at the right notch. And just goes full or retracted. But if you read my description it depends on how many interior [SIM_ATTACHMENT.n] you have VS how many flap positions. You lose 1 position for every extra attachment. So, it is the same issue.

I have already commented out code but only interior. So, I plan today to comment out all extra code calls.

Yes, there is a bug or a rule where you can’t mix EX1 code with non EX1 code. But only for interior. Exterior you can mix and compile. But you must call the 2024 code first followed by the 2020.

<CompileBehaviors version="2">
	<IncludeBase RelativeFile="Nieuport_24_2024_Exterior.xml"/>
	<IncludeBase RelativeFile="Nieuport_24_2020_Exterior.xml"/>		
</CompileBehaviors>
1 Like
8

Yes, this was the issue as calling to the base xml causes the logic to fire twice if you use the RelativeFile method.

So instead of using RelativeFile as seen here.

<Behaviors version="1">
    <IncludeBase RelativeFile="..\..\Function_Interior\model\Cockpit.xml"/>
</Behaviors>

I now just called to the exact xml I need for this model.xml.

<Behaviors Version="1">
	<Include ModelBehaviorFile="FSW_Learjet_35A\Custom.xml"/>		
	<Include ModelBehaviorFile="ASOBO\Generic.xml"/>
	<Include ModelBehaviorFile="ASOBO\Common.xml"/>			

	<Component ID="MODEL_BEHAVIORS_DEFS">
		<UseTemplate Name="Flysimware_Cabin_Template"/>						
	</Component>		
</Behaviors>
1 Like
9

Is this the fix then, and it was working as designed?
Or is there still a problem and this is a workaround?

10

Hello @Flysimware

IncludeBase includes the components so if you do this in multiple attachments, you will have duplicate components.
Sometimes, that’s something you want and you use the attached_objects.cfg alias parameter and associated mechanics to differentiate the behavior.

But if you only want to get the templates and functions, Include must be used instead.

Regards,
Sylvain

1 Like