jcogdell

Try using the subdivision tools, the create subdivision primitive is in the model menu and the edit subdivision tool is in the 3D toolset.

You can use direct RGB values for both! for colouring symbols click on the fill or pen colour in the attribute palette and then on the standard colour picker icon. for the colours emitted by lighting instruments when visualised you can access the same standard colour picker either in the lighting Device dialogue, which is accessed by using the edit button in the OIP or using the edit command in the right click menu. Or by using using the colour field in the properties dialogue opened using the edit light command from the right click menu.

If the preset colours are not doing what you want try setting the RGB values directly, you will get better control of the colour this way

thanks for the info I'll add it to the report

The bug report is opened

I'll look into it and open a bug report

Go to the edit menu and use the rotate 3D command (, note the Y axis is vertical in Vision). Both the rotate and move in 3D commands will work with group selected fixtures

The only way that I am currently aware of is to use the Cinema 4D Stage plug-in. https://hantmade.com/stage/

Braceworks does work, it has been extensively tested and functions as designed. There are some limitations, such as no ground support calculations (we currently have no way to perform wind loading calculations for outdoor structures) and certain specialized scenarios where you must have a structural engineer perform the calculations. The issue here is that the Bridle tool and hoist tool have to follow the recommended manufacturer usage guidelines. If Spotlight does not follow these guidelines then any structural engineer who works with the calculation results will automatically fail them! This means that currently hoists and dead-hangs will not connect automatically to a rigging point in the same way as a regular bridle. Current best practice for hoists and dead-hangs is to use the house rigging points as an insertion guide, you need to make sure your truss center line is centered on the point or points (snap to object works great for this) and then use the points as guides for where to insert the hoist or dead-hang (setting the high hook height or dead-hang trim height appropriately in the insertion tool preferences). Although they do not directly interact with the point, when you run a Braceworks calculation both will automatically generate a rigging point which will document all the forces acting on it, which will replace the unused original point. This reflects reality, if your truss is not directly below a rigging point the truss will be pulled out of position, as it naturally balances between the points, which in turn will drastically change the forces acting on the rigging points! And yes I know that in reality if the truss is not directly below the rigging points most onsite riggers will just move the truss into the correct position, because this is what I used to do (if there wasn't a good reason not to) when I still did rigging work. Moving forwards we are going to improve this by making it possible for hoists and dead-hangs to connect with hanging points in the same way as other bridle types. However, this is not as simple as it sounds. If we just allow them to connect when they are not perfectly aligned then it not follow the manufacturers recommended usage guidelines and potentially move the truss out of position, both of which will invalidate the Braceworks calculation. This means there will have to be some specialized options for what happens when the truss and points are not aligned such as automatically moving the truss to correctly line up with the points (not always possible, if its a complex rigging system) or maybe automatically inserting per-rig, are 2 of the possible solutions.

The tool does this when it is working correctly. There are 2 options to display the X, Y coordinates you can use the X, Y fields in the hoist label legend or the 'Display relative X, Y on plot' option to display the coordinates separate from the hoist label legend. In both cases the designed functionality is for the label to automatically update whenever the hoist is moved or the hoist origin is changed. The fix has been verified and will be in the sp3 release later this month

There are several ways to have this addressed by Vectorworks, You can post it on the trouble shooting forum as you have done and get help from the community. As @E|FA suggests you can submit a bug report or make a feature request using the links in his post. A third option is to contact our tech support team directly using the link below https://www.vectorworks.net/support/help They will work with you to find a solution.

Hi Nick The problem is that MA & ACT developed and control this plug in, we have nothing directly to do with it and it has not been updated to be fully compatible with the changes made in 2020. From my understanding moving forwards MA prefer to take advantage of the new GDTF and MVR file formats for this. This is not much help for you though, as only the MA3 software is fully compatible and to the best of my knowledge they have no plans to add this into the MA2 software as it is no longer under active development. Currently I would recommend exporting your file into 2019 and then using the plug in (not ideal I know). Sorry I can't be of more help

Sp3 is due to be released shortly and as normal will have lots of bug fixes and also some other improvements.

Hi Scott Regarding point 2 there is an existing bug where the X, Y, fields in the hoist label are not correctly updating if the hoist origin point is changed or the hoist itself is moved. The fix will be out soon. This maybe the root cause of your issue

I have opened a bug report regarding this issue.