@mitu I ran an update last night and the issue of the in-game menu causing the controller to become unresponsive until the select button is pressed has been fixed. I can now pull up the menu, take screenshots, save states, and return to the game without any problems.

The issue with running the setup from within the RetroPie OS still remains. The workaround is to sudo ./retropie_setup.sh from the terminal.

Pi Model or other hardware: 3 B
Power Supply used: inland 5.25V 2.4A Micro USB
RetroPie Version Used (eg 3.6, 3.8.1, 4.1 - do not write latest): I think 4.1?
Built From: Standard; haven't added any images or anything like that
USB Devices connected: Button converted to usb, keyboard
Controller used: none (unless you cant the button and joystick)
Error messages received: no error message, the screen just looks off
Verbose log (if relevant): idk what this means
Guide used: (Mention if you followed a guide): am following and using the parts from this youtube video:

Also looked up how to screen tilt (did the screen rotate 3) and remove black bar (took out the # in that code)
File: Don't think a file is the error, as it works fine on my monitor but not the arcade1up
Emulator: (Name of emulator - if applicable) using the retropi with atari and nintendo
Attachment of config files: don't think its a files issue as per the reason above
How to replicate the problem: to replicate the problem use one of the machines with a vertical screen (Ms. Pacman, for example) and use the parts that are listed in the youtube video: HDMI LCD Controller Board: https://amzn.to/2QlKKfr , Arcade Sticks Buttons and Encoders: https://amzn.to/2ItwRt5 , Pi 3 B

It turns out that md_lbl and md_ need to have seperate size values for the "X" for some reason... it seems to be fixed now:
57d9a835-5fcf-4668-bbba-8de3854b4899-image.png

By the way, I found the solution of this problem. You must edit ~/.config/eduke32/eduke32.cfg. You must use there ScreenMode = 0, ScreenHeight = 576 and ScreenWidth = 720 (you can play with ScreenHeight and ScreenWidth to fit the picture to the screen).

@technogeek69 sound like you have some sort of frame skip on where the games are running at 30fps vs 60. But we need to know your setup to help guide you to a solution.

@pamput Yes it does indeed appear to be fixed now

@mitu It works now. Thanks alot!

Found a solution:

720 Degrees (revision 4) on lr-mame2003 (I think I unzipped 720 and 720 rev 4, merged the contents then rezipped as 720.zip).

Paperboy (revision 3) also on lr-mame2003.

Both work very nicely now, with no nasty tearing/glitching effects.

You could move the save file to your PC, go passed the broken area and then put the save back on the Pi.

@greenhawk84 It should be fixed in my last commit.

@joabro One possibility: usually ROMs are either European or American, and these regions have different video systems compatible with the TVs of their respective markets. The former games are PAL 50Hz, meaning they refresh at 50fps. The later are NTSC 60Hz and refresh at 60fps, running slightly faster. So one possibility is that if you are from an European country and are loading a set of US ROMs, you may have this perception that it’s all a bit too fast (and they are, indeed, faster than you remember). If that’s the case, I’d say stick to them as this is how the games are meant to be played. People prefer US ROMs even in Europe, so much so that even Nintendo have loaded their European mini consoles with American versions of their games.

also, to ensure that none of my changes have affected this, i just tried a default, no rom, freshly downloaded install. still the exact same results.

Super Metroid (especially noticeable at title screen) I still notice this as well. Trying to figure it out. It also happens on my FPGA SNES so it might be an HDMI issue.

@AlexMurphy yes, thank you! I've changed the core emulator to something something genesis and now it isbfully working. So happy 😊

@mediamogul yeah I just did, and still the same. I even tried copying the love files over from another install and still the same. I will have to test love on that Pi later to see if it's the same, but last time I tried it wasn't.