MSFS 2024 Aircraft Project build - always ignores the .flt states

[MSFS 2024] Bug Reports Aircraft
, , ,
1

Version: 1.54 / SU3

Frequency: Consistently

Severity: Blocker

Context: What package? When editing and hitting project build

Bug description:

When you build an aircraft project in MSFS 2024 via Project ----> Build, it always sets the aircraft with all the engines running and any states you might have had set are totally ignored.

This makes the developing process incredible slow, as we have to restart the flight to test things we changing. Typical examples:

  • When trying to build the pre-flight elements, we adding flags, adjusting their positions, changing code in behaviors.xml, etc. you hit build to compile and see these, the aircraft loses all the covers, engines go running, and you cannot test what you were trying to do. Now you have to restart the flight to re-tests. Imagine doing this 150 times..

  • When trying to code behaviours on the aircraft to verify starting procedures, etc. same problem, imagine trying to code custom system for hot engines starts, etc. you hit build and you aircraft is now once again, fully running with wrong states, unable to test from proper cold and dark.. only way around is hitting “restart flight” and wait, wait, wait, repeat, wait, wait, wait.. repeat.. this makes us waste so much time.. honesty sometimes I feel like I am losing my mind..

  • When coding checklist, same issue, you trying to test a checklist from cold and dark, impossible, you have to restart every time.

Ideally, if I started the 1st flight on apron (cold and dark) when I hit Project —>build it should again put the aircraft as how apron.flt instructs and reset it all..

If instead, I loaded the aircraft on runway (running on runway) when I hit the Project —> build, it should this time read the runway.flt and load the aircraft once again on that state.. similarly on aproach.flt, flying, etc. this is why the .flt files are for but they seem to be totally ignored in devmode when you hit project build.

Repro steps:
Load a project at an apron, hit build.. you will notice how the covers are gone, etc. and many systems are reset as if the aircraft should be all powered up with engines running.

I would really apreciate if this could be given some sort of priority, it affects HEAVILY our speed to develop projects and surely it is on the benefit of everyone (Microsoft, Asobo, 1st party developers, 3rd party developers and customers) to expedite our 2024 native projects and conversions from 2020 so transition towards new technologies available in MSFS 2024 occurs faster,

Best,
Raul

2 Likes
2

I agree with Raul.
This would a welcome inclusion.
Stu

3

Bump.. any news?

Best,
R.

4

Not for SU3.
This will likely be addressed with SU4.

Regards,
Sylvain

2 Likes
5

That is awesome. Thanks for the reply back.

6

Hello @SimbolFSReborn

This has been changed in SU4.
Aircraft state after a rebuild should now be more consistent with the state it was originally spawned in.

Regards,
Sylvain

1 Like
7

copy, I will test as I am having some stability issues on SU4 with projects using WASM, which I will need to report.

So bear with me for this test..

R.

1 Like
8

Yes thank God, much better! this is heaven.. you guys have no idea how much I wanted this fixed.. Thank you so much.

So, it is working great for me now, except for two things:

  • When I compile it always deploy for me full flaps.
  • When I compile it always deploy the spoilers.

Everything else is staying perfectly.. Any ideas?

R.

1 Like
9

–Comment removed, solved thanks to Raul–

10

I can investigate.
Is this specific to your aircraft or you have the same behavior on the Da62 SDK sample?

Regards,
Sylvain

11

ok let me see if this happens with the example of DA62.. if it doesn’t, I send you my project via PM.

R.

1 Like