Arrays converts to blocks

Arrays converts to blocks

jporter
Collaborator Collaborator
2,270 Views
8 Replies
Message 1 of 9

Arrays converts to blocks

jporter
Collaborator
Collaborator

I have a client using AutoCAD Mechanical 2021 (fully updated) with the same issue.  To clarify. . .

  • He is using the new array command (not the classic array).  
  • He likes the new array command and is using it correctly. 
  • In his drawing he will create an ARRAY and it remains an ARRAY (as it should), but there are other arrays that he's done that mysteriously, automatically convert to unnamed blocks for no apparent reason.  
  • He has not exploded the array.  
  • He notices the issue when he saves the file, closes it, and reopens later.  
  • It's not an associative setting because it's all one block, not a lot of individual blocks.  

array-01.png

array-02.png

Any ideas?  

 

[This post has been split from another thread by cheryl.buck]

Jason Porter
ASTI Civil Solutions Technical Advisor
www.asti.com
0 Likes
2,271 Views
8 Replies
Replies (8)
Message 2 of 9

cadffm
Consultant
Consultant

Hi,

>>"Any ideas? "
Read this Thread here, ideas are already written above.

We are searching for a process which destroy the "internal links" / i don't know how should i name these internal things for you.

 

>>"I have a client using AutoCAD Mechanical 2021 "
I know about one issue what was present in 2017 (2018,2019 untested)
what is fixed in 2020 and the trouble started again in 2021 (2022/2023 untested).
But this sample is very special and pretty sure noch the case in your file.

Arrays in paperspace: If you insert this layout by "from template" into another file,
the internal block loose the link to his array dataset. Result:
The block doesn't appears as "Array" and loose all the Array possibilities.
(In AutoCAD an aray is every time a blockreference of a block, just hidden from user eyes)

I checked this old and fxed bug, and the bug is back in  Mech2021.

 


>> "He notices the issue when he saves the file, closes it, and reopens later"
If he find the issue after open the file, he should share the DWG and BAK file with the community.

a) Perhaps he didn't notice the issue in the last session because it looks normal
or
b) Perhaps the Problem is "invisible" until you reopen the file,
but in this case i guess the normal open process is not enough.
Recover? Audit?

And don't forget 3.party tools like poor written "dynblock to static" or similar.


I don't know how to help now, but i will follow this thread.

Sebastian

0 Likes
Message 3 of 9

jporter
Collaborator
Collaborator

@cadffm, an FYI - I did read the thread.  I'm checking back after several years of silence to see if there is anything else because the ideas here don't pertain to a solution.  The issue is not how he is creating the array.  I witnessed him doing it.  The original post by @jeroendewind is exactly what is happening to my client.  The rest of the posts talk about not using the new array command, the associated array setting being incorrect, the drawing being at incorrect coordinates, verifying all updates are installed, the drawing being saved with another software, purging out data, auditing the drawing, recovering the drawing, and the warning of run lisp routines.  

 

None of this pertains to my client's situation.  Prior to posting here I had already done my due diligence.  I've audited, recovered, and purged.  Nothing makes those arrays turn from blocks back to arrays. 

 

He created the file in AutoCAD Mechanical 2021 (fully updated) and I opened on my end in AutoCAD 2021 and AutoCAD Mechanical 2021.  The arrays are still blocks.  I also opened in 2022 software to see if that had any positive effect on it. 

 

The main question is, "why does a perfectly good array mysteriously convert itself to a single block, and is there no way to convert it back to an array?"  I assure you the array was not exploded because, if it was then every item in the array would be a separate individual item.   In his drawing the array comes in as one entire block.  

 

I have the drawing.  I don't have permission to post it.  But even if I could all you will see are the some arrays and some blocks.  

 

 

Jason Porter
ASTI Civil Solutions Technical Advisor
www.asti.com
0 Likes
Message 4 of 9

jeroendewind
Enthusiast
Enthusiast

Glad to read I'm not the only one 😄

Still no clue btw after all these years, so happy to see this coming up again, tho the urge is kinda gone

Message 5 of 9

jporter
Collaborator
Collaborator

I made a video to better clarify this (sorry, for some reason the Screencast wouldn't post directly as a video to the discussion):  https://knowledge.autodesk.com/community/screencast/f3f534f7-e170-4329-9345-c835ecd690bb  

Jason Porter
ASTI Civil Solutions Technical Advisor
www.asti.com
0 Likes
Message 6 of 9

jporter
Collaborator
Collaborator

@cadffm, thank you for your input.  I primarily responded to this thread because the issue appears to have been going on for some time with no real resolution.  I am hoping the more traffic will bring this more to the attention of Autodesk.  

 

I have run a recover and audit with no red flags.  There is no third party software involved.  

 

The user simply creates an array, saves the drawing, closes it, and returns to it at a later time.  He's not at all new to the software.  We've ruled out possible finger fudging or user mistakes.  The big question we both have is that, "how do you even manually convert an array to a block?'"  We've even exploded the block, thinking we can take it back to an array, but it only explodes to linework.  

 

Still searching. 

Jason Porter
ASTI Civil Solutions Technical Advisor
www.asti.com
0 Likes
Message 7 of 9

pendean
Community Legend
Community Legend
@Anonymous why the continued re-postings in an old thread, especially after a 3-ish month relapse?

And if I may also ask, why are you trying to figure out a problem "after the fact" in plain AutoCAD of a drawing create in MECHANICAL by someone else who appears to not know how it was done, maybe?

How would anyone be able to answer a 'why' question if all you have is an after-the-fact DWG file?
How does one recreate the problem on demand over and over again?

IMHO please start a new post (in the MECHANICAL forum apparently for the originating source), include a DWG file, explain how everyone can recreate the "arrays turn into blocks" process that is repeatable in that DWG file, and you might get an answer. Sadly, an after-the-fact DWG file is of no use to anyone to backtrack on why it happened. This is not to take away from the creator's experience (or yours) or lack of it in AutoCAD/MECH of course.

Curious more than anything.
0 Likes
Message 8 of 9

jporter
Collaborator
Collaborator

@pendean, I only reposted here because I found the problem here that my client, who is using Mechanical, is having.  So, since Mechanical is built on top of AutoCAD I do believe if the issue can be resolved here then it can be resolved there as well. 

 

I agree with you. . .it's hard to figure this out because it isn't until later that the problem arises.  It cannot be created on demand.  My question of "how do you even manually convert an array to a block?" was more of a "how does the software do this and not the user."  I'm not looking for an answer to this question.  I don't believe any one of us has an answer for that.  

 

And I've not posted a file because of exactly what you stated. . ."an after-the fact DWG file is of no use."  

 

This discussion can end here with me.  I've opened a case with Autodesk to see if they can help.  If they provide any insight I'll be happy to come back to this again.  

 

Jason Porter
ASTI Civil Solutions Technical Advisor
www.asti.com
0 Likes
Message 9 of 9

sylvie_carignan
Community Visitor
Community Visitor

Allo, about this topic, I have the same problem of arrays turning into johndoe blocks, It appens when I use the command "edit block in place" + add the array into the block. I guess there will be no solution to restore the array but you will at least have a new clue.

 

thank you.

0 Likes