Hmm I guess I have to explain more about how the cycles and clocks can affect things:
If changing the cycles too much, it can cause the controller to stop taking input, same with memory cards. It's due to caching the recompiled cycle count and not liking the difference it all a sudden finds. A fix is to load the game again by pressing Volume Middle with the clock and cycle adjustments in place. It will use that new cycle adjustment with controls working just fine then.
Sometimes some games prefer lower cycles and clocks, such as Wipeout XL. To make the game load faster, up the PSX CLOCK during the loading course screen until it starts going fast.
If a game just doesn't work, try two things:
- Exit PSX4ALL and load that game. Remember cycle and clock adjustments stick between loading games within the in-game menu. Also there's a bug that sometimes occurs that crashes a game on load when loading a game in-game, though rare.
- When the LOADING GAME screen comes on, HOLD DOWN PSX CYCLES TILL IT GET TO 1.0 ! If that doesn't work, repeat that but also lower PSX CLOCK TO 80. All this should be done as soon as possible while the game is initing. If it still crashes let me know and I'll test it.
Let me know what games are in need of videos, and what the recommended clock/cycle combinations are for them.
For instance:
Bust A Move 4:
- GP2X CLOCK: 266
- PSX CLOCK: DEFAULT 100
- PSX CYCLE: DEFAULT 5.25
- INTERLACE: 1
- RUNS OVER 45 FPS, WITH VSYNC *OVER* 60, MORE THAN PLAYABLE WITH SOUND!
EDIT: Just to let everyone know, there's a lot of potential with this build by finding the right combination of PSX CLOCK and PSX CYCLE. I will do per-game configuration if I get a good feedback on what settings to use for what game.