Selecting the custom “on ground - shut down” spawn loads both Apron.flt and Runway.flt
Runway.flt config
Apron.flt config
Lavrs in game
following..
1 Like
Hello,
I tried to reproduce the issue by adding the LocalVars to Runway.flt and Apron.flt as shown in your screenshots, but without success.
Do you have any other code elsewhere that might be changing the value of these LVars?
If not, we’ll need the project to be able to reproduce.
See 3) Provide Private Content
Regards,
Boris
The default 172 also spawns running
use any COWS product from the marketplace.
For the cows (DA42),
runway.flt isn’t loaded when spawning with Custom + Shutdown. I believe this is the logic you’re using that sets this LVar:
I also created two local vars in apron / runway.flt in your aircraft files :
apron.flt :
runway.flt :
This is the result when I spawn on custom - shutdown and search for FLT :
Can you test with the same steps I did above and tell me the result ?
Regards,
Boris
But you saw his video? the airplanes are starting “running” then the engine shutdown.. this is wrong because the state of the aircraft is going to be altering high quality products simulations due to such jump of states.
For example, with FSR500 you cannot start and engine that was running immediately, because it is hot, and it could cause a “hot start” of the turbo engine unless you perform a “dry-run” 1st.
Because the engine is set to run on that state, then “off” now my simulation believes the engine was running, it will set parameters in the wrong state and as soon as the user try to start the engine it will trigger most likely a hot start condition, which will puzzle the user since he chosen to start the aircraft as “cold and dark” from the main menu.
Ideally, the airplanes should come with engine totally off since it was selected as “on ground and shutdown”
You follow now what we experiencing?
Best,
Raul
2 Likes
In my previous post, I was writing about the .flt loading issue, but my bad, I should have also mentioned that I was still reviewing the aircraft running before clicking on the “ready” button.
Regards,
Boris
1 Like
I have logged the bug in our backlog for the aircraft running when spawing in custom - on ground
Regards,
Boris
1 Like
That “start_hot ++ >start_hot“ code is only triggered by “start_hot” being set to 1. (This is old code and it doesn’t increase anymore)
Anyways, similar issues can come from both files being loaded. If the user turned off the fuel on the previous flight, then the fuel pumps will run dry or the fuel lines will start to boil, causing damage or vapour lock depending on which plane.
If I would test it then I would get the same results as i had before.
This topic has been automatically closed after 60 days of inactivity since it was marked as fixed.
If there is important new information about this same report, you can use the “Request reopen” button below to ask the moderation team to review it again.
For other issues or broader discussion, please open a new topic in the appropriate category.