Jump to content

klinzey

Vectorworks, Inc Employee
  • Posts

    2,534
  • Joined

  • Last visited

Everything posted by klinzey

  1. I noticed that the fixture that you are using in from Robe. Robe updated their GDTF to use the newer glb/gltf for the 3D geometry which is not supported in Vectorworks 2023, it can only read 3ds based geometry. The best thing to do is to to select a Vectorworks symbol. With he light selected press the Replace Lighting Device... button in the OIP. Select the appropriate symbol from the Resource Browser and click Select. Uncheck the "Use GDTF Geometry" option. You will still be able to maintain the link to the GDTF and the GDTF file will be exported when you export to MVR but it will show the 2D and 3D geometry from the Vectorworks symbol.
  2. @Kevin Allen The intensity of Vectorworks light objects still be set beyond 100. @User-B We are working toward the lighting device modeling real world lights. Controlling the intensity of the light in the real world is limited to 0 to 100%. As we export the Vectorworks model to other applications, import data from other applications, and plan for more control in Vectorworks we need to more closely model the limits of the real world fixtures.
  3. If it's just your machine that is having issues, make sure you are starting in a new blank file, not a template file. In the Spotlight Preferences make sure the parameters are set to the default <Spotlight>. Try backing up then deleting your user folder. Did you migrate your user settings from 2023?
  4. This is working as designed. From the lighting device we now only allow you to set the level to a maximum of 100%. You can set it brighter by editing the light directly. As we me move forward it becomes more important that the lighting device intensity values are between 0 and 100%.
  5. Rails were never an option in the create stage command because they are not available for the stage plug. Rails are only available for the stage deck.
  6. This is a know issue. In the dialog, change your Device Type from "Light" to "Moving Light" or "Light or Moving Light". For some reason it crashes when there is nothing found matching the criteria.
  7. I gave the x4 bar 10 a quick test and I did not see any issues. It likely something specific with your file that's causing the issue. Here is my test file along withe a recording of the data exchange.x4 bar 10 Test.vwx x4 bar 10 Test.mp4
  8. From the screen recording it looks like you are using Vectorworks 2023 or prior? Have you tried this in 2024? There were issues in prior versions where it was possible to duplicate the Lightwright ID, doing a complete export to Lightwiright from Vectorworks will correct this problem if it exists. In the recording an important part of the OIP is cut off so I can't see what part of the fixture is selected for editing; the OIP may be showing you editing the accessory or a cell of the fixture. We have seen this happen frequently. Did you add the X4 Bar 10 in Vectorworks or Lightwright? There is a known issue where lights added in Lightwright do not get the proper Lightwright ID assigned in Vectorworks and this will cause sync issues. (This issue will be resolved in an update for Vectorworks 2024.) Fixtures shown in Lightwright but are not visible in Vectorworks may be on a hidden layer or class. You can show layer class and location in Lightwright which may help you locate them in Vectorworks. You can also use the Select in Vectorworks command in Lightwright to select the fixtures in Vectorworks. Fixtures could also be grouped in a hidden class? Have you tried deleting and adding the lights in Vectorworks to see if that corrects the problem? Can you reproduce the issue in a new blank file? GDTF are created by the manufacturer or a user. Vectorworks does not create or check GDTF files. It's up to users to check GDTF files and then up vote, down vote, or report problem files using the mechanisms provided in the GDTF share. For further testing in Vectorworks 2024 we would need to have the Vectorworks file and the Lightwright file so we can examine the internal IDs that are in use.
  9. In the future the IDs could be separate and it's something we are investigating but currently they share the same ID system.
  10. The ID is common between the hoists and fixtures, Braceworks wants a unique ID for all loads and supports.
  11. To correct an error and prevent additional data loss with the new equipment summary key, we have implemented a fix in Vectorworks 2024 Update 1. When the equipment summary key is edited in Update 1, the fix may cause information to be removed from the equipment summary keys created in the initial release of Vectorworks 2024. Specifically, all plug-in objects with a count larger than one will be removed from the Items and Elements to Display list of the equipment summary key and will need to be manually added. When a file containing an equipment summary key has been opened in Vectorworks 2024 Update 1, it is recommended that an image of any equipment summary keys be captured in one of the following ways: Using the Render Bitmap tool Duplicating the equipment summary key Exporting to PDF Publishing to PDF Taking a screen capture After an image of the equipment summary key has been captured, perform the following steps: Select the equipment summary key and click the Build List... button. Select the Used plug-in objects radio button. Using the image captured above, select the plug-in objects that were removed from the Available Items and Elements list and add them to the Items and Elements to Display list using the > button. Reorder the Items and Elements to Display list as necessary. Click OK. Repeat the preceding steps for each equipment summary key in the document. A video demonstrating the process is shown below.
  12. Make sure your Video Source Input names are different on the 2 projectors. In order to optimize rendering the same image on multiple screens, if the Source Input names are the same we shoe the same video. If this does not resolve your issue please let us know. Depending on the content of the stream high and low bandwidth can look very similar. The resolution may also be capped by the quality settings the Vision preferences dialogs.
  13. Yes, there are plans to add power output to lighting fixtures. It will likely be handled slightly different than a distro because we would not total the load till it gets back to an actual distributor.
  14. Try BuildResourceListN2() I think it accepts a fully qualified path to a file. The BuildResourceList calls are really designed to use folders so the users can add a file to a folder and the developer can update the original file without overwriting user created content.
  15. The class Rigging-Truss-Truss is turned off in the Viewport. Once that's turned on you should see the truss.
  16. It's likely that there is a label legend applied to the light and the accessory. Select the accessory in the OIP and change the label legend to None.
  17. It looks like you have end markers turned on for your lines. You should be able to select the object and in the attributes palette turn off the end markers. If that does not work then change the document default line marker. Deselect everything and use the attribute palette to select no end marker for the lines. Once you do that change a value on the soft goods object and the arrows should go away. What version are you using?
  18. You can use GetTickCount() at points in the script to get a sense of time. It's 1/60 of a second. If you get the count at the start of the script then you can calculate the run time to any point in the script by calling GetTickCount again.
  19. Try just incrementing by the DMX footprint, not the footprint +28
  20. It sounds like someone has customized the OIP. The control should always be there just disabled when the proper conditions do not exist. Since the option is not shown at all go into Spotlight Preferences, on the Lighting Device: Parameters tab, in the Settings Popup select <Spotlight> then click OK. The parameter should then show.
  21. The containers are shown in the Label Legend for reference only. You need to edit the container symbol itself in order to change the size of the container.
  22. You likely have a Label Legend applied to the Light and the Accessory. With the Lighting Device selected, in the OIP, select the Accessory from the Edit Accessory drop down. Then select <None> in the Use Legend drop down.
  23. No. Vision does not support export to MVR.
  24. Can you post one of your files?
×
×
  • Create New...