Version: FS2024 Dev Alpha 1.0.72.-
In FS2020 there is a Quick Reload button in the Behavior Debug window, which speeds up reloading of the plane without having to do a full build. This seems to be absent in the FS2024 dev alpha.
As the quick reload saved us a lot of hours during developement, is it possible that the button will be added again for FS2024?
Thanks,
Alex
Plus one on this oneâŠ
It seems you can do the same by using the aircraft selector tool, and click Load.
It does not reload everything. I.e. modifications to the sounds are not loaded.
+1 to this one. Though seems that the new recommended method is building package every time, as SimObject asset reloading is now enabled by default.
anyother +1 here.
+1 here too
+1 to this one also !
We spend a lot of time, compiling aicraft so each possibility to gain time is good for us. I think asobo as a developer should be aware of the problem and concerned about solving it 
that wouldnât make sense at all - the vast majority of my changes are tweaks in a files the package build doesnât care about at all other than to include them in layout.json. The idea of doing a full package rebuild each time would be crippling.
Itâs impossible to tweak flight dynamics if you have to recompile the full package every time. Or at least it would take an insanely long time to accomplish.
Save and Apply changes in the SimObject Editor also seem to have no effect. I keep changing the fuel flow scalar to see if the change takes affect and no matter what I change (tried to change the value in the source and package files and while I can see they are changed) whenever I use Save and Apply it doesnât apply the changes.
At the moment aircraft editing seems to be impossible without restarting the whole sim. Unless I am missing something.
We need a way to quickly reload CFGs, XMLs and HTML!
lol develop those in 2020 and port them over to 2024 when completed
Not efficient when the project is setup to be modular and using new EX_1 events and variables
lol sorry that was an attempt at humor
CFG/XML in the community folder can be reloaded by reloading the dummy Aircraft project and restarting free flight, but this takes about a minute each time.
This is a very helpful feature that would assist in development, please implement the Quick Reload button!
As far as I can tell, MSFS2024 will refuse to load a file from the VFS if its file size doesnât match layout.json.
We really need a dev setting to temporarily disable this - the load function obviously knows the correct size in order to be picky and decide not to load the file, so an override will be for the load function to simply use the correct size it calculated.
Then we need a simple âreloadâ button.
At the moment you canât do a simple edit to (e.g.) an XML file without changing the size, and the VFS collapses in a heap at that point.
If Asobo donât fix this, the workaround will be for people to add padding into the (e.g.) XML file so the file can be adjusted back to the size the VFS likes before saving - this is obviously not ideal.
Just another bump on this. We really need quick reload to come back to quickly iterate with Flight Models, HTML and XML edits. Otherwise we are stuck working in FS20 for the convenience aspect. I understand it was removed by design - but given the feedback from all the developers above, it seems to be a very poor design choice.
I think weâll all necessarily be repeating the same steps, which would be helpful if those were actually in the sim dev UI, i.e. a button saying âreloadâ does whatever it is Asobo thinks would be super-easy for every plane developer to do:
Thereâs a very significant underlying issue that the flight model in MSFS2020 is clearly different than MSFS2024, but thereâs never been any mention of this so it probably isnât understood or Asobo donât know what theyâve done to make the flight model behaviour different. So actually the use of MSFS2020 to iterate test the flight model is a bit of a bust even though the update-test cycle is much more productive than working in MSFS2024. YMMV but gliders require getting the flight model right as even a 2% difference in glide performance between two planes is enough to have one unrealistically trounce the other in a cross country competitive flight (totally reasonably a game company will accept maybe 40% accuracy in a glide performance in stock planes, but that doesnât cut it for our multiplayer gliding community). The deltas Iâve noticed so far in the flight models are stall behaviour and the trim speeds, but itâs impossible for me using the flight model to work out what changes the programmers have made.
To give MSFS2024 huge deserved credit, the new âWind Tunnelâ debug window is absolutely awesome, so thereâs a bit of a trade off between that and the update-test productivity hit. But net-net 90% of my flight model development is done in MSFS2020 (it takes weeks of work, and I canât afford that to be months) so I get the flight model most of the way there and then test in MSFS2024 to see whatâs mysteriously different.
I do understand this thread is flagged âby designâ so not suggesting any further development should be expected.