The following warnings occurred:
Warning [2] Undefined property: MyLanguage::$archive_pages - Line: 2 - File: printthread.php(287) : eval()'d code PHP 8.2.18 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/printthread.php(287) : eval()'d code 2 errorHandler->error_callback
/printthread.php 287 eval
/printthread.php 117 printthread_multipage



Mario Kart Wii Gecko Codes, Cheats, & Hacks
"Double Dash!!" Speedometer [Sponge] - Printable Version

+- Mario Kart Wii Gecko Codes, Cheats, & Hacks (https://mariokartwii.com)
+-- Forum: Cheat Codes (https://mariokartwii.com/forumdisplay.php?fid=51)
+--- Forum: Visual & Sound Effects (https://mariokartwii.com/forumdisplay.php?fid=56)
+--- Thread: "Double Dash!!" Speedometer [Sponge] (/showthread.php?tid=2158)

Pages: 1 2


RE: "Double Dash!!" Speedometer [Sponge] - Sponge - 10-28-2024

(10-28-2024, 03:08 AM)MKWii-Martin Wrote: I made tests with the repacked ISO of a completely vanilla game (with the speedo assets added and speedo code active, of course), both with no other codes active, and with all codes I have along with the speedo code, everything worked perfectly, with the only exception mentioned below.

The only code I have that caused a conflict with the speedo is the All Items Can Land v2 code.
Link: https://mariokartwii.com/showthread.php?tid=1720

If the speedo code is used along with the code above, and the speedo code is sorted below the above code in Dolphin's Gecko code list (even if these 2 codes are the only ones active), the speedo's animation when using star/bullet/shroom stops working, it instead only changes the color of the speedo depending on the item being used, and it also looks bugged.

This happens with both the standard version of the code, and the code modification posted by a coder named Unnamed in post #4 in that code thread.

Hopefully this helps, so thank you a lot for your time, much appreciated.

My code explicitly states that the area between 0x80001610 through 0x8000161E is used. All Items Can Land v2 has a 0x8C long string write from 0x80001600, which will cause conflicts. You will need to shift the allocated areas for at least one of the codes to avoid issues.