Regression for WindowLiningProps

Plug Ins Geometry Gym
, ,
1

Hi all and especially @jonm,

I think there’s a regression for WindowLiningProps component between v24.7.17.8 and v24.10.17.8 (more generally i think it happened during one of july’s releases).

I now get issues with the different properties being set to 0 by default, which didn’t happen before (see screenshots). Maybe this impacts other components as well.

Capture d'écran 2024-10-17 102303
Capture d'écran 2024-10-17 1023031920×1032 173 KB

Expected behaviour (v24.7.17.8)

Capture d'écran 2024-10-17 102745
Capture d'écran 2024-10-17 1027451193×1018 97.1 KB

Current behaviour (v24.10.17.8)

Can you please take a look in that? Thanks in advance!
Best

2

Hi Quentin,

Thanks for the post. Actually, this is a change to enforce schema compliance. In IFC4 and newer, zero values are acceptable. But in IFC2x3, they have to be positive. They are optional, if you right click on each input and clear the values, then the error will clear. I guess I could change the behaviour to a warning to say the value isn’t set if this is a problem.

buildingSMART have released a validation service, making it easier to detect non compliance, https://validate.buildingsmart.org/

Let me know if clearing the values does not help.

Cheers,

Jon

3

Thanks for your quick reply!

Clearing the values did work indeed. It would be great if the warning was non blocking though as suggested, as it creates issues (when used with compute for existing models in prod specifically). Do you think it could be an possible?

Thanks!

4

Yes, I’m changing it for the next build (tomorrow if that’s ok). It’s mainly a problem because initially the default values were set to be 0.

1 Like