ZDoom

Brightmaps Plus 1.9 and other mods that used to work correctly aren't loading anymore with Wadsmoosh . It sounds like this is related to a change made in recent versions of GZDoom with autoload. The issue is explained here: What's happening here is that those WADs include GLDEFS lumps for doom.id ...

EmperorGrieferus wrote:

NullWire wrote:Is there any brightmap addons for this mod?

https://www.doomworld.com/forum/topic/1 ... d-edition/

Is there a compatible set of Brightmaps though that would work with the latest version of Smooth Doom?

By the way, the WadSmoosh AutoName change in GZDoom 4.6.0 also affected Brightmaps Plus in the same way. Easy fix by just copying the doom.id.doom2 filter folder as doom.id.wadsmoosh, except for the textures one. But I'm not sure that one is worth trying to support WadSmoosh with, because of the ...

i noticed two small issues with the most recent update and with my limited slade knowledge was able to fix them. smooth doom 4-14-20 bug.png the most apparent one is that the shortgreentorch is now blue. this can be fixed by going into DECO/Decoration.txt, finding this section: Actor ShortTorch ...

GZDoom 4.7.1 macOS crashes when ran at 320x200 with the following error message whenever launching a new game: https://gist.github.com/aarodynamics/56182f566b4e655e08a2373ff750b1b7 Loading a game from the start screen in 320x200 works. Starting a new game from the start screen in any other scaled ...

I wanted to add a couple more details for anyone else who may stumble on this thread... I had to set r_noaccel true for scaling to avoid scaling issues on certain sprites on my weapon. Rachel mentioned to me that this is likely due inefficiencies with the float datatype. You can see the issue here ...

You need to do the math yourself to set custom scaling like this... ScaledY / NativeY = Y * NativeX = X * 1.2 = ScaledX You'll always know your ScaledY because that's the vertical resolution you want to achieve (400p in my case). You're solving for the ScaledX. Then run the command: vid_setscale ...

I've noticed when using 640x400 or 320x200 mode on my 2880x1800 HiDPI laptop LCD that the HUD's pixels seem to be scaled correctly even with linear filtering set to None... But, if I switch to a Normal + 0.25 scale or use the "Lowest Possible Scale" mode the HUD's pixels aren't scaled properly ...