SU5 so far so good
-
Multiple flights w/ B36TP after the SU5 release/update, no issues observed. Looking at my TO roll log file, it seems that this aircraft has more entries than all of the others ... it's really a solid platform for deepened learning, be it keeping the PT6E within parameters, ETM (thanks for enabling pop-out of the display), GTN750 advanced techniques, and at some point failures. It's so enjoyable.
-
Thanks for the report, and glad you're enjoying it
Indeed, I think the Turbine Bonanza is one of the hidden gems of my fleet. I keep thinking to myself, "oh yeah, that exists", so I'm glad to hear that so many of you are enjoying it. It's a very unique machine! -
I’m still experiencing an issue where my hobby flight hours counter is not being saved properly. It seems that the total flight time (hours counter) does not persist between sessions.
I came across a mention from Asobo about configuration files used for developer verification, which made me wonder if this issue could be related to those files or to a problem with saving user data.
Additionally, most Black Square aircraft do not retain their assigned hardware controller profiles. This is quite frustrating, as every time I start a flight, I have to manually reselect the correct controller profile (for example, my joystick profile).
-
I’m still experiencing an issue where my hobby flight hours counter is not being saved properly. It seems that the total flight time (hours counter) does not persist between sessions.
I came across a mention from Asobo about configuration files used for developer verification, which made me wonder if this issue could be related to those files or to a problem with saving user data.
Additionally, most Black Square aircraft do not retain their assigned hardware controller profiles. This is quite frustrating, as every time I start a flight, I have to manually reselect the correct controller profile (for example, my joystick profile).
@SebAvi said in SU5 so far so good:
I came across a mention from Asobo about configuration files used for developer verification
I'm not sure what this means, but if you could find this mention, I would be interested to read it. As I've said before, the hobbs saving (as opposed to triggering the hobbs to run and at what rate), is entirely handed by Asobo, so I think it's unlikely to be an issue with my aircraft. Anything is possible, though.
@SebAvi said in SU5 so far so good:
most Black Square aircraft do not retain their assigned hardware controller profiles
I have only heard of this happening to the Caravan Amphibian so far, which we theorized might be due to its long name. Which other aircraft have you seen this with? If we have some more information to go on, perhaps I can raise this with Asobo to get it fixed.
-
@SebAvi said in SU5 so far so good:
I came across a mention from Asobo about configuration files used for developer verification
I'm not sure what this means, but if you could find this mention, I would be interested to read it. As I've said before, the hobbs saving (as opposed to triggering the hobbs to run and at what rate), is entirely handed by Asobo, so I think it's unlikely to be an issue with my aircraft. Anything is possible, though.
@SebAvi said in SU5 so far so good:
most Black Square aircraft do not retain their assigned hardware controller profiles
I have only heard of this happening to the Caravan Amphibian so far, which we theorized might be due to its long name. Which other aircraft have you seen this with? If we have some more information to go on, perhaps I can raise this with Asobo to get it fixed.
@Black-Square I’m having an issue with almost all of your aircraft when it comes to saving the hardware profile. It’s strange, because for example my rudder pedals are saved correctly, and my Moza setup works fine as well, but the Bravo always loads with the default profile.
thats what I find in SU5 release note:
"Modified configure binding in freeflight aircraft selector to select the aircraft currently hover before starting the configuration."Regarding to state saving, they said:
"Fixed an issue that caused Persistent Variables to not get saved when going back to the main menu."
and maybe this:
"The PERFORMANCE_DATA section of the flight_model.cfg has been moved to the flight_performance.cfg file. It will still be loaded from the flight_model.cfg if it is missing from the flight_performance.cfg to ensure backwards compatibility." -
@Black-Square I’m having an issue with almost all of your aircraft when it comes to saving the hardware profile. It’s strange, because for example my rudder pedals are saved correctly, and my Moza setup works fine as well, but the Bravo always loads with the default profile.
thats what I find in SU5 release note:
"Modified configure binding in freeflight aircraft selector to select the aircraft currently hover before starting the configuration."Regarding to state saving, they said:
"Fixed an issue that caused Persistent Variables to not get saved when going back to the main menu."
and maybe this:
"The PERFORMANCE_DATA section of the flight_model.cfg has been moved to the flight_performance.cfg file. It will still be loaded from the flight_model.cfg if it is missing from the flight_performance.cfg to ensure backwards compatibility."@SebAvi What a pain that we can't even rely on saving control profiles. I've only installed SU5 a little earlier, and I have spent 98% of my time restarting it after crashes in developer mode.
The first of the two change notes refers to the other saved parameters discussed above, but specifically not the hobbs time. The second note has nothing to do with state saving, nor is it a feature I use in any of my aircraft.
-
Thanks for the quick response. So it looks like we’ll need to wait for Asobo. In the meantime, I’ll check how the hobbs counter is saved in the COWS DA40. I really appreciate your replies, and I’m keeping my fingers crossed for your next update to the Bonanza/Baron fleet, as well as the new aircraft you’re working on.
