block visibility

[buildwitharch]

Good morning.

 

I have a set of dynamic blocks that I have been using for quite some time. I have just recently started having a problem inserting the blocks into my working drawings which were started via my template. When I try to insert the block, it doesn't show up. I checked at 0,0 - not there.

I have checked all of the layers and they are on. I have tried inserting the block in a drawing that had not previously had the block in it as well as a dwg that does have the block already in the inserted blocks list. I have purged and reinserted with no help.

 

The block will insert into a drawing that I start from a default Acad template (dwt) that has none of my info in it. So I know it's not the block.

 

Any ideas?

 

Thanks.

Aaron

[tinkerbell]

did u try to zoom all? when u crate e block is it in 0,0,0 placing? if not then your block might me hiding sumwhere.. either too small or very far from insertion point 0,0,0 gd luck~

[buildwitharch]

Hi Tink. It's not going to 0,0 and my scale is set to 1 all around. I'm sure it's some strange setting in my template drawing because it works in a default cad dwg. Thanks tho.

[Ryder76]

Try using "quickselect" to see if you can locate the block and go from there. Are there any layers that are frozen, locked or turned off that the block may be getting inserted on?

[buildwitharch]

Hi Ryder, Thanks for the tip on quickselect. That will be useful.

 

Using it shows that the block is in the dwg. The grips show up but not the block. By selecting the grips, I am able to open the block editor and in there, the parameters and actions are visible but not the drawn parts. And still, all layers are on.

 

I think we're making a little progress.

[buildwitharch]

Has no one had this problem before?

[Dana W]

Does the block have a Visibility State Parameter? If so, Is it set where you would expect it to be?

[brl2008]

did you rename the block and then reinsert under the new name. i have had to that once or twis.

good luck

bruce

[buildwitharch]

Does the block have a Visibility State Parameter? If so, Is it set where you would expect it to be?

Hi Dana, It has multiple Vis states. The default V.S. shows up fine in the drawing started thru the acad default drawings but not in the template drawing.

[buildwitharch]

did you rename the block and then reinsert under the new name. i have had to that once or twis.

good luck

bruce

Hi BRL. So, check his out. I tried your suggestion. It works... hmmm... So I changed the name back in the drawing that I am referencing with design center and it won't work again. My theory is: I must have the block screwed up in the template drawing some how. Because the block is in the template already, it messes up weather I insert if from within the drawing or from outside. Weird. But anyway.. I will purge the blocks that are in the drawings and reinstall the ones from outside that do work. I can redefine a template with working blocks. It doesn't answer the question about why it's doing it but as long as I have a solution, I don't really care about that...

 

Thanks BRL and everyone for your input.

 

Happy Friday

[Dana W]

Hi Dana, It has multiple Vis states. The default V.S. shows up fine in the drawing started thru the acad default drawings but not in the template drawing.

 

That's pretty odd.

 

Coincidentally, I was just trying to build a dynamic block with a stretch parameter. This happened just now.

 

I got it to work, but as usual, some of the objects were not included in the stretch area through my error, so I went back and edited the block a couple more times. I erased the stretch action and the distance parameter, and than put in new ones with a stretch area including all the stuff I want to move with the stretch.

 

After a couple of opening and closings of the block for edit, my stretch parameter disappeared from the block inserted in the drawing. When selected, all I see is the insertion point of the block. I cannot access the stretch. In the block editor, the parameter is still there. Erasing the block and re-inserting does no good. Re-naming and save as, re-insert also does no good.

 

I purged it, rebuilt it, and after another edit or two, the stretch parameter disappeared again. In niether of the cases did I change anything relative to the parameters or the stretchable objects

 

I think this is alot like your problem and I have no idea what is wrong. I am getting in line behind you to see if anyone else knows what this is all about.

[buildwitharch]

That's pretty odd.

 

Coincidentally, I was just trying to build a dynamic block with a stretch parameter. This happened just now.

 

I got it to work, but as usual, some of the objects were not included in the stretch area through my error, so I went back and edited the block a couple more times. I erased the stretch action and the distance parameter, and than put in new ones with a stretch area including all the stuff I want to move with the stretch.

 

After a couple of opening and closings of the block for edit, my stretch parameter disappeared from the block inserted in the drawing. When selected, all I see is the insertion point of the block. I cannot access the stretch. In the block editor, the parameter is still there. Erasing the block and re-inserting does no good. Re-naming and save as, re-insert also does no good.

 

I purged it, rebuilt it, and after another edit or two, the stretch parameter disappeared again. In niether of the cases did I change anything relative to the parameters or the stretchable objects

 

I think this is alot like your problem and I have no idea what is wrong. I am getting in line behind you to see if anyone else knows what this is all about.

 

That sounds very similar. The key to getting mine to work was renaming the block outside of the working dwg. That way when I reinserted it, it was brand new to my working drawing. If you tried that then I don't know. Like I told BRL, I still have not clue to the problem but was happy with an alternate solution. Hopefully it will work for you too

[Dana W]

That sounds very similar. The key to getting mine to work was renaming the block outside of the working dwg. That way when I reinserted it, it was brand new to my working drawing. If you tried that then I don't know. Like I told BRL, I still have not clue to the problem but was happy with an alternate solution. Hopefully it will work for you too

 

I have not tried that. I will rename and move the block to a BLOCK LIBRARY drawing I have, which is where it will end up anyway, and insert it in a couple of test drawings to see what catches fire.

 

I think the communication between the block editor and the drawing is leaving something out. This is starting to feel like an Autodesk issue. We'll see.

 

When a subroutine (Block Edit) passes data back to the calling program, there has to be data in the "List of Stuff Not To Lose", so to speak. I think it is not passing all the data back to the program after an edit or two. The editor is probably initializing the "List of Stuff Not To Lose" one too many times or not reloading everything afterwards.

 

I won't speculate any more here because I have not been a Programmer/Analyst for some time, and it doesn't feel good. I didn't like IT, not enough of a squint, I guess.

[buildwitharch]

I have not tried that. I will rename and move the block to a BLOCK LIBRARY drawing I have, which is where it will end up anyway, and insert it in a couple of test drawings to see what catches fire.

 

I think the communication between the block editor and the drawing is leaving something out. This is starting to feel like an Autodesk issue. We'll see.

 

When a subroutine (Block Edit) passes data back to the calling program, there has to be data in the "List of Stuff Not To Lose", so to speak. I think it is not passing all the data back to the program after an edit or two. The editor is probably initializing the "List of Stuff Not To Lose" one too many times or not reloading everything afterwards.

 

I won't speculate any more here because I have not been a Programmer/Analyst for some time, and it doesn't feel good. I didn't like IT, not enough of a squint, I guess.

Let me know how it turns out for ya.