angle constraint oreinted on x-axis instead of lines

[ovski]

I'm having an issue with angle constraints that are not oriented on the lines but the x-axis.

Let me show you a working example on an older freecad version:

OS: Windows 10 Version 2009
Word size of FreeCAD: 64-bit
Version: 0.20.29177 (Git)
Build type: Release
Branch: releases/FreeCAD-0-20
Hash: 68e337670e227889217652ddac593c93b5e8dc94
Python 3.8.10, Qt 5.15.2, Coin 4.0.1, Vtk 8.2.0, OCC 7.6.2
Locale: German/Switzerland (de_CH)
Installed mods:
* A2plus 0.4.60i
* Assembly4 0.12.5
* Curves 0.6.5
* fasteners 0.4.54
* sheetmetal 0.2.61

angle_test_good.jpg (49.12 KiB) Viewed 819 times

All good, angles are displayed as they should be.





and now the same file on a current version of freecad, downloaded some minutes ago.

OS: Windows 10 Version 1903
Word size of FreeCAD: 64-bit
Version: 0.20.2.29177 +426 (Git)
Build type: Release
Branch: (HEAD detached from 0.20.2)
Hash: 930dd9a76203a3260b1e6256c70c1c3cad8c5cb8
Python 3.8.10, Qt 5.15.2, Coin 4.0.1, Vtk 8.2.0, OCC 7.6.3
Locale: English/United States (en_US)

angle_test_bad.jpg (48.54 KiB) Viewed 819 times

here the angles are somehow connected to the x-axis. I can't find a way to orient them correctly on the point where two lines meet.
this is the same file opened in both versions, so I can't imaging what I'm doing wrong.

Is this a know bug?

[chrisb]

You can always check the tracker. In this case you could find 8285.

Version: 0.20.2.29177 +426 (Git)

Did you compile the non working version yourself?

[ovski]

How would I identify 8285? I tried to find a tracker but lost myself in the git hub page of freecad.

No, I downloaded the non working version from https://www.freecad.org/downloads.php?lang=de
This version was downloaded twice yesterday ond two different systems with the same effect.

[Syres]

I'll have a go at triaging the regression today so at least someone with more C++ skills can hopefully fix it.

[ovski]

Should I open a ticket or bug report somewhere or is it okay to keep this here in the forum?

[Syres]

Should I open a ticket or bug report somewhere or is it okay to keep this here in the forum?

Please don't there's already duplicates in the issues section, most of the main updates are already in https://github.com/FreeCAD/FreeCAD/issues/8220 so I'm going to ask that https://github.com/FreeCAD/FreeCAD/issues/8285 is closed as a duplicate.


OK, so that triage was fairly quick, this regression is not a general 0.20.2 regression as first thought, it's specific to the Windows Libpack build. I'd thought to myself "Why have I not seen this on my Conda Linux build?" (I use 0.20.2 on a daily basis) because it doesn't occur. It also doesn't occur on the same system with the same config files using the Conda Windows build, it only occurs in the Libpack build so it appears to be a packaging issue at first glance and I don't have the capacity to compile Windows builds in order to prove that.

@chrisb I assume your MacOS build of 0.20.2 doesn't give this symptom either because it's built on Conda?

@uwestoehr Please be aware of this when you next release a LibPack build whether it be 0.20.3 or 0.21.x

[ovski]

Strange, I could not find those issues yesterday... seems like my google kung-fu was weak.
But I can confirm, that this does not happen on the Mac OS version.

tested on:
OS: macOS Mojave (10.14)
Word size of FreeCAD: 64-bit
Version: 0.20.2.29603 (Git)
Build type: Release
Branch: (HEAD detached at 0.20.2)
Hash: 930dd9a76203a3260b1e6256c70c1c3cad8c5cb8
Python 3.10.8, Qt 5.15.4, Coin 4.0.0, Vtk 9.1.0, OCC 7.6.3
Locale: C/Default (C)


by the way: thank you for your quick replies and support!

[uwestoehr]

@uwestoehr Please be aware of this when you next release a LibPack build whether it be 0.20.3 or 0.21.x

I can reproduce the issue but don't know what could be the cause. Since FreeCAD 0.20 I updated the OCC library from 7.6.0 to 7.6.3. It seems there is a regression. Let's cross fingers that this is fixed by the next OCC bugfix release. I cannot go back to older OCC versions because the policy is to upgrade OCC only when there are reported bugfixes affecting FreeCAD users. So going back will fix the issue here but open other issues.

[GeneFC]

I am not convinced that it is related to the Libpack.

I regularly compile using the latest Libpack. This is a result of my testing just now.

Works

Code: Select all

OS: Windows 7 Version 6.1 (Build 7601: SP 1)
Word size of FreeCAD: 64-bit
Version: 0.21.0.Unknown
Build type: Release
Python 3.8.10, Qt 5.15.2, Coin 4.0.1, Vtk 8.2.0, OCC 7.6.3
Locale: English/United States (en_US)
Installed mods: 
  * FeedsAndSpeeds 0.5.0
  * FeedsAndSpeeds-master.zip
  * freecad.gears 1.0.0
  * Help 1.0.3

Fails

Code: Select all

OS: Windows 7 Version 6.1 (Build 7601: SP 1)
Word size of FreeCAD: 64-bit
Version: 0.20.2.29177 +426 (Git)
Build type: Release
Branch: (HEAD detached from 0.20.2)
Hash: 930dd9a76203a3260b1e6256c70c1c3cad8c5cb8
Python 3.8.10, Qt 5.15.2, Coin 4.0.1, Vtk 8.2.0, OCC 7.6.3
Locale: English/United States (en_US)
Installed mods: 
  * FeedsAndSpeeds 0.5.0
  * FeedsAndSpeeds-master.zip
  * freecad.gears 1.0.0
  * Help 1.0.3

Same computer, same user config, etc, etc. This happens to be on Windows 7, but Windows 11 shows the same behavior.

Gene

[chrisb]

@chrisb I assume your MacOS build of 0.20.2 doesn't give this symptom either because it's built on Conda?

Indeed, no problem here:

Code: Select all

OS: macOS 13.0
Word size of FreeCAD: 64-bit
Version: 0.21.0.31709 (Git)
Build type: Release
Branch: master
Hash: e188802ca6997d2564e7570ab648462e6a059f87
Python 3.10.8, Qt 5.15.6, Coin 4.0.0, Vtk 9.1.0, OCC 7.6.3
Locale: C/Default (C)
Installed mods: 
  * FC_SU
  * DynamicData 2.46.0
  * freecad.gears 1.0.0
  * FeedsAndSpeeds 0.5.0
  * dxf-library
  * fcgear 1.0.0
  * fasteners 0.4.54
  * sheetmetal 0.2.60
  * ExplodedAssembly
  * Curves 0.6.6