Frequently Asked Questions (FAQs)¶
Please also see Known Issues
Why are no ROMs provided with PES?¶
Game files are distributed as ROM files. These are copies of the games which have been extracted from the original game media (e.g. a game cartridge).
Creating and distributing ROM files from copyrighted media is often a breach of copyright. PES is therefore not distributed with any ROM files.
Obtaining a ROM file of a game you already own is also seen as a breach of copyright.
For example, Nintendo’s stance on ROM creation, use and distribution can be found at: http://www.nintendo.com/corp/legal.jsp
Creating and using a console emulator is not illegal as it does not breach any copyright laws. Using a game that is subject to copyright law with a game emulator is however.
My Raspberry Pi reports that it is running at over 70C - is this bad?¶
No. The Raspberry Pi has a thermal cut out of 80C. Unless you are using your Raspberry Pi in a hot environment and have overclocked it significantly (i.e. over 1GHz) then your Raspberry Pi will happily function.
Where does PES get its game information from?¶
PES downloads game information and cover art from theGamesDB.net
Which emulator software does PES use?¶
PES uses the RetroArch engine for running console emulators. The emulators themselves are often referred to as “cores” which are loaded by RetroArch. PES is packaged with Raspberry Pi compiled versions of RetroArch and a number emulators cores as well as standalone versions. A full list can be found in the Acknowledgements
Can I update the operating system?¶
PES uses Arch Linux.
You can update the software installed under the operating system but it is possible that the emulators may stop working so proceed at your own risk.
To update all packages installed under Arch Linux run:
sudo pacman -Syu
To search for a package:
sudo pacman -Ss package_name
Install a package:
sudo pacman -S package_name
How can I get the latest version of PES?¶
The latest version of PES will always be available at:
My Raspberry Pi seems to be interfering with other HDMI-CEC enabled devices connected to my TV?¶
This is a known issue with some models of the original Raspberry Pi and is out of my control sadly. Some models of Raspberry Pi when disconnected from the mains but still plugged into a HDMI-CEC enabled TV via HDMI can cause other HDMI-CEC devices not to receive HDMI-CEC commands. HDMI-CEC can be known by different names depending on the manufacturer. For example, Samsung refer to such devices as “Anynet+”. If the Raspberry Pi is powered off, but left plugged into the mains the issue will not occur. Alternatively, if you unplug the Raspberry Pi from the mains and also unplug the HDMI cable from the Raspberry Pi the issue will not occur. For more information, please see: http://www.raspberrypi.org/forums/viewtopic.php?f=35&t=14273
The Raspberry Pi 2/3 do not suffer from this issue.
My Bluetooth adapter will not work with my PlayStation 3 control pads¶
The QtSixA that is enabled by default in the PES image can be picky when it comes to Bluetooth adapters. If you find your PlayStation 3 control pads will not connect then please try using the Linux Bluez libraries instead: Using Bluez instead of QtSixA
Adding emulator BIOSes¶
All of the emulators will operate without a BIOS file from the original console, however, they will often run better with one. For example, the PlayStation emulator will show a warning if a BIOS file is not found. Due to copyright issues, the PES image is not supplied with any ROMs or BIOS files. Please see BIOS Files for further information.
Can I use the Raspberry Pi image with a Raspberry Pi 2/3?¶
No. Although the Raspberry Pi 2 is backwards compatible with the Raspberry Pi, the PES Raspberry Pi 2/3 image does not have Raspberry Pi firmware installed. You must therefore use the correct image with your system. For Raspberry Pi 3 owners, please use the Raspberry Pi 2 image as the two are binary compatible.
Does PES support the ColecoVision console?¶
The Final Burn Alpha emulator used by PES does support ColecoVision games, however, due to the original console having separate joystick layouts for each game it has not been possible as yet to provide a generic joystick button mapping that suits all games. The issue has been raised with the emulator author and is unresolved at the time of writing (July 2015). Should you wish to run ColecoVision games with PES, please edit /home/pi/pes/conf.d/consoles.ini and uncomment the ColecoVision section and then restart PES.
Why is the Raspberry Pi 3 image only 32-bit and compiled for Arm7?¶
At the time of writing a 64-bit Arm8 version of Arch Linux (Arm) is not available. As soon as this version is available I will prepare and release a version of PES for this new operating system.
The PES GUI spills over the edges of my TV screen?¶
This issue has been reported for some TVs. If your TV supports “Fit to Screen” in its video options, please try setting this first.
If this does not resolve the issue then please proceed as follows.
- Exit the PES GUI and either via using a keyboard connected to your Raspberry Pi or via SSH, access the command line.
- From the command line run:
/opt/vc/bin/tvservice -m DMT
/opt/vc/bin/tvservice -m DMT Group DMT has 19 modes: mode 4: 640x480 @ 60Hz 4:3, clock:25MHz progressive mode 5: 640x480 @ 72Hz 4:3, clock:31MHz progressive mode 6: 640x480 @ 75Hz 4:3, clock:31MHz progressive mode 9: 800x600 @ 60Hz 4:3, clock:40MHz progressive mode 10: 800x600 @ 72Hz 4:3, clock:50MHz progressive mode 11: 800x600 @ 75Hz 4:3, clock:49MHz progressive mode 16: 1024x768 @ 60Hz 4:3, clock:65MHz progressive mode 17: 1024x768 @ 70Hz 4:3, clock:75MHz progressive mode 18: 1024x768 @ 75Hz 4:3, clock:78MHz progressive mode 21: 1152x864 @ 75Hz 4:3, clock:108MHz progressive mode 28: 1280x800 @ 60Hz 16:10, clock:83MHz progressive mode 32: 1280x960 @ 60Hz 4:3, clock:108MHz progressive mode 35: 1280x1024 @ 60Hz 5:4, clock:108MHz progressive mode 36: 1280x1024 @ 75Hz 5:4, clock:135MHz progressive mode 39: 1360x768 @ 60Hz 16:9, clock:85MHz progressive mode 47: 1440x900 @ 60Hz 16:10, clock:106MHz progressive mode 48: 1440x900 @ 75Hz 16:10, clock:136MHz progressive mode 51: 1600x1200 @ 60Hz 4:3, clock:162MHz progressive mode 58: 1680x1050 @ 60Hz 16:10, clock:146MHz progressive
If modes are reported (as seen in the above example) then continue to the next step.
- Edit /boot/config.txt, e.g. using nano:
sudo nano /boot/config.txt
Add the following:
Now save the file and exit (e.g. for nano pess Ctrl + X and then type “Y”).
- Reboot your Raspberry Pi to test the new HDMI settings: