-
Notifications
You must be signed in to change notification settings - Fork 20
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
Multi renderer backend support for Brux #69
Comments
One thing I will probably add when I do this is a function named like |
I wrote the audio portability code with that goal in mind but never got around to doing the graphics part.
Here's the problem though: SuperTux Advance utilizes A LOT of complex SDL2 functionality for graphics. I don't know how you would abstract that away without a significant amount of effort...
- hexaheximal
…On Wednesday, May 8th, 2024 at 2:16 PM, Tulpen ***@***.***> wrote:
One thing I will probably add when I do this is a function named like `rendererSupportsShaders` that returns a boolean so games can implement fallbacks for SDL2 (or just crash outright if they're needed for something that would be too slow without it (e.g. 3D))
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
|
Due to the recent merging of SimpleSquirrel support, I'll be taking a crack at this later :3 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue simply exists so I can remember to work on this for brux in the near future.
Renderers on initial completion should probably be:
I will probably split this into 2 PRs (first being initial work on making multiple renderers possible, second being SDL3 due to the lack of SDL2_GFX (and also I have to wait for SDL GPU to be merged)) and this will be started after #66 is completed and merged into unstable.
The text was updated successfully, but these errors were encountered: