SLADE Discussion - Latest: v3.2.0 (12/April/2022)

Any utility that assists in the creation of mods, assets, etc, go here. For example: Ultimate Doom Builder, Slade, WadSmoosh, Oblige, etc.
Forum rules
The Projects forums are ONLY for YOUR PROJECTS! If you are asking questions about a project, either find that project's thread, or start a thread in the General section instead.

Got a cool project idea but nothing else? Put it in the project ideas thread instead!

Projects for any Doom-based engine (especially 3DGE) are perfectly acceptable here too.

Please read the full rules for more details.
Gez
 
 
Posts: 17689
Joined: Fri Jul 06, 2007 3:22 pm

Re: SLADE Discussion - Latest: v3.1.13 (01/Jun/2021)

Post by Gez »

Enjay wrote:Is there a way to tell Slade what an Unknown lump is beyond just viewing it as Hex or Text?

I have a few single graphics that are actually in a ZDoom font format (from a time when it wasn't possible to simply print a PNG to the screen). Slade classifies these as uknown. So, is there a way for me to tell Slade that it's a font (or any other format lump for that matter)?
Yeah. Open the console first and use the "type" console command with them selected.

If you enter it without a parameter, it should print to the console a big ol' unsorted list of all known lump types. So you can scroll through and try to find which one fits your need. If you know what you want, you can use it directly, e.g. "type gfx_flat" to make SLADE consider the selected lumps to be flats.

SLADE will then try to validate that these could be what you tell them it is, and if that validation fails, the type will not be changed. In case it's a problem in the validator, you can add the "force" parameter to well, force the change anyway. E.g. "type gfx_flat force".
marco.nadal.75 wrote:Does anyone remember which of SKY1 SKY2 SKY3 gets assigned to which MAP range?
IIRC, SKY1 is used on MAP01-MAP11, SKY2 on MAP12-MAP20, and SKY3 on MAP21-MAP32.
User avatar
Kinsie
Posts: 7333
Joined: Fri Oct 22, 2004 9:22 am
Graphics Processor: nVidia with Vulkan support
Location: MAP33

Re: SLADE Discussion - Latest: v3.1.13 (01/Jun/2021)

Post by Kinsie »

Since we can view and convert Quake-format graphics lumps and texture WADs, is there any chance of being able to convert to those formats? A lot of Quake 1 tools are sadly pretty outdated, and it'd be nice to kick them to the curb.
User avatar
NeuralStunner
 
 
Posts: 12301
Joined: Tue Jul 21, 2009 12:04 pm
Preferred Pronouns: He/Him
Graphics Processor: nVidia (Modern GZDoom)
Location: capital N, capital S, no space

Re: SLADE Discussion - Latest: v3.1.13 (01/Jun/2021)

Post by NeuralStunner »

The GFX format is absurdly simple, too.

Adding to this, I'd like to be able to export entire directories of lumps (with structure). Perhaps even a tool to unpack an entire archive.
pfred1x
Posts: 11
Joined: Wed Oct 18, 2017 12:59 pm

Re: SLADE Discussion - Latest: v3.1.12 (26/May/2020)

Post by pfred1x »

JPL wrote:Hi, I'm having trouble compiling SLADE latest on my Elementary (Ubuntu-derived) system. I get this error when I run cmake:

Code: Select all

-- cotire 1.7.9 loaded.
-- wx-config used is: /usr/bin/wx-config
-- wxWidgets version is: 3.0.4
-- gtk version is: 2
CMake Error at /usr/share/cmake-3.10/Modules/FindPackageHandleStandardArgs.cmake:137 (message):
  Could NOT find Lua (missing: LUA_LIBRARIES LUA_INCLUDE_DIR)
Call Stack (most recent call first):
  /usr/share/cmake-3.10/Modules/FindPackageHandleStandardArgs.cmake:378 (_FPHSA_FAILURE_MESSAGE)
  /usr/share/cmake-3.10/Modules/FindLua.cmake:193 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
  src/CMakeLists.txt:108 (find_package)
I followed the "compiling on Ubuntu" instructions on the wiki, but they don't say anything about installing Lua libs, what else do I need?
I just compiled Slade on Debian Bullseye and this is the ldd output

$ ldd ./slade
linux-vdso.so.1 (0x00007ffffc6ab000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007fb53c406000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 (0x00007fb53c3f3000)
libwx_gtk3u_aui-3.1.so.5 => /usr/local/lib/libwx_gtk3u_aui-3.1.so.5 (0x00007fb53c353000)
libwx_gtk3u_gl-3.1.so.5 => /usr/local/lib/libwx_gtk3u_gl-3.1.so.5 (0x00007fb53c338000)
libwx_gtk3u_stc-3.1.so.5 => /usr/local/lib/libwx_gtk3u_stc-3.1.so.5 (0x00007fb53c0bb000)
libwx_gtk3u_propgrid-3.1.so.5 => /usr/local/lib/libwx_gtk3u_propgrid-3.1.so.5 (0x00007fb53bfb5000)
libwx_gtk3u_webview-3.1.so.5 => /usr/local/lib/libwx_gtk3u_webview-3.1.so.5 (0x00007fb53bf85000)
libwx_gtk3u_core-3.1.so.5 => /usr/local/lib/libwx_gtk3u_core-3.1.so.5 (0x00007fb53b74c000)
libwx_baseu_net-3.1.so.5 => /usr/local/lib/libwx_baseu_net-3.1.so.5 (0x00007fb53b6ed000)
libwx_baseu-3.1.so.5 => /usr/local/lib/libwx_baseu-3.1.so.5 (0x00007fb53b46c000)
libfreeimage.so.3 => /lib/x86_64-linux-gnu/libfreeimage.so.3 (0x00007fb53b3b1000)
libsfml-system.so.2.5 => /lib/x86_64-linux-gnu/libsfml-system.so.2.5 (0x00007fb53b3a3000)
libsfml-audio.so.2.5 => /lib/x86_64-linux-gnu/libsfml-audio.so.2.5 (0x00007fb53b383000)
libsfml-window.so.2.5 => /lib/x86_64-linux-gnu/libsfml-window.so.2.5 (0x00007fb53b35b000)
libsfml-network.so.2.5 => /lib/x86_64-linux-gnu/libsfml-network.so.2.5 (0x00007fb53b33f000)
libftgl.so.2 => /lib/x86_64-linux-gnu/libftgl.so.2 (0x00007fb53b309000)
libOpenGL.so.0 => /lib/x86_64-linux-gnu/libOpenGL.so.0 (0x00007fb53b2dd000)
libGLX.so.0 => /lib/x86_64-linux-gnu/libGLX.so.0 (0x00007fb53b2a9000)
libGLU.so.1 => /lib/x86_64-linux-gnu/libGLU.so.1 (0x00007fb53b237000)
libGLEW.so.2.1 => /lib/x86_64-linux-gnu/libGLEW.so.2.1 (0x00007fb53b18b000)
libcurl-gnutls.so.4 => /lib/x86_64-linux-gnu/libcurl-gnutls.so.4 (0x00007fb53b0f3000)
liblua5.4.so.0 => /lib/x86_64-linux-gnu/liblua5.4.so.0 (0x00007fb53b0b0000)
libmpg123.so.0 => /lib/x86_64-linux-gnu/libmpg123.so.0 (0x00007fb53b04f000)
libfmt.so.7 => /lib/x86_64-linux-gnu/libfmt.so.7 (0x00007fb53b016000)
libgtk-3.so.0 => /lib/x86_64-linux-gnu/libgtk-3.so.0 (0x00007fb53a862000)
libfluidsynth.so.2 => /lib/x86_64-linux-gnu/libfluidsynth.so.2 (0x00007fb53a78e000)
libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fb53a5c1000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fb53a47d000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fb53a463000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fb53a441000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fb53a27a000)
libgdk-3.so.0 => /lib/x86_64-linux-gnu/libgdk-3.so.0 (0x00007fb53a175000)
libgobject-2.0.so.0 => /lib/x86_64-linux-gnu/libgobject-2.0.so.0 (0x00007fb53a11b000)
libGL.so.1 => /lib/x86_64-linux-gnu/libGL.so.1 (0x00007fb53a094000)
libEGL.so.1 => /lib/x86_64-linux-gnu/libEGL.so.1 (0x00007fb53a07f000)
libwayland-egl.so.1 => /lib/x86_64-linux-gnu/libwayland-egl.so.1 (0x00007fb53a07a000)
libwayland-client.so.0 => /lib/x86_64-linux-gnu/libwayland-client.so.0 (0x00007fb53a067000)
libgio-2.0.so.0 => /lib/x86_64-linux-gnu/libgio-2.0.so.0 (0x00007fb539e89000)
libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x00007fb539d5a000)
libwebkit2gtk-4.0.so.37 => /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37 (0x00007fb536693000)
libjavascriptcoregtk-4.0.so.18 => /lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18 (0x00007fb534df9000)
libpangocairo-1.0.so.0 => /lib/x86_64-linux-gnu/libpangocairo-1.0.so.0 (0x00007fb534de6000)
libpango-1.0.so.0 => /lib/x86_64-linux-gnu/libpango-1.0.so.0 (0x00007fb534d94000)
libcairo.so.2 => /lib/x86_64-linux-gnu/libcairo.so.2 (0x00007fb534c6f000)
libgdk_pixbuf-2.0.so.0 => /lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x00007fb534c49000)
libX11.so.6 => /lib/x86_64-linux-gnu/libX11.so.6 (0x00007fb534b06000)
libXxf86vm.so.1 => /lib/x86_64-linux-gnu/libXxf86vm.so.1 (0x00007fb534900000)
libSM.so.6 => /lib/x86_64-linux-gnu/libSM.so.6 (0x00007fb5348f3000)
libnotify.so.4 => /lib/x86_64-linux-gnu/libnotify.so.4 (0x00007fb5348e9000)
libXtst.so.6 => /lib/x86_64-linux-gnu/libXtst.so.6 (0x00007fb5346e3000)
libpangoft2-1.0.so.0 => /lib/x86_64-linux-gnu/libpangoft2-1.0.so.0 (0x00007fb5346ca000)
libfontconfig.so.1 => /lib/x86_64-linux-gnu/libfontconfig.so.1 (0x00007fb534684000)
libpng16.so.16 => /lib/x86_64-linux-gnu/libpng16.so.16 (0x00007fb53464a000)
libjpeg.so.62 => /lib/x86_64-linux-gnu/libjpeg.so.62 (0x00007fb5345c4000)
libtiff.so.5 => /lib/x86_64-linux-gnu/libtiff.so.5 (0x00007fb53453e000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fb534538000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007fb534510000)
libjxrglue.so.0 => /lib/x86_64-linux-gnu/libjxrglue.so.0 (0x00007fb5342ee000)
libopenjp2.so.7 => /lib/x86_64-linux-gnu/libopenjp2.so.7 (0x00007fb53428f000)
libraw.so.20 => /lib/x86_64-linux-gnu/libraw.so.20 (0x00007fb534183000)
libwebpmux.so.3 => /lib/x86_64-linux-gnu/libwebpmux.so.3 (0x00007fb534177000)
libwebp.so.6 => /lib/x86_64-linux-gnu/libwebp.so.6 (0x00007fb53410e000)
libIlmImf-2_5.so.25 => /lib/x86_64-linux-gnu/libIlmImf-2_5.so.25 (0x00007fb533e1f000)
libHalf-2_5.so.25 => /lib/x86_64-linux-gnu/libHalf-2_5.so.25 (0x00007fb533dda000)
libIex-2_5.so.25 => /lib/x86_64-linux-gnu/libIex-2_5.so.25 (0x00007fb533d6c000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fb533d61000)
libopenal.so.1 => /lib/x86_64-linux-gnu/libopenal.so.1 (0x00007fb533c78000)
libvorbisenc.so.2 => /lib/x86_64-linux-gnu/libvorbisenc.so.2 (0x00007fb533bcd000)
libvorbisfile.so.3 => /lib/x86_64-linux-gnu/libvorbisfile.so.3 (0x00007fb533bc2000)
libvorbis.so.0 => /lib/x86_64-linux-gnu/libvorbis.so.0 (0x00007fb533b95000)
libogg.so.0 => /lib/x86_64-linux-gnu/libogg.so.0 (0x00007fb533b86000)
libFLAC.so.8 => /lib/x86_64-linux-gnu/libFLAC.so.8 (0x00007fb533b47000)
libXrandr.so.2 => /lib/x86_64-linux-gnu/libXrandr.so.2 (0x00007fb53393c000)
libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x00007fb533914000)
libfreetype.so.6 => /lib/x86_64-linux-gnu/libfreetype.so.6 (0x00007fb533851000)
libGLdispatch.so.0 => /lib/x86_64-linux-gnu/libGLdispatch.so.0 (0x00007fb533797000)
libnghttp2.so.14 => /lib/x86_64-linux-gnu/libnghttp2.so.14 (0x00007fb53376a000)
libidn2.so.0 => /lib/x86_64-linux-gnu/libidn2.so.0 (0x00007fb533749000)
librtmp.so.1 => /lib/x86_64-linux-gnu/librtmp.so.1 (0x00007fb53372a000)
libssh2.so.1 => /lib/x86_64-linux-gnu/libssh2.so.1 (0x00007fb5336f5000)
libpsl.so.5 => /lib/x86_64-linux-gnu/libpsl.so.5 (0x00007fb5336e1000)
libnettle.so.8 => /lib/x86_64-linux-gnu/libnettle.so.8 (0x00007fb533697000)
libgnutls.so.30 => /lib/x86_64-linux-gnu/libgnutls.so.30 (0x00007fb533497000)
libgssapi_krb5.so.2 => /lib/x86_64-linux-gnu/libgssapi_krb5.so.2 (0x00007fb533444000)
libldap_r-2.4.so.2 => /lib/x86_64-linux-gnu/libldap_r-2.4.so.2 (0x00007fb5333ee000)
liblber-2.4.so.2 => /lib/x86_64-linux-gnu/liblber-2.4.so.2 (0x00007fb5333dd000)
libbrotlidec.so.1 => /lib/x86_64-linux-gnu/libbrotlidec.so.1 (0x00007fb5333cf000)
libgmodule-2.0.so.0 => /lib/x86_64-linux-gnu/libgmodule-2.0.so.0 (0x00007fb5333c7000)
libXi.so.6 => /lib/x86_64-linux-gnu/libXi.so.6 (0x00007fb5333b5000)
libXfixes.so.3 => /lib/x86_64-linux-gnu/libXfixes.so.3 (0x00007fb5333ad000)
libcairo-gobject.so.2 => /lib/x86_64-linux-gnu/libcairo-gobject.so.2 (0x00007fb5333a1000)
libatk-1.0.so.0 => /lib/x86_64-linux-gnu/libatk-1.0.so.0 (0x00007fb533377000)
libatk-bridge-2.0.so.0 => /lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0 (0x00007fb533340000)
libepoxy.so.0 => /lib/x86_64-linux-gnu/libepoxy.so.0 (0x00007fb53320f000)
libfribidi.so.0 => /lib/x86_64-linux-gnu/libfribidi.so.0 (0x00007fb5331f3000)
libharfbuzz.so.0 => /lib/x86_64-linux-gnu/libharfbuzz.so.0 (0x00007fb53310b000)
libjack.so.0 => /lib/x86_64-linux-gnu/libjack.so.0 (0x00007fb5330ba000)
libasound.so.2 => /lib/x86_64-linux-gnu/libasound.so.2 (0x00007fb532fbd000)
libpulse-simple.so.0 => /lib/x86_64-linux-gnu/libpulse-simple.so.0 (0x00007fb532fb6000)
libsndfile.so.1 => /lib/x86_64-linux-gnu/libsndfile.so.1 (0x00007fb532f31000)
libSDL2-2.0.so.0 => /lib/x86_64-linux-gnu/libSDL2-2.0.so.0 (0x00007fb532da5000)
libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x00007fb532d50000)
libreadline.so.8 => /lib/x86_64-linux-gnu/libreadline.so.8 (0x00007fb532cf9000)
libinstpatch-1.0.so.2 => /lib/x86_64-linux-gnu/libinstpatch-1.0.so.2 (0x00007fb532c37000)
/lib64/ld-linux-x86-64.so.2 (0x00007fb53d7d5000)
libXinerama.so.1 => /lib/x86_64-linux-gnu/libXinerama.so.1 (0x00007fb532c30000)
libXcursor.so.1 => /lib/x86_64-linux-gnu/libXcursor.so.1 (0x00007fb532c23000)
libXcomposite.so.1 => /lib/x86_64-linux-gnu/libXcomposite.so.1 (0x00007fb532c1e000)
libXdamage.so.1 => /lib/x86_64-linux-gnu/libXdamage.so.1 (0x00007fb532c19000)
libxkbcommon.so.0 => /lib/x86_64-linux-gnu/libxkbcommon.so.0 (0x00007fb532bd6000)
libwayland-cursor.so.0 => /lib/x86_64-linux-gnu/libwayland-cursor.so.0 (0x00007fb532bcd000)
libXext.so.6 => /lib/x86_64-linux-gnu/libXext.so.6 (0x00007fb532bb6000)
libffi.so.7 => /lib/x86_64-linux-gnu/libffi.so.7 (0x00007fb532baa000)
libmount.so.1 => /lib/x86_64-linux-gnu/libmount.so.1 (0x00007fb532b4d000)
libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 (0x00007fb532b21000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x00007fb532b07000)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007fb532a92000)
libwpe-1.0.so.1 => /lib/x86_64-linux-gnu/libwpe-1.0.so.1 (0x00007fb532a87000)
libWPEBackend-fdo-1.0.so.1 => /lib/x86_64-linux-gnu/libWPEBackend-fdo-1.0.so.1 (0x00007fb532a72000)
libxml2.so.2 => /lib/x86_64-linux-gnu/libxml2.so.2 (0x00007fb5328c4000)
libsqlite3.so.0 => /lib/x86_64-linux-gnu/libsqlite3.so.0 (0x00007fb532781000)
libxslt.so.1 => /lib/x86_64-linux-gnu/libxslt.so.1 (0x00007fb53273f000)
libwoff2dec.so.1.0.2 => /lib/x86_64-linux-gnu/libwoff2dec.so.1.0.2 (0x00007fb532730000)
libharfbuzz-icu.so.0 => /lib/x86_64-linux-gnu/libharfbuzz-icu.so.0 (0x00007fb53272b000)
libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 (0x00007fb53260b000)
libgstapp-1.0.so.0 => /lib/x86_64-linux-gnu/libgstapp-1.0.so.0 (0x00007fb5325f9000)
libgstbase-1.0.so.0 => /lib/x86_64-linux-gnu/libgstbase-1.0.so.0 (0x00007fb532579000)
libgstreamer-1.0.so.0 => /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 (0x00007fb532430000)
libgstpbutils-1.0.so.0 => /lib/x86_64-linux-gnu/libgstpbutils-1.0.so.0 (0x00007fb5323f0000)
libgstaudio-1.0.so.0 => /lib/x86_64-linux-gnu/libgstaudio-1.0.so.0 (0x00007fb532372000)
libgsttag-1.0.so.0 => /lib/x86_64-linux-gnu/libgsttag-1.0.so.0 (0x00007fb532332000)
libgstvideo-1.0.so.0 => /lib/x86_64-linux-gnu/libgstvideo-1.0.so.0 (0x00007fb532279000)
libgstgl-1.0.so.0 => /lib/x86_64-linux-gnu/libgstgl-1.0.so.0 (0x00007fb5321fd000)
libgstfft-1.0.so.0 => /lib/x86_64-linux-gnu/libgstfft-1.0.so.0 (0x00007fb5321f0000)
libwebpdemux.so.2 => /lib/x86_64-linux-gnu/libwebpdemux.so.2 (0x00007fb5321e8000)
libsoup-2.4.so.1 => /lib/x86_64-linux-gnu/libsoup-2.4.so.1 (0x00007fb532149000)
libenchant-2.so.2 => /lib/x86_64-linux-gnu/libenchant-2.so.2 (0x00007fb53213b000)
libsecret-1.so.0 => /lib/x86_64-linux-gnu/libsecret-1.so.0 (0x00007fb5320db000)
libtasn1.so.6 => /lib/x86_64-linux-gnu/libtasn1.so.6 (0x00007fb5320c5000)
libhyphen.so.0 => /lib/x86_64-linux-gnu/libhyphen.so.0 (0x00007fb5320be000)
libwayland-server.so.0 => /lib/x86_64-linux-gnu/libwayland-server.so.0 (0x00007fb5320a5000)
libmanette-0.2.so.0 => /lib/x86_64-linux-gnu/libmanette-0.2.so.0 (0x00007fb532075000)
libseccomp.so.2 => /lib/x86_64-linux-gnu/libseccomp.so.2 (0x00007fb532052000)
libicui18n.so.67 => /lib/x86_64-linux-gnu/libicui18n.so.67 (0x00007fb531d4c000)
libicuuc.so.67 => /lib/x86_64-linux-gnu/libicuuc.so.67 (0x00007fb531b63000)
libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 (0x00007fb531aae000)
libthai.so.0 => /lib/x86_64-linux-gnu/libthai.so.0 (0x00007fb531aa1000)
libpixman-1.so.0 => /lib/x86_64-linux-gnu/libpixman-1.so.0 (0x00007fb5319f6000)
libxcb-shm.so.0 => /lib/x86_64-linux-gnu/libxcb-shm.so.0 (0x00007fb5319f1000)
libxcb.so.1 => /lib/x86_64-linux-gnu/libxcb.so.1 (0x00007fb5319c6000)
libxcb-render.so.0 => /lib/x86_64-linux-gnu/libxcb-render.so.0 (0x00007fb5319b7000)
libXrender.so.1 => /lib/x86_64-linux-gnu/libXrender.so.1 (0x00007fb5317ab000)
libICE.so.6 => /lib/x86_64-linux-gnu/libICE.so.6 (0x00007fb53178d000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007fb531784000)
libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 (0x00007fb531755000)
libzstd.so.1 => /lib/x86_64-linux-gnu/libzstd.so.1 (0x00007fb53167a000)
libjbig.so.0 => /lib/x86_64-linux-gnu/libjbig.so.0 (0x00007fb53146a000)
libdeflate.so.0 => /lib/x86_64-linux-gnu/libdeflate.so.0 (0x00007fb53144e000)
libjpegxr.so.0 => /lib/x86_64-linux-gnu/libjpegxr.so.0 (0x00007fb531218000)
liblcms2.so.2 => /lib/x86_64-linux-gnu/liblcms2.so.2 (0x00007fb5311b5000)
libgomp.so.1 => /lib/x86_64-linux-gnu/libgomp.so.1 (0x00007fb531175000)
libImath-2_5.so.25 => /lib/x86_64-linux-gnu/libImath-2_5.so.25 (0x00007fb53115b000)
libIlmThread-2_5.so.25 => /lib/x86_64-linux-gnu/libIlmThread-2_5.so.25 (0x00007fb531151000)
libsndio.so.7.0 => /lib/x86_64-linux-gnu/libsndio.so.7.0 (0x00007fb53113f000)
libunistring.so.2 => /lib/x86_64-linux-gnu/libunistring.so.2 (0x00007fb530fbd000)
libhogweed.so.6 => /lib/x86_64-linux-gnu/libhogweed.so.6 (0x00007fb530f74000)
libgmp.so.10 => /lib/x86_64-linux-gnu/libgmp.so.10 (0x00007fb530ef1000)
libp11-kit.so.0 => /lib/x86_64-linux-gnu/libp11-kit.so.0 (0x00007fb530dbd000)
libkrb5.so.3 => /lib/x86_64-linux-gnu/libkrb5.so.3 (0x00007fb530ce3000)
libk5crypto.so.3 => /lib/x86_64-linux-gnu/libk5crypto.so.3 (0x00007fb530cb3000)
libcom_err.so.2 => /lib/x86_64-linux-gnu/libcom_err.so.2 (0x00007fb530cad000)
libkrb5support.so.0 => /lib/x86_64-linux-gnu/libkrb5support.so.0 (0x00007fb530c9c000)
libsasl2.so.2 => /lib/x86_64-linux-gnu/libsasl2.so.2 (0x00007fb530c7f000)
libbrotlicommon.so.1 => /lib/x86_64-linux-gnu/libbrotlicommon.so.1 (0x00007fb530c5c000)
libatspi.so.0 => /lib/x86_64-linux-gnu/libatspi.so.0 (0x00007fb530c25000)
libgraphite2.so.3 => /lib/x86_64-linux-gnu/libgraphite2.so.3 (0x00007fb530bf9000)
libpulse.so.0 => /lib/x86_64-linux-gnu/libpulse.so.0 (0x00007fb530ba3000)
libpulsecommon-14.2.so => /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-14.2.so (0x00007fb530b1f000)
libopus.so.0 => /lib/x86_64-linux-gnu/libopus.so.0 (0x00007fb530ac4000)
libXss.so.1 => /lib/x86_64-linux-gnu/libXss.so.1 (0x00007fb530abf000)
libdrm.so.2 => /lib/x86_64-linux-gnu/libdrm.so.2 (0x00007fb530aab000)
libgbm.so.1 => /lib/x86_64-linux-gnu/libgbm.so.1 (0x00007fb530a9b000)
libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 (0x00007fb530a6a000)
libblkid.so.1 => /lib/x86_64-linux-gnu/libblkid.so.1 (0x00007fb530a19000)
libpcre2-8.so.0 => /lib/x86_64-linux-gnu/libpcre2-8.so.0 (0x00007fb530981000)
libwoff2common.so.1.0.2 => /lib/x86_64-linux-gnu/libwoff2common.so.1.0.2 (0x00007fb53097c000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x00007fb530954000)
libunwind.so.8 => /lib/x86_64-linux-gnu/libunwind.so.8 (0x00007fb530939000)
libdw.so.1 => /lib/x86_64-linux-gnu/libdw.so.1 (0x00007fb530890000)
liborc-0.4.so.0 => /lib/x86_64-linux-gnu/liborc-0.4.so.0 (0x00007fb53080c000)
libgstallocators-1.0.so.0 => /lib/x86_64-linux-gnu/libgstallocators-1.0.so.0 (0x00007fb530805000)
libX11-xcb.so.1 => /lib/x86_64-linux-gnu/libX11-xcb.so.1 (0x00007fb5307fe000)
libgudev-1.0.so.0 => /lib/x86_64-linux-gnu/libgudev-1.0.so.0 (0x00007fb5307f1000)
libevdev.so.2 => /lib/x86_64-linux-gnu/libevdev.so.2 (0x00007fb5307d3000)
libicudata.so.67 => /lib/x86_64-linux-gnu/libicudata.so.67 (0x00007fb52ecba000)
liblz4.so.1 => /lib/x86_64-linux-gnu/liblz4.so.1 (0x00007fb52ec97000)
libdatrie.so.1 => /lib/x86_64-linux-gnu/libdatrie.so.1 (0x00007fb52ec8b000)
libXau.so.6 => /lib/x86_64-linux-gnu/libXau.so.6 (0x00007fb52ec86000)
libXdmcp.so.6 => /lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007fb52ea80000)
libbsd.so.0 => /lib/x86_64-linux-gnu/libbsd.so.0 (0x00007fb52ea69000)
libkeyutils.so.1 => /lib/x86_64-linux-gnu/libkeyutils.so.1 (0x00007fb52ea62000)
libwrap.so.0 => /lib/x86_64-linux-gnu/libwrap.so.0 (0x00007fb52ea54000)
libasyncns.so.0 => /lib/x86_64-linux-gnu/libasyncns.so.0 (0x00007fb52ea4c000)
libelf.so.1 => /lib/x86_64-linux-gnu/libelf.so.1 (0x00007fb52ea31000)
libmd.so.0 => /lib/x86_64-linux-gnu/libmd.so.0 (0x00007fb52ea24000)
libnsl.so.2 => /lib/x86_64-linux-gnu/libnsl.so.2 (0x00007fb52ea07000)
libtirpc.so.3 => /lib/x86_64-linux-gnu/libtirpc.so.3 (0x00007fb52e9d8000)

