problems with viewbase

[Anonymous]

hi 

I am working with autocad 2016 creating ga's of building structures.

all of the parts are xrefs with detail layouts

my problem occurs when i need to change things a little, say extend a column and move a baseplate.

i alter the column xref and reload it in the main dwg, move the base plate.

then when i go back to paper space and update the viewbase, the view now shows the new baseplate shaded as it should, and also shows the old baseplate position not shaded.

I have had this problem of showing historical objects in viewbase layouts. i have tried generating a new viewbase but they are still there. ive tried deleating the layout creating a new one then generating a new viewbase but they sill persist?

the main file size is about 24mb.

im running on windows 10 and running all the updates available for autocad?

any help on how i can recover these viewbases would be very helpful as the last time i encountered this problem i ended up redrawing the whole assembly in a fresh drawing.

thanks in advance 

[john.vellek]

Good morning pimpster33,

I am sorry to hear your woes about the projected views.  Would it be possible to send me a small version (attach to the thread) of your drawing so I can try to duplicate the issue and provide a solution? I look forward to helping you work through this.

[Anonymous]

Thanks for the reply John. I'll try to find time to stipe the drawing down to a state where it still has this problem but is small enought to post.

I have tried editing the view, going into model space to de-select parts but these are historical part and no longer in model space?

the other problem that frequently occurs is the view become dead, so when i double click on it i don't get the contextual menu allowing me to go into model space to define the objects and sometime they just go blank. when this happen i just have to erase them and start again but even after creating a new view with viewbase these historical/ghost objects still appear.

i had one drawing the other day that was working fine. i was just about to pdf and send to the client and a load of these ghost brackets appeared, and they were in the same place as an old drawing that was used to create a template file that this drawing originated from? couldn't get rid of them, even erasing the sheet creating a new sheet and new view these old brackets would still appear. I had to build the whole assembly again on a fresh drawing and then detail it again.

i am left wondering if autocad is suited to this work? lots of xref models used to create an assembly and detail on layouts all being cataloged with the ssm?

is there a better way to work?

[john.vellek]

HI pimpster33,

There is a known bug with the projected Viewbase views that I recently logged so hopefully it will have a fix in the next HotFix or Service Pack. In the mean time please attach your drawings so I can see if I can help.

I have not heard anyone mention the "historical" elements issue so I would really like to explore what's going on with that.

I look forward to working through this with you.

Please hit the Accept as Solution button if my post fully solves your issue or answers your question.

[Anonymous]

Hi John

I've attached some some of the drawing and xrefs

integra model 1 is the main drawing. There will be lots of missimg xref i'll attach a few more in the next post

[Anonymous]

here ar a few more xrefs

Any help on what may cause these issues would great.

There have been a few nested xrefs in these problem drawings? are these likly to cause me problems?

[john.vellek]

Good morning pimpster33,

I apologize for taking so long to respond this morning - lot of little fires to put out!

I am looking at your drawings and unfortunately I am unable to duplicate the "Historical" issue you are describing. I have tried moving items and then updating views and I don't see the ghosting you describe. Does the problem exist in different Visual Styles?

The problem that you describe, where basically the projected view disappears, I am aware of and I have logged that bug with development.

So, to move forward, can you tell me if this happens on a much smaller drawing as well as the large one you described? If so, can you send me a drawing, for instance, that has one column, a main brace, a spacer and then maybe have one or two projected views that display the problem? I would like to see if it is a filesize issue, an xref issue, or just an issue in general with the projected view.

I think the product can handle the datasize and complexity but want to see if we are flushing out a bug or if there is perhaps an issue with graphics hardware or the like. Thanks for your patience.

[Anonymous]

Hi John

I only normally use the shaded without hidden edges for this type of drawing. And it has only happens since have been using xrefs rather blocks .

It's been niggling away at me today but I've been rather busy so didn't have much time to play around with it as I was under pressure to get the job out.

However I did have some success removing the offending xref object by editing the view, de selecting them from the view, erasing the object, detaching the xref, then RE inserting the xref then adding the object s back to the view.

