Model breaks with 2022.1.11 release upon parameter change

[GinTonic99]

OS: Debian GNU/Linux 11 (bullseye) (KDE/plasma)
Word size of FreeCAD: 64-bit
Version: 2022.111.30764 (Git) AppImage
Build type: Release
Branch: LinkDaily
Hash: ef3092bcbca5475eff4eb7ff7933eb3e9bbbe4b9
Python version: 3.9.9
Qt version: 5.12.9
Coin version: 4.0.1
OCC version: 7.5.3
Locale: German/Austria (de_AT)

The attached parametrized model works with the previous release when a parameter is modified ( not perfectly, but with one or two constraints disabled and re-enabled again it is repaired) but completely breaks with the current release with numerous broken elements.

Attached the model Shoji_01 and two scren recordings shwoing the behaviour with the current and the previous releases of linkdaily.

For the moment I have stopped using the current release and went back to the previous release.

Shoji_01.zip

Shoji.with.FreeCAD-20211015-2022-01-16_18.33.54.mp4

Shoji.with.FreeCAD-2022111-2022-01-16_18.39.14.mp4

[realthunder]

The above referenced commit is a bug I uncovered while trying your file. If you want to try it now, you can manually clone asm3 git repo into your FreeCAD user directory, ~/.FreeCAD/Mod.

But please note first, the model breaking problem shown in your screen recording is due to another problem. The topo naming encoding has changed a bit in the latest release. The side effect is that if you modify your old model, you may encounter missing reference error. It is an expected behavior. After all, the primary function of the new topo naming is to detect and report changes. You can work around the side effect by opening your file, right click the document item in the tree view, select Mark for recompute. And then click Refresh (Ctrl + R) button on the toolbar to perform a full recompute. Recompute without any modification allows FreeCAD to auto update the topo naming to the latest version.

A few extra notes on this problem. I used to pop up some dialog to warn user about topo naming algorithm changes and ask for full recompute. The thing is, a full recompute may fail due to other reasons, like OCC version changes, while on the other hand, the model works just fine as long as the user do not change it. I am still contemplating how to handle this dilemma more gracefully.

[MisterMakerNL]

I have also noticed more rebuild issues than previous.
And I work in a newly build model.

[GinTonic99]

Hi realthunder,

thank you for attending the issue. I can confirm that with the updated asm3 from the git repo and upon following your instructions, the model behaves like before with the current release.
thanks again
gin