Log In  

this happened to me a couple of times in the last few days, and just now: I left pico-8 running (not a cart, console prompt) and found it completely irresponsive after something like two hours...

windows 10, pc didn't go to sleep (I usually manually Win+L, but not those times)
edit: 0.2.0d - missed an update ;)

P#75800 2020-05-04 19:26 ( Edited 2020-05-04 19:30)

I've had the problem three times in a couple of days with 0.2.0d, but not with 0.2.0e so far. It might be related to the coroutine bugfix.

P#75811 2020-05-04 22:43

ah yes, makes sense. indeed 0.2.0e seems ok. thanks!

P#75850 2020-05-05 14:39

unresolvedtagging, just happened with 0.2.0f :(

P#75987 2020-05-06 20:05
:: zep

I haven't managed to reproduce this yet, and I'm a little lost at what could be causing it. There aren't any fundamental changes between 0.1.11g and 0.2.0* that should be able to cause something like this, especially at the command prompt.

The only suspicious change I could find is that when < 1 frame has elapsed (30fps at the command prompt), PICO-8 skips re-drawing the window to save cpu. I added some extra sanity checks in 0.2.0i to rule this out, but it seems unlikely.

If it happens again, I'd love to know:

  1. Is there any movement on the screen at all? (e.g. blinking cursor) -- this would mean it's just the input that's not responding, possibly because the application is incorrectly taken to be in the background. Can also test that by alt-tabbing.
  2. Perhaps it's running but not updating the window somehow. Try pressing esc (to get into the prompt if you're not already there), type SHUTDOWN to see if responds
  3. Otherwise, does it respond to normal system messages? e.g. can you alt-enter to toggle window, or ctrl-q / alt-f4 to close PICO-8?


P#76248 2020-05-09 17:51 ( Edited 2020-05-09 17:52)
  1. I don't think it was blinking, but not 100%
  2. could be, but already in command. ctrl-r wouldn't do anything visually, not sure I had my headphones on so can't confirm it wasn't running at all
  3. when maximizing the window it would show the screen twice, centered PLUS upper-left, same size as windowed. I think I simply closed the window.

it happened 2-3 times while I was away. last time I was working on the comp, pico-8 in the background for 1-2h. I'll leave it on purpose, will update if happens again (on version i now)

P#76257 2020-05-09 18:54

didn't take long (about 20mn)!

  • still from command, no blinking, no input seemed to do anything
  • maximizing shows the screen in place (where the window was) plus in upper-left. after a few min/max it went all black.
  • alt-enter made the window disappear but showed no fullscreen. another alt-enter made the window come back and pico-8 was back to work too! from then alt-enter would do the same, no window but no fullscreen, and back, pico still working.

win10 with dual screens, btw...

P#76266 2020-05-09 19:31

Kind of an unhelpful data point, but: booted PICO-8 0.2.0i on a Windows 7 laptop in windowed mode, moved the window over to the side but didn't type any commands whatsoever, left it open for about an hour and a half (mostly in the background), and then clicked on it - no troubles at all, everything was working perfectly as far as I could tell.

P#76326 2020-05-10 17:34

[Please log in to post a comment]

Follow Lexaloffle:        
Generated 2021-01-20 18:53 | 0.014s | 4194k | Q:27