The last snes9x release

[Dozer]

Its weird, i just tested the emu with sound and left the frameskip at what it was (3) and the speed stayed the exact same, well if it did slow down at all i didnt notice it. The sound was a lot slower however, it kept up with the game, so if like i collected a coin it tinkled at the rite time, just really slowly. Just wondered if anyone else experienced this. . Oh, by the way, i tested this on the super mario world and the mario compilation one and worms. Not sure about the rest.

 

[Delsabre]

it depends on the game.

Mega Man X runs fine w/sound at frameskip 5 @ 166MHz
SMW runs fine w/sound at frameskip 4 @ 166MHz
FZero runs a bit slow w/sound at frameskip 6 @ 166MHz

Kirby Super Star is unplayably slow at frameskip 10 with no sound @ 166MHz

 

[Dozer]

it depends on the game.

Mega Man X runs fine w/sound at frameskip 5 @ 166MHz
SMW runs fine w/sound at frameskip 4 @ 166MHz
FZero runs a bit slow w/sound at frameskip 6 @ 166MHz

Kirby Super Star is unplayably slow at frameskip 10 with no sound @ 166MHz

Sorry, i just meant the standard 133 mhz version.

 

[Delsabre]

the amount sound slows down depends on the game. the change in SMW isnt hardly noticeable. you can hear the sound speed up when the emu isnt drawing anything ( like just before the map fades in ).

 

[Grinder X]

I would love to play Megaman X with sound fullspeed.
But my GP32 wont clock to 166MhZ Just 156...

But i don't like overclocking either.

 

[Azure]

I would love to play Megaman X with sound fullspeed.
But my GP32 wont clock to 166MhZ Just 156...

But i don't like overclocking either.

Why don't you like OCing?

 

[NiN^_^NiN]

Why would he?

I dont overclock even tho i can do 166 and 156

you just dont know whats gonna happen to the machine in the long run

just running the gp32 for 2 or 3 days stright wont tell u if it stuffs something up in the future.

But lets not get into that argument again.

h34r:

 

[Azure]

Didn't Craig leave it at 166mhz for a really long time and nothing happend? I don't think anything bad can happen from OCing. It's not like your going to play the GP32 at 166mhz for a really(4 hours+) long time, so it should be safe.


After turning sound on most games I usually have to increase frameskip by 2-3 to get the same speed as no sound.

 

[declaration]

running your gp32 at anything over ithink its 66mhz is technically overclocking and it has been regarded as safe to do this for some time now. it has now been reported that it should also be safe to overclock to 166mhz.
However, i still wouldnt like to guarnatee that things won't go wrong.

 

[Tobriand]

It's always been reckoned to be safe to overclock to as much as 132MHz, but beyond that is the region that has been considered "dodgy" for some time now. That's the one that's been tested and found to be fairly safe... ish...

 

[declaration]

why ish? Has anybody reported any problems that have definitely been attributable to overclocking to 166mhz?

 

[frogger]

I haven't read any reports of problems - I guessing that 133 is seen as the last 'safe' speed as it's the maximum some machines can go without crashing, so it would be unfair to suggest that you can overclock higher.

I've had no problems as yet (touch wood) at 166 on my FLU GP32.

 

[bradley]

i like to play on the safe side with the OC situation as well, craig as far as i know only tested 1 unit didn't he, if it was more it probably wasn't many

but its pretty clear not all machines are the same, some peoples units crash going above 133 others can run 166 without any problems and some crash after a certain amount of time, all he did was show that his particular machine could do 166 without noticable problems, that doesn't mean everyone would get the same results, i'll play safe untill i can afford to take risks or theres a few more tests run

these units that crash after a certain amount of time, what actually causes the crash, is it slowly heating up over time and its reaching its limit, coz if thats the case it doesn't sound healthy stressing out the machine like that, u might have a machine thats very close to crashing but just below its limit and in the long run u find your machine dies a lot sooner than other units

 

[Rico]

bradley: i fail to see how that would work, the temperature increase has been checked and is pretty small. Still even if it dies, I won't be using it in a couple of years..

Dozer: Aladdin (lol) needs about fs5 for the short time I played it, at 156 MHz. I have yet to test my new GP32 at 166 MHz (my old one resets on the spot) so I'll see how it goes.

 

[Grinder X]

I don't like to OC cuz it might damage my GP32.
I playd on 156 for about 5min just to see if it worked.. 166 crashes after 3sec...

But hell yeah.. If somone could say that it is for sure completly 100% safe, then i would OC all the time

 

[declaration]

Why do people say that it might break their machines. What proof of this is there. if the increase in heat is minimal it should be ok to overclock....

 

[Azure]

I don't like to OC cuz it might damage my GP32.
I playd on 156 for about 5min just to see if it worked.. 166 crashes after 3sec...

But hell yeah.. If somone could say that it is for sure completly 100% safe, then i would OC all the time

I'm 99.9% sure that it is safe. If your GP32 can't handle the clock setting, it'll just freeze or restart, no damage done. A lot of us have played at a higher clock setting and nothing bad has happend.