Strange Request...But Can I Get Rid of Grid View?

mitu

@alphabetapie The memory split is the amount of video memory you're allocating to the GPU from the total RAM available on a Pi. The more you allocate, the less it remains for the system to use.
On memory constrained systems, like the Pi Zero or Pi 1, you shouldn't allocate too much, but on a Pi 4, which can have more than 1 Gb of RAM, you could allocate a larger portion (not more than 512, since it's not going to be used).

RetroPie configures a 256Gb for the Pi 3 and later models, you could increase the VRAM to 180 for EmulationStation if you have a memory intensive theme.

AlphaBetaPie

@mitu said in Strange Request...But Can I Get Rid of Grid View?:

@alphabetapie The memory split is the amount of video memory you're allocating to the GPU from the total RAM available on a Pi. The more you allocate, the less it remains for the system to use.
On memory constrained systems, like the Pi Zero or Pi 1, you shouldn't allocate too much, but on a Pi 4, which can have more than 1 Gb of RAM, you could allocate a larger portion (not more than 512, since it's not going to be used).

RetroPie configures a 256Gb for the Pi 3 and later models, you could increase the VRAM to 180 for EmulationStation if you have a memory intensive theme.

Thanks for the info. I did some testing last night, moving the vram slider. Anything under 200 and I still had menu load issues (the theme I'm using has 1080p upgrades I added and is pretty graphic intensive). When I hit around 260, things cleared up. So I just upped the slider to half of the global value and left it (to give me some headroom). That seems to have worked.

However, I did noticed that my GPU setting in my advanced config was set to only 64 by default. I've read (and as you mentioned above), the sweet spot is around 256. Should I up that? If so, what kind of benefit can I expect to receive from it? I'm a proponent in not messing with default values unnecessarily. But if there is a chance it could make things run smoother by increasing it to 256, then I'd want to do it.

mitu

@alphabetapie said in Strange Request...But Can I Get Rid of Grid View?:

However, I did noticed that my GPU setting in my advanced config was set to only 64 by default.

Post your /boot/config.txt file.

AlphaBetaPie

@mitu said in Strange Request...But Can I Get Rid of Grid View?:

@alphabetapie said in Strange Request...But Can I Get Rid of Grid View?:

However, I did noticed that my GPU setting in my advanced config was set to only 64 by default.

Post your /boot/config.txt file.

Sure, here you go (copy/pasted since I don't see a file attachment option anywhere):

# For more options and information see
# http://rpf.io/configtxt
# Some settings may impact device functionality. See link above for details

# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
hdmi_group=1
hdmi_mode=16

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

# Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on

# Uncomment this to enable infrared communication.
#dtoverlay=gpio-ir,gpio_pin=17
#dtoverlay=gpio-ir-tx,gpio_pin=18

# Additional overlays and parameters are documented /boot/overlays/README

# Enable audio (loads snd_bcm2835)
dtparam=audio=on

[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3d
max_framebuffers=2

[all]
#dtoverlay=vc4-fkms-v3d
#overscan_scale=1
disable_splash=1

mitu

That's strange, on the Pi3 models the GPU memory is set by RetroPie on the image. Are you using a Pi3B - ~~as your signature says~~ - or is this from a Pi 4 ?

AlphaBetaPie

@mitu said in Strange Request...But Can I Get Rid of Grid View?:

That's strange, on the Pi3 models the GPU memory is set by RetroPie on the image. Are you using a Pi3B - ~~as your signature says~~ - or is this from a Pi 4 ?

Just upgraded to a Pi 4 on this last build and used the latest image from the website about a month ago. So if 64 is the default, what gain would I get by upping it to 256 (if any)? Does that sort of thing cause problems sometimes? I'm looking for the most bang for my buck power wise to push my emulation, but I don't wanna open a can of worms down the line regarding performance problems.

mitu

@alphabetapie If you have a Pi4, then you don't need to set the memory in config.txt. Just adjust the VRAM as you need for the theme.

AlphaBetaPie

@mitu said in Strange Request...But Can I Get Rid of Grid View?:

@alphabetapie If you have a Pi4, then you don't need to set the memory in config.txt. Just adjust the VRAM as you need for the theme.

Ah, perfect! Well I've already done that. Although, that does pose a question I should probably also ask. I found that upping my VRAM to just 120-130 (as suggested in other threads), simply didn't do the trick for me. And I had to keep going until I hit around 260mb to get all the menus loading smooth. The global max value is 1,000MB. So I just set on a nice round, middle of the road number of 500MB. Could this cause any performance issues setting it this high? Perhaps when actually launching the emulation? Since I'm on a Pi 4, what's to stop me from just maxing out the VRAM value? Would I see any adverse affects?

mitu

@alphabetapie said in Strange Request...But Can I Get Rid of Grid View?:

Could this cause any performance issues setting it this high? Perhaps when actually launching the emulation? Since I'm on a Pi 4, what's to stop me from just maxing out the VRAM value? Would I see any adverse affects?

I don't think that 500 would be much different than 256 and frankly anything above 512 will be ignored by the Pi (no matter what RAM you have).

AlphaBetaPie

@mitu said in Strange Request...But Can I Get Rid of Grid View?:

@alphabetapie said in Strange Request...But Can I Get Rid of Grid View?:

Could this cause any performance issues setting it this high? Perhaps when actually launching the emulation? Since I'm on a Pi 4, what's to stop me from just maxing out the VRAM value? Would I see any adverse affects?

I don't think that 500 would be much different than 256 and frankly anything above 512 will be ignored by the Pi (no matter what RAM you have).

Makes sense. Thanks for the info. Now...one final, final question (since this is related and I'd rather not make another thread).

I've noticed that the framebuffer_width=1280 and framebuffer_height=720 values seem to point to a 720p setup. All my graphics I run in my custom theme are 1080p (1920x1080). Is this value somehow limiting performance, and should I change it to match the resolution I'm running? I also have this set in my video mode as well to full HD. Or is not relevant or could cause performance hiccups by bumping it up?

mitu

@alphabetapie those options don't affect the Pi4.

AlphaBetaPie

@mitu said in Strange Request...But Can I Get Rid of Grid View?:

@alphabetapie those options don't affect the Pi4.

Thank you kindly, much appreciated as always. Having said that, if someone with a Pi 3 wanted to run this custom theme (if I were to give it to them), should they bump these ups?