I also just started having this error. Before today everything was fine, well, I was able to save images after editing them. At least there is a work around.
Oh, and on top of this, today I am crashing like crazy.
Well, I justed edited my .tif file and did the Save-As. RD saved my scan. Unfortunately the file size is larger than the original file Not what I was looking for or expecting to get. At least it looks a lot better.
We installed AutoCAD 2011 and Raster Design 2011 on a Windows 7 (64) desktop. We opened an AutoCAD drawing file, inserted an image file. Used the raster design remove command to remove a part of the image. Saved the image and drawing file and the typical error popped up telling us the image cannot be saved with the existin name and must be saved as a tmp name.
New AutoCAD, new Raster design. What is the issue? When will it be fixed or am I missing something here? If anyone can correct me, I would greatly appreciate assistance.
I do not know about the other versions besides 2009, but in our testing of this issue, we noticed that using the RD 2009 Save command does actually save the original image file even though that "cannot save" error msg pops up and it then creates an additional .tmp file.
Has anybody using either 2009, 2010 or 2011 noticed that the original file is being saved even though they are presented with that error msg? You may just have to open up the original image file in MS Paint or something similar to determine it is actually being saved.
This has been a known issue since 2009 - and Adesk makes one user think they are escalating their attempt to fix this back in April of this year...where are the results of that "fix" they are working on...and will that fix be made to all versions of RD that are currently supported?
Yes, I noiticed that even though it comes up with the message about it being unable to save the tif and it does create the tmp, if I just delete the tmp it has saved the original anyway and is just fine... This is unfortunate because I believe it has caused much lost time for us to "discover" this for each person finding this error.
Just a thought... try checking the length of the path where the file is being saved to.
We have had this problem which was rectified by shortening the path name.
Not sure what the limit is but this worked.
Does anybody know if this has been fixed yet? I'm still on 2010 and this is a real pain. Seems like it should have been fixed by now if AD really put some priority on it. What about the newer versions? Thanks.