To find out where all of that comes from you can do an apt-file search of each file name.
That will return packages those files may come from. Then it is guess your best.
Every time cmake bombs it gives you little clues what it is looking for. My strategy is to
keep plugging away and try to satisfy deps as they pop up.

Some installs I recorded doing:
(use aptitude install to drag in other dependencies)
libwxgtk3.0-gtk3-dev
libsfml-dev
ftgl-dev
libftgl-dev
libfreeimage-dev
libcurl-dev
libcurl3-gnutls-dev
liblua5.4-dev
libfmt-dev
libwebkit2gtk-4.0-dev
libfltk1.1-dev

There were other things I installed from source too because the versions in the repo were too old.
Like wxWidgets. Some things I installed were so I could build it. So you may not need everything I
had to install. My notes file for installing Slade is 944 lines long and I just grepped "aptitude install"
to make that list. Also I've built a number of other source packages on my PC previously so I had a lot of dev
packages installed already. So none of that would show up in my Slade notes. The ldd list is the master
list of all of Slade's deps. You're going to need the lib and dev packages of all of that. It is quite a long list.

$ ldd slade | wc -l
208

Once you get Slade running you're going to find out that you need other helper apps. Like a BSP thingie.
I compiled something called GLBSP. Although I'm not sure if it is doing what it should do. I could not get into
the map I made using the tutorial. Today was the first day I ever tried using Slade. So far not so good.
Which is a large part of why I am here. I have questions myself. Good luck!
User avatar
Enjay
 
 
Posts: 26430
Joined: Tue Jul 15, 2003 4:58 pm
Location: Scotland

