Raspberry Pi Support

Tested in March 2020

On a Pi2, EE runs 20FPS on most stations at a resolution of 1024x768. On a Pi3, EE runs 30FPS on most stations at a resolution of 1024x768. Pi4 not tested yet, but someone else did: https://www.youtube.com/watch?v=KjDuZpA5W9g

OLD INFO, DATED!

This page is going to detail what is and is not working on a Raspberry Pi 3 as of ~ 7/4/17

This is going to get more updates as I have time to figure out what triggers crashes, the main use is to see what you can use a raspberry pi for. (And what you can not.)

I'm going to begin testing on Raspbian, will start to open bug reports after I get through most of the stations so I can see what the most common denominators are.

This is currently rawer than I would like it. Once I have tested a bit more I will start to clean up.

Building: See Build from sources for most of the information.

Please note that as of 7/4/17 there is a open bug that will prevent building from succeeding. (Bug #438) To fix just add the following to line 6 in src/gui/hotkeyConfig.h #include

Testing enviroment: Raspberry Pi 3 Raspbian OS 128 MB of VRam

Working:

• Relay Station?^EN
  • Only tested for 60 second's or so
    • opened comms with a station
    • launched a probe (This was a bit laggy)
    • messed with the alert status.
• Helm?^EN
  • Again, only tested for 60 second's or so
    • Turned
    • Flew under impulse.
    • Used Jump Drive.
• Database.^EN
  • Not much that would not work here.
• Tutorials
  • Except for the "Basics and Captian" One, that crashed.^INI
    • And by extension the "All Tutorials Button"
• Server as Game Master?^EN
  • Seems to work... Bit laggy though. (But what can you expect.)
  • I don't actually know what the GM screen can do. But hey it did not crash, so there is that.

Not Working:

• Anything that renders 3D^EN
  • Main Screen.
  • Single Pilot.
  • Ship Window.
  • Top Down 3D View.
  • Cinematic. (Works for a N'th of a second. (One frame?))
• Switching Stations?^EN
  • Only tested going between Science and Relay
    • May be due to lack of VRam.

^EN: Shaders Enabled ^INI: Shaders Disabled in INI ^BLD: Shaders Disabled during build ^ALL: Shaders Disabled both during build and in the INI

Current recomendations:

• Add a "Boss Key" That forces a (Preferably gracefull) close of the program, this may save a crashed terminal from needing to be entirely rebooted.
• Add a toggle that disables all 3D rendering. (It can even be a command line or build variable)