10eo
Posts: 10
Joined: Thu Feb 16, 2017 11:51 pm

How Do I Run Doom Faster in Dosbox On My Pi 3?

Fri Feb 17, 2017 12:28 am

I got Doom working in Dosbox on my Pi 3 recently. But, it runs slow and I tried to increase the cpu cycles in Dosbox but it did nothing. I just want to play Doom at a appropriate speed on my Pi 3, but in the meantime I can play Wolf3d, Prince of Persia, and Rogue :D.
Interested in electronics and programming. Also listen to this: https://m.youtube.com/watch?v=lcR2pHRePm0
"Sometimes it is the people no one imagines anything of who do the things no-one can imagine" Alan Turing

User avatar
mikronauts
Posts: 2732
Joined: Sat Jan 05, 2013 7:28 pm
Contact: Website

Re: How Do I Run Doom Faster in Dosbox On My Pi 3?

Fri Feb 17, 2017 1:43 am

You do realize that Dosbox has to emulate an x86 processor?

About the only thing that might help is to overclock, however the RPi3 can't overclock very far.

Best bet: go get a free hand-me-down PC.
10eo wrote:I got Doom working in Dosbox on my Pi 3 recently. But, it runs slow and I tried to increase the cpu cycles in Dosbox but it did nothing. I just want to play Doom at a appropriate speed on my Pi 3, but in the meantime I can play Wolf3d, Prince of Persia, and Rogue :D.
http://Mikronauts.com - home of EZasPi, RoboPi, Pi Rtc Dio and Pi Jumper @Mikronauts on Twitter
Advanced Robotics, I/O expansion and prototyping boards for the Raspberry Pi

jgreen71
Posts: 92
Joined: Wed May 01, 2013 12:29 pm
Location: Clarksville, IN

Re: How Do I Run Doom Faster in Dosbox On My Pi 3?

Fri Feb 17, 2017 1:51 pm

Even better, DOOM has been ported to the Pi. Just get a copy of that and play.

User avatar
mahjongg
Forum Moderator
Forum Moderator
Posts: 12410
Joined: Sun Mar 11, 2012 12:19 am
Location: South Holland, The Netherlands

Re: How Do I Run Doom Faster in Dosbox On My Pi 3?

Fri Feb 17, 2017 1:55 pm

+1 its much faster, as its running natively on the ARM processor, no slow x86 emulation needed.

PiGraham
Posts: 3671
Joined: Fri Jun 07, 2013 12:37 pm
Location: Waterlooville

Re: How Do I Run Doom Faster in Dosbox On My Pi 3?

Fri Feb 17, 2017 2:14 pm

Doesn't the Retropi image have DOOM on it as standard?

10eo
Posts: 10
Joined: Thu Feb 16, 2017 11:51 pm

Re: How Do I Run Doom Faster in Dosbox On My Pi 3?

Sat Feb 18, 2017 2:51 am

Does anyone know how to correctly install chocolate doom on the pi? Because whenever I install it, it says something like E: cannot find chocolate-doom. :shock:
Interested in electronics and programming. Also listen to this: https://m.youtube.com/watch?v=lcR2pHRePm0
"Sometimes it is the people no one imagines anything of who do the things no-one can imagine" Alan Turing

ktb
Posts: 1380
Joined: Fri Dec 26, 2014 7:53 pm

Re: How Do I Run Doom Faster in Dosbox On My Pi 3?

Sun Feb 19, 2017 6:34 am

10eo wrote:Does anyone know how to correctly install chocolate doom on the pi? Because whenever I install it, it says something like E: cannot find chocolate-doom. :shock:
How did you install it?

I just installed it from git using the instructions here -- https://www.chocolate-doom.org/wiki/ind ... _Debian/v3

Then you need to get some IWAD files.

https://www.chocolate-doom.org/wiki/ind ... omputer.3F

Code: Select all

pi@raspberrypi:~ $ chocolate-doom -iwad /usr/local/games/doom/doom2.wad

10eo
Posts: 10
Joined: Thu Feb 16, 2017 11:51 pm

Re: How Do I Run Doom Faster in Dosbox On My Pi 3?

Sun Feb 19, 2017 2:20 pm

I tried to download chocolate doom by typing

Code: Select all

 apt-get install chocolate-doom
from https://www.chocolate-doom.org/wiki/ind ... m_on_Linux and this happened:

Code: Select all

apt-get install chocolate-doom
E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied)
E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?
and I tried to go root this happens:

Code: Select all

