GZDoom Builder 2.3

[Nash]

Any chance of seeing the Visplane Explorer work with the UDMF format? I've always wanted to use the plugin but I only map for UDMF... so... XD

[Blue Shadow]

[r2028]

When selecting a thing which has blue pixels in its sprite, the following happens:

---

[NeuralStunner]

Any chance of seeing the Visplane Explorer work with the UDMF format? I've always wanted to use the plugin but I only map for UDMF... so... XD

Would it even be necessary? Engines that support UDMF shouldn't have the visplane limits that the plugin is meant to help keep you under.

Also, while the "no activation flags" warning could be useful to inexperienced or inattentive mappers, for me it would only get in the way. The majority of cases where I don't set the flags, I skipped it intentionally. For the (very few) actual accident cases, it becomes immediately obvious as soon as I test that part of the map. I too will request an option to turn of the warning entirely.

Speaking of line actions, it would be handy to have a button in the linedef edit dialogue to instantly clear actions, args, and activation flags from edited lines. (Obviously, onlly apply this change on "OK".) To take it a bit further, it could also help to have a "reset line" button to remove all extra flags, offsets, and properties. (Only keep impassable for one-sided lines, and the Two-Sided flag for others.)

[Graf Zahl]

It would be great if this could be deactivated somehow.
It gets in the way when setting up control sectors.

Yeah, current implementation is kinda obtrusive... Is there an easy way to get all linedef actions, which do not require activation?

The best point to look for is ZDoom's linedef action table in p_lnspec.h.
All that do not have a function pointer in there do not need an activation type. Note, though, that there's a handful of types that can be called from scripts but work as static init types when used directly in a map. But you'd get the majority out this way.

[Blue Shadow]

[r2028]

Got a crash on WAD close:

GZCrash.zip

[MaxED]

Curious. This plugin was made in 2010, and this error happened only now.
Probably fixed in r2030. (download GZDB r2030)
Also, missing activation flags warning is disabled in this build.
Also, this

---

Any chance of seeing the Visplane Explorer work with the UDMF format? I've always wanted to use the plugin but I only map for UDMF... so... XD

You can try asking the guy who made Visplane Explorer (here, for example). The plugin just wraps the library he made.
Also, GZDoom crashed on me when I tried loading a terrain made of ~32000 sectors. On the other hand, I have no idea if that was because of visplane overflow.

[Graf Zahl]

GZDoom doesn't even know the concept of a visplane.

[MaxED]

When selecting a thing which has blue pixels in its sprite, the following happens:

---

Well, this happens when you multiply a dark-blueish color by a non-white color... If somebody knows a better way of tinting an image, let me know.

[Graf Zahl]

Don't use primary colors, use something that got a significant value in all components, like (192, 255, 192) for tinting something green. Or use blending instead of modulating.

[MaxED]

GZDoom doesn't even know the concept of a visplane.

Then that probably was some leser known overflow

[MaxED]

Don't use primary colors, use something that got a significant value in all components, like (192, 255, 192) for tinting something green.

Selection color can be changed by user.

Or use blending instead of modulating.

Did that. Not sure if it's better this way (higher things are not selected, lower things are)

[Kappes Buur]

[feature request]

When assigning increments to 3D control sectors, could it be done to assign the same value to Ceiling and Floor in one step ?

---

[Nash]

Would it even be necessary? Engines that support UDMF shouldn't have the visplane limits that the plugin is meant to help keep you under.

Oh, I see... well I just had the idea that the "hotter" the output is = more visplanes = slower performance... figured it would be a useful performance tuning tool... I guess it doesn't really apply for UDMF then. :D

[plums]

Using the map analysis tool, I get crashes trying to dissolve invalid/0-area sectors. Attachment has the crash log, and a map that has invalid sectors to be dissolved.

e: The invalid sectors got fixed somehow on saving/loading? Weird. Hopefully the crash log is enough to go on...

e2: also, is there a way to not clear the selection if I click+drag by accident?

[MaxED]

Map Analysis doesn't detect any invalid sectors in your map...
I only got these errors:

---

Sidedef 28 has unused lower texture "METAL"
Sidedef 32 has unused lower texture "METAL"
Sidedef 34 has unused lower texture "METAL"
Sidedef 38 has unused lower texture "METAL"
Sidedef 527 has unused lower texture "BFALL1"