@cdaters These ES CLI switches may come in handy:

--force-kiosk: Volatile setting of Kiosk Mode when UI is set to Full mode.
--force-disable-filters: Disable Kiosk (and/or Kid) mode when UI mode is set to Kiosk (resp. Kid). Attn: This switch will be persisted if any change is made in the Settings via ES UI, otherwise it is volatile.

@pjft said in [ES-dev Bug Report] "Hidden" filter fails at system level after entering a subfolder and returning:

@roslof Well, check fps as well

I can create a new thread if desired, since this work is a bit off topic -- but for now, here we go:

First off, my theme is heavy, leveraging (among other things) one large 1160x1080 .jpg per system, and using roughly 80-90 systems.

VRAM LIMIT is set to 200Mb

I ran through the flow again (UI MODE from FULL --> KIOSK --> FULL) using the ES flow, and there is definitely a major performance hit during and after each subsequent load for the duration of the session.

Most notable side affects:

Load times increase dramatically Navigation through the systems UI* eventually becomes uncontrollable, as the system continues to move through games, and player input is ignored FPS tanks during step #2 above

At idle, ES reports Tex Max increases dramatically:

At Boot: 626.99 After two (2) Swaps: 930.43

All other stats remain the same after swaps.

Also, at idle, using htop, some stats increase:

VIRT: 899M --> 937M RES: 653M --> 687M CPU: 25.7% --> 32.2% MEM: 38.6% --> 40.6%

However, when hitting F4 to exit ES, then typing "exit" at console to re-launch ES, everything going back to original values. I believe using QUIT | RESTART EMULATIONSTATION also clears the performance problem.

Lastly, an early check indicates a similar, if not identical issue when switching ES Themes back and forth.

Again, hope this information is helpful.

@retroguy said in Shortcut Commands for game list:

I'd rather just push a key and change the metadata value for hidden.

There's no action for that implemented. Either edit as you're doing now or edit the gamelist.xml file directly and add the hidden tag there.

@doctorbeefy said in Majority of screen hidden when launching game:

Bumping this as I am having the same issue. Anyone come across a fix? it seems to only happen for Sega Mastersystem/genesis and lr-genesis-plus-gx, other systems and cores work fine.

For most people, this glitch is something that originates in RetroArch and needs a fix. A future release of RA will probably take care of it. In the meantime here is a workaround:

After the game starts and you see this happen, use (Hotkey + "B") to reset the ROM. It should come back with the whole screen visible.

@tackett1980 I don't think such option exist, well at least if it does it would be something like the scrapers can do. Maybe the scraping program called Skraper can help you. That is the one i use for scraping roms. It collects data from screenscraper.fr scraping database.

Otherwise i don't know any other options, but maybe someone else here does.

@mitu Hey thank you for the update. :-) Next time I update my RetroPie, I will check it out.

I use to set bios roms as “hidden” (you can do this in that page containing each file info: name, producer, cover path, year of release, and so on...)
you will still see hidden files in “normal” use, so I switch to kiosk mode (where hidden files are not shown)
when have to do some modification or trick, I easy switch back to “normal” mode by a short controller combo password (default is up up down down left right left right A B) and then when done switch back again to kiosk mode.
this way everything works great, and I am also sure that casual users (friends, or my kids too) can’t mess up with my system (kiosk mode disables almost all configuration switch and options)

The author of the game, Chris Murray, was 16 when he programmed Henry’s House.

@mrdowntempo no problem. Just remember one thing, linux is case sensitive so caps and lowercase are important. Even though if you are inside dosbox and you want to run say WOLF.EXE you can type wolf or wolf.exe, when you do it in a .sh file, even though it actually runs the commands inside of dosbox you have to have it say WOLF.EXE.

However, if you do it in a .conf file it doesnt matter.