I got stuck trying to find all the secrets on Abaddon's Void in SIGIL. I already know or spoiled all the secrets in the original Ultimate Doom episodes so I want to be able to find them all properly in SIGIL like I did last December when I was playing through No Rest For The Living.

It annoys me how many of the Doom levels have unreachable secret sectors though. Especially in Thy Flesh Consumed.

View this comment - View article - View full comments

That went well.

View this comment - View article - View full comments

I have still not gotten around to finishing The Ultimate Doom yet.

View this comment - View article - View full comments

Wait, I thought this was a Sandy map?


And then there is Glitch Pinky:

View this comment - View article - View full comments

Quoting: x_wingI ended up finishing the game (no idea about the story, I should have start by the first one :P) and didn't get any crash. I used the default Mesa packages from Ubuntu 18.04 (i.e. Mesa 19.2.8). Are you sure that the issue is related to Mesa?

All I can say is that the game crashing for me was solved when I was still able to compile Mesa as described in that forum thread, and that my experiences do match those of other players. The thread I am referencing is literally titled "Steam version of Penumbra" so I doubt it is due to my Desura copy.

Requiem's plot is always going to be out there, but yes, you would be missing out on some the character moments.

View this comment - View article - View full comments

Wanted something familiar so I am doing an Ultra-Violence run of The Ultimate Doom through Crispy Doom at the moment.



It is honestly easier than these screenshots might suggest. :tongue:

View this comment - View article - View full comments

Quoting: x_wing

Quoting: HamishFor what it is worth, I found with Requiem that the game will crash when you pick up the first audio log from Eloff Carpenter.

I've installed the game and finished the snow level (I'm now in the Alien facility... if I can call it that way XD). You get the crash when you open the log of the first level?

Yeah, it seems that what exactly triggers the game to crash is variable. I have had it crash at different points with different Mesa versions.

View this comment - View article - View full comments

Yeah, same result as before sadly.

Project name: mesa
Build started at 2020-07-07T11:28:20.925677
Main binary: /usr/bin/python
Build Options: -Db_lto=false -Db_pie=true -Db_ndebug=true -Dplatforms=x11,wayland,drm,surfaceless -Ddri-drivers=i915,i965,r100,r200,nouveau -Dgallium-drivers=r300,r600,radeonsi,nouveau,virgl,svga,swrast,iris -Dvulkan-drivers=amd,intel -Dvulkan-overlay-layer=true -Dvulkan-device-select-layer=true -Dswr-arches=avx,avx2 -Ddri3=true -Degl=true -Dgallium-extra-hud=true -Dgallium-nine=true -Dgallium-omx=disabled -Dgallium-opencl=icd -Dgallium-va=true -Dgallium-vdpau=true -Dgallium-xa=true -Dgallium-xvmc=false -Dgbm=true -Dgles1=false -Dgles2=true -Dglvnd=true -Dglx=dri -Dlibunwind=true -Dllvm=true -Dlmsensors=true -Dosmesa=gallium -Dshared-glapi=true -Dvalgrind=false -Dprefix=/usr -Dlibdir=/usr/lib32 -Dlibexecdir=lib -Dsbindir=bin -Dauto_features=enabled -Dbuildtype=plain -Dwrap_mode=nodownload '--native-file crossfile.ini'
None of 'PKG_CONFIG_PATH' are defined in the environment, not changing global flags.
None of 'PKG_CONFIG_PATH' are defined in the environment, not changing global flags.
Project name: mesa
Project version: 20.1.2
Using 'CC' from environment with value: 'gcc -m32'
Using 'CFLAGS' from environment with value: '-O0'
Using 'LDFLAGS' from environment with value: '-Wl,-O0,--sort-common,--as-needed,-z,relro,-z,now'
Using 'CPPFLAGS' from environment with value: '-D_FORTIFY_SOURCE=2'

Thanks for the suggestions regardless x_wing.

View this comment - View article - View full comments

That output is from my trying to use the DEBUG_CFLAGS in makepkg.conf, not from when I was exporting my own values in the PKGBUILD. Here is the relevant Meson log for that:
Project name: mesa
Project version: 20.1.2
Using 'CC' from environment with value: 'gcc -m32'
Using 'CFLAGS' from environment with value: '-O0'
Using 'LDFLAGS' from environment with value: '-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now'
Using 'CPPFLAGS' from environment with value: '-D_FORTIFY_SOURCE=2'
None of 'CC_LD' are defined in the environment, not changing global flags.

And Penumbra still crashes.

View this comment - View article - View full comments

crossfile.ini is created from the PKGBUILD file of the lib32-mesa Arch package:
https://git.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/lib32-mesa [External Link]

The contents of crossfile.ini in a generated package are as follows:
[binaries]
llvm-config = '/usr/bin/llvm-config32'

As for the CFLAGS, that is being grabbed from what is defined in makepkg.conf as used by the Arch Build System. Setting the 'debug' option in the PKGBUILD makes its append DEBUG_CFLAGS which is where I was instructed to add the "-O0" flag in the linked Frictional Games forum thread:
https://www.frictionalgames.com/forum/thread-54134-post-363860.html#pid363860 [External Link]

Back in April and May adding the "-O0" flag to DEBUG_CFLAGS in makepkg.conf and toggling the 'debug' and '!strip' options in the lib32-mesa PKGBUILD did do the trick. Now doing so causes it to complain about being unable to determine the dynamic linker.

Here is the relevant parts of my makepkg.conf file:
 #-- Compiler and Linker Flags
CPPFLAGS="-D_FORTIFY_SOURCE=2"
CFLAGS="-march=x86-64 -mtune=generic -O3 -pipe -fno-plt"
CXXFLAGS="-march=x86-64 -mtune=generic -O3 -pipe -fno-plt"
LDFLAGS="-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now"
#-- Make Flags: change this for DistCC/SMP systems
#MAKEFLAGS="-j2"
#-- Debugging flags
DEBUG_CFLAGS="-g -fvar-tracking-assignment -O0"
DEBUG_CXXFLAGS="-g -fvar-tracking-assignments -O0"

I have tried exporting my own CFLAGS in the PKGBUILD containing just the "-O0" flag and with that I can get the lib32-mesa package to build, but Penumbra will still crash when using these builds. I have also tried using the Meson c_args option to set the "-O0" flag to no good effect. I have also tried setting the various "-mno-sse" flags which again do nothing.

View this comment - View article - View full comments