05-05-2011, 09:00 PM
Nintendo's 8GB of system memory is proof positive that they still have absolutely no idea about how to function as an online retailer/gaming service.
05-05-2011, 09:00 PM
05-06-2011, 03:19 AM
(05-05-2011, 09:00 PM)SiliconNooB Wrote: [ -> ]Nintendo's 8GB of system memory is proof positive that they still have absolutely no idea about how to function as an online retailer/gaming service.not really
they are doing fine so far
and gaming service... i'd shut up if i were you. the 3DS uses a different online methods which are still bound to its shitty gamespy laws; but is ALOT better then the wii/DS (aka, still friend codes but its minor and not game depended and rarely lag in SSF4 tells me enough )
also, im sure that with the wii's hardware you could still make an awesome online game and use friend codes AND that rarely lags unless you go outside of region. it just requires decent programming
05-06-2011, 09:00 AM
05-07-2011, 11:24 PM
05-08-2011, 12:46 AM
05-08-2011, 06:40 AM
I wonder if the architecture is just a more powerful version of the Wii......
"Dolphin - The one and only GC/Wii/Wii2 emulator"
r2rX
"Dolphin - The one and only GC/Wii/Wii2 emulator"
r2rX
05-08-2011, 06:53 AM
05-08-2011, 07:48 PM
05-09-2011, 01:44 AM
(05-08-2011, 06:40 AM)r2rX Wrote: [ -> ]I wonder if the architecture is just a more powerful version of the Wii......
"Dolphin - The one and only GC/Wii/Wii2 emulator"
r2rX
The reason Dolphin was able to support the Wii was because the differences lied mainly in clock speed. Even if the Wii2 uses the PowerPC architecture, the rumors of it being multicore would make it quite difficult to add support, and drastically increase the hardware requirements to properly emulate. So if Dolphin does support Wii2, it'll be a long time from now and probably not on any hardware shipping today.
If this werent the case, you'd have seen 360 and PS3 emulators by now.
05-09-2011, 03:09 AM
The reason we don't have 360 or PS3 emulators, yet, is because there's barely any info out there about them and it's simply a tremendous boring amount of work of coding.
Some people have actually coded SPE emulators, idk if this has been done for the main PPC as well though. and there's at least IBM's cell simulator.
Anyway, that's not the hardest part of emulation, it's just a f**king large amount of monotone work without which nothing of the hard stuff can even be started (and doing boring work just for being able to do hard work is kinda discouraging
).
The Wii 2 won't be emulated in Dolphin because it most likely will differ in about EVERY aspect to the GC/Wii:
- CPU JIT probably needs to be rewritten, I doubt there will be THAT many common areas to the current code
- The Wii 2 will have a programmable GPU pipeline rather than the fixed-function pipeline of the Flipper/Hollywood. If it is really based on an r700 chip, it might be comparatively easy to emulate since ATI has published numerous register docs on their GPUs. Anyway, emulating THAT GPU would require compeletely separate graphics emulation code
- The Wii 2 will probably have a revamped security architecture (I guess Nintendo won't like getting hacked that hard again). Guess we can screw over our whole IOS high level emulation code as well then.
- Will have a new input system, so screw over our whole Wiimote emulation as well
- too lazy to think further, but I guess there's plenty other stuff to mention...
Generally speaking, in contrast to GC->Wii (which was merely an incremental change, raising clock speeds, adding the starlet, adding wiimotes, adding WiFi, etc), Wii->Wii2 will be a radical change in most, if not all, subsystems of the hardware. Again, emulating the Wii 2 inside Dolphin would be the same like emulating the 360 in Dolphin.
On top of that, by the time the Wii 2 gets hacked, documented, a compiler chain gets created and homebrew for testing arises, Dolphin development will have ceased to almost-no-progress anyway
Some people have actually coded SPE emulators, idk if this has been done for the main PPC as well though. and there's at least IBM's cell simulator.
Anyway, that's not the hardest part of emulation, it's just a f**king large amount of monotone work without which nothing of the hard stuff can even be started (and doing boring work just for being able to do hard work is kinda discouraging
).The Wii 2 won't be emulated in Dolphin because it most likely will differ in about EVERY aspect to the GC/Wii:
- CPU JIT probably needs to be rewritten, I doubt there will be THAT many common areas to the current code
- The Wii 2 will have a programmable GPU pipeline rather than the fixed-function pipeline of the Flipper/Hollywood. If it is really based on an r700 chip, it might be comparatively easy to emulate since ATI has published numerous register docs on their GPUs. Anyway, emulating THAT GPU would require compeletely separate graphics emulation code
- The Wii 2 will probably have a revamped security architecture (I guess Nintendo won't like getting hacked that hard again). Guess we can screw over our whole IOS high level emulation code as well then.
- Will have a new input system, so screw over our whole Wiimote emulation as well
- too lazy to think further, but I guess there's plenty other stuff to mention...
Generally speaking, in contrast to GC->Wii (which was merely an incremental change, raising clock speeds, adding the starlet, adding wiimotes, adding WiFi, etc), Wii->Wii2 will be a radical change in most, if not all, subsystems of the hardware. Again, emulating the Wii 2 inside Dolphin would be the same like emulating the 360 in Dolphin.
On top of that, by the time the Wii 2 gets hacked, documented, a compiler chain gets created and homebrew for testing arises, Dolphin development will have ceased to almost-no-progress anyway