ARpiCADE Forums

SOME games in NAOMI seem to have a slight sync issue with my monitor at the top. I get a curl for about 1 inches from the top down. It only appears in SOME of the NAOMI games... not all. Probably 40% or so of them. Are those (perhaps) PAL rips of the game creating that curl? Any way to get rid of it?

TAB in game then SLIDER OPTIONS, either the H or V size depending on monitor mounting position. Go down from the 1.000. Ive gone as low as 800 on some games, also Ive noticed under VIDEO OPTIONS you can turn things on/off (ie keep aspect ratio). Give those a try.

It is very likely to be related to the resolution, probably requireing fine tuning of the modeline behind it. Do you have Naomi running in 480i or 240p? (or a mix, if so which is the issue?).

I do not think it will be the emulator or the rom directly. But I'm very happy to try and improve it, need to relook at the res switching sometime anyway...

I imagine it very well could be a situation of one mode being in a 240px and the other in 480ix ... I'll try to determine. I'm running NAOMI in a cabinet with 480i enabled. Maybe I should disable 480i just to see what happens...

There really are only two games affected that I'd play much ... Marvel v Capcom 2 and Gigawing 2...

I suspect it is the 240p mode Naomi is using. I just checked it and it def curls on my PVM. I think (without checking) its @61hz or something to match the original 480p Naomi signal... if I can't dial out the curl via the modeline I can prob just use a slightly slower refresh rate for Naomi (one that doesn't curl, obviously).

In the middle of other bits at the moment, if I don't seem to get to it remind me.

edit /boot/[firmware]/launchers/naomi.sh and find this bit:

if [ $(contains "${use240p[@]}" "$1") == "y" ]; then
/boot/firmware/launchers/resSwitch.sh
else

change it to:

if [ $(contains "${use240p[@]}" "$1") == "y" ]; then
/boot/firmware/launchers/resSwitch.sh 240p
else

and enjoy your Naomi in 240p goodness without curl.

Unfortunately... mine already had that line. This is how it looked (pre-edit)...

#check boot resolution and monitor mounting
origres=`xrandr --current | grep "\*" | grep -E '^.{0,8}x.{0,5}' -o`
# change res and or get info
# flycast seems to run at 60 hz rather than Naomi exact
if [ $(contains "${use240p[@]}" "$1") == "y" ]; then
/boot/firmware/launchers/resSwitch.sh 240p
else
/boot/firmware/launchers/resSwitch.sh $1


The "240p" portion was already there.

EDIT: BUT WAIT! The naomi.sh on the windows drive... BOOT\LAUNCHERS\NAOMI.SH did NOT have that 240p added. I just added it and will test now.

Which set of launchers is being used? BOOT or the Linux drive set? Or both? If not BOTH can I clean up a little and delete the non-working folder to prevent confusion?

EDIT #2: Unfortunately... adding 240p to the launcher on the BOOT drive did not make a difference.

FrizzleFried wrote: ↑

Thu Mar 13, 2025 8:21 pm

Which set of launchers is being used? BOOT or the Linux drive set? Or both? If not BOTH can I clean up a little and delete the non-working folder to prevent confusion?

There should only be one set of launchers... /boot/launchers/ (or on a running pi with more current software: /boot/firmware/launchers/ - important note, this is the same exact folder, just mounted a bit differently when it is on the pi)

Where is the other set of launchers? I will have to investigate that, must have left some older files somewhere or something...

No idea why you have the 240p edit already... I may have done this previously and lost it myself in a backup restore... occationally I loose a feature between backups by forgetting to redo it. If it's not working for you, make sure the games you wan to run in 240p are also in the use240p array in naomi.sh eg.

use240p=("ausfache" "azumanga" "capsnk" "cvs2mf" "dolphin" "fotns" "ggx" "ggx15" "ggxxac" "gwing2" "kofnw" "kofxi" "kov7sprt" "mbaa" "meltybld" "mslug6" "mvsc2" "sfz3ugd")

Will test adding the rom name.

I have a launchers folder:

• BOOT/LAUNCHERS (Windows FAT32 folder)
• BOOT/FIRMWARE/LAUNCHERS (Linyx folder accessible by Paragon) (to be 100% accurate it's actually BOOT/FIRMWARE.BAK/LAUNCHERS)

FrizzleFried wrote: ↑

Thu Mar 13, 2025 11:58 pm

Will test adding the rom name.

I have a launchers folder:

• BOOT/LAUNCHERS (Windows FAT32 folder)
• BOOT/FIRMWARE/LAUNCHERS (Linyx folder accessible by Paragon) (to be 100% accurate it's actually BOOT/FIRMWARE.BAK/LAUNCHERS)

BOOT/LAUNCHERS (Windows FAT32 folder) is actually mounted as /boot/firmware/launchers (on the running Pi). They are one and the same, it's just a change in how RaspiOS works (admittedly a confusing one) - not anything I've done.

firmware.bak is backup, either created when making the initramfs or something I've done very early in the process and forgotten about... either way you can just ignore it.