-
-
Notifications
You must be signed in to change notification settings - Fork 180
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
Y2Dmg Emulator #180
Comments
Hi @leefogg and thanks for the feedback. At the moment, the EMULATORS.md does not require any minimum level of "quality" of the contents it lists, while the Emulators chapter in the main list provides a more accurate selection. Should we try to outline some kind of criteria that resources have to satisfy to be on the EMULATORS.md list? |
I think simple QC on it will do like:
|
How can you define "truthful"? Are we gonna check every documentation file and run tests on the proposed emulator? |
If they mention they pass x tests, we'll have to prove that yes. Its only to stop proposals like "runs every game perfectly" from slipping in. |
Nothing "runs every game perfectly", apart from the Game Boy itself, so that kind of proposal is excluded anyway. |
I think curating the list would be more useful- given the purposes outlined above. That said, given this and the list's size, wouldn't it be more relevant to make a separate "awesome-gbemu"/"awesome-gbemudev" list? |
Why? What's the advantage of fragmenting something that has the same scope (curated list of resources related to gb/gbdev)? Can't we outline a process for different kind of resource in the same repositories? |
GBDev and GBEmuDev actually have little interaction. Taking the Discord as an example, I see few users in both #emudev and other channels. |
Description notes that the emulator passes (all) of Blarggs test roms, it however only passes a couple. From the comments left in
DmgSystem.cs
, only 15 roms were tested out of the total 46.Until we have a method of quantifiably measuring any particular emulator's accuracy (with a number for instance), I think we should avoid qualitative descriptions.
Only raising this as an issue as many devs are looking for a readable accurate emulator (including myself) and we shouldn't waste their time.
The text was updated successfully, but these errors were encountered: