SLADE Discussion - Latest: v3.2.5 (19/Dec/2023)

[MaxED]

Not sure about the missing line breaks (though it shouldn't matter to any UDMF parsers).

It does break GZDB's UDMF parser because of some caching hacks I've added to gain 2x performance boost...

Problem 4 I can't replicate.

On my side it happens when I open any child window in the Map Editor (like Properties, Texture Browser etc.) and then move that window.

---

If that helps, here are my specs:

[edward850]

It does break GZDB's UDMF parser because of some caching hacks I've added to gain 2x performance boost...

That means the specs for your UDMF parser doesn't match. Strange or not, the bug is with your code.

[MaxED]

I'm aware of that. I had to make it stricter than UDMF format specification (GZDB's parser expects a single UDMF property per line) to gain performance boost. Adding additional checks will decrease that boost, so I don't want to add them.

[edward850]

You know if you get Slade3 to change it now, something else is going to be like that later. You cannot hope to assume that it's going to always be like that.

[Gez]

You cannot really expect every UDMF output will conform to these stricter specs (other than DB2/GZDB and SLADE3, there are many UDMF apps, like converters and more-or-less finished random map generators). Maybe you could use a special comment at the top of the file to determine whether it's made by GZDB and reliable, or not. I won't begrudge performance boosts, especially given how large UDMF maps can get. (I know I wouldn't try editing something like ZDCMP2 in SLADE's map editor.)

The missing line break is pretty simple:

Code: Select all

		object_def += S_FMT("texturefloor=\"%s\";\ntextureceiling=\"%s\";", sectors[a]->f_tex, sectors[a]->c_tex);

Literally just a \n missing. Easily changed.

[MaxED]

I've added that hack more than a year ago and nobody ever complained, so...

[NeuralStunner]

Maybe you could use a special comment at the top of the file to determine whether it's made by GZDB and reliable, or not.

Agreed here, it could be useful for other things in the future.

I've also wondered about the possibility of storing certain basic .dbs settings (game, grid size) in the UDMF "header" as comments. I think it could make it quicker to sync these settings between editors.

[MaxED]

I've also wondered about the possibility of storing certain basic .dbs settings (game, grid size) in the UDMF "header" as comments. I think it could make it quicker to sync these settings between editors.

Or create a new editor settings file format (or lump?), compatible with both editors (this way it won't be limited to UDMF map format). Or just add .dbs support to Slade.

[Gez]

I've also wondered about the possibility of storing certain basic .dbs settings (game, grid size) in the UDMF "header" as comments. I think it could make it quicker to sync these settings between editors.

Or create a new editor settings file format (or lump?), compatible with both editors (this way it won't be limited to UDMF map format). Or just add .dbs support to Slade.

Maybe. Last time the issue was broached, the idea was to support both internal and external metadata, subject to user preference. Interoperating on the .dbs files seems possible. The format is quite similar to what SLADE uses for its configurations, so parsing wouldn't be an issue. However there are differences in how both programs handle some of the most basic stuff (e.g., SLADE map configurations are split between game and port) so there would necessarily be some conceptually redundant fields which both programs would have to preserve even if they ignore it.

[MaxED]

I think instead of creating an unified map settings file (which would require hackery or unified game configurations), much easier thing to do would be just adding an importer from other editor's settings file (does Slade create / plan to create these, by the way?).

[MaxED]

...there would necessarily be some conceptually redundant fields which both programs would have to preserve even if they ignore it.

DB2 already does that. You can open a map created in GZDB, save it in DB2 and the new .dbs file will still have all GZDB-only properties.

[Gez]

I think instead of creating an unified map settings file (which would require hackery or unified game configurations), much easier thing to do would be just adding an importer from other editor's settings file (does Slade create / plan to create these, by the way?).

There's no equivalent to the dbs files at the moment, but it's planned as a long-term, low-priority feature.

[Matt]

I just downloaded and compiled the latest version on github, but it won't start saying there's a missing slade.pk3 that I can't find anywhere (even online)! What's going on???

EDIT: Nevermind, found one in the Windows binaries archive, seems to be working so far.

[Gez]

Zip the content of the dist/res folder (directly, "res" itself shouldn't be in the zip) and name that zip slade.pk3.

Alternatively, copy the entire res folder.

[Matt]

There's no res folder.