sudo apt-get install chocolate-doom
Reading package lists... 10 Reading package lists... Done
Building dependency tree... Building dependency tree... Building dependency tree... Building dependency tree... Building dependency tree... Building dependency tree       
Reading state information.. Reading state information..Reading state information... Done
E: Unable to locate package chocolate-doom
But (using your method), I already got the dependencies and downloaded the source package (I guess it is talking about the source code of chocolate doom) but, when I tried to extract the package this happened:

Code: Select all

tar xzf chocolate-doom-2.3.0.tar.gz
tar (child): chocolate-doom-2.3.0.tar.gz: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
(Also I'm new to Linux)
What do I do now?
Last edited by 10eo on Sun Feb 19, 2017 2:41 pm, edited 1 time in total.
Interested in electronics and programming. Also listen to this: https://m.youtube.com/watch?v=lcR2pHRePm0
"Sometimes it is the people no one imagines anything of who do the things no-one can imagine" Alan Turing

fruitoftheloom
Posts: 21077
Joined: Tue Mar 25, 2014 12:40 pm
Location: Delightful Dorset

Re: How Do I Run Doom Faster in Dosbox On My Pi 3?

Sun Feb 19, 2017 2:39 pm

Code: Select all

sudo apt-get update
sudo apt-get install chocolate-doom
Retired disgracefully.....
This at present is my daily "computer" https://www.asus.com/us/Chrome-Devices/Chromebit-CS10/

10eo
Posts: 10
Joined: Thu Feb 16, 2017 11:51 pm

Re: How Do I Run Doom Faster in Dosbox On My Pi 3?

Sun Feb 19, 2017 2:45 pm

Fruitoftheloom, I just tried it now and it said:

Code: Select all

pi@raspberrypi:~ $ sudo apt-get update
Hit http://archive.raspberrypi.org jessie InRelease
Get:1 http://mirrordirector.raspbian.org jessie InRelease [14.9 kB]
Get:2 http://mirrordirector.raspbian.org jessie/main armhf Packages [8,981 kB]
Hit http://archive.raspberrypi.org jessie/main armhf Packages
Hit http://archive.raspberrypi.org jessie/ui armhf Packages
Ign http://archive.raspberrypi.org jessie/main Translation-en_US
Ign http://archive.raspberrypi.org jessie/main Translation-en
Ign http://archive.raspberrypi.org jessie/ui Translation-en_US
Ign http://archive.raspberrypi.org jessie/ui Translation-en
Get:3 http://mirrordirector.raspbian.org jessie/contrib armhf Packages [37.5 kB]
Get:4 http://mirrordirector.raspbian.org jessie/non-free armhf Packages [70.3 kB]
Get:5 http://mirrordirector.raspbian.org jessie/rpi armhf Packages [1,356 B]
Ign http://mirrordirector.raspbian.org jessie/contrib Translation-en_US
Ign http://mirrordirector.raspbian.org jessie/contrib Translation-en
Ign http://mirrordirector.raspbian.org jessie/main Translation-en_US
Ign http://mirrordirector.raspbian.org jessie/main Translation-en
Ign http://mirrordirector.raspbian.org jessie/non-free Translation-en_US
Ign http://mirrordirector.raspbian.org jessie/non-free Translation-en
Ign http://mirrordirector.raspbian.org jessie/rpi Translation-en_US
Ign http://mirrordirector.raspbian.org jessie/rpi Translation-en
Fetched 9,105 kB in 19s (472 kB/s)
Reading package lists... 14Reading package lists... 27Reading package lists... 41Reading package lists... 54Reading package lists... 66Reading package lists... 77Reading package lists... 87Reading package lists... 94Reading package lists... 94Reading package lists... 95Reading package lists... 95Reading package lists... 95Reading package lists... 95Reading package lists... 95Reading package lists... 95Reading package lists... 96Reading package lists... 96Reading package lists... 97Reading package lists... 97Reading package lists... 98Reading package lists... Done
pi@raspberrypi:~ $ sudo apt-get install chocolate-doom
Reading package lists... 10Reading package lists... Done
Building dependency tree...Building dependency tree...Building dependency tree...Building dependency tree...Building dependency tree...Building dependency tree       
Reading state information..Reading state information..Reading state information... Done
E: Unable to locate package chocolate-doom
pi@raspberrypi:~ $ 
Interested in electronics and programming. Also listen to this: https://m.youtube.com/watch?v=lcR2pHRePm0
"Sometimes it is the people no one imagines anything of who do the things no-one can imagine" Alan Turing

10eo
Posts: 10
Joined: Thu Feb 16, 2017 11:51 pm

Re: How Do I Run Doom Faster in Dosbox On My Pi 3?

Sun Feb 19, 2017 2:48 pm

I guess chocolate doom isn't a package anymore. :(
Interested in electronics and programming. Also listen to this: https://m.youtube.com/watch?v=lcR2pHRePm0
"Sometimes it is the people no one imagines anything of who do the things no-one can imagine" Alan Turing

fruitoftheloom
Posts: 21077
Joined: Tue Mar 25, 2014 12:40 pm
Location: Delightful Dorset

Re: How Do I Run Doom Faster in Dosbox On My Pi 3?

Sun Feb 19, 2017 2:56 pm

10eo wrote:I guess chocolate doom isn't a package anymore. :(
Yes you are correct it is not in the repositories :oops:


Maybe try: https://www.chocolate-doom.org/wiki/ind ... _(generic)
Retired disgracefully.....
This at present is my daily "computer" https://www.asus.com/us/Chrome-Devices/Chromebit-CS10/

10eo
Posts: 10
Joined: Thu Feb 16, 2017 11:51 pm

Re: How Do I Run Doom Faster in Dosbox On My Pi 3?

Sun Feb 19, 2017 3:07 pm

I'll try build chocolate doom on Debian/v3, first. Then, I will try the one for building it in Linux (generic). Thank you, though!
Interested in electronics and programming. Also listen to this: https://m.youtube.com/watch?v=lcR2pHRePm0
"Sometimes it is the people no one imagines anything of who do the things no-one can imagine" Alan Turing

ktb
Posts: 1380
Joined: Fri Dec 26, 2014 7:53 pm

Re: How Do I Run Doom Faster in Dosbox On My Pi 3?

Sun Feb 19, 2017 8:31 pm

The error you encountered is likely caused by using the wrong file name or location for the downloaded chocolate-doom-2.3.0.tar.gz.

Try this (which is pretty close to what I did):

Code: Select all

pi@raspberrypi:~ $ sudo apt install gcc make libsdl2-dev libsdl2-net-dev libsdl2-mixer-dev python-imaging automake autoconf libtool git
pi@raspberrypi:~ $ mkdir -p ~/software/source
pi@raspberrypi:~ $ cd ~/software/source
pi@raspberrypi:~/software/source $ git clone git://github.com/chocolate-doom/chocolate-doom.git
pi@raspberrypi:~/software/source $ cd chocolate-doom
pi@raspberrypi:~/software/source/chocolate-doom $ ./autogen.sh
pi@raspberrypi:~/software/source/chocolate-doom $ make
pi@raspberrypi:~/software/source/chocolate-doom $ sudo make install

10eo
Posts: 10
Joined: Thu Feb 16, 2017 11:51 pm

Re: How Do I Run Doom Faster in Dosbox On My Pi 3?

Mon Feb 20, 2017 1:58 pm

Okay, this happens when I try to copy your code:

Code: Select all

pi@raspberrypi:~ $ sudo apt install gcc make libsdl2-dev libsdl2-net-dev libsdl2-mixer-dev python-imaging automake autoconf libtool git
Reading package lists... Done
Building dependency tree        
Reading state information... Done
gcc is already the newest version.
git is already the newest version.
git set to manually installed.
make is already the newest version.
python-imaging is already the newest version.
The following package was automatically installed and is no longer required:
  libffi5
Use 'apt-get autoremove' to remove it.
The following extra packages will be installed:
  autotools-dev libegl1-mesa-dev
  libgles2-mesa-dev libice-dev
  libltdl-dev libsdl2-2.0-0
  libsdl2-mixer-2.0-0
  libsdl2-net-2.0-0 libsigsegv2
  libsm-dev libudev-dev
  libwayland-bin libwayland-dev
  libxcursor-dev libxi-dev
  libxinerama-dev
  libxkbcommon-dev libxrandr-dev
  libxrender-dev libxss-dev
  libxt-dev libxv-dev m4
  x11proto-randr-dev
  x11proto-render-dev
  x11proto-scrnsaver-dev
  x11proto-video-dev
  x11proto-xinerama-dev
Suggested packages:
  autoconf-archive gnu-standards
  autoconf-doc gettext libice-doc
  libtool-doc libsm-doc automaken
  gfortran fortran95-compiler
  gcj-jdk libxt-doc
The following NEW packages will be installed:
  autoconf automake autotools-dev
  libegl1-mesa-dev
  libgles2-mesa-dev libice-dev
  libltdl-dev libsdl2-2.0-0
  libsdl2-dev libsdl2-mixer-2.0-0
  libsdl2-mixer-dev
  libsdl2-net-2.0-0
  libsdl2-net-dev libsigsegv2
  libsm-dev libtool libudev-dev
  libwayland-bin libwayland-dev
  libxcursor-dev libxi-dev
  libxinerama-dev
  libxkbcommon-dev libxrandr-dev
  libxrender-dev libxss-dev
  libxt-dev libxv-dev m4
  x11proto-randr-dev
  x11proto-render-dev
  x11proto-scrnsaver-dev
  x11proto-video-dev
  x11proto-xinerama-dev
0 upgraded, 34 newly installed, 0 to remove and 22 not upgraded.
Need to get 4,789 kB of archives.
After this operation, 16.0 MB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://archive.raspberrypi.org/debian/ jessie/main libwayland-bin armhf 1.11.0-2 [17.8 kB]
Get:2 http://archive.raspberrypi.org/debian/ jessie/main libwayland-dev armhf 1.11.0-2 [86.6 kB]
Get:3 http://mirrordirector.raspbian.org/raspbian/ jessie/main libsdl2-2.0-0 armhf 2.0.2+dfsg1-6 [289 kB]
Get:4 http://archive.raspberrypi.org/debian/ jessie/main libegl1-mesa-dev armhf 13.0.0-1+rpi1 [54.4 kB]
Get:5 http://mirrordirector.raspbian.org/raspbian/ jessie/main libsdl2-mixer-2.0-0 armhf 2.0.0+dfsg1-5 [67.3 kB]
Get:6 http://mirrordirector.raspbian.org/raspbian/ jessie/main libsdl2-net-2.0-0 armhf 2.0.0+dfsg1-2 [10.6 kB]
Get:7 http://mirrordirector.raspbian.org/raspbian/ jessie/main libsigsegv2 armhf 2.10-4 [28.2 kB]
Get:8 http://mirrordirector.raspbian.org/raspbian/ jessie/main m4 armhf 1.4.17-4 [238 kB]
Get:9 http://archive.raspberrypi.org/debian/ jessie/main libgles2-mesa-dev armhf 13.0.0-1+rpi1 [74.3 kB]
Get:10 http://mirrordirector.raspbian.org/raspbian/ jessie/main autoconf all 2.69-8 [340 kB]
Get:11 http://mirrordirector.raspbian.org/raspbian/ jessie/main autotools-dev all 20140911.1 [70.5 kB]
Get:12 http://archive.raspberrypi.org/debian/ jessie/main x11proto-randr-dev all 1.5.0-1 [49.7 kB]
Get:13 http://mirrordirector.raspbian.org/raspbian/ jessie/main automake all 1:1.14.1-4+deb8u1 [724 kB]
Get:14 http://mirrordirector.raspbian.org/raspbian/ jessie/main libice-dev armhf 2:1.0.9-1 [58.1 kB]
Get:15 http://mirrordirector.raspbian.org/raspbian/ jessie/main libltdl-dev armhf 2.4.2-1.11 [155 kB]
Get:16 http://mirrordirector.raspbian.org/raspbian/ jessie/main libudev-dev armhf 215-17+deb8u6 [23.2 kB]
Get:17 http://mirrordirector.raspbian.org/raspbian/ jessie/main x11proto-render-dev all 2:0.11.1-2 [20.8 kB]
Get:18 http://mirrordirector.raspbian.org/raspbian/ jessie/main libxrender-dev armhf 1:0.9.8-1 [38.8 kB]
Get:19 http://mirrordirector.raspbian.org/raspbian/ jessie/main libxcursor-dev armhf 1:1.1.14-1 [43.1 kB]
Get:20 http://mirrordirector.raspbian.org/raspbian/ jessie/main libxi-dev armhf 2:1.7.4-1 [231 kB]
Get:21 http://mirrordirector.raspbian.org/raspbian/ jessie/main x11proto-xinerama-dev all 1.2.1-2 [4,938 B]
Get:22 http://mirrordirector.raspbian.org/raspbian/ jessie/main libxinerama-dev armhf 2:1.1.3-1 [19.5 kB]
Get:23 http://mirrordirector.raspbian.org/raspbian/ jessie/main libxkbcommon-dev armhf 0.4.3-2 [145 kB]
Get:24 http://mirrordirector.raspbian.org/raspbian/ jessie/main libxrandr-dev armhf 2:1.4.2-1 [39.3 kB]
Get:25 http://mirrordirector.raspbian.org/raspbian/ jessie/main x11proto-scrnsaver-dev all 1.2.2-1 [25.0 kB]
Get:26 http://mirrordirector.raspbian.org/raspbian/ jessie/main libxss-dev armhf 1:1.2.2-1 [22.7 kB]
Get:27 http://mirrordirector.raspbian.org/raspbian/ jessie/main libsm-dev armhf 2:1.2.2-1 [33.5 kB]
Get:28 http://mirrordirector.raspbian.org/raspbian/ jessie/main libxt-dev armhf 1:1.1.4-1 [447 kB]
Get:29 http://mirrordirector.raspbian.org/raspbian/ jessie/main x11proto-video-dev all 2.3.2-1 [20.9 kB]
Get:30 http://mirrordirector.raspbian.org/raspbian/ jessie/main libxv-dev armhf 2:1.0.10-1 [46.2 kB]
Get:31 http://mirrordirector.raspbian.org/raspbian/ jessie/main libsdl2-dev armhf 2.0.2+dfsg1-6 [1,074 kB]
Get:32 http://mirrordirector.raspbian.org/raspbian/ jessie/main libsdl2-mixer-dev armhf 2.0.0+dfsg1-5 [80.4 kB]
Get:33 http://mirrordirector.raspbian.org/raspbian/ jessie/main libsdl2-net-dev armhf 2.0.0+dfsg1-2 [20.5 kB]
Get:34 http://mirrordirector.raspbian.org/raspbian/ jessie/main libtool all 2.4.2-1.11 [190 kB]
Fetched 4,789 kB in 10s (456 kB/s)                                             
Extracting templates from packages: 100%
Selecting previously unselected package libsdl2-2.0-0:armhf.
(Reading database ... 117055 files and directories currently installed.)
Preparing to unpack .../libsdl2-2.0-0_2.0.2+dfsg1-6_armhf.deb ...
Unpacking libsdl2-2.0-0:armhf (2.0.2+dfsg1-6) ..............................] 
Selecting previously unselected package libsdl2-mixer-2.0-0:armhf.
Preparing to unpack .../libsdl2-mixer-2.0-0_2.0.0+dfsg1-5_armhf.deb ...
Unpacking libsdl2-mixer-2.0-0:armhf (2.0.0+dfsg1-5) ...
Selecting previously unselected package libsdl2-net-2.0-0:armhf.
Preparing to unpack .../libsdl2-net-2.0-0_2.0.0+dfsg1-2_armhf.deb ...
Unpacking libsdl2-net-2.0-0:armhf (2.0.0+dfsg1-2) ...
Selecting previously unselected package libsigsegv2:armhf.
Preparing to unpack .../libsigsegv2_2.10-4_armhf.deb ...
Unpacking libsigsegv2:armhf (2.10-4) ...
Selecting previously unselected package m4.
Preparing to unpack .../archives/m4_1.4.17-4_armhf.deb ...
Unpacking m4 (1.4.17-4) ...
Selecting previously unselected package autoconf.
Preparing to unpack .../autoconf_2.69-8_all.deb ...
Unpacking autoconf (2.69-8) ...
Selecting previously unselected package autotools-dev.
Preparing to unpack .../autotools-dev_20140911.1_all.deb ...
Unpacking autotools-dev (20140911.1) ...
Selecting previously unselected package automake.
Preparing to unpack .../automake_1%3a1.14.1-4+deb8u1_all.deb ...
Unpacking automake (1:1.14.1-4+deb8u1) ...
Selecting previously unselected package libwayland-bin.
Preparing to unpack .../libwayland-bin_1.11.0-2_armhf.deb ...
Unpacking libwayland-bin (1.11.0-2) ...
Selecting previously unselected package libwayland-dev:armhf.
Preparing to unpack .../libwayland-dev_1.11.0-2_armhf.deb ...
Unpacking libwayland-dev:armhf (1.11.0-2) ...
Selecting previously unselected package libegl1-mesa-dev:armhf.
Preparing to unpack .../libegl1-mesa-dev_13.0.0-1+rpi1_armhf.deb ...
Unpacking libegl1-mesa-dev:armhf (13.0.0-1+rpi1) ...
Selecting previously unselected package libgles2-mesa-dev:armhf.
Preparing to unpack .../libgles2-mesa-dev_13.0.0-1+rpi1_armhf.deb ...
Unpacking libgles2-mesa-dev:armhf (13.0.0-1+rpi1) ...
Selecting previously unselected package libice-dev:armhf.
Preparing to unpack .../libice-dev_2%3a1.0.9-1_armhf.deb ...
Unpacking libice-dev:armhf (2:1.0.9-1) ...
Selecting previously unselected package libltdl-dev:armhf.
Preparing to unpack .../libltdl-dev_2.4.2-1.11_armhf.deb ...
Unpacking libltdl-dev:armhf (2.4.2-1.11) ...
Selecting previously unselected package libudev-dev:armhf.
Preparing to unpack .../libudev-dev_215-17+deb8u6_armhf.deb ...
Unpacking libudev-dev:armhf (215-17+deb8u6) ...
Selecting previously unselected package x11proto-render-dev.
Preparing to unpack .../x11proto-render-dev_2%3a0.11.1-2_all.deb ...
Unpacking x11proto-render-dev (2:0.11.1-2) ...
Selecting previously unselected package libxrender-dev:armhf.
Preparing to unpack .../libxrender-dev_1%3a0.9.8-1_armhf.deb ...
Unpacking libxrender-dev:armhf (1:0.9.8-1) ...
Selecting previously unselected package libxcursor-dev:armhf.
Preparing to unpack .../libxcursor-dev_1%3a1.1.14-1_armhf.deb ...
Unpacking libxcursor-dev:armhf (1:1.1.14-1) ...
Selecting previously unselected package libxi-dev.
Preparing to unpack .../libxi-dev_2%3a1.7.4-1_armhf.deb ...
Unpacking libxi-dev (2:1.7.4-1) ...
Selecting previously unselected package x11proto-xinerama-dev.
Preparing to unpack .../x11proto-xinerama-dev_1.2.1-2_all.deb ...
Unpacking x11proto-xinerama-dev (1.2.1-2) ...
Selecting previously unselected package libxinerama-dev:armhf.
Preparing to unpack .../libxinerama-dev_2%3a1.1.3-1_armhf.deb ...
Unpacking libxinerama-dev:armhf (2:1.1.3-1) ...
Selecting previously unselected package libxkbcommon-dev.
Preparing to unpack .../libxkbcommon-dev_0.4.3-2_armhf.deb ...
Unpacking libxkbcommon-dev (0.4.3-2) ...
Selecting previously unselected package x11proto-randr-dev.
Preparing to unpack .../x11proto-randr-dev_1.5.0-1_all.deb ...
Unpacking x11proto-randr-dev (1.5.0-1) ...
Selecting previously unselected package libxrandr-dev:armhf.
Preparing to unpack .../libxrandr-dev_2%3a1.4.2-1_armhf.deb ...
Unpacking libxrandr-dev:armhf (2:1.4.2-1) ...
Selecting previously unselected package x11proto-scrnsaver-dev.
Preparing to unpack .../x11proto-scrnsaver-dev_1.2.2-1_all.deb ...
Unpacking x11proto-scrnsaver-dev (1.2.2-1) ...
Selecting previously unselected package libxss-dev:armhf.
Preparing to unpack .../libxss-dev_1%3a1.2.2-1_armhf.deb ...
Unpacking libxss-dev:armhf (1:1.2.2-1) ...
Selecting previously unselected package libsm-dev:armhf.
Preparing to unpack .../libsm-dev_2%3a1.2.2-1_armhf.deb ...
Unpacking libsm-dev:armhf (2:1.2.2-1) ...
Selecting previously unselected package libxt-dev:armhf.
Preparing to unpack .../libxt-dev_1%3a1.1.4-1_armhf.deb ...
Unpacking libxt-dev:armhf (1:1.1.4-1) ...
Selecting previously unselected package x11proto-video-dev.
Preparing to unpack .../x11proto-video-dev_2.3.2-1_all.deb ...
Unpacking x11proto-video-dev (2.3.2-1) ...
Selecting previously unselected package libxv-dev:armhf.
Preparing to unpack .../libxv-dev_2%3a1.0.10-1_armhf.deb ...
Unpacking libxv-dev:armhf (2:1.0.10-1) ...
Selecting previously unselected package libsdl2-dev.
Preparing to unpack .../libsdl2-dev_2.0.2+dfsg1-6_armhf.deb ...
Unpacking libsdl2-dev (2.0.2+dfsg1-6) ...
Selecting previously unselected package libsdl2-mixer-dev:armhf.
Preparing to unpack .../libsdl2-mixer-dev_2.0.0+dfsg1-5_armhf.deb ...
Unpacking libsdl2-mixer-dev:armhf (2.0.0+dfsg1-5) ...
Selecting previously unselected package libsdl2-net-dev:armhf.
Preparing to unpack .../libsdl2-net-dev_2.0.0+dfsg1-2_armhf.deb ...
Unpacking libsdl2-net-dev:armhf (2.0.0+dfsg1-2) ...
Selecting previously unselected package libtool.
Preparing to unpack .../libtool_2.4.2-1.11_all.deb ...
Unpacking libtool (2.4.2-1.11) ...
Processing triggers for install-info (5.2.0.dfsg.1-6) ...
Processing triggers for man-db (2.7.0.2-5) ...
Setting up libsdl2-2.0-0:armhf (2.0.2+dfsg1-6) ...
Setting up libsdl2-mixer-2.0-0:armhf (2.0.0+dfsg1-5) ...
Setting up libsdl2-net-2.0-0:armhf (2.0.0+dfsg1-2) ...
Setting up libsigsegv2:armhf (2.10-4) ...
Setting up m4 (1.4.17-4) ...
Setting up autoconf (2.69-8) ...
Setting up autotools-dev (20140911.1) ...
Setting up automake (1:1.14.1-4+deb8u1) ...
update-alternatives: using /usr/bin/automake-1.14 to provide /usr/bin/automake (automake) in auto mode
Setting up libwayland-bin (1.11.0-2) ...
Setting up libwayland-dev:armhf (1.11.0-2) ...
Setting up libegl1-mesa-dev:armhf (13.0.0-1+rpi1) ...
Setting up libgles2-mesa-dev:armhf (13.0.0-1+rpi1) ...
Setting up libice-dev:armhf (2:1.0.9-1) ...
Setting up libltdl-dev:armhf (2.4.2-1.11) ...
Setting up libudev-dev:armhf (215-17+deb8u6) ...
Setting up x11proto-render-dev (2:0.11.1-2) ...
Setting up libxrender-dev:armhf (1:0.9.8-1) ...
Setting up libxcursor-dev:armhf (1:1.1.14-1) ...
Setting up libxi-dev (2:1.7.4-1) ...
Setting up x11proto-xinerama-dev (1.2.1-2) ...
Setting up libxinerama-dev:armhf (2:1.1.3-1) ...
Setting up libxkbcommon-dev (0.4.3-2) ...
Setting up x11proto-randr-dev (1.5.0-1) ...
Setting up libxrandr-dev:armhf (2:1.4.2-1) ...
Setting up x11proto-scrnsaver-dev (1.2.2-1) ...
Setting up libxss-dev:armhf (1:1.2.2-1) ...
Setting up libsm-dev:armhf (2:1.2.2-1) ...
Setting up libxt-dev:armhf (1:1.1.4-1) ...
Setting up x11proto-video-dev (2.3.2-1) ...
Setting up libxv-dev:armhf (2:1.0.10-1) ...
Setting up libsdl2-dev (2.0.2+dfsg1-6) ...
Setting up libsdl2-mixer-dev:armhf (2.0.0+dfsg1-5) ...
Setting up libsdl2-net-dev:armhf (2.0.0+dfsg1-2) ...
Setting up libtool (2.4.2-1.11) ...
Processing triggers for libc-bin (2.19-18+deb8u7) ...
pi@raspberrypi:~ $  mkdir -p ~/software/source
pi@raspberrypi:~ $ ~/software/source $ git clone git://github.com/chocolate-doom/chocolate-doom.git
bash: /home/pi/software/source: Is a directory
pi@raspberrypi:~ $ ~/software/source $ cd chocolate-doom
bash: /home/pi/software/source: Is a directory
pi@raspberrypi:~ $ ~/software/source/chocolate-doom $ ./autogen.sh
bash: /home/pi/software/source/chocolate-doom: No such file or directory
Update: It is now correctly working.
Interested in electronics and programming. Also listen to this: https://m.youtube.com/watch?v=lcR2pHRePm0
"Sometimes it is the people no one imagines anything of who do the things no-one can imagine" Alan Turing

