Gpsp 0.9-2xb


I'm playing Crash Bandicoot XS (E) with 250MHz, no RAM tweaks, and 4096 audio. I freezes after 30-40 mints. I did a fresh install for the latest emu version and still the same problem.

BTW, it freezes for other roms, but I play this game almost all the time.
 
Fargo said:
I'm playing Crash Bandicoot XS (E) with 250MHz, no RAM tweaks, and 4096 audio. I freezes after 30-40 mints. I did a fresh install for the latest emu version and still the same problem.

BTW, it freezes for other roms, but I play this game almost all the time.
Since we're on this lead, what's your firmware version?
 
Last edited by a moderator:
Now I could test Sonic Advance 2. (SONIC ADVANCA2NP8P) As usual with 266MHz and FS auto 2 or manual 1...
Hmm, for me, this game is far away from smooth. Maybe it's because I compare it with the MegaDrive Sonic games but I don't know. The FPS in GPSP looks always good, often above 40, 50, nearly 60 but the game don't look like 60 or 50 FPS. :( it "feels" more like 20 or less (for me) But even with 30FPS FS1 it should be smooth enough I think. Maybe Metroid isn't that fast but it feels much much smoother (particialy). Are constant 60FPS really that important for the right ingame-smoothnes?
 
Well there you go, last night I was playing the GP2x, and it crashed. I was having trouble loading savesstates too. On a hunch I booted it this morning, puzzled why I had difficulties last night - the sound buffer had reset to 2048MB somehow. So that explains the crash I had thirty minutes after starting, but not my initial savestate problems, let me explain;

I loaded up slot 0 fine, and discovered it wasn't the right one, I loaded the next slot. Screen went black and the GP2x crashed. I rebooted. I determined to load up slot one first, same result. I rebooted again. I decided to load up slot 0 again, thinking it was likely the most recent - it crashed in similar manner to slot 1. I rebooted for the third time. Then I loaded slot 2, and saved it to the game save. Then becoming very paranoid, I shutdown and copied the saves to my PC (Including 'broken' 0 and 1).

So now the question is how does a savestate become broken simply by loading it, or another savestate. It seems unlikely loading should cause a problem - this whole debacle may have been what caused the sound buffer to reset... Exophase if your interested I have the broken saves, if you want to check it out. Maybe it was my 2gb sd being weird, I don't know...

Edit; There is no GP3x :ph34r: \Waves hand. You didn't see this...
 
Maybe vsync Off is bothering you too much and your eyes-brain feels like the game is not smooth like original.

I think frameskip is working very well.

Sorry for my horrible english :D
 
Zeladin said:
I loaded up slot 0 fine, and discovered it wasn't the right one, I loaded the next slot. Screen went black and the GP2x crashed. I rebooted. I determined to load up slot one first, same result. I rebooted again. I decided to load up slot 0 again, thinking it was likely the most recent - it crashed in similar manner to slot 1. I rebooted for the third time. Then I loaded slot 2, and saved it to the game save. Then becoming very paranoid, I shutdown and copied the saves to my PC (Including 'broken' 0 and 1).
Delete your config file for the game. Or move it somewhere else, at least (deleting might get rid of any battery saves, I'm told, though I think they're mostly kept in separate files). I had exactly the same problem and deleting gpsp.cfg and gamename.cfg (from the roms folder) fixed it perfectly, though I did have to re-configure things properly. This is back on the v.9004 --> v.9007 upgrade, though, so could have changed. Worth a shot though.

This may also still apply to other random crashes... certainly it did on older versions, where deleting the old config files solved many problems, albeit for no aparrent reason.
 
Last edited by a moderator:
Rivroner said:
Maybe vsync Off is bothering you too much and your eyes-brain feels like the game is not smooth like original.

I think frameskip is working very well.

Sorry for my horrible english :D
If anyone does know how to wait for vsync on GP2X let me know because it's a much better synchronization facility than the timing. That could be off and causing the problems.
 
Last edited by a moderator:
Exophase said:
Rivroner said:
Maybe vsync Off is bothering you too much and your eyes-brain feels like the game is not smooth like original.

I think frameskip is working very well.

Sorry for my horrible english :D
If anyone does know how to wait for vsync on GP2X let me know because it's a much better synchronization facility than the timing. That could be off and causing the problems.


these might help or might not, i'm not really sure since at this point i haven't done enough coding. looks applicable though.

http://wiki.gp2x.org/wiki/GPIO_Reference
http://wiki.gp2x.org/wiki/Writing_to_the_framebuffer_device
 
