Difference between revisions of "LeapFrog Pollux Platform: sdlDoom"

From eLinux.org
Jump to: navigation, search
(Software Needed)
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
sdl doom quick tutorial
+
== Summary ==
 +
This is a quick tutorial on getting sdlDoom up and running.
  
I'd like to thank Nirvous, NullMoogleCable, PhillKll, Claude, JKent, Jburks, GrizzlyAdams and anyone I may have forgotten for their help :)
+
== Prerequisites ==
 +
[[LeapFrog_Pollux_Platform:_Build_Environment| Set Up Build Environment]]
  
requires:
+
[[Didj_and_Explorer_libSDL| Install libSDL]]
 
 
SDL http://elinux.org/Didj_and_Explorer_libSDL
 
 
SDL needs to be installed on the didj/lx and also needs the lib/headers to be installed on your PC
 
 
Framebuffer driver http://elinux.org/Leapster_Explorer_Framebuffer_Driver
 
 
   
 
   
to get the framebuffer driver you will need to compile a custom kernel for the didj/lx from the Explorer kernel sources
+
[[Leapster_Explorer_Framebuffer_Driver| 2.6.31 Kernel Frame Buffer]]
 
 
properly set environment vars (you will see a set of these when you compile your kernel)
 
  
Download sdldoom and the wad from http://www.libsdl.org/projects/doom/
+
== Software Needed ==
 +
