Help getting Brutal Doom campaign hellonearthstarterpack + Duke3d expansions to work

edmaul69

@megafacehead so the really quick and dirty way would would be just create a .sh file in /home/pi/RetroPie/roms/ports/ , give it 0777 permissions and put the info one of us gave you in it. then if you restart emulationstation it will be in the ports section and it will boot the game. as long as you put the wad files in the places listed in the script we gave you. the only problem with doing it this way, you see all the loading script and dont get the option to use the config that pops up right after selecting the game.

to do it the correct way, do this:

put the doom2.wad in /home/pi/RetroPie/roms/ports/doom2/
put the brutalv20b.pk3, hellonearthstarterpack.wad, ExtraTextures.wad and DoomMetalVol4.wad in /home/pi/RetroPie/roms/ports/brutal/
sftp into the pi. i use winscp to do that. in the sftp program, go to /home/pi/RetroPie/roms/ports/
create a new file there called Brutal Doom.sh
inside that file put this:

#!/bin/bash
"/opt/retropie/supplementary/runcommand/runcommand.sh" 0 _SYS_ brutal

save the file. now right click on the file and go to properties. change the permissions to 0777
now go to /opt/retropie/configs/ and create a folder called brutal
inside that folder create a file called emulators.cfg
inside the emulators.cfg file add this:

default = "zdoom"
zdoom = "/opt/retropie/ports/zdoom/zdoom +set fullscreen 1 +set freelook 1 -iwad /home/pi/RetroPie/roms/ports/doom2/doom2.wad -file /home/pi/RetroPie/roms/ports/brutal/brutalv20b.pk3 -file /home/pi/RetroPie/roms/ports/brutal/hellonearthstarterpack.wad -file /home/pi/RetroPie/roms/ports/brutaldoom/ExtraTextures.wad"

save and restart emulationstation. now it should work.

note: you cant just create a .sh file on windows and copy it over. you can if you download notepad++ and create it in that program. easier to just do it inside the ftp program.

Edit: you dont need the DoomMetalVol4.wad while using hellonearthstarterpack.wad

mediamogul

@edmaul69

Edit: you dont need the DoomMetalVol4.wad while using hellonearthstarterpack.wad

Ah, I almost forgot about that. I tried disabling it and you are indeed correct. The DoomMetalVol4.wad isn't used in 'Hell on Earth' and is only meant to enhance 'Brutal Doom' when the original levels are being played.

edmaul69

@mediamogul i edited all my emulators.cfg to have a zdoom and a brutalzdoom option. You know how awesome brutal chex quest is? :D

mediamogul

@edmaul69

You know how awesome brutal chex quest is?

That's too funny. Give them Flemoids hell!

edmaul69

@mediamogul one question? Is there a way to add menu and menu item select to a joystick in zdoom?

mediamogul

@edmaul69

I'm not sure exactly what you mean. Are you talking about the ability to control the game menu from a controller?

edmaul69

@mediamogul yes.

mediamogul

@edmaul69

I don't think there's a default way to map the menu controls to the joystick. I do it through xboxdrv, using the right trigger as a modifier key. When pressed, the DPad becomes the up,down,left and right keyboard keys and buttons 'A' and 'B' become the enter and escape keys, allowing me to move forwards and backwards in the menu, as well as select options. I also have it set to bring up the menu with 'selct+x' and exit with 'select+start' to mirror RetroArch.

megafacehead

Warning long post, but i'm trying to 'pay it forward' by providing working examples of .sh files.

@backstander said

Also just to help clarify: The .sh "launch script" and the emulators.cfg file are 2 different ways to accomplish the same thing so you don't need to do both. >

Ah THANKYOU for this lil nugget of info. It really all started to make sense after this.

I've been a whizz(not like it's hard tho) at setting up gamelist.xml files for all other systems and adding video/marquee/image tags and so forth and everything makes sense but the ports setup is completely different.

I've gone with the .sh way of launching the port games, it just seemed more straight forward and just worked.

