MeloNX/Ryujinx-ryubing
10
0
Fork 0
Code Issues 184 Pull Requests 15 Actions Packages Projects Releases 36 Wiki Activity

[Feature Request] A new repo for game compatibility #152

New Issue
Closed
opened 2024-11-01 17:55:34 +00:00 by VeraPhobia · 7 comments
VeraPhobia commented 2024-11-01 17:55:34 +00:00 (Migrated from github.com)
Copy Link

Overview

at the moment there is no way to know if a game is working, or how well it is working. having a dedicated repo like how it was on OG ryujinx will be helpful.

Smaller details

a new repo for game compatibility

Nature of request

having information if a new game that is released works well or not or what is the problem of games already tested

Why would this feature be useful?

same as above

### Overview at the moment there is no way to know if a game is working, or how well it is working. having a dedicated repo like how it was on OG ryujinx will be helpful. ### Smaller details a new repo for game compatibility ### Nature of request having information if a new game that is released works well or not or what is the problem of games already tested ### Why would this feature be useful? same as above
👍 2
VeraPhobia commented 2024-11-01 17:57:44 +00:00 (Migrated from github.com)
Copy Link

i just saw the readme file too, at the moment it just says how many games works and stuff but since it doesn't link anywhere it is kind of bummer that people cant see exactly what game is playable or broken

i just saw the readme file too, at the moment it just says how many games works and stuff but since it doesn't link anywhere it is kind of bummer that people cant see exactly what game is playable or broken
MoravinecKravinec commented 2024-11-01 17:58:00 +00:00 (Migrated from github.com)
Copy Link

bump

bump
GabCoolDude commented 2024-11-01 18:03:14 +00:00 (Migrated from github.com)
Copy Link

We'd have to find people who would want to manage the hundreds of issues. The old repo had a couple people like that, but now they're all gone/no longer willing to do it.

We'd have to find people who would want to manage the hundreds of issues. The old repo had a couple people like that, but now they're all gone/no longer willing to do it.
VeraPhobia commented 2024-11-01 18:06:42 +00:00 (Migrated from github.com)
Copy Link

i understand but IMO having a semi organized something can be better than not having anything. and i will regret it greatly but i can help a little here and there as well and i am sure if it exist there are others who might want to help this project someway and this can be a good way

i understand but IMO having a semi organized something can be better than not having anything. and i will regret it greatly but i can help a little here and there as well and i am sure if it exist there are others who might want to help this project someway and this can be a good way
amurgshere commented 2024-11-09 21:36:18 +00:00 (Migrated from github.com)
Copy Link

If we do do this, it would be great if we could tie it into the software itself so that it can visually indicate if a game has any bugs against it in the user interface, maybe even give a Green, Amber, Red icon on each game to show compatibility / issues.

If we do do this, it would be great if we could tie it into the software itself so that it can visually indicate if a game has any bugs against it in the user interface, maybe even give a Green, Amber, Red icon on each game to show compatibility / issues.
GreemDev commented 2024-11-09 21:38:02 +00:00 (Migrated from github.com)
Copy Link

I'm not running a game list. And I think would be unfair for me to expect other people to run it for me, for my fork

I'm not running a game list. And I think would be unfair for me to expect other people to run it for me, for *my* fork
👍 1
GreemDev commented 2025-01-29 05:57:50 +00:00 (Migrated from github.com)
Copy Link

why did i never close this

why did i never close this
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
audio
Affects Audio playback during emulation
blocked on external progress
This cannot move forward without work on an external project or service.
bug
Something isn't working
cpu
An issue with ARMeilleure, the JIT, or Hypervisor
documentation
Improvements or additions to documentation
duplicate
This issue or pull request already exists
enhancement
New feature or request
good first issue
Good first issues to work on for new contributors
gpu
Affects GPU emulation
graphics-backend:metal
Affects the Metal Graphics backend
graphics-backend:opengl
Affects the OpenGL Graphics backend
graphics-backend:vulkan
Affects the Vulkan Graphics backend
gui
Affects the Avalonia UI or translations.
help wanted
Extra attention is needed
horizon
Affects the Horizon OS HLE components.
infra
Updates to dependencies
invalid
This doesn't seem right
kernel
Affects the kernel HLE components.
ldn
Affects the LDN functionality
linux
Linux only issue
macOS
macOS only issue
not planned but open to a PR
I do not intend on working on this myself, but I would not be opposed to an implementation.
question
Further information is requested
windows
Windows only issue
wontfix
This will not be worked on
No Label
enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MeloNX/Ryujinx-ryubing#152
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?