You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This project is great and I'm doing some of my own testing of various emulators (including things like older versions of emulators for compatibility with older platforms and devices). I came up with a few ideas that could be worth implementing somehow, even if not in the ROM itself something that can be done in the assembly code (I'm having a look at it myself although my skills are very low) for compiling a custom ROM. It wouldn't surprise me if you were already considering some of these features for implementation.
Possibility of checking/unchecking which tests to run, to attempt to bypass the tests which crash really old emulators outright.
You mentioned in your video a number of tests that, in your words, wouldn't actually affect anything from a speedrunning perspective, at least not in ROMs that aren't specifically written to trigger these edge cases as you mentioned at the end of your video. A possibility of running a smaller subsection of the tests, basically just running the 86 (I think?) tests that might impact accuracy, or having these colored differently on the palette screen.
This would be more for external documentation, and possibly more someone else's project rather than your own, but potentially an indication of which popular games are impacted by specific test failures and in what way.
I imagine the ROM itself might be short on space to implement these features in a console-controllable fashion, so if they can't be included in the ROM proper, perhaps having an easy way in the assembly code to comment out certain tests so you can compile a custom ROM that only runs specific tests and displays a pattern with the omitted tests Xed out similar to the Photoshop job you did on the early tests you performed for the video.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
This project is great and I'm doing some of my own testing of various emulators (including things like older versions of emulators for compatibility with older platforms and devices). I came up with a few ideas that could be worth implementing somehow, even if not in the ROM itself something that can be done in the assembly code (I'm having a look at it myself although my skills are very low) for compiling a custom ROM. It wouldn't surprise me if you were already considering some of these features for implementation.
I imagine the ROM itself might be short on space to implement these features in a console-controllable fashion, so if they can't be included in the ROM proper, perhaps having an easy way in the assembly code to comment out certain tests so you can compile a custom ROM that only runs specific tests and displays a pattern with the omitted tests Xed out similar to the Photoshop job you did on the early tests you performed for the video.
Thanks for all the hard work you've done on this!
Beta Was this translation helpful? Give feedback.
All reactions