You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So couple of month ago I've worked on prefab feature, and used sledge-formats library for it.
I noticed, that prefab planes uses wrong texturing shifts\rotation. Initially I thought it was confused for every RMF format, so I just used a trick to route sledge-formats 'Face' fields to 'Sledge.BspEditor.Primitives.MapObjectData.Face'
But recently I've returned to that issue, and found that wrong structure applied only for v1.6 (I've used VHE 3.4 (steam version) built-in prefabs 'computers', and 'Usable Objects' packs are 1.6 version, when others seems to be fine)
(Screenshot above is made with routing 'as intended to be')
(Added same prefabs with 'proper' routing)
Since I cant find specification description other than THWL website - I cant prove i'm right or wrong
It might be even more confusing, if you notice, that VHE 3.4 has the same issue, so the problem could be hidden deeper.
The text was updated successfully, but these errors were encountered:
So couple of month ago I've worked on prefab feature, and used sledge-formats library for it.
I noticed, that prefab planes uses wrong texturing shifts\rotation. Initially I thought it was confused for every RMF format, so I just used a trick to route sledge-formats 'Face' fields to 'Sledge.BspEditor.Primitives.MapObjectData.Face'
But recently I've returned to that issue, and found that wrong structure applied only for v1.6 (I've used VHE 3.4 (steam version) built-in prefabs 'computers', and 'Usable Objects' packs are 1.6 version, when others seems to be fine)
(Screenshot above is made with routing 'as intended to be')
(Added same prefabs with 'proper' routing)
Since I cant find specification description other than THWL website - I cant prove i'm right or wrong
It might be even more confusing, if you notice, that VHE 3.4 has the same issue, so the problem could be hidden deeper.
The text was updated successfully, but these errors were encountered: