AO performance self-monitoring tool #328
Slippin-Thru-Matrix
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hey there. Problem First - Then Solution..
Situation: Not having any real knowledge on computers / programming etc - a lot of the settings/sliders are somewhat mysterious, as is the debug log. While I'm sure others know what it is, plenty don't. I have tried to use the AI to help me understand it (Gemini & Gpt) but they give different answers on different days. For example one day it says "increase from 32 to 64" and another it says "32 is way too high, try setting it 4-6"... AKA the fog thickens.
Solution
I'm wondering if there's anyway that AO can have an option to essentially look at the numbers it keeps generating in each log-update-cycle (when it refreshes every 5-10 seconds) and basically put each item into 1 of 5 brackets, something like this...
1 = WAY LOWER than it should/could be
2 = Kinda low
3 = About Right
4 = Getting Too high
5 = Absurd Game Breaking Value
Then somehow average out the results over the course of the flight, or take the worst parts (whatever you think is best) so when the session comes to an end (naturally or otherwise!) the user is presented with a "AO_report.txt" and it can say something like:
AO report for HH:MM:SS on DD/MM/YYYY
Your session lasted 2 hours 34 minutes 56 seconds.
During that time your flight covered 456nm and these were the final figures in the log:
(then go through the variable list, for each say eg)
chunk_budget_skipped:
419 - This is Kinda Low / About Right / Absurd Game Breaking etc - for a session lasting 2:34:56 where 456nm scenery was loaded....
YOU MAY WISH TO INCREASE / DECREASE (insert slider name) to improve this.
(next item)
This way users can begin to understand what values are acceptable to them, which ones aren't - and what tradeoffs they are willing to make. Right now (for me at least) it feels like i'm shooting into the fog
I realise some of these values will vary with flight duration, scenery type, New route vs same-old-same-old, but the tool will know if its serving up a 30 minute hop over the desert vs 12 hour city tour marathon. Even if covering every value would be a major undertaking and too difficult - perhaps the most crucial ones could be listed, so that someone like me can basically get a
"you can push this one a bit more, but you might wanna pull that other one back a bit, unless you like flying through New Jerkshire, Stuttersville" etc.
Cheers
Beta Was this translation helpful? Give feedback.
All reactions