Got it. I found the issue.

Using that CRT/HDMI video mode switcher added a two line statement to my \boot\config.txt that wasn't there before.

framebuffer_height=1920
framebuffer_width=1080

Not sure why it added this, but as soon as I commented and rebooted, my RetroPie core was back to normal size and not shrunken anymore.

I don't have many statements active in my config.txt so I noticed an extra "list" of other video related stuff at the very bottom. It seemed to have duplicated some of the entries that are in sections above and placed them in the last [all] section of the file. I commented it all out so none of it is active.

framebuffer_height=1920
framebuffer_width=1080
disable_overscan=0
hdmi_force_hotplug=1
enable_tvout=0
hdmi_group=2
hdmi_mode=82

@code_dredd said in Issues when mounting more than just ROMs over NFS:

It seems NFSv3 didn't really fix the issue and ran into others (e.g., weird user IDs on remapping). I've gone back to NFSv4 and increased the number of NFS servers/processes from the default of 4 up to 5 to see if that helps.

It didn't help.

@questionmark said in Splashscreen images not displaying | omxiv erroring out:

So will this cause performance to dip?

No, it will not.

@obadiahjack

I ended up figuring out a round about solution, more details on this reddit thread for those looking:

https://www.reddit.com/r/RetroPie/comments/l51c9g/playing_video_before_shutdown/

My roundabout solution:

As discussed with reddit user u/ben_theredonit, the pi4 fails to utilize the emulationstation.sh at the time of posting when shutting down. So editing emulationstation.sh, will not work to play a video before shut down. I solved the problem through a roundabout solution. I found a shutdown button that can be added via the carousel, developed by Steve Smith. Below is his video and in his YouTube description, his files:

The user Lampros in the youtube comments has a guide to install, if you find yourself getting the permission denied error, as many people in the comments have, I fixed mine by simply typing "sudo" in front of the "chmod +x" command

From there, I simply changed the 'rom' shutdown script adding the "sudo omxplayer RetroPie/roms/shutdown/shutdown.mp4" code and it worked.

Big thanks to reddit user u/ben_theredonit, who offered their help.

I hope this helps anyone that was lost as I was when trying to add a shutdown video.

This one's my favourite at the moment:

I recommend you post your splash screen here:

https://retropie.org.uk/forum/topic/29132/splash-screen-ideas-discussion

I recommend you post your splash screen here:

https://retropie.org.uk/forum/topic/29132/splash-screen-ideas-discussion

@mitu thanks, I've edited my post to just leave the systems I'm having trouble with. They all point to the 'parent' system.

EDIT: I changed the name for naomi from dreamcast and it's working.. So problem solved. Thanks for pointing me in the right direction.

I recommend you post your splash screen here:

https://retropie.org.uk/forum/topic/29132/splash-screen-ideas-discussion

@sterpa up...thanks

@huhogany Hi. where do i even find that line /opt/retropie....etc, etc? I am so lost and confused. Do I look for it on pc or use the pi4 gui screen? i have no idea where to find this. Is it a command line?

UPDATE: I got it to work. What I did...

Updated post fixes in vman 512 image... reboot
options
system tools
audio settings
set audio output to headphones

@BuZz editing /opt/retropie/configs/all/runcommand.cfg did the trick, thankyou! :-)

@mitu not until now, let's see if it works!

Either that or just disable the video - what good is a 5 seconds video ?

SOLVED

All I had to do was delete my recently uploaded splash screens through samba and reboot.. I guess you need to save video splash screen files a certain (unknown) way before you transfer

Most likely the USB stick is not 'mounted' (therefore inaccessible) when the splashscreen starts, so the video cannot be read and the splashscreen fails. Copying it to /opt/retropi.. will copy the splashscreen on the SD card, which is immediately available on boot.

@kristjan1111 As other services started on boot, the splashscreen has to wait until the system is minimally start before it can start. Since the splashscreen image/videos are on your local disk, there's nothing that can be done before the disk check is complete.
I remember that there was a bug on RPI's related to fake-hwclock that would make the disk check trigger every boot - https://www.raspberrypi.org/forums/viewtopic.php?t=198937&start=25 - so try to run a system update and see if it fixes the long boot time.

its a bug ... after each update, you will need to go to the spashscreen settings and make sure to change them to whatever it was already set to and the problem will be solved.