Hi, I managed to fix it by updating kernel and fallowing your instructions. Thanks.
I do not know how system updated to latest version of firmware. I pretty much did nothing. My Raspberry pi was offline for
pretty long time (for few months, playing retro games don't really requires internet) and this happened first time I rebooted it after connecting to Internet.
@meleu said in Useful topics/posts index:
pay attention at the bottom of the screen, you should note something saying Enter tags here, between 3 and 15 characters each.
Thanks! Found it.
Grey font on a white background on something that does not resemble a text input field in the slightest. Nice troll.
@M0dd3r4t0R said in Creating Save States with a Single Button Press:
BUT - with the hotkey now in the "nul" state, I am not able to perform the exit command through <start> + <select(hotkey)> button presses. Am I missing something?
Yes, you're missing the Hotkey. Once you've un-set it, no hotkey combination will work - pressing only Start should exit the game.
I solved my own problem! I modified the EmulationStation startup script to toggle back and forth between horizontal and vertical mode on a restart. So, now I can rotate my monitor, restart EmulationStation, and my menus match the orientation. Here is the updated file:
while true; do
rm -f /tmp/es-restart /tmp/es-sysrestart /tmp/es-shutdown
"$esdir/emulationstation" "$@" $rotate
if [ -f /tmp/es-restart ]; then
if [ -z "$rotate" ]
if [ -f /tmp/es-sysrestart ]; then
rm -f /tmp/es-sysrestart
if [ -f /tmp/es-shutdown ]; then
rm -f /tmp/es-shutdown
@Quackwalks said in Brutal Doom on Pi4 With Gamepad Controls in Menu?:
@psyke83 wow that is way simpler! I was waiting for someone with more know how to simplify things. Thanks.
Glad to help.
Keep in mind that the lzdoom-addon method also works with Sigil -- but you'd have to ensure that brutal doom is not in the addon folder, as it would try to load all three wads together and likely fail.
I added the -addon feature as a generic means of playing any kind of addon wads, but if you want to have a permanent dedicated launcher for Sigil, you could do this:
go to roms/portsand copy Doom.sh to Sigil.sh
edit configs/ports/doom/emulators.cfg, and create a copy of the lzdoom-addon port with a new name (such as lzdoom-sigil) and change /addon/* to /sigil/*.
create a new sigilfolder in roms/ports/doom/, and put the sigil wad in this new folder.
when launching Sigil for the first time, change the "default emulator for this ROM" to use the lzdoom-sigil entry.
Technically you could do something similar to have dedicated Brutal Doom launchers, but this would require a lot of duplication, as the Brutal Doom wad is designed to be compatible with Doom1, Doom2, Ultimate Doom and even Freedoom. It make sense to me to just switch via runcommand when you want the Brutal versions...
Game: Beastorizer (beastrzr.zip)
Test: Watch full intro or play game
Default Framerate: 55-57 FPS
CPU Change: Decrease to 70%
New Framerate: Between 59.8 and 60 FPS (blip of 53FPS during 3D to 2D transition)
Summary: Very good improvement. No noticeable decrease in gameplay speed.
@challenger2010 could be the ROMs aren't the correct ones for Mame2003. Mame/arcade is insanely fiddly with ROMs. Can you get those ROMs working on retroarch on your laptop/pc? That's always my trick.
Also double check it's not a bigger problem and stick a Gameboy or SNES rom and test one of them.
Update: I've been poking at the source code of lr-fceumm and found part of my hiccup:
#define NES_WIDTH 256
#define NES_HEIGHT 240
#define NES_8_7_PAR ((width * (8.0 / 7.0)) / height)
#define NES_4_3 ((width / (height * (256.0 / 240.0))) * 4.0 / 3.0)
so the core options for 8:7 PAR is calculating from a hard coded 16:15 ratio and going from there, the settings under video settings are calculating differently (the 1:1 PAR was coming back as 8:7 DAR when selected).
Okay so finished the game just now. Nothing really slows it down much, you just encounter a few crashes during gameplay. But it's doable with a couple of other tricks:-
The Blue Dragon Fast Travel causes a crash. So save state, switch to another plugin, use it then save and go back to Rice.
Also I discovered loading the World Map at any time will crash (Start then Z Button)
The second Impact boss (the big Fish Robot). Right before the fight starts Rice crashes back to emulationstation. So save there and switch to GLideN64 for the fight. It works ok in this Impact battle compared to normal gameplay.
For the final boss the sound gets a bit messed up but it is fine in Rice, you don't need to switch to GlideN64 (it seems to play terribly in that plugin)
Oh and the credits crashed in Rice ha! Typical, you get right to the end of the game and the emulator crashes! But again, just make a save state and switch to GLideN64 if you want to see all the credits.
I didn't collect all the Fortune Cats so no idea if the Boss Rush mode works or whatever.
All in, for a big fan of the game it's worth playing; you don't encounter these crashes for a fair bit of gameplay anyway. Good Luck!
How did you get brutal doom to work with lzdoom, if you don't mind me asking ? Or is there a page you could link with instructions? I swear I've been googling and working on this for hours and I just can't understand what to do. I had brutal doom, sigil, all that working fine on zdoom on the Pi 3, but with lzdoom and the Pi 4 it's just not making sense to me. Thanks in advance for any help you can give.
My guess this happens because you specifically set the resolution somewhere - either in /boot/config.txt, or in each individual RetroArch core.
EmulationStation and emulators (including RetroArch) should pick up the current resolution and run in fullscreen, without the need to set the resolution.
More specifically, when I went into the
/opt/retropie/configs/all/retroarch/autoconfig/DragonRise Inc. Generic USB Joystick .cfg file
/opt/retropie/configs/all/retroarch/autoconfig/DragonRise Inc. Generic USB Joystick .cfg.bak file
and replaced their contents ""Not a file: /opt/retropie/configs/all/retroarch/autoconfig/DragonRise Inc. Generic USB Joystick .cfg.bak" with
input_r_y_minus_btn = "11"
input_l_btn = "13"
input_r_y_plus_btn = "10"
input_up_btn = "3"
input_left_btn = "1"
input_r_x_minus_btn = "9"
input_l_y_plus_axis = "+1"
input_l_x_plus_axis = "+0"
input_right_btn = "0"
input_l2_btn = "5"
input_l_x_minus_axis = "-0"
input_r_x_plus_btn = "8"
input_r_btn = "12"
input_l_y_minus_axis = "-1"
input_y_btn = "6"
input_down_btn = "2"
input_start_btn = "4"
input_b_btn = "7"
input_a_btn = "6"
when I launched the game, (as soon as I launched Super Mario 64, when it says "press A to change settings" the system did not respond to the N64 usb controller at all.
Not sure what the problem is; if I need to format the instructions differently or do something else. If anyone has any suggestions I would apprecaite hearing them. Thanks!
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.