@dankcushions said in Pi 4b black screen issues:

@luisdent like i said, show us your config file and we can diagnose. there's an extra few lines that helps on some monitors:

hdmi_max_pixel_freq:0=200000000 hdmi_max_pixel_freq:1=200000000

in addition to a working 1080p mode, which for you may be

hdmi_group=2 hdmi_mode=82

ps, can you not SSH in to diagnose via another PC on the network?

Not sure which fixed it, but this made it work properly. It flickers a screen with the terminal/command cursor a few times quickly but i see it and then it displays the appropriate screen following that. So far i've gone in and out of config screens and reboots and it appears to be working now.

Thanks!!!

Now to fix the performance issues ;-) or i should say optimize. it runs fairly well. :)

@mitu it never seemed to kill the instance that I ran it from, but it did give ES a stroke, so I won't do it anymore :)

I guys are following the discussion :)
Whit my bad english it's already difficult to made an example........

Damn... when i made the video whit GB and CATRAP for the other my thread I could show you the example of this too :)

I also had to post the gamelist.xml but it just passed my mind ... really sorry ...

awesome

Thanks both.

This XML element is not mandatory, so it can be left out and it will evaluated to false if a theme checks this value. If it is there it has to be explicitly set 1 (or semantically equivalent) to be effective. This is why I perceive it as redundant and picked the term.

Never mind, let's keep the implementation as-is.

@2play also, please share your es_systems file here, debug logs, and while you're at it find other files with the same name on your system.

The link I shared earlier should help troubleshoot though.

Filed it nevertheless as it is useful if one does not have additional "safe shutdown hardware" or don't want to fiddle with triggerhappy.

@peppe_h

Run this from any platform folder on the RetroPie:

cat gamelist.xml | grep '<name>' | cut -d '>' -f2 | cut -d '<' -f1 > titles.txt

It will export all titles to titles.txt

Is the controller detected when RetroPie starts up ? Are you using the USB cable that came with the controller - does it work on a PC/other system ?

@samco as a fellow Guncon enthusiast I'd love to know your thoughts.

If you have a 4k TV, try setting the video resolution of your Raspberry Pi to 1080p - you can modify the /boot/config.txt file on the sdcard and set

hdmi_group=1 hdmi_mode=16

then reboot your Pi.

@h2805270 Wow, thanks for the B/W versions. Nice. I do like the rearrangement on the "Adventures" logo. And also thanks for appreciating my short writeup on the logo editing.

FWIW these are the fonts used (grepped from the accompanied README.txt in the initial post):

Font: Acknowledgement (SIL Open Font License v1.10)
Font: Amira Light, https://www.ffonts.net/Amira-Light.font
Font: BPdots Unicase Square by George Triantafyllakos
Font: FV Almelo (free personal)
Font: Nexa Rust Sans Black (free personal)
Font: Mallica Fairytale Demo (free for personal use only)
Font: Master of Break (free for personal use only)
Font: Nexa Rust Sans Black (free personal & commercial)

If someone needs the text as text logo versions (and before converted to path objects for final display) pls shout. Note that in some logos I did change the font-path afterwards.

Finally had more time to work on this. Tried generating the crash again. What’s weird is I get a blank log file when it crashes on boot. While I was looking at logs, I did some poking around.

Found and deleted a duplicate gamelist.xml under /opt/retropie for one of my systems from before I did my scraping. I thought I had cleaned those all out beforehand. The others are on the same drive as my game library.

I checked for and installed Retropie updates.

Not very scientific, I admit, so I regret if I’ve muddied the troubleshooting. That said, I’ve made progress. I’ve started getting errors about input devices:

“void InputManager::addJoystickByDeviceIndex(int): Assertion ‘joy’ failed.”

Assertion joy failed. You and me both, buddy!

Basically, it doesn’t seem to like that I have my 8BitDo dongle plugged in. I also have a couple of controllers paired directly with Bluetooth. Was trying different methods to see if one was more responsive than the other. Well, even with the Bluetooth controllers turned off, it seems like it is just enough to anger things during boot. Unplugging the dongle stopped the crashes. I just wait until after boot to plug in.

The only remaining thing that troubles me is why did it matter what theme I had before? Why did turning off favorites and last played collections help. That duplicate gamelist.xml may have mattered more than I thought.

Well, enough rambling from me. Hope this helps someone later on if they run into similar issues.

I've "solved" by keeping "pi" as login user and disabling password when doing sudo
thanks

@mitu Thank you so much for your help. I really appreciate it. I'm sorry ended up with some custom BS image, but at least I'll learn more by starting from scratch.

handshake.png

@rbezares I had this a couple of days back, somehow es had managed to remove it self, I refreshed the card and it happened again, although got slightly further in the boot as es did appear before crashing. I flashed a new image to a different micros and it has worked fine since so am putting it down to a bad card

try mupen64plus-gliden64. it should be the best performance and compatibility in general, but be warned that it's quite normal for n64 to exhibit poor performance on pi4, but several games can perform pretty well.

I tried uncommenting and changing the hdmi_group and hdmi_mode options in the config.txt, but no audio improvement.....just poor video!

from what to what? i suggest a 1080p60 mode in your config.txt (please provide copies of all configs you edit.). any further lowering of resolution you need to do can be done via the runcommand, although personally i leave everything at 1080p.

please also provide /opt/retropie/configs/n64/mupen64plus.cfg