islandmon

This error may be related to an open resource in the orginal Acad file. For example the file may be linking to a resource(s) that was not included in the DWG save ... only the alias to the resource. Hence the inability to locate a Library 'symbol' object.

The key to DTM is 3D Loci ... pure & simple. Import from AutoCad is common around here. After importing check the file for scaling weirdness and place 3D loci as required per 3D Poly and/or manually. Then create a site model and check the contour results. Errors are easily spotted and corrected via the 3D loci. Fine tune the 'Existing-site-model symbol' via 3D mesh.

Zackayak, I've used a combo of keyboard,Wacom Tablet & trackball mouse since '87. There are no input > display limitations. However, if your planning on performing 'Digitizations' on existing plan sheets that's another issue. I gave up on that approach years ago. If necessary I scan parts of plans and then reverse engineer the CAD to match. DXF/DWG is the way to get existing data into VW. CAD is virtually inconceivable without a quality keyboard with numeric pad.

Paul, Thanx for your knowledgible response. And I concur. Recent crashes in one file were linked to the 'Table & Chair' PIO ( I sent this to tech ). In the past I have used Vectorscript export to recover corrupted files involving hatchname issues. These critical issues appear resolved in VW 11.5. I'm now concentrating my efforts on identifying the PIO conflicts. Vectorscript offers a limited yet powerful 'Open Source' diagnostic option for the rest of us. I look forward to upgrading my knowledge base. The day I quit using Vectorworks is the same day I shall quit my Architectural Practice. Vectorworks , et al. is a big part of my Life.

VW has numerous approaches to curves. Choosing the most appropriate for each situation can be challenging. And therre are different 'smoothings' ... Bezier,cubic arc. What are you trying to accomplish? What is the intended result?

You can also set the dimension defaults from Preferences. Architectal use the slash wheres ASTM use arrows . Use the Info Palette to switch between various standards.

The Install CD is far superior to the download version. It took me 4 tries to get the download to almost work. There's a lot of tweeking and adjustment necessary to get 'back' to a normal workflow. Backing up your old VW directory is essential before installing the new 11.5. Then compare each of the directories to see what is old-new & missing. You will be suprised ! Be prepared to rebuild all the favorites & workspaces, etc. Make sure you trash the old preference files(2) and any links to the earlier version. A corrupted .ds file can cause misery. Now that I've gone thru all the trouble to upgrade I'm stuck with working around the numerous bugs.

Honestly, the crashes are a nighmare scenario. But on v11 there were far fewer crashes but more file structure corruptions. At least now the app just drops off before parts of the code are obliterated. There seems to be an issue with a couple .dylib routines. Rest assured VW Programmers are scrablling and eating a lot of pizza at the moment tryin to get this bug-a-thon resolved. NNA made the mistake of violating version convention when they 'Publically' jumped from 11.01 > 11.5 . If these issues were associated with 11.2 , everybody would just wait for the fix before doing the upgrade. But as it is, we were all sorta sucked into a 'free' upgrade. Imagine the indignation if we had to shell out $$. On the upside v11.5 offers some real benefits and has fixed some of the compiler issues. It includes many OSX refinements. It's just ...unstable at this moment in time. I have faith that the NNA Family is fully committed to resolving ALL conflicts.

Aqueous, Prior to OSX that's basically how we did it on Mac. Although, instead of the severe limitations of GIF you should consider 'lossy' jpeg or lossless PNG. I prefer PNG for archival images. ( see VW Preferences ) Additionally, if you're using an Image Editor like Photoshop Elements, you can save the file as a TIFF and it also saves all the layers with it, if necessary. TIFF is recommended for hi-res Grayscale output such as scanned images.

1)Try Copy&Paste of parametric values 2) For Glo effects try using a semi-transparent phong or plastic lens based on a White Texture or any other color & pattern. keeping in mind: "Becareful of what you wish for" . Every new PIO adds complexity and potential conflicts to the exist structure. C&P is an OS API. All OS capabilities should be mandatory for VW. Less is more when it comes to code bloat. Also, have you checked out some of the additional Vectorscript procedures available online ?

