Yes, but you just have to return to the menu short and go back ingame, and the screen is centered again. You don't need to change something in the screen-config.DaveC said:A few other bugs I noticed. Everytime you start the emu it shows an unscaled screen in the upper left. I go into the menu and it says "scaled" but it is not. I change to "unscaled" and it centers it. It doesn't save my settings either, I have to do it every time.
How do you skip 1/2 of a frame?fusion_power said:Yes, auto-Frameskip still is a little bit choppy here and there, maybe this could be solved with finer steps. FS 0.5, 1, 1.5, 2...
I mean FS 0.5 is XXX.XXX.XXX (X -frame, . -skip)
FS 1 : X.X.X.X.X
FS 1.5: XX.XX.XX.XX
FS 2 : X..X..X..X
DaveC said:How do you skip 1/2 of a frame?fusion_power said:Yes, auto-Frameskip still is a little bit choppy here and there, maybe this could be solved with finer steps. FS 0.5, 1, 1.5, 2...
I mean FS 0.5 is XXX.XXX.XXX (X -frame, . -skip)
FS 1 : X.X.X.X.X
FS 1.5: XX.XX.XX.XX
FS 2 : X..X..X..X
No, I just name it so. I don't know if FS work this way but FS 0.5 would just skip every 3. or 4. frame just to smooth everything while auto-FS is on... ^^""
Random freezes:
I played the whole Metroid Fusion game on GPSP and now the 2. time and the freezes are absolutely not reproduceble. Sometimes I can play hours and nothing happens, then it crashes after some second's/ minutes of play. Doesn't matter if I use Savestates or SRAM states or start a new game. (Like Castlevania COTM )
266MHz; Audio 2048; RAM-Tweaks on
It would be an improvement if the emulator wouldn't crash the whole GP2X. :lol: Even with Wrapper on from Gmenu it hangs my Handheld - no other program has this skill. ^^
You might be onto something there!Exophase said:My current thoughts are that the crashing is related to a psychological connection between yourself and the GP2X. Apparently the GP2X is engineered to most accurately prove you wrong. Try thinking pessimistic thoughts the entire time and it might not crash.
Seems to be working, its been running about three hours now... Oh no! That's not pessimistic thinking!! Agh!! Good thing I turned it off - better that way, no disappointment...Exophase said:This may not be a preferable alternative to turning it off, but if it does freeze you can probably kill it by telnetting in.
My current thoughts are that the crashing is related to a psychological connection between yourself and the GP2X. Apparently the GP2X is engineered to most accurately prove you wrong. Try thinking pessimistic thoughts the entire time and it might not crash.
The GBA audio is internally resampled to 44.1KHz, and the frame rate is at 60Hz, so there are 735 samples per frame (2 bytes per sample, 2 channels brings it to 2940 bytes). Note that this is higher than 2048 bytes, which means that's not a particularly good choice for a buffer size, IMO (I think on the PSP version anything less than 2940 doesn't even work). I think that on GP2X the buffer size has to be a power of 2, although this is only going by the settings zodttd allows. But you can see that the frame rate doesn't divide well with any buffer size, and even if it did the audio updates are still asynchronous (running in another thread, no way around this that I know of).slaanesh said:I've found that an audio buffer of 2048 bytes is a good compromise between speed and latency.
I haven't looked at the code, but was wondering how many fragments this is split into?
If the fragment size is constant then increasing the buffer would allow for more fragments, which would mean less chance of stuttery sound but increased latency (as each fragment is basically a one frame delay in playing time).
Is this correct?