Homebrew Snes9xGX Mod [Preview + WiiUPro + ScreenShot button]

[Gabriel Mejia]

More features are really not needed when many bugs are still present (FFIII and Chrono Trigger, for example, as quoted by Zopenko himself), and slower performance in some games, compared to previous versions, which affect the overall stability of the emu.

i'm just saying if they teamed up they'd be able to make a better emulator
possibly even fix the bugs you mentioned
,one of the features i'd like is a scanline feature with adjustable intensity
yes i know there's already a scanline feature,
the feature i'm referring to would be a png overlay with adjustable transparency and it's own folder for custom overlays to display over the games,

another feature that could be added is an sd card or usb drive pagefile

for those that have large sd cards or a spare usb stick or usb hard drive and want their games to run smoothly without as much bugs,an sd card or usb stick or usb hard drive page file would fix the problem since the wii doesn't have enough ram but external memory or storage can be used as virtual ram.

 

[sindrik]

?

 

[sindrik]

?

 

[Zopenko]

hi sindrik, so it would be best to use 4.2.8 source code, add the mods and then compile it with devkitppc r26?

question 1, if i use the 4.2.8 would we loose some good fixes done on versions 4.2.9 thru 4.3.2?
question 2, the history file says that version 4.3.0 was compiled with devkitPPC r26 and libogc 1.8.11, i'm wondering if the bug is due to libogc or related to the wiiu pro controller code.

 

[Pacheko17]

Know what would be great ( If possible )?
USB HID support. If I could use my USB SNES controller with this, I would turn my Wii into a SNES emulation box for sure.

 

[nakata6790]

hi sindrik, so it would be best to use 4.2.8 source code, add the mods and then compile it with devkitppc r26?

question 1, if i use the 4.2.8 would we loose some good fixes done on versions 4.2.9 thru 4.3.2?

4.2.8's superior performance defeats any minor improvements made by later versions that regressed in performance.
Please consider making a covermod based on 4.2.8

 

[sindrik]

hi sindrik, so it would be best to use 4.2.8 source code, add the mods and then compile it with devkitppc r26?

question 1, if i use the 4.2.8 would we loose some good fixes done on versions 4.2.9 thru 4.3.2?

Here's a list of the fixes between those versions.

[4.3.2 - November 9, 2012]
* Fixed lag with GameCube controllers

[4.3.1 - July 7, 2012]
* Fixed PAL support

[4.3.0 - July 6, 2012]
* Support for newer Wiimotes
* Fixed screen flicker when going back to menu
* Improved L/R buttons for GameCube - trigger button press when 50%+ depressed
* Improved controller behavior - allow two directions to be pressed simultaneously
* Timing changes
* Compiled with devkitPPC r26 and libogc 1.8.11

[4.2.9 - January 14, 2012]
* More accurate pixel scaling (thanks eke-eke!)
* Other minor changes

While i'm not an expert, maybe a 4.2.8 test could pinpoint the performance drop, then you could slowly incorporate each fix after that. Which leads me to your other question:

question 2, the history file says that version 4.3.0 was compiled with devkitPPC r26 and libogc 1.8.11, i'm wondering if the bug is due to libogc or related to the wiiu pro controller code.

I'd bet libogc and definitely not about the libwupc code. How do i know? I mentioned i compared your 4.3.2 Cover mod build against the 4.3.2 Chinese Mod (this one has libwupc support, no crashes during FFIII & Chrono Trigger battles and no weird lines in the upper part of the screen in B.O.B.), and the new 4.3.3 emu_kidid build, no problems at all!

By the way, if you can, check the FCEUGX improvements, i mentioned you at the post at that thread, it's really good!

 

[Zopenko]

Great news sindrink. I will start with the 428 version add the cover mod and wiiu pro. After that will see what we add.

Sorry for not responding on the fceugx I scrolled to the end and miss it. I'll start with snes and then move to nes emu

 

[sindrik]

Great news sindrink. I will start with the 428 version add the cover mod and wiiu pro. After that will see what we add.

Sorry for not responding on the fceugx I scrolled to the end and miss it. I'll start with snes and then move to nes emu

Thanks for your efforts, man. It sure is appreciated. Let's see how this experiment goes, i'll be ready to test and compare.

 

[Zopenko]

Thanks for your efforts, man. It sure is appreciated. Let's see how this experiment goes, i'll be ready to test and compare.

Thanks counting on your support.
Question do we know with what libogc did emukidd compiled his snes update?
I did a quick look yesterday to see if the more recent libogc version had any problems but I could not find anything.

 

[sindrik]

Thanks counting on your support.
Question do we know with what libogc did emukidd compiled his snes update?
I did a quick look yesterday to see if the more recent libogc version had any problems but I could not find anything.

Says he's using the latest version available.

 

[User556]

Also it led me, thank you. The bests versions for the moment, including "Fceugx".

 

[sindrik]

_

 

[Gabriel Mejia]

Bugs nor speed/smoothness are related to or would improve because of the hipothetical use of a pagefile. Not even GBA games need it.

Is that so? Well my friend knows how to code and even he says it can benefit with the addition of a pagefile considering the Wii
1.doesn't have that much ram.
2.doesn't have that much storage on the nand.
and
3.doesn't have that much processing power.

