JMR

Some ideas to try -Check 3D conversion settings in preferences, set to low for diagnosing purposes -Check viewport settings, set detail levels etc. to low -Check model geometry for insanely high number of polys -Check viewport rendering settings, turn off everything except eg. openGL -If still no difference turn off classes in the viewport and start turning them on one by one to find the culprit -Turn off planar information in the viewport -Check that no extra layers are visible in the viewport Hidden line viewports can be notoriusly slow, also room elevations.

After hiring a new employee, after a week or so has passed come the dreaded questions about the screen, screen aligned, 3D and working planes....they notice very quickly, that the boss might not be in complete control of these concepts himself...

Texture mapping controls are not available for subdivision objects, please see attached. In order to properly render a simple subdivision object with correct mapping, the subdivision has to be converted to eg. a set of 3D polygons, thus losing subdivision editability.

I cannot apply the mapping to a subdivision object even manually, that's the problem. Automatic operation would be great, but now I just want access to mapping controls.

Ok thanks. That answer was exactly what I was afraid of... 🙂 As a workaround I can change the subdivision object to eg. a 3D polygon and then map that. However, having to do so doesn't make any sense - what's the point of a subdivision object if it cannot be mapped=rendered properly? ...Or am I missing something obvious? Or is this something that has been completely overlooked?

Hi all, How do I control the direction of a (texture) surface hatch when applied to a subdivision? Attribute mapping doesn't work and I don't see any controls in the OIP? It doesn't matter if I select the whole subdivision of just one face. Please see attached

Interesting, thanks! I didn't know one could do that.

If I may, how does one build levels into the IF function?

Well well! This old thread saved my day. Using commas or dots did't work - but semicolon works! Why such hidden tricks....I was going nuts with my worksheets.

The VW help file is not very informative when it comes to curve degrees, here is a bit better explanation: https://knowledge.autodesk.com/support/maya/learn-explore/caas/CloudHelp/cloudhelp/2015/ENU/Maya/files/NURBS-overview-Degree-of-NURBS-curves-and-surfaces-htm.html and https://www.rhino3d.com/nurbs

I tried to do this with DV, and while it's kind of possible, it's not perfect and not quite what you want. -Line issues if using a 3D view with what's in front and what's not (top/plan would work) -Need to manually create DV settings for each year or range you wish to show -Need to use two viewports on top of each other -There are two records, date of construction and date of demolition. These are used in separate viewports.

Hmm, would it be possible to use data visualization in reverse, that is to apply zero width pen and none fill to all those buildings not in the desired data range? In essence, DV would "hide" stuff outside the data range, thus displaying only what is wanted. Not at the office to test but I would think this would work with simple box geometry at least, not sure about wall objects. I've used DV on plan drawings mostly so not certain how it behaves in 3D. I agree layers and classes are not practical for that number of different buildings.

@line-weight My humble suggestion would be to use DL's for separating different era buildings. That way your class system remains intact. Simply put buildings into correct DL's reflecting their built date. They can have the same elevation, too, if desired. Then turn those DL's off in those viewports you wish. You can still apply class overrides to them if you use two viewports on top of each other. W

Here is some further discussion on the subject and a couple of (not very fast) workarounds: A 3D tiling tool is very much needed.

Unfortunately I'm not sure how it was set up, only that using stories the walls within symbols worked.