are you using a wavebird?
Why could wavebird be the problem?
are you using a wavebird?
kevin@kevin-Xubuntu:/media/kevin/1701-3552/games/F-Zero GX [GFZE01]$ md5sum ./game.iso
81293462cf48c6a482c33e25c4097ac0 ./game.iso
Why could wavebird be the problem?
No WaveBird.
And fine I'll reverify my ISO.
Official black GameCube controllers. I've tried swapping(I've got two) and both seem to demonstrate the problem from time to time.
OK... well I have no clue if it's all ports but, if there is a course that needs a lot of power slides (L +R triggers + Analogue) sometimes for a brief moment the analogue seems stuck to the left even when the stick is centred. It doesn't stay stuck, but it's long enough to send you into a wall, off the track or generally mess up a turn.
It's not completely ruining the game, but it is frustrating when it happens. Anyway, look out for it I guess.
cause using wavebird with the gamecube adapter has the problem of getting stuck in one direction and forcing you to turn it on and off. Completely random but it does happen even on smash 4.
Its happened to me 3 times since the adapter came out and ive looked around and it seems to be a common problem. Its easily fixable though, when it does happen simply turn the controller off, wait 5 seconds and turn it on aback again.
Removing the info might not be wise but would it be possible to make an option to make the screen fade to black after selecting the game, or make the text and everything not visible? This way when running from a loader we get a black screen followed by the GC bios screen followed by the game, that's what I suggested from the very early days of Nintendont, if "removing" the info is a bad idea we can always try to "hide" them somehow, as an option of course, so that if you run into issues you can always re-enable them, this way it looks as if the games run strait, I know it serves no purpose gameplay wise but just like the bios screen it's a nice touch that's been requested many times before.
Well, that was just an idea, not even a request, not every nintendont user is a n00b, so there are a segment of users that can control exceptions, differentiate between versions, using within USB loaders, manage emuMC, etc... These same users would want an option (hiding through settings, but not removing from code) to make the GCN emulation the closest to the original hardware, I don't see a problem with that.what is the difference between "removing" and "hiding" ?
The dev just don't want noobs come here and say "dosn't work" without any details.
Noobs have been doing that even with all the on screen messages, what do you expect if those are hidden?
Well, that was just an idea, not even a request, not every nintendont user is a n00b, so there are a segment of users that can control exceptions, differentiate between versions, using whitin USB loaders, etc... These same users would want an option (hiding through settings, but not removing from code) to make the GCN emulation the closest to the original hardware, I don't see a problem with that.
I said "hide them during boot up" and "make it an option" noobs will still be able to enable them and see all the needed details.what is the difference between "removing" and "hiding" ?
The dev just don't want noobs come here and say "dosn't work" without any details.
Noobs have been doing that even with all the on screen messages, what do you expect if those are hidden?
I said "hide them during boot up" and "make it an option" noobs will still be able to enable them and see all the needed details.
Why wouldn't you? Devolution without the sample loader doesn't tell me anything why should Nintendont? If there's any issue you just turn on the debug setting via a loader. The early revs of DML had no splash screen and it always worked for me.Why would we want to remove the name of the program?
Any user who just got into nintendont will probably be using it as boot.dol and not use autoboot, so no change.Why would we want to remove the version of the program? Its hard enough to get people to report what version they are having problems with.
Any user with a little bit of common sense can find there's a newly created file on the root of their device, but wait they won't because they would be using autoboot; something you set on the external loaders and the file won't be written to the device(just memory).Why would we want to remove instructions on how to cancle the auto boot?
If the user is using autoboot then there's no problem because he knows that if something goes wrong he can just start nin without autoboot and read the status text like normal. Error messages don't have to go obviously because they don't normally occur.Why would we want to remove status and error messages during boot?