need I say more?

 

[sindrik]

Is that so? Well my friend knows how to code and even he says it can benefit with the addition of a pagefile considering the Wii
1.doesn't have that much ram.
2.doesn't have that much storage on the nand.
and
3.doesn't have that much processing power.

need I say more?

Again, are you aware that none of those things are currently a problem for the proper emulation of those systems on the Wii? Pagefile does not equal "processing power", that's complete nonsense. If your friend is such a competent coder, maybe he should implement it, and demonstrate the supposed usefulness of that feature in these emulators. Super Nintendo and Game Boy Advance roms fit fine with the current amount of memory, we're not talking about CPS-3 nor Neo Geo games here.

 

[Gabriel Mejia]

Again, are you aware that none of those things are currently a problem for the proper emulation of those systems on the Wii? Pagefile does not equal "processing power", that's complete nonsense. If your friend is such a competent coder, maybe he should implement it, and demonstrate the supposed usefulness of that feature in these emulators. Super Nintendo and Game Boy Advance roms fit fine with the current amount of memory, we're not talking about CPS-3 nor Neo Geo games here.

what you call proper emulation is nothing but a bunch of roms hacks in which they replace bits of code in the games on the fly as they're running or by disabling things which would cause performance hiccups
also i never said a pagefile equals processing power now
you're just making assumptions by twisting what i said,
what i basically said is that a pagefile is useful for performance improvements,
and that's a fact because all the raw information that gets interpreted by the emulator has to be stored somewhere and that somewhere is ram,
however the wii doesn't have enough ram which is why it needs a pagefile to store more of that
raw information including the clocking information
for the ppu the dsp and the cpu.

like i said before what you call proper emulation
is not proper emulation

[http://arstechnica.com/gaming/2011/...3ghz-quest-to-build-a-perfect-snes-emulator/]


on another note i wasn't referring to the roms not fitting somewhere,since storage and memory are two separate things,you should know that by now.

 

[Jacobeian]

what you call proper emulation is nothing but a bunch of roms hacks in which they replace bits of code in the games on the fly as they're running or by disabling things which would cause performance hiccups
also i never said a pagefile equals processing power now
you're just making assumptions by twisting what i said,
what i basically said is that a pagefile is useful for performance improvements,

Pagefile is only useful to get around RAM limitation, it doesn't improve neither emulation compatibility, accuracy or speed, for that matter
Not sure what you mean by "performance" but people usually uses this to define raw emulation speed, and implementing pagefile actually has a negative impact on emulation speed because it involves reading ROM data from SD or USB during emulation, which will always be much slower than directly running from RAM.

and that's a fact because all the raw information that gets interpreted by the emulator has to be stored somewhere and that somewhere is ram,
however the wii doesn't have enough ram which is why it needs a pagefile to store more of that
raw information including the clocking information
for the ppu the dsp and the cpu.

I don't think you understand how an emulator works. "clocking information" is not "stored" anywhere. The accuracy level of an emulator depends on the granularity of the emulated timings, which is the level at which your emulator is able to run the emulated chips (cycle vs instruction, pixel vs line , etc). RAM size has absolutely NOTHING to do with this, it all depends on how fast your CPU is so that the emulator is able to synchronize all those chips xxx times per seconds.

like i said before what you call proper emulation
is not proper emulation

[http://arstechnica.com/gaming/2011/...3ghz-quest-to-build-a-perfect-snes-emulator/]

I would suggest not quoting articles about cycle-accurate emulation when you clearly do not understand the concept of emulation (and probably not even this article itself, as many people quoting it in every discussion about cycle accuracy as if it was Holy Bible).

There is no chance of higan ever running on Wii but it has nothing to do with the amount of RAM or the ability to have a pagefile implementation but the fact the Wii CPU is too SLOW to emulate all theses SNES chips at such level of granularity and such frequency.

on another note i wasn't referring to the roms not fitting somewhere,since storage and memory are two separate things,you should know that by now.

Again, I don't think you have any idea about what you are talking (or maybe you have trouble expressing yourself, I don't know).
You store code and data in memory. Storage is a functionality and memory is a mean of storage, they are both linked.
As said before, Wii has way enough RAM to store any SNES emulator code+data as well as any SNES ROM, thus not needing any Virtual memory manager or "pagefile" implementation as you call it.

 

[sindrik]

?

 

[nakata6790]

On topic, any news on the 4.2.8. mod?

Man i compared 4.2.8 and 4.3.2. yesterday and the former is so much faster it's not even funny. Even with the hq2x filter enabled, 4.2.8 remains smooth, whereas 4.3.2 stubbles and lags.
Only issue with the current 4.2.8 is that i experience lockups when loading different roms consecutively.

 

[ShadowOne333]

On topic, any news on the 4.2.8. mod?

Man i compared 4.2.8 and 4.3.2. yesterday and the former is so much faster it's not even funny. Even with the hq2x filter enabled, 4.2.8 remains smooth, whereas 4.3.2 stubbles and lags.
Only issue with the current 4.2.8 is that i experience lockups when loading different roms consecutively.

Wait what?!
4.2.8 runs smooth with the hq2x filter enabled?! D: