OBSIDIAN - Please Check https://obsidian-level-maker.github.io/ For Future Updates

[Abba Zabba]

Thanks for your help. I replaced the offending lua file until the next release. Had a feeling it was either the fauna or the custom trees module.

[vokar]

Running with Brutal Doom I get "Too many DECORATE translations" after a few minutes in game. I've got mostly default settings, with some adjustments to monster count.

Not sure if this is a known issue or not.

[dasho]

I think any of the Obsidian devs who play Brutal-type stuff use Project Brutality, but either way I'm not sure if there's anything we can do to address such an issue if it's caused by the combination of an Obsidian map and an external gameplay mod that's not under our control.

[vokar]

Agreed. I wonder if it's because BD has so many decorates that doom overloads a buffer of some sort when run on Obsidian built maps with lots of prefabbed stuff, pillars, details, etc. I'll run a few more test when I get a chance, and if anyone else has thoughts or time to test as well that'd be awesome.

Either way, this is a great tool!

[marco.nadal.75]

If anyone in this thread gets particularly good results with Obsidian, please post your CONFIG.txt in this thread!

I am combining Obsidian's -> output.wad with DRLA (Doom Rogue Like Arsenal), with this load order:

name=DooM RogueLike https://www.youtube.com/watch?v=R2QuFcck48U
portname=GZDoom
iwad=doom2.wad
pwads=..\WADS\music\HQPSXMUS.WAD
cblood.pk3
..\WADS\monsters\LegenDoomLite_4.1.pk3
..\WADS\monsters\mk-champions[20210309].pk3
..\WADS\TC\DoomRL-Arsenal\DoomRL_Arsenal_1.1.5.pk3
..\WADS\TC\DoomRL-Arsenal\DoomRL_CMMClasses_0.6a.pk3
..\WADS\TC\DoomRL-Arsenal\DoomRL_Monsters_Beta_7.3.pk3
..\WADS\CorruptionCards-v2.0.pk3
..\WADS\TC\DoomRL-Arsenal\RPG-Lite-DoomRLA.pk3
..\WADS\TC\DoomRL-Arsenal\zetashop.pk3
..\WADS\gore\nashgore.pk3
doors-stay-open.pk3
livereverb.pk3
steve_flashlight_2018.02.12.pk7
..\Obsidian-beta19\output.wad

Of course, playing this way makes the first few maps VERY hard,
until you build up your stats a bit, as those random monsters can certainly take you by surprise.

Somebody made a megawad with Obsidian and edited is a bit, then uploaded it as a showcase of what it is capable of:
https://www.moddb.com/games/doom-ii/add ... expedition

Some people freeze at a blank canvas, or can't think of anything when starting out, so using an Obsidian map as a starting point can be good!

[marco.nadal.75]

Oh I forgot in my previous post, that was GZDooM 4.7.1 64-bit. Other versions don't seem to work with that mod combo.

[roundtree]

Hello, I just want to say thank you for making Obsidian! I run Linux 99% of the time now, and I've had no problem compiling past versions of Obsidian, but I have to tell you... the last two versions seem to have corrupted source code. They won't compile at all. I keep getting error messages saying I need to have fltk 1.3.0 or newer, but I've had that exact version for a while now. What about Obsidian has changed in the last two versions that requires an update to my build environment?