[http://www.libsdl.org/projects/doom/src/sdldoom-1.10.tar.gz sdlDoom Sources]
  
You can now skip most of the steps below and just go and download my updated sources on github: http://github.com/Reggi3/ExplorerDoom
+
[http://www.libsdl.org/projects/doom/data/doom1.wad.gz sdlDoom Wad File]
  
Just compile and install as per the instructions further down, now on with the now outdated tutorial.
+
You will also need the SDL libs/headers on your host PC
  
 +
[http://github.com/Reggi3/ExplorerDoom sdlDoom Preconfigured] (git repo) Just compile.
  
wget http://www.libsdl.org/projects/doom/src/sdldoom-1.10.tar.gz
+
== Hardware Needed ==
tar -xvf sdldoom-1.10.tar.gz
+
[[LeapFrog_Pollux_Platform:_Console_Access| Console Access]]
cd sdldoom-1-10
 
wget http://www.libsdl.org/projects/doom/data/doom1.wad.gz
 
gunzip doom1.wad.gz
 
./configure
 
make -j5
 
  
change -j5 to reflect the number of cores on your cpu +1
 
  
copy the doom file to /usr/bin on your didj/lx
+
== Configure and Compile==
 +
Download and extract the source files.
  
copy the wad file to a folder on your didj/lx, somewhere like /LF/Bulk/doom on the lx or /Didj/doom on the didj
+
You'll need to fix some button mappings edit doomdef.h
 +
#define KEY_ESCAPE 109 // 'home button'
 +
#define KEY_ENTER 120 // 'brightness button'
  
browse to the folder where you put the wad file
+
To get sound working a bit better as there is a possible sample rate issue, edit i_sound.c and change line 56:
 +
#define SAMPLERATE 44100
  
run doom:
+
Make sure your Build Environment is set up and run the configure program then make. Change -j5 to reflect the number of cores on your cpu +1:
doom
+
  ./configure
 
+
  make -j5
as it stands the buttons don't do anything (dpad up/down/left/right and l/r shoulder move stuff around in the menus but thats it)
 
 
 
fix this by editing doomdef.h
 
 
 
change 2 lines to look like the following:
 
 
 
  #define KEY_ESCAPE 109 // 'home button'
 
  #define KEY_ENTER 120 // 'brightness button'
 
  
recompile.
+
Copy the doom file to /usr/bin on your device
  
now we can get into the game, yay but we still can't shoot stuff :( boo
+
Copy the wad file to a folder on your device, somewhere like /LF/Bulk/doom on the Explorers or /Didj/doom on the Didj.
  
make a blank text file called doomconfig
+
This will allow control for all things but shooting, to configure we need to make a config file.
  
save it in the same folder as your doom wad on the lx
+
Browse to the folder where you put the wad file and make a blank text file called doomconfig:
 +
# echo > doomconfig
  
run doom, using the following on the command line:
+
Run doom, using the following on the command line:
 
  doom -config doomconfig
 
  doom -config doomconfig
  
load a new game, run around and pick up something (not sure if this is entirely necessary), go to the menu and save the game, doomconfig should now be populated
+
Load a new game, run around and pick up something (not sure if this is entirely necessary), go to the menu and save the game, doomconfig should now be populated.
  
 
Edit doomconfig, change these 2 lines to the following:
 
Edit doomconfig, change these 2 lines to the following:
Line 108: Line 95:
  
  
this will give you 'fire' on the A button and 'use' on the B button
+
This will give you 'fire' on the A button and 'use' on the B button
  
 
Other buttons either don't work or don't work as expected if you try and change them via doomconfig, doomdef.h or m_misc.c (defaults get defined here if the config file isn't found), not sure why its behaving like this.
 
Other buttons either don't work or don't work as expected if you try and change them via doomconfig, doomdef.h or m_misc.c (defaults get defined here if the config file isn't found), not sure why its behaving like this.
  
Sound sort of works, looks like it gets the samplerate wrong when doom/sdl opens it :/
+
[[Category:Didj]]
 
+
[[Category:Leapster Explorer]]
 
+
[[Category:LeapPad Explorer]]
'''update'''
+
[[Category:LeapFrog Pollux Platform]]
 
 
To get sound working a bit better, edit i_sound.c and change line 56 #define SAMPLERATE to:
 
 
 
#define SAMPLERATE 44100
 
 
 
recompile doom and copy it to your didj/lx
 

Latest revision as of 17:33, 31 August 2011

Summary

This is a quick tutorial on getting sdlDoom up and running.

Prerequisites

Set Up Build Environment

Install libSDL

2.6.31 Kernel Frame Buffer

Software Needed

sdlDoom Sources

sdlDoom Wad File

You will also need the SDL libs/headers on your host PC

sdlDoom Preconfigured (git repo) Just compile.

Hardware Needed

Console Access


Configure and Compile

Download and extract the source files.

You'll need to fix some button mappings edit doomdef.h

#define KEY_ESCAPE 109 // 'home button'
#define KEY_ENTER 120 // 'brightness button'

To get sound working a bit better as there is a possible sample rate issue, edit i_sound.c and change line 56:

#define SAMPLERATE 44100

Make sure your Build Environment is set up and run the configure program then make. Change -j5 to reflect the number of cores on your cpu +1:

./configure
make -j5

Copy the doom file to /usr/bin on your device

Copy the wad file to a folder on your device, somewhere like /LF/Bulk/doom on the Explorers or /Didj/doom on the Didj.

This will allow control for all things but shooting, to configure we need to make a config file.

Browse to the folder where you put the wad file and make a blank text file called doomconfig:

# echo > doomconfig

Run doom, using the following on the command line:

doom -config doomconfig

Load a new game, run around and pick up something (not sure if this is entirely necessary), go to the menu and save the game, doomconfig should now be populated.

Edit doomconfig, change these 2 lines to the following:

key_fire  97
key_use   98

Alternatively you can copy and paste the following into your doomconfig file replacing anything that's in there, A= fire, B=use, R should = strafe right, weapon switching doesn't currently work, nor does strafe left or backwards:

mouse_sensitivity	5
sfx_volume		15
music_volume		15
show_messages		1
key_right		174
key_left		172
key_up			173
key_down		175
key_strafeleft		99
key_straferight	114
key_fire		97
key_use 		98
key_strafe		184
key_speed		999
use_mouse		1
mouseb_fire		0
mouseb_strafe		1
mouseb_forward	        2
use_joystick		0
joyb_fire		0
joyb_strafe		1
joyb_use		3
joyb_speed		2
screenblocks		10
detaillevel		0
snd_channels		3
usegamma		0
chatmacro0		"No"
chatmacro1		"I'm ready to kick butt!"
chatmacro2		"I'm OK."
chatmacro3		"I'm not looking too good!"
chatmacro4		"Help!"
chatmacro5		"You suck!"
chatmacro6		"Next time, scumbag..."
chatmacro7		"Come here!"
chatmacro8		"I'll take care of it."
chatmacro9		"Yes"


This will give you 'fire' on the A button and 'use' on the B button

Other buttons either don't work or don't work as expected if you try and change them via doomconfig, doomdef.h or m_misc.c (defaults get defined here if the config file isn't found), not sure why its behaving like this.