[4.1] Slow Game Launch (any game/emulator)

[paradadf]

@Raphael-Bueno-Hatencia what's the output of tvservice wirh CEA?

[Raphael Bueno Hatencia]

@paradadf said in [4.1] Slow Game Launch (any game/emulator):

ervice wirh CEA

I don´t know if understanded. But my tv output is 1080p.

I did change global videomode to default, so my recalbox is always on 720p and there is no change on resolution. I thought this whould fast things up but no, still slow to startup.

[paradadf]

@Raphael-Bueno-Hatencia if you read the link I gave you thoroughly you will understand that setting video.globalmode to default isn't the best option (always). It defaults to the tv standard resolution wich might be very high, this the slowdowns!

So please, give me the output of the command tvservice explained at the bottom of the same page.

[Raphael Bueno Hatencia]

@paradadf said in [4.1] Slow Game Launch (any game/emulator):

So please, give me the output of the command tvservice explained at the bottom of the same page

hmm I thought that by using only 720, that was going to be so CPU intensive. Thank you =D

tvservice -s

state 0x12000a [HDMI CEA (4) RGB lim 16:9], 1280x720 @ 60.00Hz, progressive

tvservice -m CEA

Group CEA has 14 modes:
mode 1: 640x480 @ 60Hz 4:3, clock:25MHz progressive
mode 2: 720x480 @ 60Hz 4:3, clock:27MHz progressive
mode 3: 720x480 @ 60Hz 16:9, clock:27MHz progressive
(prefer) mode 4: 1280x720 @ 60Hz 16:9, clock:74MHz progressive
mode 5: 1920x1080 @ 60Hz 16:9, clock:74MHz interlaced
(native) mode 16: 1920x1080 @ 60Hz 16:9, clock:148MHz progressive
mode 17: 720x576 @ 50Hz 4:3, clock:27MHz progressive
mode 18: 720x576 @ 50Hz 16:9, clock:27MHz progressive
mode 19: 1280x720 @ 50Hz 16:9, clock:74MHz progressive
mode 20: 1920x1080 @ 50Hz 16:9, clock:74MHz interlaced
mode 31: 1920x1080 @ 50Hz 16:9, clock:148MHz progressive
mode 32: 1920x1080 @ 24Hz 16:9, clock:74MHz progressive
mode 33: 1920x1080 @ 25Hz 16:9, clock:74MHz progressive
mode 34: 1920x1080 @ 30Hz 16:9, clock:74MHz progressive

[paradadf]

@Raphael-Bueno-Hatencia first of all, your global.videomode should be CEA 4 HDMI.
You have slowdowns in SNES, right?
What about a bad power supply? Don't you get a lightning icon on your screen?

[Raphael Bueno Hatencia]

@paradadf Yeah, i putted back to CEA 4 HDMI

Nope, my slowdowns on starting the game is on any emulator, gameboy, snes, gba, mega drive etc.

But yesterday I´ve tried Dreamcast, and it ran super fast. I pressed X, recalbox zoom in the coverart, and dreamcast logo was showing on screen. It was instantly.

Not, i had that problem last year, but i bought a new power supply and the lightning icon never appeared again.

[Substring]

@Raphael-Bueno-Hatencia then it's related to retroarch only ... N64 should start very fast too

[Raphael Bueno Hatencia]

@Substring Yes it was faster than anygame that uses retroarch.

But it is a clean install from 4.1 image, and I didnt touch anything retroarch related, why the problem remains?

I did another script: https://file.ac/qmVg05xNb0A/

[Substring]

@Raphael-Bueno-Hatencia are ypu using a usb key ? Or did you just reinstall from scratch and test with the free roms ?

[Raphael Bueno Hatencia]

@Substring I reinstalled from scratch the 4.1 img using sd card and the first tests was using the free roms. Them I added the roms of other system for testing. All roms are in the SD card

[paradadf]

@Raphael-Bueno-Hatencia could you try another tv?

[Raphael Bueno Hatencia]

@paradadf I´ve tryed in another tv HD, native 720p and it worked fine!

Them another test in a common pc monitor, All roms starting fine and fast.

I thought the problem could be a config on my main TV fullhd, but when I tested it, it was working fine too after the other tests, nothing was changed, not even a rom.

I really don´t understand.

[Raphael Bueno Hatencia]

@paradadf After turning off and on again, it was slow again!

I tried to change everything on my tv, hdmi ports, gamer mode, everything, nothing worked.

I realized that in my other screens tests, I used ps3 controller, not my ps2 controller with twin ps2 adapter usb. Trying without it, using only ps3 via bluetooth it worked fine!

So this is the problem? Maybe I should only use that adapter when playing multiplayer with 4 controllers. It was pratical because there is no need to recharge battery. Is there anything we can do to make speed with adapter works normally?

[paradadf]

@Raphael-Bueno-Hatencia good finding. Sadly, I can't help you with that... I'm not a developer. Maybe one reads this and has an idea.

[Raphael Bueno Hatencia]

@paradadf No problem. I just hope this is really the problem.

I will still verify if this is correct, try to plug it after recalbox is on just for testing purposes.

Any news I'll bring here.

Thanks a lot for helping me.

[Substring]

I have no b****y idea why a USB adapter would slow down the start of RA ...

[Raphael Bueno Hatencia]

I´m not so sure now. The slow on starting games returned, but most times recalbox is restarted, speed is fine (without the usb adapter).

I´m out of ideas what is causing this problem on a clean image.

[rockaddicted]

Did you try an other SD card ?

[ls45]

Hello, I've had the same problem, and found the solution by chance.
Deleting retroarchcustom.cfg makes game launch fast again.
If I save configuration from retroarch's menus, it creates a new 97Kb retroarchcustom.cfg...
And everything is lauching slow again...

There's something in this big retroarchcustom.cfg that makes it launch slow.
I didn't take time to analyse the full retroarchcustom.cfg, but there's a big difference with retroarchcustom.cfg.origin : input_joypad_driver is set to "sdl2" before saving. Saving from retroarch changes input_joypad_driver to "udev"...

[secreus]

I've discovered on my own (same issue btw) that Retroarch launches just fine. There's no delay in the launch, it just takes a bit to display on whatever TV we're using. To test that, you can press [Hotkey + B] 2 or so seconds after clicking the game in EmulationStation. When the screen does display, it will display the Retroarch menu. This proves that Retroarch runs at a normal time, and that input is accepted. It's either an issue with EmuSta or your monitor