PSX Short Draw Distance, specifically in Crash Team Racing
langest last edited by
I played through Crystal Cup on resolution hack without speed hack.
The sound went silent a few times but the frame rate seemed constant. Sewer Speedways was without any issue. Roo's Tubes and the Dingo Canyon were the ones where sound went for a couple of seconds.
Worth noting is that I'm good at the game relative to the AI, so I rarely see multiple racers on the screen or items being used. That could be a cause of the better results. That being said, I have not over clocked my pi to the limit so you could crank up the clock speed even more and you probably wouldn't have the sound issue.
Great, thanks for the results. I'm going to pick up a Pi 4 this weekend so I have this to look forward to.
I now have a Pi 4 (4GB not overclocked) running Lakka/PsxRearmed.
I set the resolution hack on, turned off the dynamic re-compiler and set the internal FPS counter on. The game's internal FPS is 30FPS. The game does slow down a bit, sometimes as far as 25FPS while racing and further during animation scenes but the slowdown isn't really noticeable when you play.
I overclocked my Pi4 by following the instructions in this ETA Prime video:
CTR now maintains an unwavering 30FPS on every track I tried. I think the slowdown on the victory laps etc. may be accurate emulation of the PS1's slow GPU.
BillyH last edited by
It's as they say, if at first you don't succeed, try try again with better hardware.
George Spiggott last edited by George Spiggott
We're probably at the peak of what can be done with the current core. If/when Beetle makes it to ARM systems we will see some improvements there with even higher resolution and removal of bending issues.
The saga of the perfect CTR play experience continues.
On my current build (Weekly 4.5.13) the sound cuts in and out on CTR if I have enhanced graphics and interpreter selected (but not if I only select one of them). I'm overclocked on the CPU to 2000, the GPU is unmodified as AFAIK it has no affect on PSX reARMed.
Can anyone replicate or fix this with the existing settings?
quicksilver last edited by quicksilver
@George-Spiggott if you are running enhanced resolution and running interpreter at the same time you are probably pushing your cpu too hard and the game is slowing down, which is why the audio is getting choppy. A dynarec is much faster but causes issues with this game. So I would recommend not running the enhanced resolution option if you are also running interpreter.
It's not just that the game is slowing down/skipping sound. I did had a pi4 build run CTR flawlessly in hi res without the dynarec (under Lakka). I appreciate Lakka may have different overheads that isn't the issue here. The thing is that one very other retroarch/lr-psxreamed Pi build I have had (both on my pi3 and pi4) CTR and other games would slow down and the music would distort rather than cut out which is less noticeable when you're playing.
I think this cut out sound vs distort sound may be a settings question.
After a little testing I found thst keeping the dynarec off, enhanced graphics on and switching on the speed hack seems to be the least graphically intrusive option. Sound still cuts out, but only very occasionally, and a couple of weapons look odd but the rest of the game looks extra pretty.
I could also overclock more but I'm already at 2k on the CPU.