Current rendering and game logic
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 611
- Forks
- 211
- PR merge metrics
- No merged PRs in 30d
Description
As I understand it, game logic and SDL rendering operations run synchronously. When running on devices with several cores but limited single-thread performance, it would be helpful to hive off rendering into a separate thread, allowing it to proceed asynchronously on a second core. We have examples of games on Raspberry Pi which would run at 30fps in this mode but which are currently stranded (even after a fair bit of optimisation on the SDL side) nearer 20fps.
I'm sure we could knock something up, but if this is feasible it might be better if it were done by someone closer to the project. We would consider providing a bounty to get this done.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the synchronous game-logic and SDL rendering entry points, then investigate whether rendering can safely move to a separate thread on multi-core Raspberry Pi devices. Determine the synchronization and performance requirements before changing the architecture; done means a validated asynchronous design that achieves the stated frame-rate improvement without breaking game behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- game-dev, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100