Question about UDMF sector properties and crossport compatibility

[SuaveSteve]

Hey guys. I'm a little confused over something in UDMF.

DSDA introduced some sector properties to make life easier without ACS. For example: frictionfactor, yscrollfloor, scrollfloormode.

A pleasant surprise is that these work in GZDoom.

Three questions:

1. What are the thoughts on updating the wiki to include all the compatible properties and sourceport they originated from? While my opening example is for sectors, this would include properties for all UDMF entity types.
2. Can someone point me to the source code that does parse the properties? I may take a swing at updating the Wiki myself.
3. Since GZDoom still honours the scrolling and friction properties without caring if namespace is "zdoom", does that mean that namespaces are not meant to imply rejecting features from another sourceport? They have nothing to do with features, per se?

Just a thought: Going forward, if different ports support all sorts of properties, it might get confusing what supports what.

Possibly related: UDMF features from latest DSDA release

-Steve

[boris]

The UDMF properties supported by the ZDooms are documented here:

GZDoom: https://github.com/ZDoom/gzdoom/blob/ma ... _zdoom.txt
UZDoom: https://github.com/UZDoom/UZDoom/blob/t ... _zdoom.txt

There also this with tables of what port supports what UDMF properties: https://github.com/biwa/engine-udmf-support

[camper]

Each port has its own namespace in UDMF, meaning that map geometry is compatible in this format in the simplest case, close to the Doom namespace. But no one uses this namespace as specified. Each port has a slight difference. I used to think that a universal map format should work everywhere, but that's not the case. Different definitions for extensions and different line actions and so on prevent this. UDMF is a fiction; it's compatible only with simple geometry, without slopes, 3D floors, elevators, doors, and the like.