The gyro values WarioWare Twisted receive appear to be half of their expected values. This results in TASers unable to do certain strategies RTA runners are able to do.
Example TAS Run: https://youtu.be/wDAfECnju24?t=326
Example RTA Run: https://youtu.be/fb40Vu8fVhc?t=324
Here is a pastebin noting the exact read/writes WarioWare Twisted uses to read out gyro state: https://pastebin.com/tgQfUhgx
I suspect the issue is that starting the ADC conversion process (or perhaps unsetting the ADC conversion process bit) should output bit 15 of the gyro state immediately, and subsquently triggering a serial clock afterwards should set bit 14 in the serial bit, not bit 15.
Attached are testroms (mb and cart variants both provided) to prove/disprove this theory.
adc_clear_test.zip
read_gyro_test.zip
src.zip
The gyro values WarioWare Twisted receive appear to be half of their expected values. This results in TASers unable to do certain strategies RTA runners are able to do.
Example TAS Run: https://youtu.be/wDAfECnju24?t=326
Example RTA Run: https://youtu.be/fb40Vu8fVhc?t=324
Here is a pastebin noting the exact read/writes WarioWare Twisted uses to read out gyro state: https://pastebin.com/tgQfUhgx
I suspect the issue is that starting the ADC conversion process (or perhaps unsetting the ADC conversion process bit) should output bit 15 of the gyro state immediately, and subsquently triggering a serial clock afterwards should set bit 14 in the serial bit, not bit 15.
Attached are testroms (mb and cart variants both provided) to prove/disprove this theory.
adc_clear_test.zip
read_gyro_test.zip
src.zip