can you make ocarina codes with the dolphin emulator?

Started by f0x, August 01, 2011, 07:55:43 AM

Previous topic - Next topic

f0x

Hi  I'm interested in learning assembly and how to make codes for the wii  and I was wondering is some thing you could do with the wii emulator?

dcx2

Dolphin has very limited support for code types.  I do not know of any remote debuggers for Dolphin, but I tend to stay away from piracy tools.  You might be able do some basic hacking, but you won't get much support from this forum, which is dedicated to hacking retail Wiis with a USB Gecko.

biolizard89

Not entirely sure why you're referring to Dolphin as a piracy tool.  Most people I know who use it either use it because (much less common) they don't have a Wii (which is legal, provided they buy the games -- see Sony v. Connectix), or (much more common) because the graphics are much higher quality than on the Wii.  I'm in the latter camp... I have a 1080p TV, and Dolphin looks much better on it than my Wii does (1080p resolution, anti-aliasing / anisotropic filtering, pixel lighting, the option of stereo 3D).  Some people call HBC a piracy tool; people here know better than that, so why use the same logic to call Dolphin a piracy tool?

dcx2

HBC doesn't play games you downloaded from an iso on a warez site.  Dolphin does.  There's nothing that you can do with Dolphin that you can't do with Gecko OS, short of making games look prettier.

Further, emulating a system that is still sold at retail is, IMO, hardware piracy.  It's one thing to emulate a NES, because you can't buy them anymore (yes, VC complicates this, but only marginally).  It's another thing to emulate a console that you can still buy brand new.

biolizard89

Quote from: dcx2 on August 04, 2011, 06:07:27 PM
HBC doesn't play games you downloaded from an iso on a warez site.  Dolphin does.  There's nothing that you can do with Dolphin that you can't do with Gecko OS, short of making games look prettier.

Further, emulating a system that is still sold at retail is, IMO, hardware piracy.  It's one thing to emulate a NES, because you can't buy them anymore (yes, VC complicates this, but only marginally).  It's another thing to emulate a console that you can still buy brand new.
The court case Sony v. Connectix established that (in the U.S.) emulation of current-gen consoles is not piracy.  Connectix was marketing a commercial product that allowed PSX games to be played on a PC (while the PSX was still popular).  The court ruled that Sony's lawsuit against Connectix was anti-competitive.  Under this case law, Dolphin is a competing product with the Wii hardware, not stealing the Wii hardware.  (Obviously, this only holds true so long as all of Dolphin's code is produced via reverse-engineering; if Dolphin were to steal documentation/code from Nintendo, that would be illegal.)

Also, I see Dolphin as different to Wii backup loaders in that Dolphin's main purpose (indeed, the purpose advertised on their website) is higher-quality graphics.  Given that many PS3 gamers chose the PS3 because its graphics are better than the Wii's, this is a major selling point that attracts a major market.  Yes, Dolphin can be used for piracy, but that's not its main purpose.  In contrast, the backup launchers' sole purpose is to bypass copy-protection (and while I realize that some users have bad DVD drives, or want faster loading times, those use cases are much more rare than wanting high-quality graphics).

(Not trying to start an argument, just putting in my opinion.  :) )

biolizard89

Quote from: Sharkbyte on August 04, 2011, 10:28:58 PM
I've tried this dolphin emulator once... Failed so bad I had to laugh at all the fail. First of all, it is mostly a piracy tool. Second of all, the compatibilty is shit. Third of all the load times are ridiculously slow and it often craps out in a game. I actually tried it out about 6 months ago out of being curious on games I own and the load time (if you get the settings right and go through all the bullshit of getting .dlls and missing files and reading a bunch of posts on sites and getting directx and configuring all that shit) it was running at 33% speed and sound was not with the video. It was NSMB wii and it couldn't even run that.

And before you ask my specs, I had the latest version of dolphin (6 months ago) and I have 8GB ram windows 7 64bit and a 3.2Ghz processor and i great graphics card. I don't know what you have but that app is fail to me and I never want to even try it again no matter how many different releases there are to it. I don't use emulators anymore.
Thank you for the rant.

As you have discovered, emulating a foreign instruction set takes a lot of CPU power.  I've worked with virtual machines that implement a custom instruction set; the VM I worked with (Interactive C for the GBA) was 76 times slower than native code.  At that rate an 800MHz processor (e.g. the Wii) would require 60GHz of CPU power to emulate.  Dolphin is faster than that because it cuts corners and doesn't actually emulate the Wii accurately, as well as using a JIT recompiler and various other tricks that make it more efficient than Interactive C.  Even so, it's a difficult and slow process, and I'm personally quite impressed that Dolphin works as well as it does.

3.2GHz doesn't tell me much, since different architectures are quite different in their suitability to run Dolphin... if it's an AMD CPU, then yes, your 3.2GHz AMD is probably not fast enough.  Also, the settings you choose make a big difference.  Had you done your research you would have found that RAM and GPU power don't make much diff for Dolphin, not that I can tell anything by your statement that you have a "great" GPU.  If you want it to "just work" then use a real Wii.  No one ever claimed that Dolphin was as easy to use as a Wii.  In fact, that's also why PSX did just fine competing against Connectix's emulator -- the real PSX was far easier and "just worked."  Dolphin is for people who want better graphics than the Wii, who have money for a good CPU, and who are willing to spend time tinkering.

Also, I think it should be pretty obvious that since Dolphin takes a $2000+ computer to run anything at good speeds, that in itself makes it a poor tool for people who just want to pirate.  Pirates want the lowest cost possible, right?  You're a pirate, compare your options: $2000 for a PC with a fast CPU (with free games courtesy of piracy), or $150 for a Wii plus just buy each of your games.  Not to mention that the even cheaper option is to buy a USB drive and pirate games on an actual Wii, which is what pirates actually do.  No one would be stupid enough to use Dolphin for the exclusive purpose of piracy unless they already had a crazy expensive PC (which is not a large part of the market).  (There's also the fact that my $2000 figure is assuming you bought the parts from NewEgg and built yourself the PC... if you're buying from Alienware expect to pay much more.)

(I hope I'm not coming across as harsh... but your post strikes me as quite misinformed....)

dcx2

I don't think locking this thread was fair to biolizard.  He makes a valid point; Dolphin is both legal and interesting software, and I respect the intellect necessary to make such software possible.  It is not the developers' fault if a user abuses their software.

Unfortunately, it's probably still off-topic here.  It only supports the most primitive of code types, certainly useless if someone wants to learn ASM since there's no C2, and it has no remote debugger.

I'm pretty sure that you can't use retail discs with Dolphin unless you have one of those special DVD drives, which means you're probably going to a warez site to get your games.  Or you're ripping them with a USB loader yourself.  I know that neither of us have the statistics to show what percentage of games that run on Dolphin are rightfully owned, but I'm betting it's lower than the percentage of games that run on Gecko OS.