-
Notifications
You must be signed in to change notification settings - Fork 26
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
How to render pygame Surface? #40
Comments
There isn't. In OpenGL there are framebuffer objects, but I think that exposing those for general use might be a long way off. How I wrote Tron in Pygame Zero isn't exactly how I would write it with hardware accelerated graphics. I'd just keep creating line segments and trust that it will remain fast. |
Could in theory open up for people to write to pygame surfaces and upload to texture: That could be an awesome or a terrible a idea depending on how you see it. |
Yes for the Tron game, it worked well with line segments. And looks like you are adding tile-maps for 1.4, which was the other use I was anticipating for pygame surface |
Yes, I think this is a good idea. This would allow people to migrate from Pygame and immediately get the benefit of things like post-processing effects. |
Via @einarf
|
@mkraljt Tile maps are now available on |
@robertpfeiffer's original article explains it better than the code linked above: |
pygamezero examples use pygame Surface to render and test/set pixels, eg Tron example.
How do you render a pygame Surface in Wasabi2D?
Or is there an alternative for Surface use-cases in pygamezero examples?
The text was updated successfully, but these errors were encountered: