-
Notifications
You must be signed in to change notification settings - Fork 2
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
Run multiple instances of the same game #43
Comments
Would be pretty nice to pass a void* or similar across all calls so that we wouldn't have to be so dependant on globals or singletons. 🙏 |
@arthurlutz The best option for this right now is to run another instance of the core and game in a different thread. |
I think this should be generalized to also allow different games and even cores. Possible use cases:
|
+1 for the connectivity "emulation" and link "emulation. Not sure I understand the 3rd bullet point. |
This would allow to check manual scans and maps directly in RA without terminating the current content. Btw, i guess this way it is more a Frontend-related issue, not libretro API related... |
This is a far fetched issue I'm submitting, but it's a way to start discussing this idea.
The idea would be to enable a multiplayer mode for single player games where players would play side by side the same game. For example a 2 player launch would launch two windows side by side with an instance of retroarch configured for player1's gamepad on the left and an instance of retroarch configured for player2's gamepad on the right. The players would then manually synchronize and play together (for speed or points, or anything the imagination can think of). 4 players would split the screen in four. With the size of flat screen TVs and the small resolution of retro games, this would be visually feasible right ?
Original issue submitted on libretro/RetroArch#2024 @RobLoach suggested I post the issue here with a mention of the following (I don't know what it means) :
The text was updated successfully, but these errors were encountered: