Log In  


i've been tinkering around with Buildroot and got me an image that I'm happy with that boots up, connects to wifi then starts pico-8. the problem I'm having is that once pico-8 starts, the inputs aren't recognized as if pico-8 doesn't have focus. I'm not sure how to force it to have focus though. anyone have any idea what might be causing the issue? i haven't tried using a controller, so I have no idea if that would work or not. my goal was a minimal image for running Pico-8 :)

it does the same thing, even if I run pico-8 manually and not @ startup.
here is the output of me using the keyboard while pico-8 is up and running and after I have killed pico8_dyn from the console, so I know the OS is recognizing inputs, just not pico-8.

thanks in advance for any advice!



Hello! Can you give a lot more info about your setup? :D

For example

  • is your screenshot from a virtual console, or a terminal running within a graphical environment?
  • does pico8 run when you run './pico8_dyn`?
  • what is the screenshot meant to show? why did you run 'test1'?

@merwok first off, thanks for the reply and trying to help. that's a screenshot i took with my camera of the monitor. yes, pico8_dyn runs and brings up pico8, but anything I type is grabbed by the console and not pico8. i was just typing random things to show that it was being recognized, but behind pico8. :/

I have a copy of my .config from buildroot if that's of any use.


Are you running in a virtual console or within a graphical environment?


Console


Hm I don’t understand the note about focus then. In a virtual console there are no windows, just one rectangle of pixels that should be used by pico8 to display until you exit. Can you take a 5-second video of your whole screen to show more?


@merwok left screen is my computer, right side is the raspberry pi connected to another monitor. i ssh'd from my comp to the Pi and executed ./pico8_dyn, typed some letters and killed pico-8 from the ssh session and you can see all the text that appears on the right screen (the pi0w) once pico-8 has stopped.
https://photos.app.goo.gl/ZM1gXQ7x8L726GiV6


@merwok i'm sure there's something simple that I have overlooked and not configured, just no clue what it might be. :/


Ah you didn’t say that you had two computers and were using SSH!

You can run commands in a shell with SSH, also graphical programs (but that has security and performance issues so is not recommended), but the protocol does not share keyboard or mouse.

The intended way is to connect screean and keyboard (or gamepad) to the raspi.


It's directly connected, Pico-8 just runs on boot up. I was just using ssh b/c I didn't have another keyboard close by, but the results are the same locally and through ssh. Pico-8 will start up, but the typing is always captured by the console and not Pico-8


Yes, that is normal, as SSH is not meant to send keyboard/mouse events to another computer!


Right, but I hooked a keyboard up to the Pi0w and it does the same. SSH isn't the issue unfortunately


Can you share a screenshot or video of that?


Sure, I can do that. It's going to show the same. Pico-8 is called directly from inittab

Edit:
@merwok I'll have to rebuild the image, I ended up overwriting the sdcard with something else, but I'll see if I can get it done today at some point.


I have done some config for my pico8 dev station today!

Using a pi zero, raspbian without X, an HDMI medium size LCD screen and a USB hub.
I couldn’t connect to wifi, maybe because the USB wifi stick drew too much power, so I didn’t update the system. I downloaded a wiringpi deb package on my laptop and added it to the raspbian SD card, then booted and installed it.

Trying to start pico8_dyn gave an error due to missing libsdl, but to my surprise the static pico8 just worked! It booted in the console, using all screen space (with borders on the side), sending sound to the screen speakers, and with keyboard working.. I suppose that zep builds pico8 with a libsdl that has directfb enabled!

I didn’t get to see the mouse; from a quick search it should be directly supported (no need for 'gpm' for example), so I’m not sure about what do to.


@merwok not sure what your mouse issue is. i haven't tried using a mouse, but I do see the pointer in the top left of the screen when Pico-8 boots up. my issue is that I'm trying to do all of this from scratch via buildroot and not raspbian, so I'm kinda clueless when it comes to all that's needed, but I'll keep plugging away at it and eventually I'll get there, I hope anyhow...



[Please log in to post a comment]