Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
fabian

PrBoom+ 2.6.66 (Jun 20, 2023)

Recommended Posts

That means there was an error in parsing the UMAPINFO lump; note that MAPINFO and UMAPINFO have different syntax.

Share this post


Link to post
16 minutes ago, JadingTsunami said:

 

It's easier if you post your UMAPINFO contents.

MAP E1M1
    levelname = E1F1
    next = E1M2
    nextsecret = E1M10
    music = D_GET
    intermusic = D_INTER

Share this post


Link to post

You need braces, like:

MAP E1M1 {
    levelname = E1F1
    next = E1M2
    nextsecret = E1M10
    music = D_GET
    intermusic = D_INTER

}

Share this post


Link to post
15 minutes ago, Redoom said:

MAP E1M1
    levelname = E1F1
    next = E1M2
    nextsecret = E1M10
    music = D_GET
    intermusic = D_INTER

 

In addition to what @Shepardus wrote, don't forget you need quotes ("") around elements that have quotes in the documentation. In your case all the values should have quotes around them.

 

E.g.:

levelname = "E1F1"

 

Share this post


Link to post

I hate to ask this, but does anyone have a more recent Windows build? I'd compile it myself but I'm not technologically literate enough.

Share this post


Link to post
2 hours ago, maxmanium said:

I hate to ask this, but does anyone have a more recent Windows build? I'd compile it myself but I'm not technologically literate enough.

Assuming you have a GitHub account and you're on 64-bit Windows (process is similar on 32-bit):

  1. Go here: https://github.com/coelckers/prboom-plus/actions
  2. Click the latest workflow run
  3. Scroll down and download the artifact called vs_x64
  4. Extract the archive's contents to a folder of your choosing
  5. Go here: https://github.com/coelckers/prboom-plus/releases/tag/windows_dependencies
  6. Download the latest file (currently windows_dependencies_v4.zip)
  7. Inside this archive, navigate to dependencies_x64\bin and extract its contents to the previous folder
  8. Done! Optionally you can delete the .pdb files if you want.

Hope this helps! :)

Share this post


Link to post
3 minutes ago, Andromeda said:

Assuming you have a GitHub account and you're on 64-bit Windows (process is similar on 32-bit):

  1. Go here: https://github.com/coelckers/prboom-plus/actions
  2. Click the latest workflow run
  3. Scroll down and download the artifact called vs_x64
  4. Extract the archive's contents to a folder of your choosing
  5. Go here: https://github.com/coelckers/prboom-plus/releases/tag/windows_dependencies
  6. Download the latest file (currently windows_dependencies_v4.zip)
  7. Inside this archive, navigate to dependencies_x64\bin and extract its contents to the previous folder
  8. Done! Optionally you can delete the .pdb files if you want.

Hope this helps! :)

 

Wow, I didn't even know this was a thing. So github just builds it after each commit or what?

Share this post


Link to post
3 minutes ago, maxmanium said:

Wow, I didn't even know this was a thing. So github just builds it after each commit or what?

Indeed, you can get a build of each commit using this method.

Share this post


Link to post
Spoiler

image.png.2acd7135468beec0c19f54466a87ecc6.png

Sorry, gotta stop running those workflow now -- gotta keep the nice round number :P

Share this post


Link to post

I came across a weird issue while setting up a bunch of PWAD autoload stuff, but I'm not sure if it's a bug or something on my end. I have D2DEHFIX.DEH in the doom-all folder, which works fine regardless of anything else autoloaded... except for Eternal Doom. I have a wad by NightFright with a widescreen status bar and a DEHACKED patch, but the patch doesn't interfere with any frames, and I can't figure out why D2DEHFIX.DEH isn't loading:

 

Spoiler

sdfgdgf.png.28da88eb6dd2b93e94826c88772c6d44.png

 

Share this post


Link to post
3 hours ago, Giant Jumbo Jellyfish said:

Is there a fix planned for tracker module support?

For some reason DBP 36 (which features module music in multiple formats) crashes on the title screen using the latest CI build, yet it works on my laptop running Linux building it from the same source, and dsda-doom (on Windows) also works. Seems to be specific to how the PrB+ builds are generated or the dependencies used...

 

2 hours ago, Redoom said:

<youtube embed>

This was fixed a long time ago, update to 2.6um or later.

Share this post


Link to post

so how do i use this port on linux? im new to linux in general and i want to play some doom on it do i have to compile the port myself?

Share this post


Link to post
1 minute ago, omalefico32x said:

so how do i use this port on linux? im new to linux in general and i want to play some doom on it do i have to compile the port myself?

You have to compile it. 

Share this post


Link to post
Just now, Lol 6 said:

You have to compile it. 

ah shit well there's a first time for everything i guess

Share this post


Link to post
20 minutes ago, omalefico32x said:

so how do i use this port on linux? im new to linux in general and i want to play some doom on it do i have to compile the port myself?

Maybe the output from the CI workflow could be used (e.g. this)? I'm not sure what distribution that's for (edit: it's compiled against Ubuntu 20.04), though, and you'd need the dependencies anyway, so maybe you're better off building it yourself. You can refer to this guide written for compiling on Windows using MSYS2 - building on Linux is largely the same process, though how you install the necessary dependencies will differ depending on your distribution. (edit: for Linux you can also refer to the INSTALL guide in the repo)

 

Maybe it'd be feasible to build an AppImage that'd work across distributions...

Edited by Shepardus

Share this post


Link to post

I tried to launch the development binaries in Ubuntu 20.04 and I couldn't, so in the end I compiled them myself... and they work

Share this post


Link to post

Is anyone else having problems with screenshotting ? I set the bind and when i try to take a screenshot it just gives the message: "m_screenshot: error writing screenshot"

Share this post


Link to post
25 minutes ago, unkles4m said:

Is anyone else having problems with screenshotting ? I set the bind and when i try to take a screenshot it just gives the message: "m_screenshot: error writing screenshot"

Try setting "screenshot_dir" in the config to a directory and make sure you have write access to it.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×