ARpiCADE 3.X (that's a ten, I thought 10 may be confusing...)

[jeffamay]

I was finally able to get everything(i thought) up and going. I have had some issues copying some of the mp4 files from the old system to the new SD card with 3.X installed. I just bypassed that as assuming it was not a big deal since just previews of the games. But with that said I have now got it running and noticing that several games, Moon Patrol, Bad Dudes, etc are giving me Input Not Support when I try and launch them. Not sure what is going on since this is a new card and just copied over the ROMs, some games are working without issue. Any help on this error would be greatly appreciated. I know they at least worked on the old system before I had some issues with that card, as I am a big Moon Patrol player and played it all the time without issue. Thanks.

[dee2eR]

not sure what is going on there. What emulator are the offending games in?

[skeletroll]

Hey all.

I can't get my arpicade running 3.X to sync for the life of me. The tv of choice is a PVM 8044Q. It doesnt do 480i. I've looked at settings files from all over the interent and the resulting images from trying them out are always garbled junk no matter what I do.

This is my config.txt. I'm at my wits end. What am I doing wrong here? Raspi model 3 btw. Just trying to see the title screens and main menu clearly before I even get to roms.

Code: Select all

# For more options and information see
# http://www.raspberrypi.org/documentation/configuration/config-txt.md
# Some settings may impact device functionality. See link above for details

# disable Rpi rainbow splash
disable_splash=1

# Comment/uncommment to flip the image to account for monitor mounting 
# this is a 180 degree flip NOT hori/vert mounting
# (see bottom of file for horizontal/vertical mount option)
#display_rotate=2

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

# make sure the pi outputs to correct scanlines without overscan
# use this even when playing with overscan settings for best results
# on CRT monitors always use this setting
disable_overscan=1
overscan_scale=1

# uncomment the following to adjust overscan / picture position. Use positive 
# numbers if console goes off screen, and negative if there is too much border
# also use overscan_scale so the emulators comply & still use disable_overscan
# do not adjust top and bottom or you will loose scanline perfect output although
# you can move the picture up or down evenly with okay-ish results better not to
overscan_left=33
overscan_right=70
##overscan_top=4
##overscan_bottom=-4

# ignore edid - we just want video output to do as we say anyway
hdmi_ignore_edid=0xa5000080

# force hdmi output
hdmi_force_hotplug=1

# uncomment to force a HDMI mode rather than DVI so audio works
hdmi_drive=2

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

# use full spectrum RGB over HDMI
hdmi_pixel_encoding=2

## PLEASE NOTE: due to the resolution switching launcher scripts changes made
## in this section are at your own risk, 480i is default for this build
# Use group 1, only change the mode.  For Group 1 Mode 8 is 720x240, 
# Mode 6 is 720x480i & Mode 1 is 640x480p.  Any mode except 1, 6 and 8
# may have unexpected behaviour (see /boot/launchers/resSwitch.sh)
hdmi_group=1
## Use only one mode at a time
# Boot and menus in 480i (rotated games in 480i, non rotated games in 240p/256p/288p)
#hdmi_mode=6
# Boot and menus in 240p (all games in 240p/256p/288p)
hdmi_mode=8
# Boot and menus in 480p (no res switching, just 480p)
#hdmi_mode=1

# Increase gpu mem for complex Attract-Mode themes to work properly
gpu_mem=256
#gpu_mem=128

# Uncomment to overclock RPi2
#arm_freq=1000
#sdram_freq=500
#core_freq=500
#over_voltage=2
#temp_limit=80 #Will throttle to default clock speed if hit.

# Experimental RPi3 overclocking - reported stable, you may want a heatsink
# the 1A fuse on a RaspberryJAMMA can be safely upgraded to a 2.5A fuse for RPi3
# and probably should be for overclocking
#arm_freq=1350
#over_voltage=4
#sdram_freq=550
#core_freq=550
#gpu_freq=550
#temp_limit=80 #Will throttle to default clock speed if hit.

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

# Enable 4 player adaptor over i2c
#dtparam=i2c_arm=on

# Additional overlays and parameters are documented /boot/overlays/README
# Experimental keyboard based JAMMA controls - no working hotkeys system currently
#dtoverlay=raspberryjamma

# I need to test these
#disable wifi
#dtoverlay=pi3-disable-wifi
#disable bluetooth
#pi3-disable-bt

# Depreciated settings for ARpiCADE do not unhash these settings to use them
# Really, DO NOT UNHASH THESE SETTINGS they are not RPi boot settings and need to 
# be hashed out exactly as is to work properly.
# to set vertically mounted monitor create an empty text file in /boot called vert.txt
# or just use the service menu, don't use the old depreciated line below
#monitor_mount=

[dee2eR]

how is the pi hooked up to the PVM?

[Sdscribe]

Hi,

I recently moved from 3.84 to 3.X.1. As I'm sorting out the new tweaks, two questions regarding the shifting refresh rates come to mind.

1. Can the repetitive shifting of different refresh rates as we move through different games negativity impact the CRT in terms of lifespan or quality?

2. There seems to be a consistent audio pop that emits from the cabinet when exiting Attract Mode and entering games. Could this be indicative of anything negative occurring with the DAC?

Thanks!

[dee2eR]

@Sdscribe
1. not to the best of my knowledge (assuming you don't switch to an unsuitable res/refresh). While you (probably) wouldn't switch original game boards as often as you can change game on a emulator setup it's not really any different to the monitor. Some arcade games and consoles used to switch between 480i and 240p too, eg. MegaDrive/Genesis Sonic 2 is generally 240p but uses 480i for the 2 player mode and possibly the menus (I can't remember offhand).

2. I don't hear it on my test bench setup (may be my tiny speaker or it's specs or a volume level difference...) but it sounds like it could be caused by the DAC resetting when the resolution switches - I get a similar (at least I think it maybe similar to what you're describing) pop through my desk speakers if I reset my PCs DAC while the speakers are powered up. If it is just the DAC resetting it's perfectly normal for the DAC as the HDMI signal cuts out breifly before starting up again in the new res.

[canussie]

I have recently upgraded my Pi 3 powered cabinet to ARpiCADE 3.x.1.

Initially I have thrown a few games on such as Donkey Kong, Burger Time, Pacman, 1941/42.. they all work nicely. I was able to copy over my old hiscores etc.

The problems began when I tried to get NBA JAM and NBA JAM TE running. I have tried it on all of the mame versions but the same thing happens, when I launch the game the screen will go black, then I get the NO SIGNAL message on my monitor (VGA via a HDMI->VGA adapter). I think it must be something to do with the res switch script? Any hints?

[dee2eR]

Sounds like you might have the board running in low res mode. The default settings load in 480i and switch to 240p (or another progressive low resolution) when you load a game.

Assuming your monitor is horizontal mounted, the games you listed that worked wouldn't have swapped res as they're rotated games and use 480i for more screen real estate.

Editing config.txt to use hdmi group 1 & mode 1 (480p highres mode) should fix all your issues, if I'm not mistaken. Hope that helps.

[canussie]

Thanks for the quick response; here is the relevant part of my config.txt, I think that is already configured as you suggested:

Its in a cocktail cabinet, so i have it load attract in horizontal and games such of Donkey Kong and Pacman rotate the screen but games like NBA JAM are horizontal.

Snip from my /boot/config.txt

Code: Select all

## PLEASE NOTE: due to the resolution switching launcher scripts changes made
## in this section are at your own risk and may have unexpected behaviour
## (see /boot/launchers/resSwitch.sh)
## High res setting
# Boot and menus in 480p (no res switching, just 480p)
hdmi_group=1
hdmi_mode=1

## Low res settings - use only one, either 240p or 480i
# 1920x240p@60 - 240p, 250p and 288p only
#hdmi_timings=1920 1 52 208 260 240 1 6 10 6 0 0 0 60 0 38400000 1
# Boots in 960x480i - uses240p etc for games
hdmi_timings=1920 1 48 192 240 480 1 6 3 16 0 0 2 60 1 37560000 1
# either low res setting needs the next two lines
hdmi_group=1
hdmi_mode=1

Is the hdmi_timings correct?

[dee2eR]

comment out the hdmi timings line with a "#" in front of the line, it isn't needed for high res.

Also you have the hdmi mode and group settings in there twice, both the same. Shouldn't hurt anything but figured I'd mention it.