I’ve got it working! Runs very smoothly although the sound is a bit choppy. It might be resolved by turning down the sample rate and number of voices in the settings.
Oh, and for anyone trying this out… Do not touch the display settings. If you do, the game will instantly render in 640x480 and you can’t get rid of that setting. Only way is to go into you settings file using SSH and changing it to 320x240 manually again.
So with all that said, let’s rock! Very awesome to play this classic again!
Thanks for the tutorial. It was very clear, and the game runs smoothly.
I put the sample rate to the minimum, and turned up voices to the max, and haven’t noticed any choppiness in sounds so far doing that.
Any recommendations on how you setup the controls? I’ve only ever played duke3D with both a mouse and keyboard, and I cant decide how to set it up optimally for the gameshell
I tried this 3 times and keep getting errors during the build… Followed it several times… Made sure I had everything type right, not sure why it’s not working!
EDuke32 r(?)
Built Sep 23 2018 12:06:05, GCC 6.3.0, 32-bit
Using /home/cpi/games/Duke3D/ for game data
Using /home/cpi/.config/eduke32/ for game data
Initializing SDL 2.0.5
Initialization failed! (No available video device)
Non-interactive mode enabled
Searching for game data...
Checksumming DUKE3D.GRP... Done
Using "DUKE3D.GRP" as main game data file.
Compiling: GAME.CON (151190 bytes)
Including: DEFS.CON (35992 bytes)
Including: USER.CON (45482 bytes)
GAME.CON: In actor `ORGANTIC':
GAME.CON:3967: warning: found `else' with no `if'.
GAME.CON: In state `pigshootenemystate':
GAME.CON:5890: warning: found `else' with no `if'.
Found 2 warning(s), 0 error(s).
Script compiled in 57ms, 65684 bytes
Initialized 96.0M cache
Initializing OSD...
0 joystick(s) found
If you get the output from above, also check your script:
$ cd ~/apps/launcher/Menu/GameShell/
$ cat 'Duke Nukem 3D.sh'
Is anyone able to still get eduke32 to compile correctly? It compiles with errors for me. I’ve tried redownloading and making it several times with the same outcome. When I try and run the resulting eduke32 I get a “Segmentation fault” error. Any ideas?
They introduced something incompatible in December. November: no segmentation fault. December: segmentation fault.
Furthermore, eduke32 seems to boot the setup menu now instead of the game.
The best way forward is for me to make a new stable tag for the GameShell, fixing those new changes. I will first have to pinpoint the difference between November and December.
You can of course take the November build and make it, but you will still have to deal with this setup menu somehow.
Wow… thanks for figuring this out! I am going to give the November build a shot and see what it does. Is there a ForceSetup = 1 setting in cfg file that can be changed to a 0 by chance?