david c.
-
Posts
14 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Articles
Marionette
Store
Posts posted by david c.
-
-
Thanks for the tips guys. I've thought about other possibilities, however, our project teams have been at times as big as 8 architects all sharing and referencing the same files. It is a necessity to work from the server today. As for the backup, it is only run during non-work hours when files have been closed. Even then, the backup server does not have rights to restore or update back to the working directories on it's own. This new issue has only come up recently with the update to 12.5, never in the past have I had network file corruption issues like this.
-
Katie, a new issue just came up today. This is not the same user. Client is VW 12.5, OS X 10.4.7. Server is OS X Server 10.4.8. File was opened over the network for viewing and closed without saving. The result is a 4k corrupted file. The entire path and file name is fairly long. We have large projects, multiple users accessing files, many files nested deep within project folders. It's always possible that someone else may have tried to open the file. The main problem I see is that things have changed for the worse after I updated to 12.5. I saw this happen once pre12.5 and about 5 times now post 12.5. Thanks for your help as always.
-
A subrow (or database row) can be selected in its entirity, but not by single cells. What are you trying to accomplish? If you're looking to make a change to a value defined in a cell of a database row, you will have to change it in the data pane of the object info pallette.
-David
-
Katie,
My most recent occurrance of a corrupted file happened on Friday of last week. It resulted in a 4k file. The client is on Mac OS X 10.4.7, VectorWorks 12.5 and the server which he was working from is Mac OS X Server 10.4.8.
Disk Utility/Repair permissions was last run on Wednesday after a server software update. Repair permissions is usually run when running software updates, but not frequently since it only repairs system file permissions.
-David
-
I'm having similar issues. We are running Mac OS X Server, Mac OS X 10.4.x and VectorWorks 12/12.5 on client machines. We end up with 4k and (zero k) 0k corrupted files that cannot be recovered. I've been recovering successfully from backup, but it has happened enough now that I'm starting to get curious about what's happening. This has occurred pre12.5 but I've had 3 issues in the past week with 12.5 upgraded clients.
-
I have two 4MVs and really haven't had any issues with them. They're the oldest printers in our office and at least one of them is used several times daily. For VW12 output, it's still very good.
-
The serial number is required at the beginning of the install process. It is what determines which options are installed, whether you have Architect, RenderWorks, etc. You should still install from the CD, it just sounds like you have a bad serial number. I'd call sales rather than tech support.
-
As Kevin pointed out, these items are available through the Tool Sets palette. Even VW12 Fundamentals has some of the detailing you're looking for I think...so if you cannot find the menu item Tool Sets, it's possible that you're in a different Workspace like maybe Classic as opposed to Standard?
[ 01-16-2006, 08:39 AM: Message edited by: david c. ]
-
The new layer you worked on likely has a different scale than your previous layers. It is not possible to edit objects on another layer if the scale is not the same as the working layer.
-
I suppose if you had v10 and converted to v11, you got the v11 appended to the file name. Maybe it was never removed at that point so now you're converting v11 files to v12...with VW12's new rename feature the new file doesn't get a v12 anymore, just the original file name which included the v11. So then it would be confusing because the file was converted to v12, but still says v11. I don't know if that makes sense at all
![[smile]](images/icons/smile.gif)
so...in Mac OS X, the icon says VW12 or VW11 on it. I think it's safer to determine a file's version by the icon as opposed to the file name appendage if you had to know just by appearance.
Personally, I think the "v??" should be cleaned up on old files preventing some confustion like this once the conversion is made. NNA is attempting to help us by the convert file/rename feature in VW12.
-
Craig,
Like Travis, I'm fond of Epson printers as well but have not really used the large format models. For over ten years I've had great luck with HP DesignJet plotters (650, 755, 1055 and now a DesignJet 4000). I think the key to having success plotting on the Mac is to find one that is PostScript compatible. It makes all the difference in the world in terms of setup and troubleshooting. Lastly, network capabilities and color are excellent on the HPs.
-David
-
As I understand it, one of the features of V12 is to retain the original file name after conversion and add the v11 to the older converted file. This is normal and actually reverse from previous versions where the old file retained the original name and the new file was appended the version number.
Open an old file and the convert dialog box appears. There you have the "settings..." button which enables you to make it work either way you want.
-
I had the same issue and I found the fix here on this site. Go to...
http://kbase.nemetschek.net/index.php?ToDo=view&questId=72&catId=19
There is a downloadable VectorScript that you can run on your file to clear the print settings, solving this issue.
Lost Vectorworks Files
in General Discussion
Posted
I hadn't noticed before, but there are possibly several builds of VW 12.5. Like some of you, I had downloaded VW 12.5 update on day one and proceeded to use that updater to upgrade all of my machines. I ended up with build 60762. You can see the build number in About VW (or equivilent in Windows). I downloaded the update again yesterday and ran it on top of 12.5. It updated my 12.5 (build 60762) to 12.5 (build 61447). Only needed to update a few files including the core application. While there hasn't been enough time to test if this will solve my issue, it's another step I'm trying out.