GZDoom Builder 2.3

[MaxED]

UDMF keys are treated as case-sensitive.

Fixed.

[Siberian Tiger]

I've seem to have ran into a problem with the latest GZDoom Builder revision: 2450. When using an '#include' instruction in ACS with an absolute path to an exact file, now returns an error of

Code: Select all

Unable to load include file 'd:\projects\zdoom wads\tgrdm3\scripts\standardlibrary.acs'!.

This error is also shown in a pop-up "Errors and Warnings" window when first loading the map in the editor. In the previous builds I did not run into this issue before and the scripts are just fine. If I comment out the include instruction and past the entire file contents of 'StandardLibrary.acs' into the map's ACS script, it will work just fine, but not when using the include statement.

Using builds from DRDTeam
Issue first occurs build: revision 2448
Last working build: revision 2447

ACS Scripts Related

• StandardLibrary
• Acerbus [Map Script; ACS ZDoom]

---

Project Version Control: https://github.com/SibTiger/TGRDM3
Compiler: Requires Bootless Star, and Morgenstern.bat. Do NOT use Compiler_Map.bat! (I can't be certain of possible issues if you run it without the required initializations and declarations). Contact via PM and I'll walk you through the compiling. However, I don't believe you really need a resource build as the scripts are 'as-is' by design.
Affected Maps: Abandoned Misery (and Lite), Acerbus. Or all playable maps to this date.

[boris]

There's a problem with the stuck thing checker and Boom multiplayer flags. It reports things as stuck, even when they will not show up at the same time in game. Example: two monster occupy the same space.

• Both have the "multiplayer only" flag set.
• Thing 1 has the "not deathmatch" flag set
• Thing 2 has the "not coop" flag set.

This will result in the following in game:

• Neither thing will show up in single player
• Thing 1 will show up in coop only
• Thing 2 will show up in dm only

However, GZDB reports them to be stuck in each other. It worked find in DB2 revision 1715.

An example WAD is attached. It's pretty easy to try out:

Coop: gzdoom -file difficulty.wad -host 1 -warp 1
The arachnotron on the blue floor shows up

Deathmatch: gzdoom -file difficulty.wad -host 1 -deathmatch -warp 1
The arachnotron on the red floor shows up

[Tormentor667]

Feature Suggestion
In the "tag" field, you can use the expression ">=N" to give multiple lines/sectors/things a unique tag, starting with N and going up according to the amount of sectors. Could you also add this function to other fields, for example to a line special's tag field (or simply globally)? That way you could easily generate tags and also connect them with specials (useful for a 3d staircase)

Re-suggesting that as Kappes Buur's suggestion doesn't work in this case. With the Tag Plugin I can actually define tags of lines itself but I can't automize tag ranges of line specials. So what I would find very useful is having the possibility to use the expression also here:

[MartinHowe]

*.acs include path should be relative to the root path of the resource this file is located in. In your example it should probably be #include "maps/map01acs/map01.acs"[/quote]
Thanks very much - this works

[Siberian Tiger]

MaxED, revision update 2451 works for me. Thank you for resolving that issue!

[prepper]

Hello, I am new to the forum and I have a problem with the visualmode, its not possible make a render of middle textures using "renderinside" or type 5 in a model 3dfloor.

[MaxED]

Can you provide an example wad of some sort?..

[prepper]

Can you provide an example wad of some sort?..

Sure, I did some screenshots to show.
'An image is worth a thousand words'

---

i show a simple map here in this case hexen format

[Zanieon]

Dude, when he means an example wad, is to you give him a wad with the problem happening, in the case you could use this one of the pics since doesn't seems to have anything much trivial other than custom texture, also don't worry about unrelased content, MaxEd only gets stuff for fixing bugs in GZDB and don't leaks nothing to anybody (AFAIK).

[MaxED]

Looks like I'll need some feedback from Graf first...

[Nash]

Quick question: why is GZDoom Builder's default map border limits set to +-32k when no Doom engine can actually support that? I think for ZDoom, the safest region is within +-8192... anything outside that and collision doesn't work correctly. :S

[Zanieon]

Nash, anything can work normally within that area GZDB provides, if you start mapping from one the limits but still it's a small map, nothing special happens, what really matters to break map's collision and starts wrap it, is the map itself be larger than 32767 map units.

[MaxED]

Quick question: why is GZDoom Builder's default map border limits set to +-32k when no Doom engine can actually support that?

Dunno. Ask CodeImp...

[Nash]

Nash, anything can work normally within that area GZDB provides, if you start mapping from one the limits but still it's a small map, nothing special happens, what really matters to break map's collision and starts wrap it, is the map itself be larger than 32767 map units.

I don't think that's true. I've had hitscans fail when a map crosses roughly +-16k on either X or Y...

Quick question: why is GZDoom Builder's default map border limits set to +-32k when no Doom engine can actually support that?

Dunno. Ask CodeImp...

Heh, probably assuming someone was going to expand the limit in source ports in future... something that hasn't happened yet. =P