-
Notifications
You must be signed in to change notification settings - Fork 380
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
Bizhawk Bug Filers need approved set of "Upstream" emulators #3879
Comments
As you were told on Discord, ported cores have their name shown in the status bar, and should have a hyperlink in Links could be added to this table in the readme (edit: as below), but I fear that would make it too information-dense. I think writing a guide specifically for reporting bugs in games would be better in the long-term; a good chunk of our bugs are that kind, but we have about 2 lines total of documentation for it at the moment.
|
Upstream column in that table would be exactly for telling people what to test on, so I don't see a problem in one more column. |
(Edited my previous comment to show a sample table.) Pointing to "the upstream" for each core is complicated by the fact that we generally aren't keeping up with updates for them; we should really be pointing testers at the standalone version matching the one we include, and not just the latest or the project's homepage. Hence I think expanding the table in the readme won't be sufficient. |
Like in the GPGX's case, we can backport individual fixes if we can't afford updating the whole thing. And people telling us how everything works upstream is all the more nag to pull from it properly (which is why newly ported cores are organized to make it as easy as possible). |
Given that this is the case, I don't feel we need to do anything else. Is this ticket about frustration finding upstreams in general, or just GPGX-specific? |
This ticket is about all cores, not gpgx specific. GPGX does not appear in the bug title or description. |
When filing bugs in games, the first reply is inevitably "did you test in upstream". However people filing bugs that use BizHawk may have no idea what this means. Therefore, an approved set of links to upstream emulators are necessary to expedite the reproduction process.
The text was updated successfully, but these errors were encountered: