-
Notifications
You must be signed in to change notification settings - Fork 1
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
EverDrive support #23
Comments
Thanks to fenhl/OoT-Randomizer#14, reading and writing data works now. The next steps are to finish designing the USB communication protocol (I've written a first draft) and implement it as a PR for the randomizer. |
I've posted my current draft of the USB communication protocol at OoTRandomizer/OoT-Randomizer#2042. |
This is now in progress on the |
The |
This is now available as of version 15.2.0. See the release notes for caveats. Leaving this open until it lands on the main Dev branch of the randomizer, as there is still more work to do before a pull request can be opened. |
Some models of the EverDrive-64, such as the EverDrive-64 X7, have a USB port that can be used for communication between the game running on the EverDrive and a connected PC. This could in theory be used to add multiworld support for EverDrive by having the randomizer implement a protocol similar to the one the Mido's House Multiworld app uses to communicate with the BizHawk and Project64 plugins, with some adjustments required to accomodate the idiosyncracies of the USB interface and since the EverDrive loses its state when resetting the console (e.g. savewarping).
I've tried prototyping this and detecting whether an EverDrive is present works. However, reading data does not. The latest attempt can be found at fenhl/OoT-Randomizer@dev-fenhl...everdrive. Resources used for this implementation:
The text was updated successfully, but these errors were encountered: