stayathomedad

@Scott C. Parker I still haven't had the bandwidth to clean up a drawing enough to share with you guys. But I can 100% confirm that this has something to do with the Internal Origin. I had this happen today and thanks to the post from @michaelk I had a new option to try. The LX fixtures in the referenced viewport were being shown offset from where they "should" be. Many of them outside of the bounding box for the reference that they are part of. I opened the source file and when I turned on the Internal Origin I could see that the distance it was away from the User Origin was exactly the same distance that the fixtures were being shifted. I aligned the User and Internal Origins on the drawing and resaved it. When I updated the reference to the newly aligned origins, the fixtures were now being shown exactly where they should be. The shifting issue was gone. Thanks Team!

@Scott C. Parker I wish I could simply share the files, but the work is proprietary. I will try to strip out enough content to make a generic file and see if I get the same behavior. What ever this issue is, I only see it from certain LDs that we work with. Not all of them. I've been seeing this happen for at least the last year. My work around only takes a few seconds, so pursuing an answer hasn't been top priority, but I've got some bandwidth and I'll try to post files soon.

I use Referenced Viewports and occasionally have this weird little glitch show up. All objects will display in the viewport as expected, but the lighting objects will be shown as offset from their actual location. When this happens the lighting devices are not selectable. If you look at the screenshot - in this file, there is only one object and it is the referenced viewport. If I try to select those four lights on the bottom that are outside of the highlighted slection box, it is as if they are not there. This tells me that VW is simply displaying the referenced lighting devices in the wrong place, but thinks they are in the correct location. Updating and redefining the referenced file doesn't fix it. I can save the file as a copy and when I first open the copy, things are aligned correctly. But, as soon as I refresh the viewport in this new file, the visual offset happens. My current work around is to have a lighting device only viewport and then align the lights with the rest of the rig. The second screenshot shows a lighting only referenced viewport and you can see again how the selection box does not align with the displayed objects. Has anyone else seen this behavior? Any insight into what may cause this?

After finally getting back to the office after a couple of weeks and we confirmed that this has something to do with our print drivers. If I publish the pdf, upload to the cloud and then print from my phone, the pages come out as expected. I'm running the latest OSX and printing directly to a Canon ImageRunner. The whole print dialog interface has been updated and somewhere in that mix, parts of my printed sheets get greyed out. Go figure.

@Pat Stanford I tired to do a quick copy into a new file and get the behavior, but I couldn't. I can't post the file publicly but I did DM you a link.

Not sure what is going on here. The attached picture shows a published Sheet Layer with and without Data Tags for the hoists. For some reason the Data Tag has a box around it that greys out the truss in places where the data tag isn't. This does not show up on the pdf, only when I print them off. I experimented a little with the text box that is in Data Field in the layout that defines the dynamic text. I tried to shorten the #name# I gave it, but that did not seem to affect this. Any thoughts? - Possible Bug?

@Tom W. Worked perfect thank you! Turns out the text box locations were the same but I had to force one text block to be picked first by aligning it to the top.

I have a couple of very similar Data Tags for trusses. When I open the Edit Tag Data window they have the same data fields, but are in a different order. One Tag has the #LENGTH# data field at the top and the other has the #SYSTEMID# data field at the top. Does anyone know how to control the order that the data fields are placed?

Ahh. So my issue is in fact my custom truss symbols. Thanks for that clarification. When I start looking at updating the Cross Section window, the only way I edit the Height/Width data is to create a custom cross section. Is that the step I missed? I did change the Height/Width in the Truss Properties window but is that not enough? Do I need to use the "Custom..." dropdown option? Also - sorry about the large file I DMed to you 🙂

I sent you a DM with a file so you could see the behavior.

I just stumbled across this issue also. I don't have time to understand exactly what is happening , but I can 100% confirm that something funky is going on with the "Change Trim Height of System..." command.

Using Update 3 on OSX. I dug a little deeper. Definitely a bug. I plan to submit this as a bug report. This is what I do to see the behavior: 1. Insert a truss series with the Distributed Insertion mode. First click defines the start of the truss sections. The second click defines the end of the series. Just as expected. 2. Now with the Truss Tool still in Distributed Insertion mode, if I go to a different location in the drawing and double click, it will duplicate, in place, the previous truss series that I most recently added. I now understand why I had some mysterious duplicated truss sections in my latest project.

I am working with the Truss Tool and have found some odd behavior. When I double click in Single Insertion mode it inserts truss as expected. But if I have the mode set to Distributed Insertion a double click inserts truss in a completely different location. Is this behavior expected and I missing the intention, or is it a hiccup with the Truss Tool?

@Nikolay Zhelyazkov It has been fixed with Update 3! Thanks again.

The load data file for distributed loads and for point loads are both called LoadData.xml In Mac OSX they are located in [user]>Library>Application Support>VectorWorks>2024[or whatever version you are using]>Plug-ins>VW_Spotlight>Data>Braceworks. You should see two folders here - PresetDistLoads & PresetPointLoads. The LoadData.xml files are located in the corresponding folder. I use a general text editor and when I make changes to the xml file. No restarting of the program or reloading of the drawing should be needed. I can see those changes right away.