10eo
Posts: 10
Joined: Thu Feb 16, 2017 11:51 pm

Re: How Do I Run Doom Faster in Dosbox On My Pi 3?

Mon Feb 20, 2017 2:24 pm

How do I run Chocolate Doom, now? I have the ultimate doom in my downloads folder. Is there any special commands I need to type in for chocolate doom to run with my iwad?
Interested in electronics and programming. Also listen to this: https://m.youtube.com/watch?v=lcR2pHRePm0
"Sometimes it is the people no one imagines anything of who do the things no-one can imagine" Alan Turing

10eo
Posts: 10
Joined: Thu Feb 16, 2017 11:51 pm

Re: How Do I Run Doom Faster in Dosbox On My Pi 3?

Mon Feb 20, 2017 4:26 pm

I got it working :D. But it is a slow as doom running under dosbox. But, I think setting the software renderer might help with this but which config file do I set it up in and is there a specific spot I need to put it?

Code: Select all

[WARNING: it looks like you are using a software GL implementation.
To improve performance, try setting force_software_renderer in your
configuration file/code]
Interested in electronics and programming. Also listen to this: https://m.youtube.com/watch?v=lcR2pHRePm0
"Sometimes it is the people no one imagines anything of who do the things no-one can imagine" Alan Turing

ktb
Posts: 1380
Joined: Fri Dec 26, 2014 7:53 pm

