slowing down using the block editor

[Antonio1981]

Hi guys more and more often I get a troublesome moooolto problem that is driving me crazy:
in my drawings use of the blocks, sometimes even simple sections of beams without nets and anything else so as to be as light as possible, but every time I open a block to change it, save and exit from the editor autocad blocks implant, become very slow and snappy, it happens to me both on the version 2011, 2012 and 2008 !!!:angry::
the only way to resume fluidity is to close and reopen the design.
but how it is possible that if it is a programama bug if they bring it back from four years old!
Give me some help because I'm freaking out.

a greeting to all of you

 

[PlannerRoad]

Do you do it with all the drawings or just with some?
even with simple blocks?
and instead using the local modification of the block?

 

[Antonio1981]

with all drawings, even with simple blocks and while changing in local

 

[Antonio1981]

I tried on another machine with operating system xp 64bit and autocad 2011 installed this morning, but the problem looks the same, confirms me even more than it can be a bug!!

 

[Tristan]

I tried on another machine with operating system xp 64bit and autocad 2011 installed this morning, but the problem looks the same, confirms me even more than it can be a bug!!

never happened, from 2006 to 2012...

 

[PlannerRoad]

never happened, from 2006 to 2012...

Me neither!

 

[Antonio1981]

perbacco...!, I happen to both on pc at home and in the studio...the size of the files are in the order of about 10 mega, how could I do to locate the cause.? ? ?

 

[stefanobruno]

come potrei fare per individual la causa..???

already it is difficult to solve when you have the file in hand, let alone not having it.
did you try to erase everything except what you actually see on the monitor?
Sometimes you have hidden entities that cause this kind of trouble.

 

[robertobacci]

It happens to me if I open files made with other cads or exported from the 3d in dwg and one if I create blocks, once the editor of blocks the mouse goes to snaps and I have to close and reopen the file. If I create another block, I have to close and reopen again.
It's really annoying!

greetings
roberto

 

[GP.]

seems not to exist an absolute remedy, tempted with these suggestions, one at a time: http://forums.autodesk.com/t5/autoc...r-accessing-block-editor-or-xref/td-p/2491565or this: http://usa.autodesk.com/adsk/servlet/ps/dl/item?siteid=123112&id=14898223&linkid=9240617

 

[Giuseppe Mauro]

that of the building of the blocks with subsequent slowdown is a bored problem of autocad. but he also has an explanation.

First, the 10mb antonio file is a heaviness monster, especially if (as it says) tries to keep it light in management.

I have a finished file just yesterday, which contains 18 boards a little larger than a1, complete with square masks etc.
the total objects of the drawing (and with objects I also mean the blocks, which count as 1 object, but contain several entities) are just over 17 thousand. my file weighs 4.3mb. a 10mb "clean" dwg, how many entities will it have to contain? ?

we know that another dwg is that the design database, and that for each entity' there is a list of features that defines it (starting and ending points, rotations, color, layer, line, subential events' associated as dim control points, attributes etc)
well, this database, compressed on disk in dwg format, is expanded in ram to be able to operate.
when an entity is changed, its new definition is rewritten in the database that is in ram, but the old It is not thrown away to allow that simple command that is undo.
autocad does not have a limit in the level of undo (unlike many other programs), so that you could theoretically work for 12 hours on a dwg and return after 12 hours to the state of departure to fury of undo.
but this means that in ram, it remains trace of all modified entities, and this happens every time it changes, even a modified entity.
When this change affects not a single entity, but a block, it goes as if the change of one entity, actually affects 1 entity, multiplied the number of insertions of the block.

that means that modifying a block, increases the size of the database, which is written not only in ram, but also on disk (if sometimes autocad crashes, search in temporary and you will find your beautiful undoxxxx.ac$ files)
therefore to make those beautiful menatite type selectionpreview, autocad must know to the mouse passage which entities are flowing under the mouse, and to know it must access the updated database, which in part remains in ram, and the disk part (with the slowdowns of the case).

All this ends when? When autocad knows we won't need the grapes anymore and he'll drop the data to go back. When does this happen? when we close the drawing. Not when we save. but only when the design is physically closed. only then will the undo levels be permanently abandoned and the recompacted database.

here explained the behavior of autocad and the failure to solve the problem. if we eliminate the undo command, 99% the problem disappears, but who would be able to work without undo?

rather you have to work with more awareness, and give a hand to your pc.
retina: one of the maximum commitments for the autocad database and the video card. Although it seems simple, every single line of a retino, for autocad is an entity, which must be written, managed and redesigned. It's like a huge block repeated according to specific rules, and it usually occupies a sea of space compared to other entities.
test: autocad is born to manage shx fonts (the ones in simple line, to understand us. type romans, romand etc.). the management of the ttf files (font of windows) although now on the agenda, but commits resources, less in the database than in the phase of redesign. have as standard text style an arial, compared to a romans, weighs heavily on the work of redesign to video (and therefore the responsiveness of the pc)
blocchi: Blocks usually lighten the autocad database, but only the one on disk. have a file consisting of 100,000 insertions of a block, consisting maybe of 4 lines and a retino, will probably reduce the dwg to a few kb, but in ram will become 400,000 lines and 100,000 nets. If it wasn't, it wouldn't be possible to snap on a block line or use an entity contained in a block as a cutting limit or extension, for example.
Objects: one of the biggest damage to the size of files on disk. Many insert in autocad for example images simply dragging them into the dwg, or with copy and paste. Nice... practical... comfortable.
but try to look at the difference in the file size between a jpg inserted as external reference and the same jpg inserted as ole.
with copied images like ole, autocad files begin to swell in a disproportionate way, things like my 18-table dwg, if the cover images were not external references, would have passed from 4mb to 80-90 without problems

Keep yourself "clean" in autocad dwgs, and the "scattosity" problem you will see very little.

I'm sorry for the huge amount of juice, but it can be that it's for someone in the future.