Matt Panzer

Will RestObject(pioHandle) do what you need? It will force a PIO to regenerate.

If you haven't visited our online CameraMatch User Gallery lately, come check it out! There's some pretty cool stuff in there. BTW: We're alway looking for new images to add. If any of you CameraMatch users out there have anything you'd like to share, please send them to: gallery@panzercad.com Visit the CameraMatch Gallery:

Craig, CameraMatch 2011 is still available and compatible with both VW 2011 and 2012. Unfortunately, there is no trial period for that version.

If you're using Ambient lighting, try setting it's brightness lower (or turn it off). If your using HDRI lighting, try editing the HDRI (via the Resource Browser), click the "Options" button and turn down the brightness.

Hi Craig, If you're using Vectorworks 2013, download and take CameraMatch 2013 for a FREE 10 day trial: CameraMatch 2013 Downloads You may be interested in some of these links: This is a gallery of user images: CameraMatch Gallery This 3 minute video gives you the basic idea of what CameraMatch does: This 10 minute video shows you a CameraMatch rendering of an interior space being created (start to finish) in real time: If you still want to see more (a lot more), this 50 minute video is of a recent Webinar I did. It's much more in depth with tips and tricks: Let me know if you have any questions.

Hi Doug, Have you tried using Tiles?

Hi Matt, CameraMatch 2011 only works with VW 2011 and 2012. You would need to upgrade to CameraMatch 2013. I think the improvements are well worth it - although I may be biased ;-)

Hi Vincent, Yes. It was quite awhile ago. Just over 4years now. I'm glad you like it! I still find myself using this command when I want all snaps off for a series of tasks. As for the character for "Snap to Working Plane", have you tried "R"? These characters all coincide with the NV default keyboard shortcuts for the snaps. Since "R" is used for both Tangent and Working Plane, I think it may do it for you.

Hi Michelle, As the others mentioned, there is the key press that will temporarily disable snaps while doing other operations. Nevertheless, the command still comes in handy for me once in a while. To install the command, you need to copy the "Snaps?.vsm" file to the "Plug-ins" folder in the VW User folder. You can get to the VW User folder by Going to the VW preferences in the "User Folder" tab and click the "Reveal in Finder" button (Mac) or "Browse" button (Windows). Once you copy the file ti the Plug-ins folder, Restart VW (if it's running) and add the command to your workspace using the Workspace Editor and give it a convenient key command. Note: I have it setup to toggle only the "qwsd" snaps. You can change the snaps as desired by changing the plug-in string using the Script Plug-in Editor like this: Select the command in the editor and click on the "Strings" button. You will see just one string category (with an ID of 3000) called "Snaps". Select it and click "Edit". You will see just one string (also with an ID of 3000) and it's string displayed. You should be able to change the string to any combination of the following characters with no spaces or other characters: qwerasdf Here's a key for each character: A: Snap To Grid Q: Snap To Objects S: Constrain Angle W: Snap Intersection D: Smart Points E: Snap To Distance F: Smart Edge R: Constrain Tangent I know it's not the most intuitive plug-in I've created, but it's free and it gets the job done. :-)

I agree. These types of objects should have a "Constrain Proportions" option and have it on by default.

Take a look at ForEachObjectInList. This should have options to do what you want. I'd expand on this farther, but I'm on my way out the door.

This is a very common problem with a not so obvious solution. I would vote that VW ALWAYS creates viewports with a solid fill attribute (no matter the document settings). The user can always go back and remove the fill later.

Thanks hippothamus, Sam Jones and Raymond Mullin lent me a hand on the Vectorscript Mail List. I was using ForEachObjectInList but had it set not to look in groups. Apparently, Symbol Folders are considered groups in this case. All is well now.

Hi Ian, Unfortunately CameraMatch 2013 will not work in VW versions previous to VW 2013. So far, each major release of CameraMatch added new features that take advantage of newly added vectorscript calls. For these reasons, we've never been able to make it function in earlier VW versions. Generally, the version number of CameraMatch matches the current version of VW that it was originally written for. But, as with CameraMatch 2011 (also compatible with VW 2012), some versions may continue supporting future versions of VW. That all said, I cannot predict what the future holds. :-)

Is there a way to get a list of all symbol definitions (including any nested in symbol folders) that are only in the current VW document?

CameraMatch has now been updated to version 2013.0.2! Among the fixes is vastly improved vanishing point tuning (in the Tune View dialog). We strongly recommend all CameraMatch 2013 users download this free update. Please download the update here: Download CameraMatch 2013

From what I understand, this is an OS issue. After installing a new version of VW, the OS is told to use the new icon for files with the ".vwx" extension. Since the older version VW files use the same extension, they're also shown with the new icon. BTW: In ancient times, Mac OS 9 and earlier dealt with this differently where each individual file stored its own icon.

Miles, The change was made in VW 2013. While I agree that it's more steps, it is more consistent with assigning other attributes (ie: image fill, gradient, etc.).

Miles, While Line Types (formerly know as Dash Styles) are now resources (available in the Resource Browser), they are still available through the Attributes palette. They're just accessed little differently. In the Attributes palette change the Pen Style to "Line Type" and you'll see the Line Type options appear on the palette. While it may be a little more cumbersome than in previous versions, it's now consistent with how other attributes are accessed.

CameraMatch has now been updated to version 2013.0.1 This version requires Vectorworks 2013 We recommend all CameraMatch 2013 users download this free update. Among other bug fixes, this update fixes problems when cutting holes into Mask and Shadow objects. Please download the update here: Download CameraMatch 2013

CameraMatch has now been updated to version 2011.0.8 This version requires Vectorworks 2011 or 2012 We recommend all CameraMatch 2011 users download this free update. Among other bug fixes, this update fixes problems when cutting holes into Mask and Shadow objects. Please download the update here: Download CameraMatch 2011.0.8

This probably has to so with antialiasing in photoshop. Setting the fill color to none makes only the white colored pixies invisible, the antialiased pixels remain opaque because VW doesn't support alpha channels.

You're right Vincent. Texturing by component leaves no options. Maybe the Obj Info palette should be expanded to allow texture settings for each individual component.

Hi John, Unfortunately, I've dealt with this only by typing a horizontal offset and looking at the rendered result, adjusting the horizontal offset and looking again, rinse and repeat as necessary until they look close. If anyone has a better solution, I'd love to hear it. I've entered in a bug/enhancement request to NV to have the "Use World Z for Origin" feature changed to something more like "Use world Origin for Origin". Aligning textures only in the Z direction is only good for horizontal "line" textures like horizontal siding. Things like brick and board & batten need more and, as you now know, are VERY tedious to deal with.

Hi VvierA, Have you tried: GetBBox( objHand, topLeft.x, topLeft.y, botRight.x, botRight.y );