Very long winded and still not 100% effective. And by the time I have done this a couple of times I've lost all dim association.

So a couple more thing that I'm wandering might be related.

Some of the xref have been nested at one point other have just been normal xrefs. Is nested a good idea?

They don't seem to be effected by changes to the xref but rather there position or rotation in the main assembly.

To try to reduce the layers In the main assembly drawing all the parts are on layer 0 then when inserted in the main assembly I put them on different layers and set all the colours to by layer. This work fine most of the time but sometimes the colour shading will be missing on parent view and it usually missing on any detail view I pull off the parent view.
I personally find it looks cleaner without the shading but the customers like it so must persist with it.

I'm sure I'll come across the problem again and when I do I'll try to isolate it as much as i can and post some better examples. In the mean time if you can think of anything else I should avoid doing to try to avoid this happening then please let me know.

Thanks for your help

[john.vellek]

HI pimpster33,

I wish I could duplicate this so I could gain more insight as to what is causing this to happen. I don't think nested XREFs should be an issue.

Next time you run into the problem, check each individual drawing by using AUDIT and PURGE. If the drawing was not created clean you could even go to the point of using -EXPORTTOAUTOCAD. 

We should also check on file path types and whether xrefs are attached or overlay.

Please try to document for me what you can and if possible send me a small (simplified) drawing set that shows the problem.

Thanks for your patience.

[Anonymous]

Hi John

Ive had another look at the intergra drawing i sent you yesterday. 

I stripped out all of the unreferenced part and erased them.

I then erased all but 2 of the columns, went back to paper space and checked it was set to auto update the view

The view still didn't represent the model

I created a new viewbase and pulled some projection off it, these still showed all of the columns even thought model space only has 2 in.

I started to erase the old view and in doing so discoverer 2 views, one on top of the other? this was very strange as to best of my knowledge i had only created 1 view.

unfortunately i erase 1 of the before the significance dawned on me, but the one i erased showed an almost complete model with parts that hadn't been loaded?

anyway ive attached the stripped down drawing that also shows the 3 new view all showing old column that have been erased from model space?

as a bit of background i'm using windows 10 

intel xeon cpu E3-1220 v3 @3.10GHZ

16mg ram

with nvidia Quadro K2200 driver version 10.18.13.5362

thanks 

[john.vellek]

HI @Anonymous,

Wow! I am definitley able to see what you are seeing now. The only way I could force it to really do an update was to create a new projected view but that came in with only a view frame and no content. This is a bug I identified a while ago and have submitted to the Development team. I am going to escalate your case and tag it with the bug number so they can help you once they have determined a fix.

Thank you for your patience.

[Anonymous]

Could you please let me know if and when there is a solution to this as well.

Thank you

[john.vellek]

Hi @Anonymous,

If you subscribe to this post I will keep it updated as I find out any updates.

Thank you and others for your patience regarding this issue.

[john.vellek]

Hi @Anonymous,

A solution that has helped in some cases has had to do with turning off all layers, updating views, turning on a layer, updating view, turning on the next layer, updating views, etc.

@elshawadfy wrote up a lisp routine to help automate these steps. I have attached it here for you to

Please select the Accept as Solution button if my post fully solves your issue or answers your question.

[Anonymous]

Hi John,

Unfortunately, this lisp file does not seem to work for me. All my Views are still incomplete after I run VBUP

[john.vellek]

Hi @Anonymous,

Is it possible to recreate the views?  Some users have had issues that when creating the views that not all the geometry was present.  The problem also appears to be related to creating views in older releases and then opening in newer releases.

[Anonymous]

Thanks for your help with this issue,

All the views and Drawings are created using AutoCAD 2017 and the geometry is incomplete

However, the Blocks I am currently using were created using AutoCAD 2015. (Not sure if this is the issue)

If I use AutoCAD 2015 everything works great.

[Anonymous]

It doesn't seem to matter if I delete the views and re-do them. It still doesn't draw all the geometry in the views

[john.vellek]

Hi @Anonymous,

Is it possible to attach a drawing so I can try to duplicate the problem?

[Anonymous]

I have attached a drawing that has this issue.