If I decompile my own map, is there something i should expect to be different?

Q. What are VMEX's limitations?

A.

1. It can't (as of v0.98) tie areaportal brushes to their corresponding func_areaportal or func_areaportalwindow entities. This isn't too high priority, since you can tell usually tell what is an areaportal from it's texture, but it should be fixable.
2. It can't recover any editor-specific information such as visgroups. Hammer's default visgroups work for some things, and VMEX places certain brushes (clip and hint brushes) in a visgroup so they can be turned off easily.
3. It can't precisely recover to size and position of brushes. Rounding errors during the compiling/decompiling process may lead to tiny differences in position, which cause leaks and other problems if trying to recompile a decompiled map.
4. All detail brushes are recreated individually (rather than many brushes being tied to one func_detail, as is more realistic). Unfortunately there is no grouping information retained in the BSP, so this is the best VMEX can do.
5. Currently, info_overlay entities are only tied to their correct brush faces when decompiling in brush mode (-m3). Also, occasionally a decompiled overlay may be incorrectly oriented (flipped or mirrored).

Click to expand...