Ok, and what about the Progressive hack?
well the buzzing wich i think its a beep might happen more often depeding on your options tell all your nintendont options and such, mcemu size log/osreport and forced stuff do push more memory if it didnt buzz for some peope is becuase they didnt had so much memory being used.Yeah I had that off too.
I was reading a post by FIX94 and he was saying it happens because the way they copy audio data to memory and it can cause buzzing sound. I see a few other people asking question about it too.
its just as region free as loading from sd and usb, same thing.I know Nintendont supports loading games from disc, But does it support games from other regions on Disc? Like a PAL copy of Wind Waker on a NTSC Wii.
Oh that's pretty awesome.its just as region free as loading from sd and usb, same thing.
I can confirm this.Odd issue with Timesplitters 2. When playing multiplayer, with 2 or more players, in this case, specifically 3, the game freezes and crashes the Wii U hard. Like, crashes with the loud, emitting "EEEEEEEEEEEEEEEEEEEEEEEEEEEEEE" noise. I'm using the latest version of N'don't, the mayflash gamecube adapter and original 'Cube controllers. The game is a 1:1 rip of my personal disc. I haven't experienced this with any other game, yet. Anyone else experience similar?
It seems to happen on multiplayer only. Not coop. That's the difference.i only did 2 player timesplitters story mode and always worked wonders did 3 or 4 missions, never did 3 players tough but for me 2 players never crashed.
say all your nintendont settings no matter how useless you think they are just making sure i can test with all your settings.
last time i saw anyone saying default settings from usbloader gx their nintendont settings had osreport and log on becuase of some old usbloader gx default mode make sure that isnt ON ashwhell.I can confirm this.
Using latest Nintendont (I know I'm supposed to state the actual revision.... Anyways, the one from the OP.)
And Wii Classic Controller Pro. (Original, not third party/fake)
It seems to happen on multiplayer only. Not coop. That's the difference.
BTW, Default settings and I launch it from USBLOADER GX.
well the buzzing wich i think its a beep might happen more often depeding on your options tell all your nintendont options and such, mcemu size log/osreport and forced stuff do push more memory if it didnt buzz for some peope is becuase they didnt had so much memory being used.
I noticed the buzzing a lot when playing ToS with devo, and occasionally the game would even freeze, but I am fairly certain that was due to the Wii U's underpowered usb ports. (I think I was using r200, it was before Nintendont could play anything really besides windwaker)I see, I have turned all options off, the only thing I can think I do different is I use actual memory card.
Sometimes it is very minor, sometime its quite a sharp buzz. I did try Devoloution too, I notice when entering very first battle there is a slight hint of same thing but ever battle after that it will play perfect like from disc.
Ps3 controllers have pressure sensitive triggers so to do an half press you just press half , of course if you have an old controller ini just delete it, nintendont internal controller ini for ps3 already has everything correct.
nope, it's because of some DSP mem copying that's why the buzzing is caused. (fix94 said that)I noticed the buzzing a lot when playing ToS with devo, and occasionally the game would even freeze, but I am fairly certain that was due to the Wii U's underpowered usb ports. (I think I was using r200, it was before Nintendont could play anything really besides windwaker)
It is less logical to find in github than it was on google code but it is possible.would do some more testing once I get some time and more importantly "learn how to download older versions" because I just so happened to have a copy of 3.336 on my other hard drive.
Alright, I need all the versions from 3.336 and up, just download them normally as "loader.dol" and put them in files labeled as the revision number so I know which is which and put them in a rar file, I'll do all the testing for using cheat codes, I just wanna know which revision broke the cheat codes but I know v3.336 works fine which I'm using right now.It is less logical to find in github than it was on google code but it is possible.
I was thinking of making a quick tutorial but i too lazy.. just tell me what version you want and i will give you the link..
lol, ok, it is gonna be a big rar though..sure you don't want links?Alright, I need all the versions from 3.336 and up, just download them normally as "loader.dol" and put them in files labeled as the revision number so I know which is which and put them in a rar file, I'll do all the testing for using cheat codes, I just wanna know which revision broke the cheat codes but I know v3.336 works fine which I'm using right now.