I'm sorry that wasn't helpful.
I guess it might also be useful to try getting other SDL1/SDL2 apps working
without pygame.
That's probably where the issue is anyway.
But if they do work, that should make it much easier to find where the
problem is in pygame.
Thanks you for very detailed instructions.
>0) try different bit depths than 32.
I tried 8, 16, 32. It didn't help.
>1) try building pygame with SDL2.
Built it. It even doesn't return the list of modes. Here is the result:
pi@raspberrypi:~ $ sudo python3 test.py
pygame 1.9.5.dev0
Hello from the
Hello,
Things to try in order of easiest to do...
0) try different bit depths than 32.
1) try building pygame with SDL2.
2) instructions on how to debug things and get stack traces.
3) ask your vendor for support.
1) try building pygame with SDL2.
It's not a regular exception. How can I get that stack trace?
I've tried: hdmi_cvt 480 320 59 6 0 0 0
The result was the same.
On Wed, Nov 21, 2018 at 7:07 PM Luke Paireepinart
wrote:
> Should the third parameter to hdmi_cvt of 60 really be 59 since that
> matches the refresh rate in the
Should the third parameter to hdmi_cvt of 60 really be 59 since that
matches the refresh rate in the other list?
On Wed, Nov 21, 2018, 7:39 PM Ian Mallett According to the linked issue, you say it segfaults. That should
> definitely not happen; can you provide a stack trace?
>
According to the linked issue, you say it segfaults. That should definitely
not happen; can you provide a stack trace?
Hi,
I'm facing the issue with Pygame and Waveshare 3.5" HDMI display.
It looks like Pygame cannot detect the native hardware display resolution -
480x320
More details can be found here:
https://www.raspberrypi.org/forums/viewtopic.php?f=45=227235
Does anybody know how to fix the issue?
T
