islandmon

Cipes is right and make sure that you're in Plan View ! >Creation of the Cut Line @ 3'6" is a little harder and requires that you create a hybrid-symbol and then 'ungroup' the PIO and then twiddle the 2d line & text.

The Door PIO includes the default Record Fields. These can be manipulated in menu>organize>script>vectorscript plug-in editor>Door>parameters The changes experienced by Psychofish occur during the string in-put within the PIO dialog. The fields do not change only the in-puts. And the PIO will default to the 'parameters' each & everytime it is called via Door Tool. Each Tool Call results in a new Door object ID# for the instance. Each ID# includes all the record fields as defaults unless they are changed via the PIO dialog.

Kool ... although I keep a pretty tight rein on my system issues I shall give this a try. thanx

My VW11.5 app is kernel panicing every 15 minutes or so no matter what I do. System reports show different functions with dylib dropping memory. But I've found the answer: In the old days when I was a beta test for little Old Minicad and worked directly with the handful of developers things were simple and version numbers went in increments of .01. Now with versions jumping from .01 > .05 volunteering to be a Beta Tester is simply not an option. It seems that the entire Vectorworks community is now conscripted into being unwitting Beta Testers for new functionalites that would never see the light of day unless idiots like me did the Beta on them. In the old days there was a quid pro quo between Diehl Graphsoft and the Beta Testers. A common currency of free code exchanged. Today all we Unwitting Beta Testers get is the hammer without so much as even seeing the nail. maybe the nail is located somewhere in Las vegas. Well that being said I can now re-launch VW and do a little more work on the file before the next crash session. See you all then. eja

Check out all the diverse threads working this critical issue. You can take comfort in the fact that you are not alone.

By it's very nature the Door PIO has basic conditional limitations. You can also create a 'normal' bi-part door in a new file. Then export to vectorscript and tweak the parameters to suit your needs. Then re-import >convert to symbol>copy & paste into your working drawing. The possibilities are endless.

M Oz, Perhaps, it's just that old habits die hard ... but I've grown to rely on the absolute predictablity of that 2d profile. The idea that it stays put at the creation origin is a 'Life Safer' in situations where objects may get 'arbitrarily' moved around. It may seem confusing but it does exert a form of discipline to the process of extruding to 3d. I normally extrude all symbols at the 0,0,0 coordinates and other 2d shapes at the 'exact' location. Overall any weakness in coordinates can be overcome with symbols and/or 3d Loci.

Experiencing similar issues on the Mac side. The other day while working on a very basic survey plan use of the Zoom Tool caused an immediate kernel panic. The space#text in the ParkingSpace PIO was too large to view on a Cinema20" !

Yes, use Image Props and/or Textures. the versatility is endless. Mix & match to achieve the most efficient results.

The habitual placement of 3d Loci is all I ever do. If there's a better way ... great !

Refer to Archtectural Standards ch.18 , and especially page 803, 'Solar Angles'. Describes the parameterrs and requirements. A PIO should be based on these fundamentals. Energy calcs are fundamental to efficient design.

Back in dem good ol' days. I routinely archived my Minicad files as 'text format'. They can be imported as Vectorscript ! Sometimes pasting in a generic header is required. Neverless, Mac Classic can run Minicad4-9 with OSX. What about the file translator provided by NNA ? How far back does it go? There's also the possiblity of changing the 'Type:MC6d' into 'MC5d' ...

Here are a couple very basic low overhead pieces of Rope. Based on a single 15deg NURB fractal textured with Berber Carpet & rotated 15deg & stacked to form a piece of rope. Any multiple of 90deg is allowed, ie. a 10deg. ______ The basic Fractal> http://www.fractalnet.org/ART/FRT_Rope/FRT_ROPE-15-1.jpg Woven Fractals> http://www.fractalnet.org/ART/FRT_Rope/FRT_ROPE-2WAY.jpg http://www.fractalnet.org/ART/FRT_Rope/FRT_ROPE-3WAY.jpg This simple Fractal approach is ideal for Geodesic & Tensegrity structures. eja

Quick note to Users: To avoid re-installing and replacement of Plug-ins sometimes all you need to do is trash the '.ds_store' ( invisible database file which gets corrupted) within the Plug-in Folder. >Quit VW >use DSwipe or similar to trash '.ds_store' >Open VW and it will rebuild the data file for the directory. This trick works wonders with most apps.

