DOOM Port for the Openmoko Freerunner

Contents

Release Roadmap

* DOOM DBus Interfacing to assure perfect cohabitation with phone device

This includes seemless switching between doom and other applications
- Such as a phone call
- Or user activated switch to focus on other background apps.

Design X Interface, touch friendly gui.
- Game Configuration, Front End
- Networking/Multi-player Front-End
Run Community Multi-player Server
- Implement, Matchmaking Interface
Time-Date Stamped Saved Games (Since typcial use with no keyboard)
Expose Cheat Codes to CFG
Implement Configurable Touchscreen Buttons (Size, Position)
Vibration Feedback

Optimize for CPU Usage (Its currently a hog)
Interface/Scale GPS position to physical map coordinates (may find a need for a digital compass.. although we have the accelerometers to help interpret events)
- this could potentially be demanding cpu wise?

opkg install libsdl-1.2-0 libsdl-mixer-1.2-0 libsdl-net-1.2-0 opendoom_0.1.1_armv4t.ipk
Bug #1244 Has apparently been fixed. Just in case, Here is patched version of
Xglamo.
- I'll remove this as soon as I've varified that the patch has made it into the stable feeds with scaling correct as well.
copy XGlamo to /usr/bin on your freerunner
Remember to check out your ~/.opendoom/opendoom.cfg There is a massive amount of control exposed to you. (Thanks PRBOOM)

* Please write me at scottrcarlson@gmail.com for write access to the repo!

Works Great.
Moves fast 320x240 and choppy 640x480 (Need to implement video acceleration, when its availible on the freerunner)
Sound Effects and Midi Music
Full Touch Screen Interface
Full Accelerometer Interface
Network has been tested, and its unstable. (Waiting for more feedback)
DOOM itself uses about 40-60% CPU with Xglamo taking another 33% (ouch)

The user can change whether to use Accelerometer control or Full Touchscreen (only) control.
- See opendoom.cfg and change accelerometer0_touchscreen1_toggle to an appropriate value (0 or 1)
Ideally All Freerunner users will want to use Accelerometer control.
All Neo 1973 owners can only user touchscreen interface

Navigating Menus
- Enter/Exit the menu with the top right corner of the screen.
- Up/Down/Left/Right are where you would expect them on their corresponding border.
- Enter is tied to the center of the screen.
Finger Tipping
- The basic idea behind finger tipping involves placing your finger tip anywhere on the touchscreen. The x,y coordinates are logged as the origin until you remove your finger from the touchscreen. Now, slightly tip your finger and your new x,y coordinates will be calculated with the origin to come up with a vector. The circular region around your finger tip will be called the tipping boundary. With our vector value we can now handle our event in several different ways. There will be definable tipping boundary radius and deadzone (also a radius). We can now define our angle boundaries and sub divide our tipping region into different events. To add sensitivity we only need to look at the magnitude of the calculated vector and apply at will.
Drawing Vectors
- Using similar concepts as described above, one can also touch the screen to create an "origin" and then slide the finger away from that point to control motion.
Strafing
- The strafe can be accomplished by sliding the finger from left to right (I've also found the thumb to work well)

Auto Tare
- Happens whenever you leave the main menu and return back to the game.
- This feature takes the current position of the device and calls it "home". Think of it as a neutral position.
  - It is helpful to goto the main menu and back as often as necessary, this allows you to "readjust yourself" for comfortable play.
Motion Control
- Tipping the Phone Forward and Backward to move.
- Tipping from side to side. (and also a steering wheel motion) will turn you appropriately.
- Holding the AUX button will allow you to strafe by tipping/steering.
- Scaling Factors
  - Acceleration factors are tunable through opendoom.cfg.
    - In opendoom.cfg you will find under the accelerometer settings, xscale, yscale and zscale. The axis labels can be confusing. Currently the Z-Axis of accelerometer is tied to Y-Axis motion in the game (i.e forward/backward)

and the Y-Axis on the accelerometer is tied to the X-Axis of the game (i.e. left and right).

Deadzone can also be tuned in the opendoom.cfg file. Think of the deadzone as the size of the "Home" or "Neutral" position.
- These are called accelerometer_xwindow, ywindow, zwindow.

Works well.
- check out prboom-game-server included. (Want to make a nice front end, if any one is interested in chipping in on this, I'd appreciate it!
- I'd like to setup a community server, and possibly test fr to fr long distance..

Picture a bunch of people in a park, running around with Freerunner like devices in their hand.
- Now imagine that a combination of GPS/AGPS and Accelerometers to track coordinates in the game level maps.
  - WIFI Multiplayer Holodeck style Deathmatch!!!!!!!!!!!!!!!!!!!!