A little thing about testing on Dolphin.


Views: 20,069,405	Home \| Forums \| Uploader \| Wiki \| Object databases \| IRC Rules/FAQ \| Memberlist \| Calendar \| Stats \| Online users \| Last posts \| Search	04-27-24 04:49 PM
Guest:

0 users reading A little thing about testing on Dolphin. | 1 bot

Main - Archived forums - General SMG hacking - A little thing about testing on Dolphin.

Hide post layouts | New reply

shibboleet

Posted on 06-27-14 08:11 PM

Link | #43177

Fire Mario
DROP TABLE users;

Level: 123

Posts: 2586/4661
EXP: 20896060
Next: 335206

Since: 07-07-12

Last post: 1351 days ago
Last view: 364 days ago

Many people like to test out their stuff on the Wii Emulator, Dolphin. Normally this is a quick way of testing so people don't have to start up their wii and everything, but it also has a lot of bad things about testing it.

1) Dolphin does not have a proper debugger.
If the game crashes, you're on your own on this. It doesn't print anything useful, so it's not handy. Although, the wii debug actually prints exactly what went wrong (or something close to it.) so it's easier to trace.

2) Dolphin sometimes loads a level, but the Wii crashes it.
Dolphin has been known to "ignore" certain crashes. (Like Boomerang Bros without a path, launch star without a path, some model replacements)
Before you release something that you tested with Dolphin, look at it on a Wii BEFORE you test. If you do not have a Wii, ask me or somebody who does to test it for you. If it does, they can try to give you the debug.

These are the top 2 things that can go wrong with this, but if you still want to use Dolphin, be careful.

Thanks for reading.
~MrRean

____________________
a

Main - Archived forums - General SMG hacking - A little thing about testing on Dolphin.

Hide post layouts | New reply

Page rendered in 0.017 seconds. (2048KB of memory used)
MySQL - queries: 26, rows: 192/192, time: 0.010 seconds.
[powered by Acmlm]