Re: How Do I Run Doom Faster in Dosbox On My Pi 3?

Mon Feb 20, 2017 5:54 pm

10eo wrote:But it is a slow as doom running under dosbox.
I really find that hard to believe.

However, I'm on kernel 4.9.9 and using the vc4-fkms-v3d overlay.

itsmedoofer
Posts: 359
Joined: Wed Sep 25, 2013 8:43 am

Re: How Do I Run Doom Faster in Dosbox On My Pi 3?

Tue Feb 21, 2017 12:54 pm

fruitoftheloom wrote:
10eo wrote:I guess chocolate doom isn't a package anymore. :(
Yes you are correct it is not in the repositories :oops:


Maybe try: https://www.chocolate-doom.org/wiki/ind ... _(generic)
Hmmm still showing in the debian repo, does that mean it's just missing from ours ?

https://packages.debian.org/jessie/chocolate-doom

User avatar
ulysess
Posts: 306
Joined: Thu Aug 02, 2012 6:35 am
Location: Spain
Contact: Website

Re: How Do I Run Doom Faster in Dosbox On My Pi 3?

Thu Feb 23, 2017 4:53 pm

Did you try my script here ?
Mis apuntes de...Raspberry Pi: http://misapuntesde.com
Google Docs RPi: http://goo.gl/Iwhbq

