if it's screensaver / screenblanking shouldn't it happen when other screens are attached as well ? the settings about it do not change when switching screens so in theory he should have the issue on every screen attached then
You're using an unsupported installation method, that's why you're having problems. I guess you've been installing based on a certain outdated and wrong youtube video.
So now to my porblem... If i run the n64 emulator called "mupen64plus-gles2n64" I have a very small picutre in the left corner of my screen. I set my retoarch settings to use 16:9. Also if i select a specific resoloution it wont apply it.
With the other emulators like "mupen64plus-gles2rice", "mupen64plus-GLideN64-highres" and "mupen64plus-GLideN64" i get a bigger screen but only 4:3 ratiation and it's not play able.
@mitu ok but yes, i tried different roms and the bios is there and correct, validatd the hash. it is getting recognized by mGBA too. i thought maybe it's related so i answered in this thread. It really seems like a BIOS problem though because at first start there is no gba intro only after the restart and the following restarts the intro appears, really weird problem. Are there other known gba roms with skip-intro problems maybe so i could test those?
It may be a power issue - are you using a proper power source ? Can you try and test your controller via jstest to see if the buttons/d-pad/joysticks are registering ?
You can use the "collections" functionality to have all the Pokemon games on a single list. When a game is selected, it will launch the game with the emulator required for the rom. I recommend checking the documentation ( https://retropie.org.uk/docs/ ), so you can setup the games with the best emulators. Once that's done, check this guide (look up collections) : https://github.com/RetroPie/RetroPie-Setup/wiki/EmulationStation
From what I understand, the version of DraStic that we have access to is just a generic ARM build and isn't well optimized. It works ok on previous pi models under the legacy Vc4 drivers, but using fkms on the pi 4 it seems to have issues.
I had an issue almost the same as this. I have a pi4b with a 7” touchscreen. When I plug it in to my tv it starts fine color burst and command line show fine on my tv and the 7” screen together, but as soon as emulation station starts the picture goes away and only the sound comes through the TV. If I go into command line or pixel desktop the picture comes back on the tv. After a couple weeks of frustration I figured out if I take the power off the touchscreen everything will work perfect on my tv.
Thanks to all. I just bought a Pi 4. Mainly because it is more future proof. I will play around with Lakka for some time, waiting for Retropie to be fully compatible.
I had the same issue. The problem is that RetroPie manage default resolution very bad.
To solve this and other performance issues just play with the resolution and set the best that fits your needs.
You have to enter the raspbi-config -> display options.
If the system crashes when you select display options, use this trick:
Enter the menu and before opening display options disconnect the HDMI.
Than open display options (with screen off) and connect HDMI again.
It should solve the problem.
After I changed resolution I experienced a big performance jump!
And all that glitches and sprite problems was solved
