Forum Replies Created
- trixsterParticipant03/24/2016 at 22:59Post count: 76trixsterParticipant03/24/2016 at 21:51Post count: 76trixsterParticipant03/16/2016 at 21:23Post count: 76
It is possible to do it right now with uae4arm but it requires you to setup a relatively complicated workbench with whdload installed which has been set up with winuae. This can then run whdload cd32 versions of games directly from workbench. You could even fully emulate cd32 cd images with something like Idefix but that’s well beyond the scope of RetroPie.trixsterParticipant03/16/2016 at 17:37Post count: 76trixsterParticipant03/15/2016 at 23:34Post count: 76trixsterParticipant03/15/2016 at 23:20Post count: 76trixsterParticipant03/15/2016 at 21:17Post count: 76trixsterParticipant03/13/2016 at 19:06Post count: 76
I think it’s a memory issue. It turns out that I was actually using only 256mb for the gpu, not 320 as I thought. Bumping it up to 320 allows quake 3 to run. Mario kart and zelda will now run too. Goldeneye still freezes on the intro so perhaps more memory is required. I counted that I have over 20 systems now running in Emulationstation so perhaps that’s why a 256mb and even a 320mb split is not quite enough…trixsterParticipant03/06/2016 at 18:19Post count: 76trixsterParticipant02/26/2016 at 16:53Post count: 76trixsterParticipant02/22/2016 at 21:34Post count: 76trixsterParticipant02/21/2016 at 23:57Post count: 76trixsterParticipant02/21/2016 at 15:46Post count: 76
I’m going to make the assumption that you know how to manipulate files on the pi and you can use a program like winscp to ssh into the pi to edit config files.
Basically what you want to do is add a small script for each game which tells uae4arm to launch and load a config file which will immediately start an amiga game rom without all the hassle of using the uae4arm interface.
At the moment the directory /home/pi/RetroPie/roms/Amiga probably has two scripts in it called “+start UAE4ARM.sh” and “+start UAE4ALL2.sh”
+start UAE4ARM.sh contains the following text:
This is telling it to change directory to /opt/retropie/emulators/ and then execute the ./uae4arm program.
You can make a copy of this file and add a flag to tell uae4arm to run a config file immediately after it starts.
I have one for speedball 2 called “+start Speedball2.sh”
/opt/retropie/supplementary/runcommand/runcommand.sh 0 “./uae4arm -f conf/speedball2.uae”
This is essentially the same as the other scripts with an added config file.
Go into uae4arm. Load your speedball2 config but make sure in the miscellaneous options that you deselect “show GUI on startup”. Save the config with the same filename that you’re telling “+start speedball2.sh” to execute, so in my case it is speedball2.
Then in winscp ensure you change the permissions of your new script so that the owner is pi and it’s executable.
When you reload emulationstation you should see you script under the Amiga menu and clicking on it should start UAE4ARM and boot straight into Speedball2.
HTHtrixsterParticipant02/20/2016 at 16:00Post count: 76trixsterParticipant02/20/2016 at 15:50Post count: 76
I’ve been using a ps4 pad which I think is excellent. I’ve also finally managed to just about get a sega Saturn pad and virtua stick working too – the arcade stick is excellent for beam-em-ups.
I did use a pair of Xbox one pads too with previous builds of RetroPie but they’ve not worked since a firmware update. The latest update to xboxdrv does not seems to fix the issue sadly…trixsterParticipant02/19/2016 at 12:52Post count: 76
This is still not working for me either.
I’m running retropie 3.5, I’ve updated the setup script and rebuilt xboxdrv from source. Both my xbox one controllers are using the latest firmware.
Following a reboot, plugging in the xbox controller will bring up some dialogue in the raspberry pi’s console. Running jstest seems to recognise the controller but none of the buttons are toggled when pressed. When loading emulationstation the xbox one controller is not recognised.
Thoughts?trixsterParticipant02/19/2016 at 12:17Post count: 76trixsterParticipant01/31/2016 at 16:04Post count: 76trixsterParticipant01/31/2016 at 15:48Post count: 76
[quote=115594]You have to start fresh, unfortunately.
No you dont. It’s possible to upgrade from wheezy to Jessie first and then update to retropie 3.4. There’s a thread on the raspberrypi forums which tells you what to do. It’s not a simple procedure but it does work. I know this because I’ve done it on a couple of installs with no issues.
Check this thread:trixsterParticipant01/31/2016 at 09:56Post count: 76trixsterParticipant01/28/2016 at 22:37Post count: 76trixsterParticipant01/27/2016 at 21:20Post count: 76trixsterParticipant01/27/2016 at 21:19Post count: 76
So from the Retropie menu I can go into the retroarch rgui and manually bind the dpad controls. this works in the rgui menu. I can save that retroarch config, and when delving into that new config file I get the following settings:
input_player1_up = “up”
input_player1_up_btn = “12”
input_player1_up_axis = “nul”
input_player1_down = “down”
input_player1_down_btn = “14”
input_player1_down_axis = “nul”
input_player1_left = “left”
input_player1_left_btn = “15”
input_player1_left_axis = “nul”
input_player1_right = “right”
input_player1_right_btn = “13”
input_player1_right_axis = “nul”
So I would assume that pasting those settings into the HuijiaUSBGamePad.cfg would work. It does not. Buttons work fine with the autoconf but the dpad still refuses to work.
Funnily enough jstest sees the dpad as an axis, with left as -5 and right as +5. I’m not sure why retroarch sees the dpad as a button and jstest sees it as an axis. Is this normal?trixsterParticipant06/23/2015 at 00:12Post count: 76
This thread explains what’s going on:trixsterParticipant06/23/2015 at 00:05Post count: 76
Ive manually added Beebem following haprpi’s guide in the link. At the moment there’s no way to create a save state with Beebem operating under RetroPie as the GUI crashes the pi. It works under the desktop though. There’s a thread about it somewhere in this forum.trixsterParticipant06/20/2015 at 18:49Post count: 76
I’ve just updated from version 3beta2 to version 3beta4. It went a lot better than I expected. So far it looks like the only files i’ve had to change back are es_systems.cfg, gngeorc (the neogeo config file) and then copy across my uae4arm amiga adfs and conf files.
Other than that it looks like an easy and pain free update. I really like the way controls seem to have been integrated. This is a big big improvement. Time will tell though.
If you’re updating from version 2.6 then expect a massive headache if you’ve heavily modified various congfigs to get them running correctly. In such a case it’s really just worth starting agaion from scratch.
But going from 3beta2 to 3beat4 seems fine (with a few precautions take first of course!).trixsterParticipant05/15/2015 at 15:07Post count: 76trixsterParticipant05/12/2015 at 15:27Post count: 76trixsterParticipant05/11/2015 at 18:46Post count: 76
pi@RPi2 ~ $ tail /var/log/messages
May 8 10:17:10 RPi2 kernel: [ 5.094844] bcm2708_spi 3f204000.spi: SPI Contro ller running in dma mode
May 8 10:17:10 RPi2 kernel: [ 5.102943] bcm2708_i2c_init_pinmode(1,2)
May 8 10:17:10 RPi2 kernel: [ 5.107612] bcm2708_i2c_init_pinmode(1,3)
May 8 10:17:10 RPi2 kernel: [ 5.113434] bcm2708_i2c 3f804000.i2c: BSC1 Contr oller at 0x3f804000 (irq 79) (baudrate 100000)
May 8 10:17:10 RPi2 kernel: [ 6.078649] EXT4-fs (mmcblk0p8): re-mounted. Opt s: (null)
May 8 10:17:10 RPi2 kernel: [ 6.258898] EXT4-fs (mmcblk0p8): re-mounted. Opt s: (null)
May 8 10:17:10 RPi2 kernel: [ 6.687723] input: stmpe-ts as /devices/soc/3f20 4000.spi/spi_master/spi0/spi0.1/stmpe-ts/input/input2
May 8 10:17:10 RPi2 kernel: [ 15.237104] Adding 102396k swap on /var/swap. P riority:-1 extents:1 across:102396k SSFS
May 8 10:17:11 RPi2 fbcp: Primary display is 480 x 320
May 8 10:17:11 RPi2 fbcp: Second display is 480 x 320 16bpstrixsterParticipant05/11/2015 at 17:06Post count: 76
Are you running RetroPie 3.0 or later? I cannot help you with RetroPie 2.6.
I got this to work on a Rpi2 with 3.5″ resistive PiTFT.
I did not edit /etc/init.d/asplashscreen as it does not exist on my install. Instead I edited /etc/rc.local:
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will “exit 0” on success or any other
# value on error.
# In order to enable or disable this script just change the execution
# By default this script does nothing.
# Print the IP address
_IP=$(hostname -I) || true
if [ “$_IP” ]; then
printf “My IP address is %s\n” “$_IP”
the end of my config.txt looks like this:
# — added by adafruit-pitft-helper Wed Apr 15 15:11:37 UTC 2015 —
# — end adafruit-pitft-helper Wed Apr 15 15:11:37 UTC 2015 —
hdmi_cvt=480 320 60 1 0 0 0
You would have to change the “pitft35r” to pitft28r for a resistive screen or pitft28c for a capacative one. You will also need to change the hdmi_cvt line to match your screen’s dimensions.
It’s probably best not to bump up the fps and speed too much – maybe use the # commented line for dtoverlay rather than the line i’ve added at the end. And DO NOT overclock your core beyond 250Mhz. Mine will not work with any form of core overclock.
My overclock settings are:
#uncomment to overclock the arm. 700 MHz is the default.
force_turbo=1trixsterParticipant05/06/2015 at 21:05Post count: 76
I believe RetroPie uses this version:
I personally think the Chips version is currently the best:
You can easily integrate this version into RetroPie with a little bit of work.trixsterParticipant05/06/2015 at 20:54Post count: 76trixsterParticipant04/30/2015 at 00:03Post count: 76trixsterParticipant04/28/2015 at 22:18Post count: 76
I think the problme is Beebem thinks it’s running in x. If you startx into the Desktop, open a terminal and run Beebem, selecting a disc image doesnt crash beebem, rather it brings up a File Selector.
What we need is way to fool Beebem into thinking it’s running in X when we launch it in emulationstation and get it to bring up a File Selector which works outside of X. I have a feeling that’ll require some coding which is way beyond my abilities!
The other alternative is to get b-em compiled so it doesnt just work in X and will run using dispmanx. Again that’s beyond me.