I created a Dynamo script to load in a series of materials to a project that are used in another Dynamo script. The materials are simple single color fills with a Raytrace material shader definition and flat shaded color definitions. And the script uses an import call from another project as a library file.
The problem occurs when I try to change the material definitions within the project after the materials have been loaded into the project.
If I assign a new RGB value to that Raytrace shader and render or change the view ot raytrace, the material shows the revised color scheme (i.e. the box that previously rendered blue now renders green). However after changing the shaded view color definition, the updated color setting for the shaded value does not apply (i.e. the blue box is still a blue box and not green). If I go back to the material settings dialog, it shows the correct material setttings for both shaded and raytrace shaders.
If I create a new material or duplicate the material, the objects with that new material then show correctly in both view styles, so it does not seem to be an issue related to the family.
Anyone encounter this before? Could this a result of using a Dynamo script to import my material pallate? Other thoughts?
This is in Revit 2015 and using Dynamo build 0.9.1. Although I have the same problem with Revit 2016 as well.
Also, I can't build the material definitions into the template since my office will not allow me to make those types of changes to our corporate template. And since this is used on multiple projects, the import script seemed the easiest way to incorporate it into the project each time the main Dynamo script was run. Thanks in advance.
Edited on: Tue, Mar 22, 2016 at 6:49:30 PM
|
Search