So we can tie this up with a neat little bow and others who might have the same problem can check in the future i'll provide my setup below.

doom.wad doom2.wad Plutonia.wad Tnt.wad in roms\ports\doom folder

brutalv20b.pk3 Extra Textures.wad hellonearthstarterpack.wad in roms\ports\brutal folder

separate zdoom.ini for brutal doom located in configs\ports\brutaldoom folder

hexen.wad hexdd.wad heretic.wad each in their own seperate folder named the same as wad in roms\ports\ (eg hexdd.wad in roms\ports\hexdd)

games that launch with lr-prboom
doom 1 (doom.sh)

#!/bin/bash
/opt/retropie/supplementary/runcommand/runcommand.sh 0 "/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-prboom/prboom_libretro.so --config /opt/retropie/configs/ports/doom/retroarch.cfg /home/pi/RetroPie/roms/ports/doom/doom.wad" "lr-prboom"

doom 2 (doom2.sh)

#!/bin/bash
/opt/retropie/supplementary/runcommand/runcommand.sh 0 "/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-prboom/prboom_libretro.so --config /opt/retropie/configs/ports/doom/retroarch.cfg /home/pi/RetroPie/roms/ports/doom/doom2.wad" "lr-prboom"

doom tnt (Tnt.sh)

#!/bin/bash
/opt/retropie/supplementary/runcommand/runcommand.sh 0 "/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-prboom/prboom_libretro.so --config /opt/retropie/configs/ports/doom/retroarch.cfg /home/pi/RetroPie/roms/ports/doom/tnt.wad" "lr-prboom"

doom plutonia (Plutonia.sh)

#!/bin/bash
/opt/retropie/supplementary/runcommand/runcommand.sh 0 "/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-prboom/prboom_libretro.so --config /opt/retropie/configs/ports/doom/retroarch.cfg /home/pi/RetroPie/roms/ports/doom/Plutonia.wad" "lr-prboom"

games that launch with zdoom
brutal doom (doombrutal.sh)

#!/bin/bash
/opt/retropie/ports/zdoom/zdoom +set fullscreen 1 +set freelook 1 -config /opt/retropie/configs/ports/brutaldoom/zdoom.ini -iwad /home/pi/RetroPie/roms/ports/doom/doom.wad -file /home/pi/RetroPie/roms/ports/brutal/brutalv20b.pk3

brutal doom 2 (doom2brutal.sh)

#!/bin/bash
/opt/retropie/ports/zdoom/zdoom +set fullscreen 1 +set freelook 1 -config /opt/retropie/configs/ports/brutaldoom/zdoom.ini -iwad /home/pi/RetroPie/roms/ports/doom/doom2.wad -file /home/pi/RetroPie/roms/ports/brutal/brutalv20b.pk3

brutal doom tnt (Tntbrutal.sh)

#!/bin/bash
/opt/retropie/ports/zdoom/zdoom +set fullscreen 1 +set freelook 1 -config /opt/retropie/configs/ports/brutaldoom/zdoom.ini -iwad /home/pi/RetroPie/roms/ports/doom/Tnt.wad -file /home/pi/RetroPie/roms/ports/brutal/brutalv20b.pk3

brutal doom plutonia (Plutoniabrutal.sh)

#!/bin/bash
/opt/retropie/ports/zdoom/zdoom +set fullscreen 1 +set freelook 1 -config /opt/retropie/configs/ports/brutaldoom/zdoom.ini -iwad /home/pi/RetroPie/roms/ports/doom/Plutonia.wad -file /home/pi/RetroPie/roms/ports/brutal/brutalv20b.pk3

brutal doom hell on earth (hellonearthbrutal.sh)

#!/bin/bash
/opt/retropie/ports/zdoom/zdoom +set fullscreen 1 +set freelook 1 -config /opt/retropie/configs/ports/brutaldoom/zdoom.ini -iwad /home/pi/RetroPie/roms/ports/doom/doom2.wad -file /home/pi/RetroPie/roms/ports/brutal/brutalv20b.pk3 /home/pi/RetroPie/roms/ports/brutal/hellonearthstarterpack.wad /home/pi/RetroPie/roms/ports/brutal/ExtraTextures.wad

