Doom Legacy - Doom Split-screen Source port

Solid One

@quicksilver So, what about force DL to run without dispmanx on the doomlegacy.sh file opened by EmulationStation, and solve the video scaling problem by changing DL default resolution from 640x480 to the default one used by RetroPie (1280x720 or 1920x1080)? That should work. And if you need lower resolutions, you could run tvservice through runcommand-start / runcommand-end, to change resolution and revert it afterwards.

quicksilver

@Solid-One changing the game res to 1920x1080 and fullscreen mode worked for me. Windowed mode at 1920x1080 was glitchy and didn't work right. Thanks for the advice.

Do I still need to apply your patch to get analog sticks to work on my Xbox 360 controller. It doesn't seem like they are being detected.

tpo1990

@quicksilver No it doesn't look like it is running from the terminal with dispmanx.

If it works with changing to 1920x1080 and fullscreen, then that could be considered a workaround until the scaling issue on the Pi 4 gets solved.

Solid One

@quicksilver No need. The latest version already includes the changes mentioned above. However, you'll still need to create your "bindjoyaxis" settings manually, for allowing moving / aiming / strafing through both analog sticks.

About controllers' detection, make sure your controller is plugged before opening DL (since there's no hotplug support yet). And if you have multiple controllers, make sure you're using the first one for menu navigation, because the others won't navigate through menus properly.

Govik

Please help! I just installed the script and it seemed to compile fine. It has the doom.sh and other XXXX.sh files in the ports folder. I can start the games from emulation station and it brings me to the main menu and I can select options. As soon as I go to start a new game, either singleplayer or 2 players, it crashes back to emulation station. I ran the script from the command line to see if it would indicate any errors but nothing just crashes back to the command line with no error messages showing.

Not sure if there are any logs anywhere.

Looks like I have RetroPie 4.5.15 (stretch). Does this ONLY work with 4.6 (buster)?

BTW amazing work! Was playing SplitWolf and thought I need some split-screen Doom for my retropie and stumbled upon this.

Solid One

@Govik Are you sure that, when running from the command line, no message shows up regardless of its nature? By Default, DL should show up a lot of messages in the screen, just like most sourceports, and the error should show up just fine.

Take a look at the log file which shows up in this window. According to it, errors should be logged in /tmp/runcommand.log (the file path may differ, depending of the RetroPie version you're using):
alt text

tpo1990

@Govik Thanks for the appreciation. It should also work on (stretch) how ever do take note that there might be some difference when running the game such as the resolution not fitting correctly between Stretch and Buster versions.

If it doesnt' run it could be caused by the scriptmodule not being able to build a binary (doomlegacy) file that the runcommand need in order to be successfully able to run the game.

You can try uninstalling from Retropie-setup and then reinstall it again.

AdamBeGood

I accidentally pulled the power lead out of my Pi during an initial install of this, and now I am having a problem.

I tried to do the install again, and before that I selected "Delete Build Directory" or something similar in RetroPie-Setup.

I am trying to install from Source, and the build just sits at this line for a very long time.

There is no temp/build/doomlegacy folder when I log into WinSCP once I am returned to RetroPie-Setup. There is definitely a difference in the amount of lines I am seeing now compared to the initial aborted install, but I can't see the evidence of any files or directories that I can delete to "reset" this now.

When I am kicked back to RetroPie-Setup, the error is (/home/pi/RetroPie-Setup/tmp/build/doomlegacy/bin not found)

Log is here: https://pastebin.com/gbXA41qJ

Solid One

@AdamBeGood Try compiling something else, just to see if the "power leading out" isn't affecting other parts of your OS.

I'm saying this because I've already got similar problems in the past, when I forced a shutdown of my PC during a source compilation. After this, I was unable to compile anything, and I had to format my OS in order to solve this problem.

Although it happened years ago and probably it won't happen again on newer Ubuntu / Debian versions, maybe something like that happened on your side, so test it to see if it's indeed ok after shutting your RPi down.

mitu

@AdamBeGood

...

= = = = = = = = = = = = = = = = = = = = =
Getting sources for 'doomlegacy' : Doom Legacy - Enhanced splitscreen port of the official DOOM source
= = = = = = = = = = = = = = = = = = = = =


bzip2: Compressed file ends unexpectedly;
	perhaps it is corrupted?  *Possible* reason follows.
bzip2: Inappropriate ioctl for device
	Input file = (stdin), output file = (stdout)

this means the sources haven't been downloaded or the download is corrupt.

AdamBeGood

@mitu Is there anything I can do to resolve that? Or is it at the source's end?

Edit: Actually looking at this again (note to self: read the entire thread before you post a comment), it seems that maybe @quicksilver had this problem in May and it resolved after a while. So I will try again tomorrow

@quicksilver said in Doom Legacy - Doom Split-screen Source port:

So it looks like the problem is that I cant connect to https://liquidtelecom.dl.sourceforge.net/ im not sure what the issue is. If I try from my PC it just says it took to long to respond.

AdamBeGood

@Solid-One Thanks for the tip, I did try this. Both source and binary worked absolutely fine for other cores, I did worry that I had done something horrific to my Pi initially, but it seems happy enough apart from the ongoing issue with this install.

Edit: This still isn't working, is there anywhere on my Pi that something could be stored from the previous install that is being referenced here and causing trouble? There is nothing in the tmp/build folder.

Solid One

@AdamBeGood Did you manage to grab DL files manually from Sourceforge, and then tried compiling it? If true, what is the last messages from the terminal, after running "make" command?

If the compiling process is successful, a "doomlegacy" binary file should be created in the same folder as the source. The scriptmodule, then, copies it to another folder, in order to make it work on EmulationStation. Can you at least confirm if it indeed compiled fine and the binary was created?

AdamBeGood

@Solid-One said in Doom Legacy - Doom Split-screen Source port:

Did you manage to grab DL files manually from Sourceforge, and then tried compiling it?

@Solid-One I wouldn't even know how to go about doing that. Let me have a look through this thread and see if I can work out how I would do that.

I have literally just been going "Install from Source" within RetroPie-Setup up to this point.

If I look at the scriptmodule, does that have the steps within it? Maybe I'll have a look at that.

Solid One

@AdamBeGood Anyway, when you choose "Install from Source" in RetroPie-Setup, the scriptmodule will basically do the following steps:

Go to sourceforge, where DL source is hosted, and download the source files from the latest version (1.48.4);
After source download is complete, it'll unpack the file and compile DL from source, which will create the DL binaries if the compiling process finishes succesfully;
With the DL binaries in hands. The scriptmodule finally installs it on RetroPie by copying the files to a folder that RetroPie recognizes, and finally the DL shortcut will be added in EmulationStation's PC games section.

By the errors you reported above, I assume that the scriptmodule is having trouble downloading the files from sourceforge. That is a recurring problem that seems to happen only on sourceforge's end. Maybe we could revise the scriptmodule in order to grab the files from other place besides sourceforge, such as tpo1990's github.

It even happened already with other members in this post, such as this one from quicksilver. He solved it by editing the scriptmodule file and changing the URL where sourceforge is downloaded, and then running it again.

Anyway, as a workaround, try following the instructions from quicksilver in the link above. It should work.

AdamBeGood

@Solid-One That works! The Port itself doesn't seem to work very well yet, and I only have Doom Shareware as an option despite having all the WADs in place in the Doom directory. But I haven't looked at this properly yet, and the change to the location within the Script Module worked a treat. Thank you!