Hi all,
This is a bit of a weird one - there is a bug in OpenRoads Designer where it loads Nested References, even when Nesting is disabled. The display of Nested References is honoured, but you can see them being read on file open and there are numerous "file not found" messages for these Nested references in Message Centre. This is compounded by the fact that files in ProjectWise do not copy out these Nested References (as it sees they are disabled) and we get a "freeze" of the session every time it does something to attach a reference or open a file.
As there may be sometime till the next release where this will (hopefully) be fixed, does anyone know of any variables that can force the Microstation environment to not load Nested References?
I need all the reference files, but need to somehow force it not to look at Nesting (we don't use Nesting anyway due to the overcomplexity of tracking OpenRoads dynamic element relationships). As we have dozens of large reference files, each with their own long list of reference files and models, this is really slowing us down.
Regards,
Mark
Has anyone found a fix to this issue? It seems to persist in 2021 R1, regardless if using nesting or not. The only workaround I have found is to manually copy out all the files in our main design folder so ProjectWise finds all of the references of each design file. This still breaks if references outside the main design folders or if files from other projects are used.
OpenRoads Designer 2022 R1 | MicroStation CE Update 17 | ProjectWise CE 3.434
Mark,
Sorry if I've missed this. That makes it something where my knowledge ends.When you try to document this better, make sure to check that there are no errors in the references. Check for files that are only referenced in or renamed in 2D or 3D model only. Pay extra attention to the files that you reference, one or more of them might have some error that causes the references in that file to appear as nested in the file you are using.
Jan
Thanks Jan, but none of our files use Nesting? I'll have to spend some time to document this a bit better to demonstrate.
OpenRoads Designer 2022 R3 (10.12) | Microstation 2023.1 | ProjectWise CE 3.4
The short answer to your question is: it's looking for those nested reference files because you use nesting.If that is what the project needs, I think the question changes from what Openroads is doing looking for those files, to why isn't Projectwise copying those files to your local drive location.
I have just tested this using some of our files.The moment I change the nesting settings of an already referenced file, the nested files are copied from the PW server and loaded. If I save this file back to PW, close ORD, purge all local files, and reopen the file, all files are available locally.
I've seen this behaviour before with dwg files and assume it's by design, otherwise you can't use nested files.When opening a file, the PW pop-up window reports a certain amount of files to copy. During the copy process, the number of files increases according to how many nested files are needed. I sometimes end up with over 20 files, but only some of those are directly referenced to the file I'm opening.
If you don't want those nested files to be read at all, you will need to change the nesting depth, or set it to No Nesting. Otherwise I don't see any other solution.
Hi Jan,
Checking the files, others have things attached correctly, but Projectwise does not give me the references in their files unless I open it up myself. When I open up each of the reference files, i get all the references of these files and therefore no longer see the error.
But if I work on large projects where i may never open up files of others in different areas, I won't have had the nested references in my system and therefore get the error, which takes us back to the point of why is it looking and reading nested references at all?