I have noticed recently that the Flight Time hobbs meter in the SWS Kodiak is incrementing 4 x real time. The Block Time seems to be correct.
Also as I understand it, the Flight time hobbs meter is activated by an airspeed switch but I don’t know if that is how SWS handle it however is it normal for the Flight time hobbs meter to reset to zero before each flight?
I seem to have the Same issue. Itl thought it might be per airframe though but that doesn’t seem to be the Case. The information provided by SWS doesn’t really Help.
I saved my flight after shutdown, lets See If the logged time stays now…
I think that might be a deliberate decision in Order to Speed up engine wear… Otherwise we would almost never experience engine failures within a reasonable time frame…
If SWS is like the other developers, typically the state saving is done per airframe, so if you change anything, either registration or livery, it’ll save another state.
But, state saving requires ending the flight properly, IOW, going back to the main menu after the flight and shutting down MSFS properly (not the x in the top right corner). The file save command can’t be properly performed otherwise.
What happens if the “flight time” meter, which is accelerated, reaches a critical level? Will the aircraft introduce failures and just become unusable after a while? I have all failures disabled in the sim, by the way. Can we somehow reset this or something?
I’m pretty certain that the SWS Kodiak is not modeling system wear over time. The Hobbs meter incrementing quicker than real time is just messing with my OCD
I think this is on purpose. What it does is introducing starter failures the more time passes. This is even stated in the manual if i recall correctly. In order to have that happen without having to wait 1.000 hrs the hobbs meter runs at an accelerated rate. What the ultimate goal of this system is, i do not get (nor what would happen to the timer in such a case) because “repairing” or “replacing” the engine can simply be done by restarting the flight. At least that´s what can be found in the documentation.
I think it was done with the best of intentions but just doesn´t play out very well in practice…