Add save state to the behaviors tool

Ideas
1

Hi Asobo,

Would be very helpful for the SDK Behaviors tool to be save state. I can click build 200+ times in a day. And you’re asking me to re-select two dropdown filters for the model selection each time and also have to type my variable text back into the variable filter window.

This will expedite updating and fixing errors!

2

Nice idea! :slight_smile:

Not 100% sure when that can be done since this tool is being maintained by the Cockpits Team rather than the SDK Team - but I’ll check with them.

Best regards,

Eric / Asobo

1 Like
3

Hi @EPellissier,

Glad you like my idea. Will be looking forward to this in the future! :heart_eyes:

4

Guys,

Any chance this could be implemented? I am wasting so many hours on this everyday.. is getting really tiresome.

With a modular aircraft is even worse, you have an aircraft with over 30 parts, you trying to implement custom animations or code in XML / RPN and you have to build and debug lots of time, last night I think I hit build over 400 times and every single time I had to:

  1. Select my main aircraft from the behaviour tool
  2. Then select the xml relevant to the part I am working on (wing, engines, gears, etc.) this is having to hit the dropdown, and scroll until I find the one I was using.
  3. Then having to select the animation tab, or the tab I was using to debug wherever I was doing, note the changes.
  4. Test
  5. Buid
  6. Repeat the above once again..

Imagine 1 week doing this more than 400 - 600 times per day, I am losing my sanity.. surely your internal teams when they build aircraft must be suffering the same fate as us 3rd party developers?? don’t they raise these concerns? I am struggling to understand how they cannot feel the pain we have, they must be suffering as much as we do.

Same goes for other tools, please consider the way we work with airplanes / scenery during the build process, help us to be efficient and save time.

Best,
Raul

1 Like
5

I also voted because this affects me as well. It’s not really the tedium that is the problem but the time wasted that could be used for higher quality. The problem is compounded when you have many attachments and have to scan a long list.

If at all possible, the dev tools should prioritize a quick cycle between reload - observe - debug - edit code - reload …
Any improvements to the efficiency of any of these steps get compounded so they have high value. UI quality-of-life is also nice but of lesser priority, I would think.

2 Likes
6

Here’s a tip to make this a lot less painful: you can use the SimObject and attachment filters to have the correct attachment selected on package build.
These fields will not be cleared and if you set them so a single entry matches, your attachment will always be selected:

image
image483×118 10.7 KB

Another suggestion, use the Behavior viewer to recompile (Ctrl+R) a behavior file.
Although this will not change the runtime behavior of the aircraft, it will allow you to make sure the file compiles, the anims/emissive/mouserects are created and the generated code matches your expectations.

Regarding what states should be saved, so far your suggestions covers:

  • SimObject
  • attachment
  • selected tab
  • tab section filters (variable name, input event name, component name, node name, etc…)

Is there anything else?

1 Like
7

This helped a tiny bit because now it brings both up like save state and then you only have to paste the text in the filter by variable name.

The Behavior viewer did nothing when pressing ctrl + r and to me seems like it just displays and loads logs.

Looking forward to the update. If not in your list we need to save the text in the filter by variable name? This is a must!