Jump to content

Recommended Posts

  • Vectorworks, Inc Employee

The DMX Xforms should work in both, since the function has been directly ported form Vision to Showcase.
The main difference is that Vision uses the Y axis as the vertical vs the Z axis in Vectorworks.
The workflow for setting up a DMX tansform in Vision is a little different as well, its set up in the properties of the object, in the xform section and works with the parent child structure that Vision uses in the Scene Graph. This means you can select the top level object in the scene graph and apply the transform to it and all the objects that are children will move, rotate or scale with the top level parent object. You can drag and drop items in the scene graph to assign them to a parent.

  • Like 1
Link to comment
  • 3 weeks later...

Thank you for an advice.

Objects rotate on my (dmx) command, but I still struggle with setting rotation origin correctly. I've exported a single MVR file with a pipe and fixtures on it and then imported this MVR file into Vision. I need to put kind of a hinge on one end of a pipe, so this point stays static and the rest rotates relatively to this point.

It is something to be managed before export from Spotlight I suppose.

Link to comment

I haven't used Vision in this way in a couple of years, but when I used to import scenery and move and rotate it using DMX transforms, the rotation and location point was determined by the VW internal origin at the time of MVR export.  When you merge in the MVR, the objects will be merged in at point 0,0.  You can then set the X,Y, and Z positions to match the "hinge" that you are looking for (recognizing that the Y and Z axes are flipped between VW and Vision), then use the DMX transform to rotate on the hinge.

 

This usually does necessitate having a separate VW file for prepping objects to send to Vision.  When I used to do this often, I always had a "Vision Prep" file that had each lighting position on its own layer.  I would "zero" the position to 0,0,0 and export each as its own MVR file, then merge them in to a Vision file.  That way each position was given its own tree on the scene graph, so it was really easy to change trim heights or move positions as necessary.

Edited by Jesse Cogswell
  • Like 1
Link to comment
On 12/14/2024 at 6:30 PM, Jesse Cogswell said:

I haven't used Vision in this way in a couple of years, but when I used to import scenery and move and rotate it using DMX transforms, the rotation and location point was determined by the VW internal origin at the time of MVR export.  When you merge in the MVR, the objects will be merged in at point 0,0.  You can then set the X,Y, and Z positions to match the "hinge" that you are looking for (recognizing that the Y and Z axes are flipped between VW and Vision), then use the DMX transform to rotate on the hinge.

 

This usually does necessitate having a separate VW file for prepping objects to send to Vision.  When I used to do this often, I always had a "Vision Prep" file that had each lighting position on its own layer.  I would "zero" the position to 0,0,0 and export each as its own MVR file, then merge them in to a Vision file.  That way each position was given its own tree on the scene graph, so it was really easy to change trim heights or move positions as necessary.

It is working! Bless you! 🫡

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...