Terrain in modelviewer needs to be reworked

[ufdada]

The current terrain viewer is not really a big help.

The following things should make it a little more useful:

• support for fixed / dynamic rooms
• support for quad-tiles
• support for alternative materials
• support for different maps (currently it just loads the terrain of alcatraz)

[belgianguy]

support for fixed / dynamic rooms support for quad-tiles

What is meant by this?

support for alternative materials

How does the process work of discovering these in the original assets?

support for different maps (currently it just loads the terrain of alcatraz)

This is hardcoded, but are then all items we're seeing loaded in ModelViewer only from the Alcatraz map? E.g. would a "Mercenary Portal" model then only show up in ModelViewer for a map that contains it? Wouldn't the union of all sets of models per map then be preferable?

[ufdada]

What is meant by this?

• fixed / dynamic rooms are things like dungeon heart or the training room
• quad tiles are tiles, that depend on 4 different textures that have been stitched together, something like the claimed path for example

How does the process work of discovering these in the original assets?

• It's not that easy, just take a look at setTileMaterialToGeometries in Maploader. Currently only our decay mechanism makes really use of it.

Wouldn't the union of all sets of models per map then be preferable?

oops i mixed it up with objects, terrains should be the same for all maps. alcatraz is only used for loading this information. my bad.