Re: SLADE Discussion - Latest: v3.1.13 (01/Jun/2021)

Post by Enjay »

I'd had an ISO of a CD mounted and had used Slade to look inside a PAK file inside the ISO.

Later, when the ISO was unmounted, I tried to start Slade simply by double clicking the exe. Slade popped up a message saying that it couldn't start and listed the PAK file as the problem.

All I had to do was go into my appdata and delete the file history entry for that file and Slade could start. (Fortunately I knew to look there.)

Slade doesn't normally refuse to start when a previously opened file is missing so, after a little digging, I think that the problem is that the file path was to a drive that doesn't exist once the ISO is unmounted. So, I tried putting spurious file names into the cfg. As long as the drive existed, Slade would open (and on closing the spurious file would disappear from the recent file list in the cfg file) but if I put any file name in with a path to a non-existent drive, Slade refused to start.

Image

Short version, if Slade has a recent file in its config that is on a drive that doesn't currently exist on the machine, Slade will refuse to open.

Can Slade be changed so that it treats such paths in the same way as it does files that no longer exist? - i.e. open normally and erase the reference to the file in the recent file list.
User avatar
nova++
Posts: 177
Joined: Sat Sep 04, 2021 3:13 am

Re: SLADE Discussion - Latest: v3.1.13 (01/Jun/2021)

