need track replay Overtemperature timer missing leading 0 in seconds

[FalcoGer]

When the TGT exceeds safe limitations for continuous flight a 30 minute timer appears on the engine page. if the seconds on that timer are below 10, the leading zero doesn't show such that it reads for example "29:4" instead of "29:04". It's a minor thing but it looks awkward and should be easily fixed.

Edited March 28, 2022 by FalcoGer

[charliefox2]

Can confirm, I've seen this behavior as well. There's actually a space so it's formatted as "29: 4" currently iirc, but yeah seems like it should be "29:04"

Edited March 28, 2022 by moridar

[Raptor9]

I've seen this as well.

[hotrod525]

Excuse my ignorance, but, wait what ? There is a countdown starting whenever you over throttle the bird ? Didnot even know' lol.

[FalcoGer]

"Needs track replay"? Are you serious? I told you exactly what the problem is. MULTIPLE people confirmed it, including raptor9 which is a SME.

There is no need for a track replay. If you need a track so bad, then just put your hot apache on the ground in syria in the middle of summer and torque up and wait 50 seconds. The time it takes to do that: about 120 seconds, including loading time. The time it takes me to do that for you: 15 minutes, including saving the track, uploading it here. On top of that I'd need to try to get the "needs track replay" nonsense out of the way because apparently even IF i were to add a track, nobody ever checks anything again after it has gone onto the "needs track" pile.

I'm not your bug hunting team, I report bugs as I find them. If you need more, then reproduce the steps outlined by me and others. There is no need for a track that is clearly a visual or formatting error that appears 100% of the time in conditions that are reproducible reliably. I like to fly the products I have bought from you, not debug your problems for free, thank you. If you were to pay me, I'd happily send you all the tracks you want.

 

PS: Please check your messages @NineLine

[NineLine]

As I told you in the PM, we have guidelines for reporting bugs, we ask that each report come with a short simple track. We need to make tracks to view and verify the issue, and we need the track to send to the team as well. Now imagine you are not the only one reporting bugs, and the -64 is not the only module we are working with. I dont think it is a big ask to include a track, and its not like it is this one time for you, it is every report you refuse to give us a track. While we appreciate any efforts to help us make these modules the best that they can be, help us out a little with getting the proper info and required files. 

Please and thank you.