Hey all,
Before I submit a ticket to Bentley support and packup up examples of everything, I thought I'd ask in here:
In a number of different instances now, users have come to me complaining that their references aren't updating anymore; Take a typical 2D sheet with some external references into the default model (at 1:1) and then a scaled self-reference into the sheet model. Normal behaviour is that all references are automatically updated - we have MS_REF_NEWLEVELDISPLAY set to 1 as a site variable and most of these problems are appearing in newly-created sheets from seed. Even if we key-in "update reference", or manually reload the reference, it refuses to update. The really fishy thing is that the self-reference refuses to update - if we draw any old thing in the default model, even that isn't appearing in the direct reference attached to the sheet model of the same file. So far the only fix is to detatch the file completely and re-attach it but that wastes all the work done in the file after the references and is a complete nightmare for layouts with multiple clipped references rather than something like a simple, single plan view in the sheet.
I have searched the forums briefly but can't find much other than the keyin, or the MS_REF_NEWLEVELDISPLAY variable. For the record, the reference files are not in use according to the reference status and the "reload reference" command ought to update regardless of whether someone else is using that particular reference, right?
Maybe it's a bug, maybe I'm wrong to expect all references to update dynamically, but I thought that the whole point of referencing instead of using saved views was so that you always saw the latest, live data.
Any suggestions/help appreciated.
I did find a work around but its still not tested enough...
Go to the nested ref file ...
detach the sub ref that has the new data that was not displaying save and close
open the the previous nest and reattach the sub ref
draw a line in the active parent nest ( its open now) delete the line ..
Save settings and exit
go to your drawing open the view and the updated nest and its children should now show the new data and new levels...
I have had this problem with nested files for years, I build the nest and use it in lots of drawings, then later the designers add extra features and levels in the child refs that were not on or present or used at the time I built the nest so next time I batch print these updates are not reflected in the prints... microstation should not behave this way ... it doesnt happen with non nested refs so why does it have to happen with nested refs.. we should not have to go through all this clumsy processes , after all how are we supposed to know the designers have changed the child refs, dont say they should tell me, refs are dynamic so why not nested refs.. this is a FLAW in the software and there should be a clear and easy variable to put in to the workspaces so it either does dynanic updates for everything or it doesnt because we want it too either way !
Its enough to put you off using nesting at all.....!!!! Come on Bentley Bros give us a variable for V8i ( and NO I dont want to use CE yet, we've enough problems in V8i! without find more issues .... and roll outs , retraining, custom tools and custom programs rebuilds etc very expensive very hard to justify to our masters benefits of the upgrade against downside increase costs)
FYI I found another simple fix was to unnest all the nests , in every drawing it was used, I recorded a macro since it was the same offending nest and batch processed ran it at client submission time to make sure everything was on and visible..... but talk about a bazooka to kill a fly....!
Lorys
Started msnt work 1990 - Retired Nov 2022 ( oh boy am I old )
But was long time user V8iss10 (8.11.09.919) dabbler CE update 16 (10.16.00.80)
MicroStation user since 1990 Melbourne Australia.click link to PM me
Unknown said: Go to the nested ref file ... detach the sub ref that has the new data that was not displaying save and close open the the previous nest and reattach the sub ref draw a line in the active parent nest ( its open now) delete the line .. Save settings and exit go to your drawing open the view and the updated nest and its children should now show the new data and new levels...
I bookmarked this just so I could try it whenever this glitch popped up again. This worked for me.
I have 20 or so files which reference the same nested reference file. I made updates to the nested reference file, and then after a batch print I saw the changes printed on only 1 of the 20 sheets. I followed your workflow for making changes to the nested reference file, then re-ran the batch print, and all printed sheets now show the updates made in the nested reference file.
Unknown said: Lorys Go to the nested ref file ... detach the sub ref that has the new data that was not displaying save and close open the the previous nest and reattach the sub ref draw a line in the active parent nest ( its open now) delete the line .. Save settings and exit go to your drawing open the view and the updated nest and its children should now show the new data and new levels... I bookmarked this just so I could try it whenever this glitch popped up again. This worked for me. I have 20 or so files which reference the same nested reference file. I made updates to the nested reference file, and then after a batch print I saw the changes printed on only 1 of the 20 sheets. I followed your workflow for making changes to the nested reference file, then re-ran the batch print, and all printed sheets now show the updates made in the nested reference file.
Lorys Go to the nested ref file ... detach the sub ref that has the new data that was not displaying save and close open the the previous nest and reattach the sub ref draw a line in the active parent nest ( its open now) delete the line .. Save settings and exit go to your drawing open the view and the updated nest and its children should now show the new data and new levels...
there really should be a better way ....!
Timothy Hickman
CADD Manager | CADD Department
timothy.hickman@colliersengineering.com
Main: 877 627 3772|
1000 Waterview Drive Suite 201 | Hamilton, New Jersey 08691
Yes to both ...
I build container nested file with refs attached and make up sheets for packages of works...
Later after client review the designers modify the ref files adding in more information and either populating old levels with new or changed data our levels are governed by dgn libs so they dont need to create new levels from scratch.. all levels are already there but not always used... my problem is that if some levels were off with or without data when they add new info my sheets dont reflect the new data changes....