Uploaded January 2016 | Updated November 2026, 4 hours ago
In this video I am controlling one of the transport helicopters that can be seen in the first level of the game.
The helicopter is difficult to control in this level with narrow paths. If you manage to land it, it has a small animation where its rotors stop rotating and the back door opens up for a little bit, then it closes and the helicopter takes off again. You need to take care when flying around the map, because going to the spot with the knocked out Western Frontier grunt makes the game forcefully remove all WF helicopters, so the game will be softlocked if you are flying one at that moment.
I did not narrow down the exact ID of the helicopters. Instead, I set the mUnitFlags value of all air vehicles in the level to be the same as the starting grunt unit, and I set the UnitInstanceFlags to 0. I also set their affinity to WesternFrontier, and set mNoMap/mNoRadar to eFalse so the helicopters appear on the radar as well as the map. Normally, the transport helicopters do not appear as little icons on the radar or map. I also set the maximum health and ramming resistance of all air vehicles to a high value, and the damage factor to 0 to make the helicopter more resistant to crashes so I could show off the landing and try to maneuver around the narrow corridors of the map.
As a bonus, the Spy Balloons appear as friendly and you can attempt to command them around, but you cannot control them. The Tundran helicopters at the end of the map are also friendly to the player, causing a bit of a commotion with the Tundran grunts.
Jumping/flying light recons are caused by setting the mYOffset value of the ground vehicles by the Western Frontier to a value higher than 0. (10 in this case)
In this video I am controlling one of the transport helicopters that can be seen in the first level of the game.
The helicopter is difficult to control in this level with narrow paths. If you manage to land it, it has a small animation where its rotors stop rotating and the back door opens up for a little bit, then it closes and the helicopter takes off again. You need to take care when flying around the map, because going to the spot with the knocked out Western Frontier grunt makes the game forcefully remove all WF helicopters, so the game will be softlocked if you are flying one at that moment.
I did not narrow down the exact ID of the helicopters. Instead, I set the mUnitFlags value of all air vehicles in the level to be the same as the starting grunt unit, and I set the UnitInstanceFlags to 0. I also set their affinity to WesternFrontier, and set mNoMap/mNoRadar to eFalse so the helicopters appear on the radar as well as the map. Normally, the transport helicopters do not appear as little icons on the radar or map. I also set the maximum health and ramming resistance of all air vehicles to a high value, and the damage factor to 0 to make the helicopter more resistant to crashes so I could show off the landing and try to maneuver around the narrow corridors of the map.
As a bonus, the Spy Balloons appear as friendly and you can attempt to command them around, but you cannot control them. The Tundran helicopters at the end of the map are also friendly to the player, causing a bit of a commotion with the Tundran grunts.
Jumping/flying light recons are caused by setting the mYOffset value of the ground vehicles by the Western Frontier to a value higher than 0. (10 in this case)


![[Mario Kart DD] More Cups Progress! Grand Prix
I got the single player Grand Prix in Mario Kart Double Dash working with the additional cups! To show it off, Im playing one of the extra cups while having the worst luck with avoiding items and obstacles.
MKDD Modding Discord: http://discord.gg/fUU36aH
Featured custom tracks:
Blooper Race by tarsa129
Wii Rainbow Road by Double Cherry [Mario Kart DD] More Cups Progress! Grand Prix](https://i.ytimg.com/vi/VyR2F9aC_aY/mqdefault.jpg)

![Who needs walls anyway [MKDD collision modding]
Thanks for the 100+ subs!
In recent times I have been working on custom collision for Mario Kart Double Dash with the help of a few other people. Its still a long way off but here is a video on something fun I encountered while messing with the collision file of daisys cruiser. It is possible to completely abolish the walls of the level.
Sadly, some of the inaccessible areas just caused my cars to fall through but there is still some neat tricks that are possible. I think this also confuses the game so that you cant properly complete a lap without going through it as intended. Who needs walls anyway [MKDD collision modding]](https://i.ytimg.com/vi/WJ2pu_VGAEo/mqdefault.jpg)



![Pikmin 2: Debug Heap/Process Bars
Turns out Pikmin 2 has these colorful Heap and Process bars that the developers likely used for debugging the game. You might recognize these from Zelda: The Wind Waker and Mario Kart Double Dash which also had (pretty much) the same bars that could be enabled using cheats. See below for the gecko codes I created to make the debug bars visible.
The heap bar is the top one. The colors are as follows: The purple-ish bar on the left states the code size and it should never change during the game. The blue bar is the entire ram that the game uses or can use. The bright pink and purple on the right seem to belong to the current heap, with the bright pink showing the free space and the purple being the used space. Sometimes the current heap isnt drawn and the space itd occupy remains blue. Changes in the current heap length can indicate major scene changes. What is interesting (but not surprising) is how in the cave area the amount of free space in the current heap is significantly bigger than in the overworld area.
The thick bottom bar is the process bar and it seems to represent cpu usage of various processes. I havent been able to figure out what the bars mean though because the process bar rendering code is significantly more complex than the code for the heap bar rendering. Interestingly there seems to be some sort of scaling going on sometimes.
Cheat codes for enabling the debug bars in Pikmin 2:
$ Enable Heap and Process bar [USA] [Yoshi2]
04030a98 60000000
0402f28c 60000000
* Heap bar represents memory usage (in the order code,user ram (blue),current heap free,current heap) and process bar represents cpu usage.
$ Enable Heap and Process bar [PAL] [Yoshi2]
04030b58 60000000
0402f34c 60000000
* Heap bar represents memory usage (in the order code,user ram (blue),current heap free,current heap) and process bar represents cpu usage.
For comparison:
Debug bars in Wind Waker: https://tcrf.net/The_Legend_of_Zelda:_The_Wind_Waker/Debug_Content#Colored_Bars
Debug bars in MKDD: https://tcrf.net/Mario_Kart:_Double_Dash!!#Draw_Debug_Process_Bar Pikmin 2: Debug Heap/Process Bars](https://i.ytimg.com/vi/XciMuna8aTg/mqdefault.jpg)

