Levels are set as Default in Templates in one file

In my "model" file where I have all my templates running, the templates levels are all set to default.

When I go to my "geometry" file where we I do all my linework, the templates levels are correctly set.

They use the same ITL and are in the same Workspace.

When I reattach the ITL it'll show it as the correct level, but when I try to apply the template, it goes back to default.

Is there a setting I accidentally have on that's breaking it?

For further clarification, I do not have Element Template Association on with an active level.

Parents
  • We experienced something similar. If memory serves, the DGNLIB that houses the feature definitions needs to have the levels in the file, they can't simply be available through the workspace. Once those were present, we saw levels managed properly by the Element Templates used in the ITL. Not sure it is exactly what you are seeing, but would be worth checking.

    Steve

    Steven Litzau, P.E. - Senior Consultant

    www.envisioncad.com

    ORD - 10.12.02.04 / 10.10.21.04 / 10.10.01.03 / 10.08.01.33
    Power GEOPAK / Power InRoads - 08.11.09.918
    Civil 3D - 2021 / 2022

  • The "rule of thumb" with OpenRoads- as my experience has taught me- is that all levels must be housed within the default feature definitions library (default: Features_Annotations_Levels_Elem Temp Imperial.dgnlib for English). I ran across an issue with SUDA a while back where I created levels within that library which were not replicated in this default library. In creating a new drawing, those levels were not seen resulting in the SUDA models being displayed on the "default" level. Upon moving these levels to the Features_Annotations_Levels_Elem Temp Imperial.dgnlib and removing them from the SUDA library, all of the levels showed up with their correct symbology. 

    Perhaps something else is going on here, but keeping the levels/ symbology in one single file seems to have made my life a bit easier.

    Mark

    Mark Anthony Plum
    Chief Technology Officer

    1601 N.W. Expressway, Suite 400
    Oklahoma City, OK  73118
      
Reply
  • The "rule of thumb" with OpenRoads- as my experience has taught me- is that all levels must be housed within the default feature definitions library (default: Features_Annotations_Levels_Elem Temp Imperial.dgnlib for English). I ran across an issue with SUDA a while back where I created levels within that library which were not replicated in this default library. In creating a new drawing, those levels were not seen resulting in the SUDA models being displayed on the "default" level. Upon moving these levels to the Features_Annotations_Levels_Elem Temp Imperial.dgnlib and removing them from the SUDA library, all of the levels showed up with their correct symbology. 

    Perhaps something else is going on here, but keeping the levels/ symbology in one single file seems to have made my life a bit easier.

    Mark

    Mark Anthony Plum
    Chief Technology Officer

    1601 N.W. Expressway, Suite 400
    Oklahoma City, OK  73118
      
Children
No Data