@hari.lallGSCRP wrote:
Folks
I tried the process of elimination. Divide the xref into half and half and see it how it behaves and I can confirm the problem is not the xref but the excessive data in xref which the CPU cannot process. If I divide my xref in 2 parts and bring it in one at a time there is not issue. Bring both in and I am back to square one. During this task I was also keeping an eye on the PC performance manager. Even attaching, detaching and panning is giving a huge spike in cpu utilization. Jumping from about 5-10% to 60-70%.
Anyway my conclusion based on this and all the advise given on this post is that my CPU is bottle necking the drafting procedure when huge data is xref'd into a drawing. So to back to IT for an upgrade 😞
I would have used a similar process for testing but I don't think it's an inadequate processor. A better one may hide the issue, it might not, but unless this workflow is well established and other people doing the same thing require a better processor, I wouldn't come to that conclusion.
Most of the time these issues can be solved with proper file processing, i.e. cleaning up. If this is a file from a 3rd party source, you can't rule out bad CAD without further investigation. That's why we ask to see the file. Some of the people here are really good at finding issues with files.
I would post your question in the C3D forum if you absolutely cannot share the file. This is the AutoCAD forum and there are a lot of things about C3D that primarily AutoCAD users may not know.
Rob
Drafting is a breeze and Revit doesn't always work the way you think it should.
