I am using OpenRoads Designer CONNECT Edition - 2020 Release 2 Update 8 - Version 10.08.01.33.
When using the Drawing Production tools to generate plan sheets, it seems that the nesting depth parameter of the resulting Drawing model and Sheet model are arbitrarily hard-coded to a value of 99. I would have expected that the nesting depth value should have been "passed through" from the DGNLIB that is being used to generate the sheets. Here are some screen grab images.
The left side image is from the DGNLIB and the right image is from the resulting plan drawing model.
The left side image is from the DGNLIB and the right image is from the resulting plan sheet model.
Can someone please confirm that no matter what value is used in the DGNLIB file that the resulting drawing model and sheet model will always have a value of 99? Is there something special about this value of 99 that is being used?
If the nesting depth value cannot be controlled in the DGNLIB file, then is there perhaps a Configuration Variable setting that dictates the value in the resulting drawing model and sheet model files?
So far, the only work-around I have been able to come up with is to create a VBA macro to post-process the cut sheet files to adjust the nesting depth values in the drawing model and sheet model to values of 1 and 2. This macro is pretty sluggish, but I might try to revise it to run in a background thread of MicroStation as opposed to having to open each DGN file and model.
Any updates on this? Wondering why also, using 10.10 r2
Anyone know if this is still an issue? Crazy if it is.
Steve:
I am on ORD 10.12, and my best recollection is that this issue is still the case. I will check again when I get into the office tomorrow.
Best Regards,
Mark
Someone correct me if im wrong, but is this really an issue?
Although Nesting of the Sheet/Drawing models are set to 99, it will not override the nest level of the references downstream, ie. only dig down to the respective nest levels for each nested reference. The setting of 99 just caters for an instance you ever have nested references going that deep (which no one would), but ive never seen it go any deeper than the settings used in the design models.
The file open nested reference loading ssue is something a little different and is not affected by specific Nest levels in the DGN. They fixed it in Microstation CE 17.2, but my understanding Civil models still have this issue due to how it loads dependencies (which i hope gets fixed soon).
Regards,
OpenRoads Designer 2023 | Microstation 2023.1 | ProjectWise 2023
I was under the impression that the 99 nesting depth was a primary cause of performance issues, especially on large projects working on ProjectWise. We are certainly experiencing that now on a large project, but i haven't done detailed testing to verify that is the issue.