Export the file to Vectorscript then Import into New File. Check the error log... Open the Vectorscript in a text editor & match the line numbers to see the problem.

Eddie, Check your Console>VW>Crash Report Note the NURBSTessellator.dylib failure or the TrimVertex.dylib failure. The problem is in the .dylib code NOT in your technique. I've managed similar crashes with very basic extrudes. VW is working to address this issue , now. Hopefully it will be solved by the end of the month. eja

Macabuser, "transparency on, anti-alias off" should be 'on' if you desire to have blending edges. OSX Quartz requires anti-alias 'on' to make shadows appear realistic.

MW, Texures,hatches & Imagesprop are all very specific and each has its nuance to application. A screwwed up texture can take down your file .. ditto for hatches. A misplaced ImageProp can result in render issues. You need to establish a set Protocol for each type of object and the various parameters. It can become very confusing. Global assignments require careful thought. Once the Class attributes are established then you can >menu>organize>custom selection>create script ie, select-C=Interior Wall-6 once created ...click the script. Symbols must be manipulated individually. Also keep in mind that VW must somehow track all the changes. So give the app time & space to do its work. Try not to get too far ahead of yourself and avoid multiple Undo's. eja

Getting a complex Hatch to match up & square with the poly requires patience and skill. Sometimes it's much easy to use an ImageProp and then Preview as you tweak the coordinates.

To delete a Linked Layer ...do Menu>unlock then delete the Linked Layer(s) as required.

The DTM Border is based on the 3d Loci of the 'Existing DTM'. Tweek the 3dLoci to update. The Border is default and viewable as a Class just like the contours & Hull.

Also keep in mind that the placement of Loci detemine how the wall is 'cut'. Many clever shapes can be accomplished by tweeking the location of 3d loci. My Cathedral requires very specific Gohic historical windows wwith masonry trims.This was accomplished using opposing 3d Loci on each side of the wall. Hybrid Symbols were created for the different wall types & thicknesses.

Extrudes and NURBS combined with Hybrid Symbol 2d lines & polys & hatch is the way to go. Quick, easy and reliable.

To get around this issue my Title SCALE Block always includes the page size, ie SCALE : 1" = 10' @ 24x36. This avoids misunderstanding when the output is scaled at the PDF or Printer.

Ape, Got me goin' ... although I use Cron scripts every week and the UNIX terminal does normal maintenance during Boot, I started fresh from the Install CD Disk Utility and even upgraded to Cocktail3.5 (highly recommended). Did all the permissions, Re-binding, Lookup, Whatis and cleaned out the .ds files. The end result was VW became a tad faster which should be expected. But the problems with the 'dylib' were not affected and the app crashes regularly during OpenGL NURBS rendering. Now I'm goin use XCode to see if I can figure out : Thread 0 Crashed: 0 libGLU.dylib 0x90caa604 TrimVertexPool::clear() + 0x38 eja

After years of trial & error , I simply use layers for Objects and Classes for the attributes of those Objects. This avoids naming issues and allows me to avoid protocol conflicts. In otherwords forgeting to activate an object when it is in an 'invisible classe' is easy to do but much harder with Layers. All objects on a Layer would need to be invisible and easily noticed as a mistake. Every Object must have at least one visible 'boundary' part during every instance.

On MacG5 OSX , these problem exist but are remedied by use of the excellent Utility 'Cocktail ' which allows you to 'Re-bind" the system files and 'Re-Locate' & 'Whatis" & update the permissions database. Also, dswipe the VW applicate folder & subfolders. Use of Cocktail Cron scripts brings everything back into focus... presto !

-39 errors are usually fatal file corruptions. Export your file to Vectorscript then try to import into a new file. What errors do you get. All is not lost if you exercise some patience. DO NOT continue working on that file !

This issue is similar to the 'Name' data field owner problem. Let's say you desire to import / reference to a file. There can only be a single instance of a 'name'. All others must be different. The origin / source must remain pristine whereas the import>into file shall be changed to suit the conditions. In this regard ' standards, & common protocols work best. When scaling is an issue, I will copy & paste & rescale. Travis offers an excellent compromise.