GZDoom Builder 2.3

[ZZYZX]

This line is handled REALLY inadequately:
http://i.imgur.com/Hv7UQyZ.png

When you draw anything that touches it, all linedefs of the new shape will be ONE-SIDED, except those that directly merge with this line, like so:


All geometry around it is also then broken recursively, like all lines start to reference the largest sector around or smth.

[Tormentor667]

Version: 2.3.0.2638
Copying and pasting whole sector structures with mid-textures (2-sided) still removes the textures and you have to readd them. This also happens when moving sectors (drag and drop), all 2-sided mid-textures get removed. I also noticed that moving vertices makes this happen, it doesn't even remove the texture but also make an impassible line automatically passible.

[Chl]

Um guys, Max knows about this and has been trying to fix it for some time now. Just check his latest posts.

[Hellser]

It's good to put a little pressure. But not too much. I think MaxEd fixed this in a recent updated (R2638). I'll see if this indeed fixes it.

[Tormentor667]

I think MaxEd fixed this in a recent updated (R2638). I'll see if this indeed fixes it.

It's nothing about pressure, it's simply that the bug isn't fixed in the latest version, that's why I post this.

[blood]

I confirm it's not fixed, so now he is alerted, let's wait.

[boris]

Latest version crashes when trying to compile a script after creating a new map and not having it saved yet. It passes an empty string to Path.GetDirectoryName in compilers/AccCompiler.cs, line 109, and that throws an exception ("Path has invalid format").

---

***********SYSTEM INFO***********
OS: Microsoft Windows 7 Home Premium
GPU: NVIDIA GeForce GTX 970
GZDB: R2638

********EXCEPTION DETAILS********
Der Pfad hat ein ungültiges Format.
bei System.IO.Path.NormalizePathFast(String path, Boolean fullCheck)
bei System.IO.Path.NormalizePath(String path, Boolean fullCheck)
bei System.IO.Path.GetDirectoryName(String path)
bei CodeImp.DoomBuilder.Compilers.AccCompiler.Run() in x:\Source\Core\Compilers\AccCompiler.cs:Zeile 109.
bei CodeImp.DoomBuilder.Data.WADReader.CompileLump(String lumpname, Int32 lumpindex, ScriptConfiguration scriptconfig, List`1 errors) in x:\Source\Core\Data\WADReader.cs:Zeile 1282.
bei CodeImp.DoomBuilder.Data.WADReader.CompileLump(String lumpname, ScriptConfiguration scriptconfig, List`1 errors) in x:\Source\Core\Data\WADReader.cs:Zeile 1211.
bei CodeImp.DoomBuilder.Controls.ScriptLumpDocumentTab.Compile() in x:\Source\Core\Controls\ScriptLumpDocumentTab.cs:Zeile 96.
bei CodeImp.DoomBuilder.Controls.ScriptEditorPanel.buttoncompile_Click(Object sender, EventArgs e) in x:\Source\Core\Controls\ScriptEditorPanel.cs:Zeile 1069.
bei System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
bei System.Windows.Forms.ToolStripButton.OnClick(EventArgs e)
bei System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
bei System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
bei System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
bei System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
bei System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
bei System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
bei System.Windows.Forms.Control.WndProc(Message& m)
bei System.Windows.Forms.ScrollableControl.WndProc(Message& m)
bei System.Windows.Forms.ToolStrip.WndProc(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

[MTrop]

R2638 (or a recent version) broke ACS script #include directives. Path resolution no longer resolves to paths inside included resources, and if it checks for more than one location for the path, a failure on ANY of those locations results in a compiler error, when it should be a failure on ALL of them resulting in an error.

[Breezeep]

Strangely, on R2639 of GZDoom builder, an error pops up at random whenever I try to undo something.

[MaxED]

Moar details ples...

[simc]

Two comments about the behavior of r2639/2638.

DRAGGING AND DROPPING SECTORS:

If you move a sector over an other sector (so that their linedefs cross each other) the underneath leaving parts of the original structure are removed.

---

(in every traditional mode)
For example if I move the sectors on the left over the sectors on the right.

The result:

But could there be an alternative way of not loosing any linedefs? Keep everything but just add new sectors and vertices to the linedef crossings? Lots of my editing has been combining separately made ceiling structures with floor structures.

----------------------------
SECTOR VALIDITY?:

If you move a linedef going through an other line GZDB now automaticly adds a vertex to the crossing point and renumbers the sidedef sector references. But now editing any traditional special effects (invisible walkways and such) is quite impossible. Dragging and dropping lines or vertices will renumber the sidedef sector numbers instantly. Could this feature be switched off temporarily?

(EDIT: I don't want to make demands or create pressure with this. If this is the new system then all right.)

[NeuralStunner]

Small bug here: When in 3D mode, pressing the keys assigned to Grid Increase/Decrease will change the grid size. (I have the [ ] keys set up to change floor/ceiling heights in 3D mode.)

[MaxED]

Grid size is actually used in Visual mode. There are "Move texture offsets by grid size" actions, Ctrl-Shift-dragging textures also change offsets by grid size, "Move Things" actions also change things position by grid size.

[Sandro]

I found a weird behavior concerning joined sectors:

1) Create two sectors and join them.
2) Create a new sector inside one of them.
3) Now the first two sectors aren't joined anymore...

I guess that is not intentional, right?

[MaxED]

It's intentional.