VW25 Truss "Trim Height" not accurate in OIP

[hdmcclx]

Howdy.

Ive just noticed a bug in the file im currently working in. My "Trim Height" for the trusses according to the OIP is reading 23.8m when the truss is first inserted (Z position reading 0)

When changing Trim Height with the "Change Trim Height of system" command, if i set it to say 5m Absolute, the truss will change to a Z of 5m with a Trim Height of 28.8.

So essentially the Z height, and "Change Trim Height of System" are correct to the drawing, but the "Trim Height" in the OIP is wrong.

The issue does seem to be localized to this file, and happens with an assortment of different truss symbols (PI wanted to check it wasn't a bug with my symbols)

It's not a "major" problem because as stated Z height etc. is still accurate. Just can't work out where the OIP "Trim Height" is getting its value from.

[stayathomedad]

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.

[jcogdell]

Have you set a layer elevation?

 

Please post the file so I can take a look, I've not been able to replicate this myself yet.
 

[stayathomedad]

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

[Scott C. Parker]

@hdmcclx and @stayathomedad
Please check the cross sections of your truss and be sure the height and width fields match the truss symbols you're playing with. If the internal numbers do not match the truss symbol sizes, your trim results will be off, even if they are grayed. 
Let me know if you need more info. If you do, Please post a test file here showing the issues. We don't need a complete drawing. Just a couple of offending truss symbols. 

hth, Scott

[stayathomedad]

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 🙂

Edited February 21, 2025 by stayathomedad
Calrity

[Scott C. Parker]

On 2/20/2025 at 8:42 PM, stayathomedad said:

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?

Yes, the tool uses both sets of information, and in this case, they should match. With custom truss symbols, you'll need to double-check that both have the appropriate information. As soon as I changed the .000 to 1.708, the trim field worked properly. 

[jasonhildner]

I'm having the same problem with native objects. 

Trusses and Light ladders, in particular are showing up with a trim height somewhere in low earth orbit.

No amount of editing even the most secret of super secret menus has managed to sort me out.

 

Copilot suggests this may be a known bug.

Can anyone confirm?

[klinzey]

Have you moved the user origin?
Are you using the latest service pack?

[Scott C. Parker]

10 hours ago, jasonhildner said:

I'm having the same problem with native objects. 

Once you check @klinzey's suggestion and still see issues, please post a sample file.

[LMorga]

This is definitely a bug, or possible bug.
 

I have found this in a few files in our workflows. To verify when you see the trim height issue, go into a front view and cross check your rulers. 
 

Z-zero will not be 0. There is no way to adjust the internal or user z origin.

 

Work around fix is to copy and paste in place file data to a new uncorrupted file.

 

We have found this to happen between DWG conversions.

[klinzey]

9 hours ago, LMorga said:

There is no way to adjust the internal or user z origin.

@LMorga is correct but there was a bug there moving the XY origin would effect the how the Trim Height is reported.
Your method of copy and pasting into a new file likely fixed the problem because the user origin was not moved in the new file.

[jasonhildner]

I'm hoping I can solve this without a "workaround".
Attaching a little test file with the objects in question. 

I have only tried these types of objects.

 

Thank you,

Untitled test for forum.vwx

[Scott C. Parker]

@jasonhildner I opened your file, and the trim heights seem to be correct. Would you please take a screenshot from a side view and post it?

[NEL129]

Stumbled upon this thread as I am having the same issue. I'm using native symbols (Tyler Truss) and setting trim heights using the "Change Trim Height of System" button. Things seem to be okay when I am navigating in Top/Plan but as soon as I use the flyover tool to check things relationally in 3D space my truss trim height changes to 5.86.....e38. I'm on the latest service pack and have not moved the origin. Curious if there have been any developments here since May. Thanks! 

[Scott C. Parker]

Please post a sample file so that the collective can take a look.