Pauses on disk based games.

lostless

FWI all, just installed retropie x86 and got the same pauses. So i think its a retroarch issue. I haven't seen it recently on the pi.

DD-Indeed

I think too, that the problem lies within the Retroarch system and I have a feeling, that it loads too much and too fast the data into RAM and when it needs to load again, the game freezes briefly, before it gets new data. This could be fixed with smoother constant data loading that prevents Retroarch from loading too much data into the RAM too fast, giving the way to HDD sleep. It can happen with all memory devices. Smaller older games don't have that issue, as they can be fully loaded into the RAM straight away.

DD-Indeed

Again I today withnessed it, I had my PiStation lid open, suddenly the game freezed for couple seconds and then the USB stick started to flash, indicating that it's transferring data and then the game continued. So either Retroarch puts the memory device to sleepmode too quickly or then it loads the data in too big chunks and when runs out of the data, the game freezes.

mitu

@dd-indeed said in Pauses on disk based games.:

Again I today withnessed it, I had my PiStation lid open, suddenly the game freezed for couple seconds and then the USB stick started to flash, indicating that it's transferring data and then the game continued. So either Retroarch puts the memory device to sleepmode too quickly or then it loads the data in too big chunks and when runs out of the data, the game freezes.

The sleep mode might be triggered by the OS (Linux), not Retroarch, which doesn't know what storage is beneath your file system.
If you check the os logs - via dmesg - when the pauses occur, do any error/message show up ?

DD-Indeed

@mitu said in Pauses on disk based games.:

@dd-indeed said in Pauses on disk based games.:

Again I today withnessed it, I had my PiStation lid open, suddenly the game freezed for couple seconds and then the USB stick started to flash, indicating that it's transferring data and then the game continued. So either Retroarch puts the memory device to sleepmode too quickly or then it loads the data in too big chunks and when runs out of the data, the game freezes.

The sleep mode might be triggered by the OS (Linux), not Retroarch, which doesn't know what storage is beneath your file system.
If you check the os logs - via dmesg - when the pauses occur, do any error/message show up ?

So should I open that in command promp immediately after the game has had those brief freezes ?

DD-Indeed

I started the device, started a game till the brief freezing occured and immediately after that exited and went into the command promp to apply that command you told. I didn't see any particular issues in it, except for two lines stating this:

And that is about the USB stick where I have the games. Is that something about the system not having catche enabled or something ?

mitu

@dd-indeed said in Pauses on disk based games.:

And that is about the USB stick where I have the games. Is that something about the system not having catche enabled or something ?

That message is from the system boot, when the stick is initialized first, doesn't seem to be something wrong with it.

You could try to play with the sdparm (or hdparm) command and disable the idle/power saving , but I doubt this works for the stick. The more I think it could be the USB port that's put into some sort of power saving (?), but I don't know offhand how we could check that.

DD-Indeed

@mitu

I'll check that, thanks. Further investigation is definitely needed in this issue, since it happens in all games.

DD-Indeed

Update:

I found these instructions and tested them:

link text

What I did for USB memory stick was to input these settings to be used (settings for regular HDD might be different):

sudo hdparm -B 255 /dev/sda
sudo hdparm -S 0 /dev/sda

I first tested them for 30 mins in Driver 2 and then for about 20 mins in Gran Turismo 2 and then again with Driver 2 for 5 minutes. With the Driver 2, I didn't encounter a single freeze in 30 mins. Then I went for the GT2. There I withnessed 3-4 freezes overall. Then I went back to the Driver 2, because I started to think, that maybe heat or something triggers the freezing issue. But on the second tryout with Driver 2, no freezes at all.

So now I'm wondering, that could it be about the emulator software or does the game have differences in data loading methods. Needs to be further investigated and someone else could try with that guide I linked.

Update: I now discovered, that there is audio cuts during the GT2 Arcade Disc's demo, that starts rolling after a while when sitting on the main menu. Maybe the issue could be related to that as well, sync problems you know.

DD-Indeed

This post is deleted!