Post by nova++ »

Rather than continue to annoy everyone on the github issues page, I'll babble about some stuff I've been encountering over here...

I've been having issues with the linux version of slade's map editor just being choppy and unresponsive and generally kind of unhappy. It's not unusable, but it's not super great either. It's inconsistent, though. And it also is a lot better when I've tried it on different hardware - in this case, my ryzen 2200G seems to digest it much better than my ryzen 1700. The latter also has a GTX 1070 and nvidia has kind of a reputation when it comes to linux drivers, so maybe that has something to do with it, too... I have my own build of it with a few quick hax for my own uses but I don't think that has much to do with it (same build on both systems anyway). Plenty of background stuff going on in the 2200G system too, and it still just feels generally more responsive. It's weird.

It runs a lot better under wine, meanwhile, super fluid and responsive in the editor. Of course, the file browsing is a nightmare and a lot of the UI is kinda wonky under wine, but I guess it's something...

I dunno what to do with this information though, or if it's any use to anyone else.


Edit: I made a comparison between the two. It tends to get worse over time on linux (as per https://github.com/sirjuddington/SLADE/issues/1016 ) and this is after letting it sit for a while. Make sure youtube is playing at 60fps when watching, otherwise it hides the stutters



(there are some slight differences between these builds as the native one is my own with as mentioned earlier, but it's nothing that would affect it so much. later I will make a windows build with the same changes and try that too, but I don't expect much)
User avatar
Rowsol
Posts: 907
Joined: Wed Mar 06, 2013 5:31 am

Re: SLADE Discussion - Latest: v3.1.13 (01/Jun/2021)

Post by Rowsol »

For some reason, over night, Slade has started to freeze whenever I look at a graphic. I've tried 2 version and it happens on both. Is there a reset option?

Resetting my PC stopped the freezing and I found the .cfg file in Appdata, because of course it's there.
CJacobsLP
Posts: 2
Joined: Fri Dec 03, 2021 2:59 am

Re: SLADE Discussion - Latest: v3.1.13 (01/Jun/2021)

Post by CJacobsLP »

Not sure where this belongs at all because I think it's intended behavior, but splitting lines does not seem to align the resulting vertex to the grid even with grid snapping enabled. As far as I can tell there's no way to make that so. Is there one that I've missed?
User avatar
Kappes Buur
 
 
Posts: 4037
Joined: Thu Jul 17, 2003 12:19 am
Location: British Columbia, Canada

Re: SLADE Discussion - Latest: v3.1.13 (01/Jun/2021)

Post by Kappes Buur »

CJacobsLP wrote:....., but splitting lines does not seem to align the resulting vertex to the grid even with grid snapping enabled. As far as I can tell there's no way to make that so. .....


does work with slade_3.2.0_b3.
illYay1337
Posts: 3
Joined: Tue Feb 01, 2022 4:19 am

Re: SLADE Discussion - Latest: v3.1.13 (01/Jun/2021)

Post by illYay1337 »

So I made some new texture cleanup tools for SLADE in a pull request.

https://github.com/sirjuddington/SLADE/pull/1313

Similar post here: https://www.doomworld.com/forum/topic/1 ... for-slade/

I'm not sure how active SLADE is these days but I'm hoping the next release might have this. I currently was only able to build SLADE on a mac, but most of my doom modding and playing takes place on Windows with Ultimate Doom builder.
Drake Raider
Posts: 474
Joined: Fri Jul 18, 2008 12:27 pm

Re: SLADE Discussion - Latest: v3.1.13 (01/Jun/2021)

Post by Drake Raider »

After a ubuntu update (to 22.04) I can no longer access any of the executables from Slade: zdbsp, acc, and the like. No idea why, it just ignores them completely. They're all still installed in the correct locations, but all my maps are being built without nodes now. Any idea how to bugfix?
User avatar
Enjay
 
 
Posts: 26430
Joined: Tue Jul 15, 2003 4:58 pm
Location: Scotland

Re: SLADE Discussion - Latest: v3.1.13 (01/Jun/2021)

Post by Enjay »

Just wondering - when converting a TEXTURE1 lump to a TEXTURES one, should Slade use the keyword WallTexture instead of Texture?

Entries in a TEXTURE1 lump are likely to be set up, first and foremost, as walls and should probably be in that namespace when converted. I'm particularly thinking about this in relation to the STEP1 and STEP2 textures where it is more important that they have the correct namespace because of the name clash with the STEP1 and STEP2 flats.
Gez
 
 
Posts: 17689
Joined: Fri Jul 06, 2007 3:22 pm

Re: SLADE Discussion - Latest: v3.1.13 (01/Jun/2021)

Post by Gez »

Yes, it should use WallTexture.
User avatar
NeuralStunner
 
 
Posts: 12301
Joined: Tue Jul 21, 2009 12:04 pm
Preferred Pronouns: He/Him
Graphics Processor: nVidia (Modern GZDoom)
Location: capital N, capital S, no space

Re: SLADE Discussion - Latest: v3.1.13 (01/Jun/2021)

Post by NeuralStunner »

I've encountered a singularly annoying behavior where any kind of modification on a single PNG - offset changes or color remap - will muck with the stored palette. Usually just changing which index is used for transparency (it seems to prefer the first unused color that's not #0) but also tends to "upgrade" 16 color PNGs to 256 (where the remainder of the palette is filled in with grayscale values) or even truecolor. What's extra weird about it is that doing these modifications on multiple PNGs at a time leaves their palettes alone, which is the correct/preferred behavior.
User avatar
sirjuddington
Posts: 1019
Joined: Wed Jul 16, 2003 4:47 am
Location: Australia

Re: SLADE Discussion - Latest: v3.1.13 (01/Jun/2021)

Post by sirjuddington »

I've just released SLADE v3.2.0 beta 4, which should hopefully be the last beta release before 3.2.0 proper.

https://github.com/sirjuddington/SLADE/ ... g/3.2.0_b4
https://slade.mancubus.net
illYay1337 wrote:So I made some new texture cleanup tools for SLADE in a pull request.

https://github.com/sirjuddington/SLADE/pull/1313

Similar post here: https://www.doomworld.com/forum/topic/1 ... for-slade/

I'm not sure how active SLADE is these days but I'm hoping the next release might have this. I currently was only able to build SLADE on a mac, but most of my doom modding and playing takes place on Windows with Ultimate Doom builder.
This is in beta 4 :)
Enjay wrote:I'd had an ISO of a CD mounted and had used Slade to look inside a PAK file inside the ISO.

