Hello,expected time for the xbox version?
This is a really well done plane for MSFS2024. I really enjoy it. Great work blacksquare.
Question about flaps. Iām using an alpha bravo throttle and the flap system in the plane is not playing nicely by default. Any tips on how to bind the 2 way up and down switch to the 3 position flap lever thatās modeled in game?
Not sure how a two position switch would work. Do you not have a similar binding somewhere for say the ubiquitous Cessna 172 as that is a similar setup? I personally just use two momentary buttons: one for increase and one for decrease. That works perfectly
Nick is working on this.
Looking at a couple of weeks Iād think. No guarantees but that kind of timescale.
State Saving still doesnāt work reliably in the Commander. I thought it is now working differently from previous BKSQ aircraft, but it is still bugged. For example, the Commander always spawns with no chocks deployed, no matter what I try. Same goes with the state of radios. All three state saving buttons are switched to āonā and I exit the game via āQuit to desktopā. Tried other methods like restarting the flight before quitting. That gave me deployed engine and pitot covers, but no chocks. Tried it again with restarting before quitting, and now the covers were not deployed again. Itās basically similar behaviour as with the Duke and other BKSQ aircraft.
Now I wonder whatās wrong. Because allegedly, state saving is done in a completely new fashion then older aircraft.
Can anyone help?
Oh, and the Hobbs meter works fine, thanksā¦ 
Well, you can talk to the planeās actual author over on the Just Flight Forums. If anyone can help, he can!
(MS doesnāt allow devs to do support on this forum, so I understand him spending his limited time on the JF forums.)
Nickās a great dude, heāll certainly help (if no one else beats him to it!)
Iāve had similar issues. My guess is that state saving with the 114 works off a timer.
I did some testing: If I end the flight immediately after an action (like turning off the master switch), next time I start the master may or may nor be off. If I wait a little before ending the flight then all seems well. If it is a timer, it would be good to know what the interval is.
Lucky you, mine gets reset every time. The Hobbs is using MSFS default gauge logic, so Iām worried it will be one of those āwait for Asoboā things.
I sort of had the same experience. I turned off all the switches in the middle, quickly ended the flight, then went back and the nav light was on. Maybe youāre onto something with the timing aspect.
Isnāt that saved in the Cloud? That may be the reason why it seems like there is a timing thing. Itās writing to the Cloud but not every instant. Just a wild guess eh.
PC, MSFS2024, MS Store, Commander 114 purchased from Just Flight.
So far I am very pleased with this aircraft, although it has taken some time to learn. My Hobbs seems to retain the accurate value. My radios keep the frequencies from the prior flight. I donāt think the chocks and tiedowns are in place at the start of a new flight even setting them in the BlackSquare tablet before exiting the prior flight. I will test further.
Hereās a reply from Nick at Black Square for you:
"The Commanderās state saving method is indeed completely new, though I am still at the mercy of Asoboās software, as I canāt save anything to disk myself. Luckily, I havenāt received a single complaint about the new state saving method since the 114 was released, which was better than I could have hoped for. Hopefully what youāre seeing can easily be explained, or is a very isolated local issue.
The wheel chocks, for instance, are not a symptom of the state saving. The issue is that MSFS 2024ās flight start sequence has the aircraft fully loaded and bouncing around violently on the apron as the camera zooms in from deep space. This means thereās no way for me to determine what is aircraft movement that should remove the chocks after the flight starts, or before the flight starts. I just made some changes to this for all my aircraft, which somewhat improves the situation.
As for the rest, Iām still improving the state saving, since this was a very late addition to the Commander, but it would be useful to know whether youāre only seeing the couple of things you mentioned fail to be recalled, or also the other 220 items fail too. If you would like to investigate further, I would be delighted to help on the Just Flight forums. Thanks, guys!"
I hope that is of some help.
And a reply from Nick at Black Square on this too:
The state saving interval is discussed in two locations in the manual:
āThe several hundred parameter states are saved on a rolling basis, with all states being saved approximately every sixty seconds. The state saving options on the tablet interface are saved immediately, meaning that an option may be selected, and then the flight immediately restarted to achieve a default state.ā
āNOTE: To maximize performance, the state variables are saved on a rolling basis. It may take approximately one minute for all the variables to be saved. Quickly exiting the flight after shutting down the aircraft may result in some variables not being saved in their shutdown configuration.ā
Again, I hope that insight helps you all.
Thanks
In other words - donāt rush off, sit and fill out your logbook.
For the life of me, I cannot figure out why they chose to have the physics running during the loading sequence. I think itās on during the aircraft selection menu as well.
So what is the special sauce that A2A uses that makes their state saving so well executed? Is it the use of that Accu Sim engine or something else?
And where exactly is the state stored, and is it JSON or otherwise human-readable? The state.cfg only has the (Asobo-flawed) Hobbs hours. I didnāt find any other obvious locations.