TyrQuake
TyrQuake 0.71 is the Quake engine, packaged for FPLinux with software and GPU renderers. The package does not contain the game itself: you need a legally obtained pak0.pak from Quake.
Install
Section titled “Install”Install fplinux-tyrquake.apk as described in Packages. Its installed package name is fplinux-tyrquake.
Provide the game data
Section titled “Provide the game data”The game reads pak0.pak from this path, and also any readable pak1.pak to pak9.pak in the same directory:
/mnt/card/fplinux/quake/id1/pak0.pakThe files stay where you put them; the game reads them in place and never writes to that directory. Choose one of the following places, using a filesystem and boot profile supported on your phone page.
On a microSD data card
Section titled “On a microSD data card”Mount the card at /mnt/card, create the directory fplinux/quake/id1 on it, and upload pak0.pak there as described in Connect from a PC. The files stay on the card.
On a phone with supported FAT32 data-card use, if /mnt/card is not mounted, quake mounts a FAT32 card read-only by itself. Mount an ext4 card yourself before you start the game.
On a microSD system card
Section titled “On a microSD system card”When the phone runs from a microSD system card, keep the game data in a directory of the system and bind-mount it at /mnt/card. With /mnt/card not yet mounted, run on the phone:
mkdir -p /var/lib/quake-data/fplinux/quake/id1 /mnt/cardmount -o bind /var/lib/quake-data /mnt/cardThen upload pak0.pak to /mnt/card/fplinux/quake/id1/pak0.pak. The data stays on the card; repeat the bind mount after each boot. Do not put game data on the FPLBOOT partition.
Without a card, for one session
Section titled “Without a card, for one session”With /mnt/card not yet mounted, run on the phone:
mkdir -p /mnt/cardmount -t tmpfs tmpfs /mnt/cardmkdir -p /mnt/card/fplinux/quake/id1Then upload pak0.pak to /mnt/card/fplinux/quake/id1/pak0.pak. The file takes phone memory, which leaves less room for the game, and disappears when the phone shuts down.
Start the game
Section titled “Start the game”Stop the graphical session and run the game from the USB shell, following Direct-display applications:
quake--heapsize sets the memory the game reserves for itself, in kibibytes, from 8192 to 262144. The default is 32768. Game data kept in phone memory comes on top of this reservation, so in that case a smaller value may be needed:
quake --heapsize 16384If the value is smaller than the game data needs, the game stops during startup.
Performance overlay
Section titled “Performance overlay”Add --stats to show frame rate, average frame duration, CPU time, GPU scene time, resident memory and temperature:
quake --statsThe overlay works with both renderers and updates about once a second. CPU is average process CPU time per frame, including the engine’s threads and excluding blocked waits. GPU scene time covers scene and HUD rendering; it excludes the output conversion and display transfer. A metric the phone cannot provide is shown as --; the software renderer has no GPU scene time. TEMP is the phone’s single readable thermal sensor, not necessarily a CPU sensor.
Measurements have overhead. For a frame-rate counter alone, use show_fps 1 in the game’s console. A timedemo plays a recorded demo as fast as possible for benchmarking; its movement speed does not represent normal gameplay.
Controls
Section titled “Controls”You can use the phone keypad, keyboards and mice at the same time: a PC keyboard through the USB keyboard bridge, and Bluetooth keyboards and mice where the phone supports them. A device that connects during the game is picked up, and a device that disconnects does not end the game.
Phone keypad
Section titled “Phone keypad”On a phone with a portrait display, hold it turned counter-clockwise, with the display on the left and the keypad on the right. On a phone with a landscape display, hold it upright.
| Key | In the menu | In the game |
|---|---|---|
| D-pad Up / Down (portrait display) | Left / right | Turn left / right |
| D-pad Left / Right (portrait display) | Down / up | Walk backward / forward |
| D-pad Up / Down (landscape display) | Up / down | Walk forward / backward |
| D-pad Left / Right (landscape display) | Left / right | Turn left / right |
| Centre or Dial | Select | Fire |
| Right soft | Back | Open the menu |
| Left soft or * | — | Jump |
| 0 | — | Fire |
| 1 / 3 | — | Strafe left / right |
| 2 / 5 | — | Turn left / right |
| 4 / 6 | — | Walk backward / forward |
| 7 / 9 | — | Previous / next weapon |
| 8 | — | Show scores while held |
| # | — | Not bound; you can bind it for the current game |
Some questions, such as starting a new game during a game, accept only Y, N or Escape. On the keypad you can only cancel them, with Right soft.
Keyboard and mouse
Section titled “Keyboard and mouse”A keyboard keeps its own key meanings; the phone mapping above applies only to the phone keypad. The keyboard uses the game’s standard bindings with these changes: you always run, and W, A, S, D move and strafe. As a result, A and D no longer look up and swim up as they do in the original game; look with the mouse instead.
| Control | In the game |
|---|---|
| W / S | Forward / back |
| A / D | Strafe left / right |
| Mouse | Turn and look |
| Left button, Ctrl, Enter | Fire |
| Right button, Space | Jump |
| Wheel up or ] | Next weapon |
| Wheel down or [ | Previous weapon |
| 1 to 8 | Select weapon |
All other keys, including the arrow keys, keep the game’s standard bindings. The mouse turns and looks up and down; while you hold the game’s strafe modifier, it moves you sideways instead. Side buttons on the mouse do nothing.
Press Right soft to open the menu, choose Quit, and confirm with Centre. Restart the graphical session from the USB shell after the game exits.
Limitations
Section titled “Limitations”- Settings, key bindings and saved games are lost every time the game exits, on every kind of boot.
- There is no sound.