A user here has an Autocad reference which has a nested Autocad reference in it. In XM the nested reference shows up but in V8i it doesn't. Any ideas of why this would be happening?
Does the nested xref possibly create a self-reference? A DWG cannot be referenced to itself, no matter how far down in the reference tree it might be. If the reference nesting will eventually cause the DWG to reference itself, AutoCAD will not display it. However, during the opening process, AutoCAD will almost always display a message if a circular reference like this one is found - problem is, it displays all kinds of stuff when opening a file, so ti can be missed. Press F2 once AutoCAD is done and you can seeall the messages it displayed - perhaps one of them will explain what happened. I'm guessing it's the self-referencing issue, though.
Hope this helps,
Thanks Jeff but we're not trying to open this file in AutoCAD. The problem is there is a serious difference between opening the file using V8i and XM.
Do the undisplayed references show up in the reference list as unresolved/red? If yes, then it's unlikely we are talking about circular refererences but an incorrectly defined MS_RFDIR.
No they don't show up red. We are using the same network config stuff for both V8i and XM so I'm a little perplexed as to why the reference would show up in XM but not V8i.
I assume that means they appear in the hierarchy, but do not display. It is unlikely any of the obvious answers (e.g. Ignore Attachment when Live Nesting) apply b/c the references display in XM. However one thing to verify is that you are resolving the same reference in both XM and V8i. If you hover your cursor over the attachment in the References dialog, a tool-tip will display showing the path to the reference. Are the paths identical in XM and V8i? If the undisplayed references appear in the reference hierarchy, ignore attachment when live nesting is OFF and the reference paths are identical between versions, then I would ask you to ZIP the files and place them on the FTP site.
I checked the path using both XM and V8i and they are both the same. I've uploaded the test case to the ftp site and the file is called "jkkTest.zip". If the you open the DGN file, the reference file that is not showing up is called "x-Restaurant.dwg". Let me know if you need any other clarifications. Thank you.
The issue here concerns how MicroStation handles DWG references placed on user defined levels. A bug resulted in MicroStation not only controlling display using Global Freeze, but also View Display and Global Display. Until TR 249261 is fixed, the workaround is to identify the level on which the undisplayed reference is placed and ensuring that the Level Display is not OFF. I sent you a private message placing the workaround in the context of your data set. Let me know if you have any questions.
We are having a similar problem. I found that, if I opened the original file in AutoCAD, and re-attached the problem Xref, it would show up as a 2nd reference once I reopened the file in V8i. At that time, one ref would display, and the other wouldn't. So, I just deleted the problem reference.
Of course, this is just a workaround--we don't want to have to continually be reattaching Xrefs in AutoCAD.
That does not sound like the same problem John initially has. John's issue is directly related to levels in DWG reference file that get globally turned off (as opposed to globally frozen). This particular scenario has triggered a bug described in Chris's previous response and the result is that elements on these levels, though globally turned off, should be displayed in master file but they are not. If you saw entire reference file not shown in V8i, that could be a different issue. Was the same problem present on XM? Do you still have the original file for us to take a look at?