We traded some work to a client for a hardly ever used 1999 HP430 which is PC only and which never worked for them and ACAD. As soon as got my hands on the thing,I installed some old Laserwriter8 RAM attached a Belken Centronix cable with USB. Then installed GIMP Drivers and now that ol HP430 sings with OSX.3.8 better than it ever could with the OEM Drivers. It's a work horse !

After studying your unique design and awesome rendering style, I've come to the conclusion that a 'background' process may have interrupted the I/O memory cache during the 'batch' rendering. Note there are both light & dark pixellations which are not random but clustered during specific events. Use Activity Monitor > Show Processes > Info and check to see if there are any hangs, etc. Rendering is horiz. line by line Upper Left to Upper Right. Also consider using TechTools X which came with your system to check the Cache RAM & VRAM... If all checks ... then I suggest > decompose the file and check each texture & image components individually against both black & white backgrounds. ouch ! Good luck and enjoy the ride...your work is inspiring ; ) islandmon

Believe me when I say 'sympatico': Please refer to these postings for tips & tricks: http://techboard.nemetschek.net/ubb/ultimatebb.php?ubb=get_topic;f=12;t=004748

jeremyw, Perfectly concise ! May I suggest practicing with the =Deg2Rad function ... in order to get a sense of the placements.

My approach would be to create 2 (or more depending on the extent of the curvature... more > better curve) NURB surface profiles and then Loft the surfaces into a 'solid' model of the curved portion of the stair.

Travis points out that modifying the ID label text fields will NOT make changes to the Door PIO text fields and therefore the schdule will not reflect the changes. This is absolutely correct. The Door.vso PIO & the ID Leader.vso PIO are separate and distinct procedures. One doesn't translate to the other. In both instances the Record() Fields unique to the PIO. Nevertheless, the technique can be applied democratically to all PIO objects ! eja

Travis, You make an important point. Howevr, the procedure 'TagText' only accesses the Label ID TagText: 'string'. Modifying the string via text editor=modification via PIO 'TagText':field. The door data can also be modified using this technique. The schedule uses the symbol name:string criteria to generate a list of all the door symbols and the fields: Record(LNewObj,'ID Leader'); /////// Field(LNewObj,'ID Leader','TagText','D-1'); Field(LNewObj,'ID Leader','Fld1Text',''); Field(LNewObj,'ID Leader','Fld2Text',''); Field(LNewObj,'ID Leader','Fld3Text',''); Field(LNewObj,'ID Leader','Fld4Text',''); Field(LNewObj,'ID Leader','Fld5Text',''); Field(LNewObj,'ID Leader','Fld6Text',''); Field(LNewObj,'ID Leader','UID','349223'); Field(LNewObj,'ID Leader','Prefix','D-'); Field(LNewObj,'ID Leader','Label','1'); Field(LNewObj,'ID Leader','Suffix',''); I've used the VSS export/import often when 'global' changes are required to particular classes of objects. The critical path concept is to clearly identify and isolate each instance prior to export like 'all door labels', only. Mixing and matching PIO's doesn't work ! eja

Lynda, There's ton of stuff to DTM. It takes loads of trail & error to get good results. Even the smallest artifact and scramble the process. Look out for duplicate 3d Loci ... and be certain that the classes are correct. Avoid using more vertices than necessary for the task.

How bout posting an image ... ???

Try this neat trick: { If you have more than a dozen doors or windows to renumber} >Assign a Class 'Label-DR' to each Door Label >Menu>Organize>Sel Only>Class>"Label-DR' >Group>Cut paste to new layer (safe) >save >Create new empty doc at same page scale>paste >Export to Vectorscript >Open in text editor>search for 'string'> Field(LNewObj,'ID Leader','TagText','D-1'); or begin at the number of the new door , ie. Field(LNewObj,'ID Leader','TagText','D-33'); From here then renumber the doors> 'TagText','D-XX'); as required >save as new text file version# >Import vectorscript into new doc >Copy all new ID >paste into original file > Label layer This technique is superb for working with PIO text changes of all types. Note: the Door ID is a symbol so edit symbol to make sure the text is the correct font&size. eja

These are the 'bad' memory addresses Offset codes for each crash below: Offset: 004c7fdc Offset: 0030b677 Offset: 0053709e Offset: 004c13a3 Please see my latest post > http://techboard.nemetschek.net/ubb/ultimatebb.php?ubb=get_topic;f=12;t=004748;p=1#000024 eja