Help,
I used refedit to freeze a couple of items that were nested. My drawing file/machine locked up when I attemped to freeze them. I had to reboot it, when I opened the file again I was still stuck in refedit mode. I cannot use refclose to get out our that command. It wants me to use refedit again. I need to get back to my work.
THanks,
Jim
You need to post to one of the AutoCAD groups. Let us know what version you're running.
Allen Jessup
Allen Jessup
CAD Manager - Designer
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
Then your best bet would be to post to the MEP group or the Autocad 2012 group since Refedit is a basic Autocad command.
Allen Jessup
Allen Jessup
CAD Manager - Designer
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
Yes my autocad is up to date.
I was in a design drawing and I needed to freeze a few lines in the nested structural drawing. When I double clicked on the structural drawing I went into the refedit mode. That's when the problems started. I am still currently stuck in that command. How can I resolve this.
So what you are saying is for me to insert this drawings into a new blank drawing file? How will that allow me to get out of the refedit mode? If I can't get out of this mode I will loose quite a bit of work.
Thanks for your reply.
Jim
Well, layout information won't be salvaged via Insert.
But, if the model space informaiton comes thu to the new file, it's certainly better than nothing. It's possible that importing the layouts from the old file via Design Center will bring in the paper space information -- I've never had a drawing in that situation, so I'm not sure what ADC will be able to grab.
On a side note to the OP -- what version of CAD are you running? My initial experiences with REFEDIT were less than satisfactory (corrupt drawings etc) and I've never been willing to try it again since the initial release. If your software is current, then I think I may continue to ignore that 'feature' as too dangerous to use despite the superficial advantage over XOPEN.
If your software version is older, you might want to post the dwg file, and we can see if a new version can open and recover.
Oops - just noticed that you are running 2012 - still, worth trying to recover in a newer version.
@pendean wrote:
This is a known 2012 problem, pre-update: once a file is messed up there is nothing to do to recover it intact. It's been posted and discussed before, and acknowledge by a 'Desker.
Good to know. although noting the OP states his 2012 version was updated My initial experience with RefEdit corrupting Xref'ed drawing files pre-dates the 2012 release, and were not at all related to being stuck in RefEdit as the OP is experiencing. I've not had a willingness to corrupt other working drawings using the command, and haven't heard that it's become bulletproof in the interim. Then again, I haven't paid a lot of attention to it -- XOPEN works quite well, and is (so far, knock on wood) entirely reliable.
I will use RefEdit to tweak a block instead of block editor - especially those that come from DGN files, since every cell instance becomes a unique block rather than an instantiaion of a single block definition, but do not consider it worth the risk for Xref files. YMMV
To the OP - instead of using RefEdit to simply freeze a layer in your reference file, the Layer command will do a better job, especially if your are working with Visretain on. Freezing a layer in a referenced file will not impact the display in the working drawing if Visretain is enabled.
I had a similar problem with Civil 3D 2021. I saved the Xref changes, I then opened the XRef that I was editing and saved and kept it open. In the original file where I was 'editing in place' I discarded the changes made to the xref. That then closed the Refedit. I managed to save the original drawing and then re-loaded the xref. No work was lost in both files.