mej35ch
Posts: 1
Joined: Sat Feb 25, 2017 7:13 am

Re: How Do I Run Doom Faster in Dosbox On My Pi 3?

Sat Feb 25, 2017 7:48 am

Hi,
this is my 1st post on this forum. 2 days ago I got my Raspberry Pi 3 and I installed Raspbian. I saw Chocolate Doom is supported for my OS so I installed it as follows and everything works fine. This link works on Pi 2 and 3, probably on older versions too.
Link: http://www.knight-of-pi.org/doom-on-a-raspberry-pi-2-b/

cd ~
sudo apt-get update
sudo apt-get install libsdl1.2debian libsdl-image1.2 libsdl-mixer1.2 libsdl-mixer1.2-dev libsdl-net1.2 libsdl-net1.2-dev timidity.
mkdir Doom
cd Doom
sudo wget http://www.chocolate-doom.org/downloads ... 0.0.tar.gz
tar -xvf chocolate-doom-2.0.0.tar.gz
cd chocolate-doom-2.0.0
./configure
make
sudo make install
cd ..
sudo wget http://www.jbserver.com/downloads/games ... m1.wad.zip
sudo unzip doom1.wad.zip

To run the setup, type
chocolate-doom-setup -iwad DOOM1.WAD

To simply run Doom, type
chocolate-doom -iwad DOOM1.WAD

I hope this will be helpful for you!
Using Raspberry Pi 3 with custom Lego case and 80mm red LED fan.
Since RPi 2.

IBM Portable PC
Posts: 46
Joined: Sun Apr 26, 2015 10:18 am
Location: Melbourne, Australia

Re: How Do I Run Doom Faster in Dosbox On My Pi 3?

Mon May 29, 2017 12:33 am

10eo wrote:I got Doom working in Dosbox on my Pi 3 recently. But, it runs slow and I tried to increase the cpu cycles in Dosbox but it did nothing. I just want to play Doom at a appropriate speed on my Pi 3, but in the meantime I can play Wolf3d, Prince of Persia, and Rogue :D.
What settings did you use in dosbox.conf?

Ger_Pa
Posts: 56
Joined: Thu Mar 09, 2017 7:00 pm

Re: How Do I Run Doom Faster in Dosbox On My Pi 3?

Tue May 30, 2017 5:33 am

Try Crispy-Doom is a fork of Chocolate Doom, a bit more friendly if you are using a modern monitor.

Return to “Gaming”