3D Component OffsetHeight Input Units

For general Protocase Designer questions. Anything and everything about Protocase Designer except support questions.

Moderators: cduffney, akirk, mpyne, mrodden

Post Reply
patrick_keys
Posts: 1
Joined: Tue Mar 12, 2024 4:04 am

3D Component OffsetHeight Input Units

Post by patrick_keys »

When using an imported 3D component, it is possible to set the offset height of the part. I have Protocase Designer set to use millimetres, hence the OffsetHeight field is displayed in mm. However, when I enter data in this field, the input seems to require inches - for instance, entering "1" will result in 25.4mm being displayed, "2" results in 50.8mm and so on.

Can this bug be added to the queue to be fixed?

dhyha
Posts: 1
Joined: Sat Feb 07, 2026 12:20 am

Re: 3D Component OffsetHeight Input Units

Post by dhyha »

Yes, this definitely sounds like a unit mismatch bug. Submitting it to the Protocase team for a fix would be the right step. Thanks for reporting it.

Mattheurma
Posts: 1
Joined: Mon Feb 09, 2026 11:17 am

Re: 3D Component OffsetHeight Input Units

Post by Mattheurma »

I’d recommend reporting it to Protocase support or their issue tracker with a short repro description like the one you wrote they’re usually pretty responsive to clear, unit related bugs like this.
Edit by: msn games

dissimilar
Posts: 1
Joined: Mon Feb 09, 2026 11:44 pm

Re: 3D Component OffsetHeight Input Units

Post by dissimilar »

I can confirm you’re not imagining things — I’m seeing the same behavior on my end as well.

Even with units set to millimetres, the OffsetHeight field for imported 3D components still appears to interpret raw input as inches internally, then converts it to mm for display (hence the 25.4 mm increments). That strongly suggests the UI label is following the global units setting, but the underlying input logic hasn’t been updated to match.

As a workaround for now, I’ve been:

Manually converting mm → inches before entering values, or

Entering the value, then immediately adjusting it visually until it matches the intended offset

Definitely feels like a bug rather than intended behavior, especially since other numeric fields respect the unit preference correctly.

I agree it should be added to the fix queue — thanks for flagging it. Hopefully the devs can align the input handling with the displayed units in a future update.

Post Reply