Log In  

Yo @zep,

Instead of just turning the corner performance/stats graph on and off, maybe cycle through off, current size, and something closer to the full screen?

This could allow showing twice as much history on the graph, as well as showing a finer resolution of time within each tick. Right now we're only seeing 1-2 seconds (depending on _update/_update60) and the vertical resolution is very limited.

The large view might also accommodate more information that's not currently in the corner view. I'm not sure what information to choose—I'm just throwing the idea out there for you to think about.

Whatcha think?

P#77090 2020-05-23 21:50 ( Edited 2020-05-23 21:50)

how do you access this graph you're talking about? is it a new hotness?

P#77112 2020-05-24 07:25

Ctrl-P

P#77117 2020-05-24 08:15

agree - chart is way too fast

P#77122 2020-05-24 09:50
:: p01
1

The perf widget could use an extra line or two to show the min and max CPU and FPS.

Now, ear me out for another wild idea:

What if pico8 could emit a flamegraph showing, for each frame, which functions were called, stacked in call order, and how long they took.

Obviously that is too much information for a pico8 display. So the other option is to dump these performance snapshots to an external file that can be consumed by, say, the Chrome DevTool ;)

Would it really help and be worth the trouble of implementing this ?

P#77129 2020-05-24 13:59
1

I like that the screen is smaller and not covered.
Is this a far cry from pico8?

P#77131 2020-05-24 14:40 ( Edited 2020-05-24 14:43)
:: Felice
1

@shiftalow

Ah, that's a good idea too! Cut the resolution by half (or a third) and use the empty border to show debug info. Nice!

PICO-8 only has so many pixels, of course, so it would have to work like sspr() and omit every other pixel to draw it at half size, but still, it'd work.

P#77334 2020-05-28 21:03 ( Edited 2020-05-28 21:04)

[Please log in to post a comment]

Follow Lexaloffle:        
Generated 2021-01-20 09:39 | 0.024s | 2097k | Q:24