Last edited by a moderator:
having decided that i would wait for a few presentational tweaks before look at this properly i some how found myself playing final fantasy tactics advance at what felt like full speed to me.

i hadnt looked through many of my roms - they started with A and Advance Wars has some pretty bad sound issues, so i had tried that and then thought i would wait for more work to be done....but yes its true, this is a lovely little emulator and it makes me feel all squishy inside :)
 
Exophase said:
Rivroner said:
Maybe vsync Off is bothering you too much and your eyes-brain feels like the game is not smooth like original.

I think frameskip is working very well.

Sorry for my horrible english :D
If anyone does know how to wait for vsync on GP2X let me know because it's a much better synchronization facility than the timing. That could be off and causing the problems.

... So there's no vsync on Gpsp? Either way there's definitely something funny about it drawing to the screen (I checked unscaled too), the fps is fine is more, something like ghosting, tearing, but kind of not like either of those...

@Tobriand I'll give that a shot.

Now to go and fix that typo before anyone else gets excited...
 
Last edited by a moderator:
rokdcasbah said:
sounds like the problem i had. it turned out to be the ram timings. once i screwed around with them even more, gpsp started running really smooth, with no breakup in the audio whatsoever...but a tiny bit of lag, but i like the lag because it lets me know there isn't a crash on the horizon :)
The emulator actually seems to run very well, no lagginess or stuttering, (clocked to 230ish, with Craig's ram timings, audio buffer 2048/4096/8192 and manual FS 2)

But I would be interested to try your ram timings, would you be kind enough to share?

This problem looks like it may be very elusive, I wonder if it is somehow relates to specific models of the unit or something.. it seems strange that some people have no problems, and others seem to suffer a lot.

We need some kind of across-the-board tests I think, and narrow it down-- ie; a number of people with different revision units playing a certain game, running on a certain firmware with specific settings...

.. or maybe create a page in the wiki, where we can put our exact settings/conditions and report crashes there...?

what do people think? should I start a new thread for this and create a wiki page?

Exophase/Zod, would this even be useful in tracking the problem?
 
Last edited by a moderator:
I think the model specific issues started to appear when I put in the cpu_speed application within gpSP2X. Maybe it's time to rip that out and make something more streamlined.
 
zodttd said:
I think the model specific issues started to appear when I put in the cpu_speed application within gpSP2X. Maybe it's time to rip that out and make something more streamlined.
Agreed! All that is required is an on/off switch for optimized Ram Timings. Speed should be a seperate setting. And that's it!
 
Last edited by a moderator:
i borked my gpsp dir and had to reinstall it, i then found out i was missing mmuhack.o so i just copied the one from squidgessnes. and when i fired up mariokart, it had some flimsy artifacts in the opening but seemed faster (artifacts were gone when playing)

gpsp latest@240mhz, no ramtweak,autoframeskip 2,audiobuffer 8192

any body seing similar results ?

metroid Z,F and Yoshis island seems "speedier" to
 
Yes, i tried some time ago mmuhack.o from Picodrive and had same result.
With last GPsp release from Zodttd you will not have artifacts.

I used that mmuhack because i though all mmuhack.o were the same and that mmuhack had the date more recent.
mmuhack.o from Zodttd is from July.

Máybe the speeds are differents, i dont know.
 
Exophase said:
Fargo said:
I'm playing Crash Bandicoot XS (E) with 250MHz, no RAM tweaks, and 4096 audio. I freezes after 30-40 mints. I did a fresh install for the latest emu version and still the same problem.

BTW, it freezes for other roms, but I play this game almost all the time.
Since we're on this lead, what's your firmware version?

FW version 3.0.0

One thing that I forgot to mention and might be useful in debugging. Sometimes, The emu suddenly slows down to ~13fps for few seconds or a minute then goes back to normal speed for few minutes then slows down and so on. It goes through this cycle of several slow downs and speed ups before it freezes.
 
Last edited by a moderator:
everybody keeps talking about how great yoshis island plays. I can't get it to run at all. I get through the menu screen etc flawlessly and that rotating mode7 island is looking smooth and overall great. But when I am about to go ingame, it suddenly freezes out of nowhere, where it is supposed to show a scene of yoshi dino cuteness... damnit. The screen is going to fade in but it freezes while the image is still sorta grey. I am using an EU rom, not hacked, no revision. It's a regular image. I am also using the right bios. what the heck?
 
Have you erased the cfg from yoshis rom? Maybe is that.
I am using (U)
 
I will give it another try, eventhough I do not believe that an ingame freeze which only ocurrs at a specific spot might be caused by that .cfg problem. If it works, I will knock my head against a wall for not trying before...
 
Back
Top