hexen (zdoom) (hexenzdoom.sh)

#!/bin/bash
/opt/retropie/ports/zdoom/zdoom +set fullscreen 1 +set freelook 1 -iwad /home/pi/RetroPie/roms/ports/hexen/hexen.wad

hexen deathkings (hexddzdoom.sh)

#!/bin/bash
/opt/retropie/ports/zdoom/zdoom +set fullscreen 1 +set freelook 1 -iwad /home/pi/RetroPie/roms/ports/hexen/hexen.wad -file /home/pi/RetroPie/roms/ports/hexdd/hexdd.wad

heretic (hereticzdoom.sh)

#!/bin/bash
/opt/retropie/ports/zdoom/zdoom +set fullscreen 1 +set freelook 1 -iwad /home/pi/RetroPie/roms/ports/heretic/heretic.wad

Thankyou very much for your help, particularly backstander, mediamogul and edmaul69. Just a few remaining questions-

1.getting back to my first post, has anyone had any luck playing any of the duke3d expansions?eg duke caribbean life's a beach, duke nuclear winter and duke it out in dc??Again i have all the required files, .grp files for all the expanions for example, but don't know how to make them launch?

2.Can anyone provide a sample launch script on how to launch the 'h' doom games (heretic, hexen and hexen deathkings) using lr-prboom?As above i can launch them via gzdoom piece a piss but damned if i can create a working lr-prboom .sh file for any of them.
3.@mediamogul said

I don't think there's a default way to map the menu controls to the joystick. I do it through xboxdrv, using the right trigger as a modifier key. When pressed, the DPad becomes the up,down,left and right keyboard keys and buttons 'A' and 'B' become the enter and escape keys, allowing me to move forwards and backwards in the menu, as well as select options. I also have it set to bring up the menu with 'selct+x' and exit with 'select+start' to mirror RetroArch.

How on earth did u do do that?That would be awesome as it's the only downfall of zdoom on the retropie, needed to have a keyboard at the ready simply to launch/exit the game, save or otherwise access and navigate the menu in anyway.Could you perhaps provide a 'for dummies' way of how you managed to create your workaround.

Thanks again guys.

edmaul69

@megafacehead even though i post the info showing the wads in different folders per game i actually have them all in one folder myself. (All 45 games) I also do not keep them in ports myself because updating the pi would change the original doom game back to the shareware version. (Not sure if it still does) having them all in one folder makes making the config files easier. I use a .sh file and an emulators config file for every game. This allows to make more than one config for a game. So when i start a game, i can go into the runcommand and change between zdoom config and a brutal zdoom config of each game. Or pr-boom if i wanted.

mediamogul

@megafacehead

Could you perhaps provide a 'for dummies' way of how you managed to create your workaround.

I've written a step-by-step guide on how to use xboxdrv as a key-mapping solution. Other than going over the necessary steps in detail, there's really no way to simplify it. Don't let it scare you off though. Try it out, ask questions and just like anything else, before long you'll find that you've got a handle on it.

megafacehead

@mediamogul said
I've written a step-by-step guide on how to use xboxdrv as a key-mapping solution.

Oh neato!This should be a cakewalk, a nice guide and everything, i'll just click that link and...

alt text

Oh my god lol.

The more i read on this forum the more i'm convinced it's either populated by mensa members OR i'm that stupid i must be missing a chromosome.

I'm sorry mediamogul it looks like you've put a lot of work into that but it's super intimidating.Your setup sounds awesome though, this one specifically-

@mediamogul said in I do it through xboxdrv, using the right trigger as a modifier key. When pressed, the DPad becomes the up,down,left and right keyboard keys and buttons 'A' and 'B' become the enter and escape keys, allowing me to move forwards and backwards in the menu, as well as select options. I also have it set to bring up the menu with 'selct+x' and exit with 'select+start' to mirror RetroArch.

