Skip to content

Troubleshooting

Jump to bottom Edit New page
ProfessorKaos64 edited this page Jan 10, 2015 · 2 revisions

Table of contents

Why is the joystick so erratic or doesn't work?

This seems to be only a problem with Sony PS3 Sixaxis controllers when used over a USB connection. The axis behave and perform correctly in jstest-gtk, but some applications (such as PCSX2 and antimicro) do not report the axis correctly. The issue may be with the version or usage of SDL1/2, but I am not sure. The eratic or incorrect behavior currently affects these systems:

  • PCSX (Playstaiton 2) - Some games exhibit the behavor in which after exiting, restarting, and loading a save state, the joystick will not work. The only game so far I have had affected by this issue is Metal Slug Anthology. Issue ticket has been entered with developer.

Possibly solutions to calibrate the joystick axis are:

  • jscal
  • jscalibrate
  • antimicro
  • jstest

Please see issue(s) #83 for more information

Why do I get a blank screen when RCB sits a while?

alt text

You sometimes may receive the above screen if RCB sits for an undetermined amount of time. The quick fix is to just back out the main RetroRig-ES screen and then enter RCB (Rom Collection Browser) again. This issue is still being looked into.

You may also references this RCB developer ticket to follow the issue.

Why is the artwork missing for console X?

If you are missing some artwork for a game there are a few things you can try.

In General

If one game or just a few are missing artwork, head over to the one of the scapers actual website to make sure your game exists, and that it is named correctly. I can't tell you how many times I had a few characters different in a title and didn not have artwork pull correctly. You can also change the method of the scrapers when importing games. The default mode is "accurate."

The curernt list of scraping websites (base on RCB's config.xml) is:

Please refernce the RCB Google page on scrapers for more info. RetroRig-ES does not maintain any of these scapers, and are solely maintained by the RCB developer.

MAME

For MAME games, the artwork files are way too huge. At some point I may place the artwork archive into a torrent file, but I am not sure about the legality of such a thing. Please see the corresponding Rom Collection Browser wiki entry to add Artwork to the offline scraper currently implemented. If you don't care about the artwork, you can carry on :) In summary , place the applicable image types into the premade folders RetroRig-ES already has:

  • action
  • cabinet
  • marquee
  • RCB
  • boxfront
  • gameplay
Game Boy Advance

For GBA games, the images pulled down from the online scrapers seem to be corrupted. You can manually replace the photo in the Arwork/GBA folder, but the easiest workaround for now, is use the "giantbomb.com" scraper when importing your GBA games. To do this, hit the switch to "Change scrapers for this run" when importing GBA games (you don't need to do this for all games, and it may mess other games up). Change Scraper 1 to "giantbomb.com." This is a known issue and submitted to the RCB dev under Issue 176

Help! XBMC freezes on start/exit!

This is now fixed in the Ubuntu beta branch(s)

This is a known issue (see issue #45) with RetroRig-ES. The hang on startup is not immediate until you try and press the play button. Myself and JC (a contributor to the project) are working actively to try and fix this annoying issue. It seems to be a skin issue, but we cannot rule that out. Performing a reboot, or killing the process, and finally restarting RetroRig-ES solves the issue. What is happening is when XBMC loads or unloads the skin, or an image resource, it hangs.

First and foremost

  • Try to exit RetroRig-ES/XBMC normally and restart RetroRig-ES from the desktop or Unity taskbar.

Switch to another TTY line

  • Press CTRL+ALT+F2 to switch to another virtual TTY line
  • Login with your username and password you chose

Kill XBMC

ps -aux | grep xbmc
kill -9 ####

Example output:

test@test-pc:~$ ps -aux | grep xbmc
root       970  0.0  0.0  17972  1512 ?        S    05:44   0:00 /bin/bash /usr/share/applications/gp_autodetect_xbmc.sh
test      1621  0.0  0.0   4444   652 ?        S    05:44   0:00 /bin/sh /usr/bin/xbmc
test      2002  2.1  3.5 1504168 72308 ?       Sl   05:44   0:03 /usr/lib/xbmc/xbmc.bin
test      3976  0.0  0.0  15944   920 pts/0    S+   05:47   0:00 grep --color=auto xbmc

Substitute the number of the PID that xbmc.bin is contained. In my example above, that would be 2002

OR

Reboot sudo reboot

Switch back to XBMC if you did not reboot

  • Press CTRL+ALT+F7 to return to the default Unity session

Thank you immensely for your patience.
-pk

Why can't I launch a game?

Possible reasons:

  • Incorrect resolution in configuration file
  • Missing ROM/BIOS file(s)
  • Code issue, segfault, general technical issue
  • Bad game ROM
  • Incompatible emulator settings

Please enter an issues ticket for any strange issues.

(VirtualBox) Help! I ran out of space for ROMs!

If you used a fixed disk size for your VM, and need to expand it, you must clone the disk using the Vboxmanage command (resizing fixed disks is not supported currently). Make sure you fully shutdown (do not save the state) the VM, and for safety, VirtualBox itself as well. The following syntax applies:

VBoxManage clonehd "OLD.vdi" "NEW_NAME.vdi" --variant Standard

In my case, the command to resize my VM to 45 GB was:

VBoxManage clonehd "Ubuntu 14.04 LTS.vdi" "Ubuntu 14.04 LTS (new).vdi" --variant Standard

We now have a dynamically-resizable disk image, which means we can expand our disk to, say, 50 GB via the following command:

VBoxManage modifyhd NEW_NAME.vdi --resize 51200

The Choice
Where 51200 is the MB equivalent of 50GB. You can choose whatever size you like, as long as you're sure it fits in your hard drive. This resizing process may take a couple minutes, depending on the size. Note that this command only works because we have a dynamic disk image. A fixed-size disk image would give us an error, and if you do get an error here, that's most likely it.

Example output:

mikeyd@archboxmtd /m/s/v/Ubuntu> 
VBoxManage clonehd "Ubuntu 14.04 LTS.vdi" "Ubuntu 14.04 LTS (new).vdi" --variant Standard
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Clone hard disk created in format 'VDI'. UUID: e0d34a4d-a4c8-4088-a4e7-6fa081632436

You have a choice: if all you want to keep your newly-dynamic disk image, you can stop here. If you want to go back to a fixed-size disk image for the speed benefits (and I wouldn't blame you if you did), keep reading.

Changing drives
We're done with the command line. The next step we have to take is within the VirtualBox GUI. Open up VirtualBox. Select the virtual machine you resized and go to 'Settings'. Now go to 'Storage' on the left-hand side. Within the 'Storage Tree' box, highlight 'Controller: SATA' and click on the small 'Add Hard Disk' icon (it should be on the right). Now click on 'Choose an existing disk' and browse to the location of your newly-created virtual drive. Select it and click Open. You should see it appear under the 'Controller: SATA' label. If there are any other drives there, be sure to remove them by highlighting them and clicking the red 'Remove Attachment' icon at the bottom. You're done!

Resizing
The last thing to do is expand the disk using gparted. You have to grow the main partition to the entire disk space. Click the main partition on the bar displaying the disk space and click the Resize icon at the top. In this new window, drag the slider to the end of the disk so there is a 0 in the 'Free Space Following' on the disk (or as little as possible), hit Resize, and click the check mark icon back in the main window to apply the operation. After this completes, you have a larger disk at your disposal!

Source: Ruben.codes

Back to Home

Main Documentation List
Quick Links

External Links

Clone this wiki locally