ZDoom

The newest AMD release seems to help with this - but it does have other issues - some of them fairly serious. (GLES is completely unusable in the new driver, for instance) "fairly serious" -- Racheal, you sure know how to make a guy sweat! toad sweat.png I think I will be okay with my current ...

Major Cooke wrote:Please make a new thread.

Because of Necroposting or because dev builds have reached version 4.8.1?

I'm using 4.7.1 dev build and this bug crashes the game https://devbuilds.drdteam.org/gzdoom/gzdoom-x64-g4.8pre-269-g4049a0d8f.7z I'm using Project Brutality Custom Build from this link: https://telegra.ph/Project-Brutality-Custom-Build-03-05 When I am running PBCB with OpenGL API, the .m3D and ...

Thanks for the clarification Rachael. I tried Softpoly and that has the same issue with 3d models as OpenGL. I switched back to Vulkan, enabled High Performance mode, and restarted GZDooM. I updated my AMD driver to 22.2.3, disabled VSYNC, and forced AMD Sync (I am using AMD Sync monitor) In Hunter ...

To Everyone who replied, Thank You so much! Framerate is noticeably lesser, but it fixed the problem and visual quality seems improved too. I can use OpenGL for 2D mods and Vulkan for mods using 3D models. Yay! Such a simple fix, just change rendering API. BTW is POLYMOST renderer derived from jDuke ...

This bug seems to affect GZDooM 4.2.1, 4.6.1, 4.7.1 64-bit in OpenGL mode. 3D models are flattened along one axis and appear as flattened shapes with messed up textures. The 3D models in D4D mod, Elementalism and Hunter's Moon are rendered incorrectly, they are crushed along one axis and thus appear ...

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.

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 ...

Any chance of making the player mortal? Game is no fun if there's no challenge.

Otherwise, cool mod, I can see playing slaughterwads with this.

Thank You simc, that's exactly what I wanted. By the time I read your reply, I was nearly done with this project. But DEUtex will certainly come in very useful as I make more update patches to Compendium. I ended up copying and pasting the maps into new .WADs one by one, SLADE keyboard shortcuts ...

As for splitting maps into separate files, I think you may be better served with wadext for that. Thank You for answering. I tried to use WADext, but it doesn't seem to recognize the file PS K:\Doom\Slade\WADext> .\wadext 32OF64-LR.WAD 32OF64-LR.WAD: not a WAD file PS K:\Doom\Slade\WADext> .\wadext ...

SLADE 3.1.13 does not build a REJECT table when I save a map in the editor. How do I force it to build the REJECT table when I save? Also is there a way I can split a megawad into individual .WADs easily? Example 32OF64-LR.WAD contains 34 maps, I want to export them to individual WADs, one for each ...

A new version you say? I checked on your Google Drive and it still says "V5" is the latest.

Hello HyperExia, thank you for keeping this mod alive. Slayer's Rampage is one of my favorite mods for GZDoom, as it uses very little system resources and runs well even on weak systems like my Lenovo 450T. The pace is very fast and I love the enemy movement and sequence breaking afforded by double ...

Yes, and it is super easy to make your own. Using SLADE, I exported two sets of music lumps from MusicDarkAmbient.pk3 and STRAIN.WAD, Used bulkrenameutility.exe to rename them from D_<lumpname>.mus / .ogg to STRAIN_<lumpname>.mus / Dark_Ambient_<lumpname>.ogg, then wrote a DMUSDESC to tie them ...