-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Resolution limitations for OpenGL ES instances? #9
Comments
@MakerMatrix sorry not to get to this today. What version RPi are you running on? I think the RPi 4 with the fake KMS driver will go up to 4k screen sizes OK but you need to set the GPU memory allocation high enough (what are you set at?) It's possible to run pi3d in multiple processes (well, I managed with two) and to split images across them. The fake KMS will only work with a display surface provided by X11 but it is possible to do this from the command line with xinit so that none of the desktop stuff gets loaded. Is there a specific reason you don't want X11? But I'm not aware of a size limitation apart from a) GPU memory b) the earlier RPis had to have Texture2d widths at certain values ...1024, 1080, 1920 (being the widest, pre-RPi 4). But pi3d will resize images to these widths automatically if they don't match. Does the stack dump give any indication of the problem? Is there any pattern to the demos that don't work? |
No hurry, appreciate the response! Currently testing on Pi3B. I believe I gave the GPU 128MB, I can increase that and see, thanks for the idea. I'll try increasing GPU memory and if I cannot make that work will give more details about how things fail. Thanks again. |
Jarrod, I would expect 128 to be big enough to be honest so it might be something else. It would be nice to get to the bottom of it. Wolfgang has posted lots of detailed info on running pi3d without desktop (and other things) on thedigitalpictureframe.com |
I'll check the link you sent, thanks. But is are the details on what I'm seeing. This is the stack trace for ball.py when I have the hi-resolution display (Sharp SX03 vi hdmi to mipi board) hooked up: ############################################## ############################################## The display is configured thus:
|
Well I'm not really sure but the |
That's in the [pi4] section and I was on a pi3. I want to believe that section gets ignored in that case. That overlay is commented out in the [all] section. Anyway I probably have tried it both ways but maybe I've flubbed that. I have spent a lot of time learning the ins and outs of the video options on Pi platforms these past two weeks, just so I can get arbitrary hi-res screens to work at all. I now have 2560x1600 and 2560x1440 tablet screens (with HDMI->MIPI) working on both Pi3 and Pi4. Those GL drivers are still somewhat of a mystery to me though. I need to pay closer attention to them. I have digested some of the photoframe site and it seems that project wants you to have X11 running. So I have reinstalled with the desktop version on both computers. Next is to figure out how to disable the window manager and go right into Earth.py, for example. |
I have been searching for python bindings to OpenGL ES, to make a simple OpenGL image server type app that will run on a console window (no X11).
I thought pi3d was exactly what I needed. I tested the ball.py prog and it worked. But then I installed a high resolution screen with custom HDMI timings and got a stack dump on that same prog. Then I noticed that not all the demos were working even on the original 1080P screen.
What are the limitations of pi3d with respect to running an OpenGL context on the console, outside of X11? If pi3d doesn't fully support this, do you have another recommendation for me? The features I need a quite simple. 2D only, basically just blitting images to the screen and maybe applying a texture with alpha.
The text was updated successfully, but these errors were encountered: