Some surfaces and polysurfaces acting funny in some display views

I’ve been receiving this model from another party and the polysurfaces and surfaces are staying solid even in wireframe mode, and retains its layer color even in rendered view.


(rendered view)

I’ve copied one object’s detail info below, it does look different than a regularly generated polysurface.

ID: 168d0ec8-7dcc-41b5-bb2f-dcee2197a1ac (4594)
Object name: (not named)
Layer name: 03_Materials::03_Massing
Render Material:
source = from layer
index = -1
Attribute UserData:
UserData ID: CE28DE29-F4C5-4faa-A50A-C3A6849B6329
Plug-in: 17b3ecda-17ba-4e45-9e67-a2b8d9be520d
description: User text (0 entries)
saved in file: yes
copy count: 487
UserData ID: 2D69C54F-CBC0-4118-BEDA-4B2FF58C6703
Plug-in: V-Ray for Rhino
description: V-Ray For Rhino Object
saved in file: yes
copy count: 53
UserData ID: 0D007E84-79CC-4b4a-850B-C23EF2CEC640
Plug-in: Rhino
description: Hide user data
saved in file: no
copy count: 2

Valid polysurface.
closed solid polysurface with 16 surfaces.
Edge Tally:
42 manifold edges
Edge Tolerances: 0 to 0.000959232
median = 6.40722e-09 average = 0.000319748
Vertex Tolerances: 0 to 0.000960191
median = 8.25354e-09 average = 0.000411512
Render mesh: 16 fast meshes 138 vertices 128 polygons
Analysis mesh: none present
Geometry UserData:
UserData ID: 6ADBBF65-A1D4-4d54-A0C8-BFAAB1A6086D
description: Technical Drawing Data
saved in file: no
copy count: 2

Hello - run SetObjectDisplayMode on these and make sure they are set to ‘UseView’


Thank you! Can you tell by the object detail that what kind of workflow will result in such change, other than directly using the SetObjectDisplayMode command.

Hello - I have a script I use - it will tell you if an object has overrides in what views, but not what that is:

To use the Python script use RunPythonScript, or a macro:

_-RunPythonScript "Full path to py file inside double-quotes" (2.0 KB)


1 Like