The other thing is yesterday after I had the problem, I updated my g++, gcc, cmake (compiled the new one) clang and reinstalled fltk. Obsidian will not compile at all. Gets a LOT of errors during the process, mostly stuff about fread, pragma, and fgets. No idea what any of that means. I don't understand code 1%. Also, during the first Cmake command in the compilation process, it says that it found fltk! It just doesn't work anymore during the compiling. =(

I run a youtube channel, and compiling obsidian for linux is one of my featured videos. (I think I'm the only one making them) I've already got 3 videos about it. So if you know how to help me, I will post a video showing people how to compile it properly for Linux. (I am running Linux Mint 20.3 if that helps)


Thanks again,

-roundtree

[dasho]

Just to scope the problem, when you say last two versions, do you mean (for example) Beta 18 and 19, or do you mean the last couple of iterations of the current unstable branch (Beta 20)? We recently made some changes to CMake along the lines of adding presets and such, but this is the first time I've heard of compilation issues to such an extent, and we do have regular Linux users on the contributor team.

If you could post some output from the compilation process, hopefully we can figure out what's going on.

[Phytolizer]

Hello, I just want to say thank you for making Obsidian! I run Linux 99% of the time now, and I've had no problem compiling past versions of Obsidian, but I have to tell you... the last two versions seem to have corrupted source code. They won't compile at all. I keep getting error messages saying I need to have fltk 1.3.0 or newer, but I've had that exact version for a while now. What about Obsidian has changed in the last two versions that requires an update to my build environment?

The other thing is yesterday after I had the problem, I updated my g++, gcc, cmake (compiled the new one) clang and reinstalled fltk. Obsidian will not compile at all. Gets a LOT of errors during the process, mostly stuff about fread, pragma, and fgets. No idea what any of that means. I don't understand code 1%. Also, during the first Cmake command in the compilation process, it says that it found fltk! It just doesn't work anymore during the compiling. =(

I run a youtube channel, and compiling obsidian for linux is one of my featured videos. (I think I'm the only one making them) I've already got 3 videos about it. So if you know how to help me, I will post a video showing people how to compile it properly for Linux. (I am running Linux Mint 20.3 if that helps)


Thanks again,

-roundtree

Hi, I'm one of the Obsidian contributors who uses Linux. Can you please inform me what these commands output?

Code: Select all

> g++ --version
> cmake --version
> apt info libfltk1.3-dev

Also, could you provide an example compiler error in full?

In turn:

I am able to compile the stable (obsidian), unstable (obsidian-unstable), and release (Obsidian-Current-Stable) versions with no errors and few warnings using the following toolchain:

Code: Select all

> g++ --version
g++ (GCC) 11.2.0
> cmake --version
cmake version 3.22.2
> pacman -Qi fltk
Name            : fltk
Version         : 1.3.8-1
Description     : Graphical user interface toolkit for X
Architecture    : x86_64
URL             : https://www.fltk.org/
Licenses        : custom:FLTK
Groups          : None
Provides        : libfltk_images.so=1.3-64  libfltk_gl.so=1.3-64  libfltk_forms.so=1.3-64  libfltk.so=1.3-64
Depends On      : gcc-libs  glibc  hicolor-icon-theme  libfontconfig.so=1-64  libglvnd  libjpeg-turbo  libpng  libx11  libxcursor  libxext  libxfixes  libxft  libxinerama  libxrender
Optional Deps   : None
Required By     : None
Optional For    : None
Conflicts With  : None
Replaces        : None
Installed Size  : 6.81 MiB
Packager        : David Runge <dvzrv@archlinux.org>
Build Date      : Tue 28 Dec 2021 10:14:33 AM CST
Install Date    : Mon 28 Feb 2022 08:06:54 PM CST
Install Reason  : Explicitly installed
Install Script  : No
Validated By    : Signature

Here is my build process:
For the newer versions (obsidian and obsidian-unstable):

Code: Select all

> cmake --preset dist
> cmake --build --preset dist

For the release version:

Code: Select all

> cmake -B build -DCMAKE_BUILD_TYPE=Release
> cmake --build build

Please let me know so we can get to the bottom of this quickly

[roundtree]

Just to scope the problem, when you say last two versions, do you mean (for example) Beta 18 and 19, or do you mean the last couple of iterations of the current unstable branch (Beta 20)? We recently made some changes to CMake along the lines of adding presets and such, but this is the first time I've heard of compilation issues to such an extent, and we do have regular Linux users on the contributor team.

If you could post some output from the compilation process, hopefully we can figure out what's going on.

Thank you for getting back to me. I'm glad you didn't say, "Linux? There's your problem!" =) To answer your question, I am referring to the last couple of iterations of the current unstable branch, not beta 18 and 19. I have recompiled several more times after learning (about 15 minutes ago) how to properly redirect stdout and stderr. Can't believe I didn't know how, basic stuff! Anyway, I put the output from the first cmake command in output1.txt. I put the complete output from the second cmake command in output2.txt. And if you would just like to read the errors only, I have output those to error.txt.

[dasho]

Right on...it looks like the only true error (as in, the only reason it's failing to compile from your output) is that it is failing the version check for FLTK. Could you post the output of running

apt info libfltk1.3-dev

From your terminal?

[roundtree]

Sure, no problem. But my apt command did not have an info function, but it does have a version function, so I typed 'apt version libfltk1.3-dev' and the output was:

1.3.4-10build1

[dasho]

Right on, I'm going to fire up a Mint VM and try to sort it out, as we haven't been able to recreate it on our own boxes yet. Might be a bit, though.

[roundtree]

Ok, and sorry to make you go to all the trouble! Thank you, and I think I'm going to do the same thing over here. Dying to know if its my build environment, if I messed it up somehow? It will probably take me a little while too.

[dasho]

I was able to compile it on Mint 20.3 without complaints...here were my steps:

From a clean install and root terminal-
apt update/upgrade to get system up to speed
apt install g++ binutils make cmake
apt install libfltk1.3-dev libxft-dev libxinerama-dev libjpeg-dev libpng-dev libfontconfig1-dev
apt install flex clang-tidy
apt install git

Then from a regular terminal-
git clone https://github.com/dashodanger/obsidian
cd obsidian
cmake --preset dist .
cmake --build . -j6

After that, I was able to execute obsidian as usual. I also report the same version of FLTK when I check the apt versioning.