That one specifically.From what i can tell, brutaldoom/gzdoom really only needs two extra buttons to become fully manageable with a controller.You need to bind a button to ESC to access the menu, and go back a step after going further into a sub menu, and another button to act as ENTER, to confirm menu options.After initial setup you really shouldn't need any dpad buttons to affect any slider controls.You also need a single keystroke letter assigned to a button to name any manually saved games, but again, i can live without that, the autosaves beofre the start of each map should suffice.

To this end, i have tried my best to follow your guide and have come up with this.I downloaded xboxbdrv through the setup menu, and enabled it.

I did read step 1 of your guide but i am actually using a real 360 controller for this whole thing, so i assumed it didnt apply??It seemed it was only a necessary step in case you were using a ps3/logitech or some other controller that wasnt specifically a 360 controller.

And, rather then work through the console, i prefer to create and modify files using notepad++ on my computer thats connected to the retropie on a network.All im trying to do is assign the guide button as esc and the start button as enter when zdoom launches, and then revert back to normal when i quit a zdoom game.

So anyways i created the file runcommand-onstart.sh in configs/all folder which consists of

if [ "$1" = "ZDoom" ]
then
sudo killall > /dev/null 2>&1 xboxdrv
sudo /opt/retropie/supplementary/xboxdrv/bin/xboxdrv > /dev/null 2>&1 \
	--evdev /dev/input/by-id/* \
	--silent \
	--detach-kernel-driver \
	--deadzone 4000 \
	--mimic-xpad \
	--ui-buttonmap guide=KEY_ESC,start=KEY_ENTER \
&
fi

then through the console on the retropie ran the command
chmod +x /opt/retropie/configs/all/runcommand-onstart.sh

after that,

i also created the file runcommand-onend.sh in the same folder (configs/all) which consist of

sudo killall > /dev/null 2>&1 xboxdrv
/opt/retropie/supplementary/xboxdrv/bin/xboxdrv > /dev/null 2>&1 \
	--evdev /dev/input/by-id/* \
	--silent \
	--detach-kernel-driver \
	--deadzone 4000 \
	--mimic-xpad \
	--evdev-absmap ABS_*=x1,ABS_*=y1,ABS_*=x2,ABS_*=y2,ABS_*=lt,ABS_*=rt,ABS_*=dpad_x,ABS_*=dpad_y \
	--evdev-keymap BTN_*=a,BTN_*=b,BTN_*=x,BTN_*=y,BTN_*=lb,BTN_*=rb,BTN_*=tl,BTN_*=tr,BTN_*=guide,BTN_*=back,BTN_*=start \
	&

then through the console on the retropie ran the command
chmod +x /opt/retropie/configs/all/runcommand-onend.sh

As you can tell i mainly just copied and pasted the examples you had in your guide, deleted some stuff i didn't need changing and modified the buttons i wanted to replace.

Needless to say it doesn't work, obviously some stupid fault of mine.

So yeah, im trying to not completely be a helpless baby bird here, i did try but yeah, 'do or do not, there is no try'- and it appears i did not.

mediamogul

@megafacehead

To be fair, Major Toht wasn't the most handsome guy before he opened the Ark. Plus if you watch the movie in reverse, he ends up OK and always has a clever way to hang his coat.

I'm sorry mediamogul it looks like you've put a lot of work into that but it's super intimidating.

No need to apologize. It took me a while to wrap my head around it before I could even write the guide. I just kept looking at it and experimenting until it all worked.

i created the file runcommand-onstart.sh in configs/all folder which consists of:

I can see a couple of issues here. First of all:

if [ "$1" = "ZDoom" ]

should be:

if [ "$1" = "zdoom" ]

Also, the examples given in the guide that refer to * should be replaced the controller information obtained from evtest in the first step. so, looking at your command:

	--evdev /dev/input/by-id/* \

Should contain your own specific id. Other than that, everything looks to be OK.

megafacehead

Hey i'm back from outer space.

I just can't get this to work mediamogul, this whole time, on and off obviously, since my last post in this thread, i have tried to make this damned thing work.I'd have a crack for a few hours, throw my hands up in frustration and just go 'f**k it' but then a day or two later i come back with a clear head and rinse and repeat.

I have followed your guide to a T, the only thing that's different from my earlier posts is i'm trying to get this to work with a wii u pro controller, connected to the pi via a bluetooth dongle (wii u pro mayflash adaptor).Essentially, all i'm trying to do is make the select(back), home(guide) and start(start) button on the wii u pro controller register as key b, key enter and key esc respectively, when brutaldoom launches (will eventually wan't this to work with duke3d as well via eduke32 but let's focus on this for now).

I have installed xboxdrv, then disabled it.

i have the following in my /opt/retropie/configs/all/runcommand-onstart.sh

if [ "$1" = "zdoom" ]
then
sudo /opt/retropie/supplementary/xboxdrv/bin/xboxdrv \
	--evdev /dev/input/by-id/usb-HJZ_Controller_1189A89-event-joystick \
	--silent \
	--detach-kernel-driver \
	--deadzone 4000 \
	--trigger-as-button \
	--four-way-restrictor \
	--mimic-xpad \
	--evdev-absmap ABS_X=x1,ABS_Y=y1,ABS_RX=x2,ABS_RY=y2,ABS_TL2=lt,ABS_TR2=rt,ABS_HAT0X=dpad_x,ABS_HAT0Y=dpad_y \
	--evdev-keymap BTN_EAST=a,BTN_SOUTH=b,BTN_WEST=x,BTN_NORTH=y,BTN_TL=lb,BTN_TR=rb,BTN_THUMBL=tl,BTN_THUMBR=tr,BTN_SELECT=back,BTN_MODE=guide,BTN_START=start \
	--ui-buttonmap guide=KEY_B,start=KEY_ENTER,back=KEY_ESC \
	-- \
&
fi

It simply won't work.

(this is my /opt/retropie/configs/all/runcommand-onend.sh

sudo killall xboxdrv

I don't get any error messages or anything, i just load any version of brutal doom(or any game for that matter) and the buttons i have assigned to keyboard strokes
(specifically guide=KEY_B,start=KEY_ENTER,back=KEY_ESC)
simply don't register.
I've tried using the

--evdev /dev/input/event*

setting, where event* is event2, but no difference.

Why is this so diffcult, so god damned obtuse??

Like seriously all jokes aside i'm willing to drop some money into someones paypal account if we can get this sorted.Any mercs for hire?

If i take into account how many hours i've spent on this and charge it out even at minimum wage i've theoretically wasted hundreds of dollars!

mediamogul

@megafacehead

As I stated early on, the best way to learn something like this is to first experiment and then to come back and ask questions as you run into obstacles. I could have given you several ways to troubleshoot your setup and will do so here if you're still interested. What's going to help the most though, is to take a step back and calm down, as you're obviously worked up over the issue. Troubleshooting any technical problem becomes exponentially more difficult when frustrated. I see it's been seven hours since your post, so hopefully you've already cooled down.

Moving forward, there are two things I'd like you to do. First, Launch 'Brutal Doom' and then once it loads, exit it completely. Afterwards, open /dev/shm/runcommand.info and post the contents here. Secondly, let's find out if there's anything wrong with the xboxdrv command itself. It appears to be formatted correctly, but any errors it may contain will surface by entering the isolated command into the command line and executing it. If any errors do present themselves, post them here afterwards. Using the example you gave above, the isolated command will be:

sudo /opt/retropie/supplementary/xboxdrv/bin/xboxdrv \
	--evdev /dev/input/by-id/usb-HJZ_Controller_1189A89-event-joystick \
	--silent \
	--detach-kernel-driver \
	--deadzone 4000 \
	--trigger-as-button \
	--four-way-restrictor \
	--mimic-xpad \
	--evdev-absmap ABS_X=x1,ABS_Y=y1,ABS_RX=x2,ABS_RY=y2,ABS_TL2=lt,ABS_TR2=rt,ABS_HAT0X=dpad_x,ABS_HAT0Y=dpad_y \
	--evdev-keymap BTN_EAST=a,BTN_SOUTH=b,BTN_WEST=x,BTN_NORTH=y,BTN_TL=lb,BTN_TR=rb,BTN_THUMBL=tl,BTN_THUMBR=tr,BTN_SELECT=back,BTN_MODE=guide,BTN_START=start \
	--ui-buttonmap guide=KEY_B,start=KEY_ENTER,back=KEY_ESC

megafacehead

I don't know if i've mentioned it before but i pretty much do all (possible) editing/modifying on the pi via a networked connection to my pc, and edit any files with notepad++.

I see alot of people throw around terms like 'just fttp into it' or 'use samba share' and then they've lost me.Surely most people would work on their pi's this way and not through command lines right?

It seems as though most guides are geared towards the latter, maybe that's how these linux heads have always done it, but with the pi becoming more mainstream, and the mainstream using their windows pcs to 'get er done', like they've always done, whether it be installing mods for pc games or getting some unwieldy sound blaster driver to work, this is something that should be considered more by people writing these guides perhaps.

Anyways, with that in mind, i'm already lost at the first hurdle, where is this runcommand.info file? I have no 'dev' folder, using the pi via a networked connection i have 4 folders, bios-configs-roms-splashscreens as i'm sure your aware.

So yeah.Point 1 is stalled.

Onto the next point, i did follow your advice and using the command line ran the following

sudo /opt/retropie/supplementary/xboxdrv/bin/xboxdrv \

and it spat out an error

(as a side note this is another reason i don't like using command lines how the hell do i post the results here, besides typing it out??meh)

--error--
Error couldn't claim the usb interface: LIBUSB_ERROR_BUSY
Try to run 'rmmod xpad' and then xboxdrv again or start xboxdrv with the option --detach -kernel-driver.

I ran the command

sudo rmmod xpad

and that appears to have done nothing.I have the detach kernel driver setting already in the runcommand-onstart.sh

Any ideas?
p.s. did i also mention all the work i've been doing getting this to work and even posting these replies has been done with a 1.5 yr old climbing all over me saying 'trucks' over and over begging me to watch youtube truck videos for the umpteenth time?

mediamogul

@megafacehead

You can access /dev/shm/runcommand.info over SSH/SFTP by first enabling SSH and then using something like Putty (Windows) or CyberDuck (Mac). From there you can view the file with notepad++.

The error you got from the command itself would seem to indicate that there's already a driver (xwiimote) in play, preventing xboxdrv from grabbing the controller. there are two ways to solve this. You can either disable xwiimote entirely and use xboxdrv as you're main driver, or you can unload xwiimote on launch in the runcommand-onstart script and then reload it on exit with the runcommand-onexit script. I believe the latter should be possible, although I've never tried it and the prior should just be a matter of uninstalling xwiimote and following the xboxdrv guide like any other controller.

megafacehead

@mediamogul

I don't have xwiimote installed...?

At least i don't think i do.I have never manually installed that from anywhere.

The wii u pro controller connects to the pi via 2 ways.

Onboard bluetooth-which detects the wii u pro controller as itself, but is buggy and has random ghost inputs.

That's why i instead connect it to the pi via a wireless dongle called a mayflash wii u pro adaptor. It connects to the pi via a usb cable, which then connects to the wii u pro controller via a wireless sync.

The adaptor then 'lies' to the pi and tell it that the wii u pro controller is actually a xbox 360 wireless controller.

At no point has this 'xwiimote' ever come into play.That i know of.

edmaul69

@megafacehead you might want to seperate the words "adapter." and "It" in your last post. You accidently created a link to some odd website.

mediamogul

@megafacehead

I don't have xwiimote installed...?

Ah, OK. It was just a guess based on the error. Still, something had already grabbed the controller at the time you ran the command. Try restarting the Pi completely right before you try again. Also, is this the only controller connected to your setup?