Later, when the ISO was unmounted, I tried to start Slade simply by double clicking the exe. Slade popped up a message saying that it couldn't start and listed the PAK file as the problem.

All I had to do was go into my appdata and delete the file history entry for that file and Slade could start. (Fortunately I knew to look there.)

Slade doesn't normally refuse to start when a previously opened file is missing so, after a little digging, I think that the problem is that the file path was to a drive that doesn't exist once the ISO is unmounted. So, I tried putting spurious file names into the cfg. As long as the drive existed, Slade would open (and on closing the spurious file would disappear from the recent file list in the cfg file) but if I put any file name in with a path to a non-existent drive, Slade refused to start.

Short version, if Slade has a recent file in its config that is on a drive that doesn't currently exist on the machine, Slade will refuse to open.

Can Slade be changed so that it treats such paths in the same way as it does files that no longer exist? - i.e. open normally and erase the reference to the file in the recent file list.
This is fixed in beta 4
NeuralStunner wrote:Adding to this, I'd like to be able to export entire directories of lumps (with structure). Perhaps even a tool to unpack an entire archive.
This is actually possible already (not sure if it was in 3.2.0 beta 3 but it is in beta 4), just select the directory/directories you want to export, right click and select export. Currently the export icon on the left will remain disabled in this situation but the action itself actually works fine.

Return to “Creation, Conversion, and Editing”