Differences in Freecad between 32 bit windows and 64 bit windows

[wmayer]

Does it work now?

[rasomei]

Hi,

have I something to do with the git commit ?

After installing the vcredist_x86.exe and deleting the Python.dll it is the same as before.
I attached some logs and screenshots.
FreeCAD-0.15.4671_x86 runs stable as before but no one of the 0.16 versions (32bit and 64bit)
I tested



FreeCAD_0.16.6076_x64_dev_bin
FreeCAD_0.16.6109_x64_dev_bin
FreeCAD_0.16.6114_x64_dev_bin
FreeCAD_0.16.6124_x86_dev_bin

You said you can exchange the numpy 1.9.1 by copiing the numpy of the Winpython to the FreeCAD\lib.

Perhaps my whole windows installation is bad and I should reinstall windows completely new ?

[rasomei]

Hi wmayer,

I tested the following FreeCAD Version I have on my PC.

OS: Windows 8
Word size of OS: 64-bit
Word size of FreeCAD: 32-bit
Version: 0.16.5772 (Git)
Build type: Release
Branch: AMM-oldWokrflow6-rebaseMaster
Hash: 85dea389cc349e54c33a65224cf9418e5cc7ce12
Python version: 2.7.8
Qt version: 4.8.6
Coin version: 4.0.0a
OCC version: 6.8.0.oce-0.17


FreeCAD is starting with the assembly modul. But in this distribution i have the same as in the 64bit versions of FreeCAD.
Solving the assembly constraint some are flipping . Please see attached screenshot.

[wmayer]

have I something to do with the git commit ?

No. It only tells you that if a new version is out it should no longer abort due to this issue.

Perhaps my whole windows installation is bad and I should reinstall windows completely new ?

Rather unlikely. But it's strange that DW still shows the side-by-side error.

FreeCAD is starting with the assembly modul. But in this distribution i have the same as in the 64bit versions of FreeCAD.
Solving the assembly constraint some are flipping . Please see attached screenshot.

This all is weird. But at least it shows now that it's not a 32 vs. 64-bit issue but related to something else. numpy is still a possible candidate.

[rasomei]

Hi again,
actually I´m working on Linux Mint 17.3, but my aim is to continue my work on Win 10 64 bit.
It is running smother with my older Nvidia quadro FX 1800 graphics card.
Do you plan to implement numpy 1.3 (64 bit) into the Freecad package in the future?
Perhaps this could resolve my assembly2 problem.

regards
Ralf

[lutz_dd]

Have been triggered by assembly2 in the reply above ... maybe already fixed, but with using

OS: Windows XP
Word size of OS: 32-bit
Word size of FreeCAD: 32-bit
Version: 0.16.6408 (Git) .... download 1 hour ago (FreeCAD_0.16.6408_x86_dev_bin.7z)
Build type: Release
Branch: master
Hash: f942bf2729fe73998453830773cc936e8c4cb208
Python version: 2.7.8
Qt version: 4.8.6
Coin version: 4.0.0a
OCC version: 6.8.0.oce-0.17

the fresh installation is challenged by typing a simple "import numpy" in the Python window and returns

>>> import numpy
Traceback (most recent call last):
File "<input>", line 1, in <module>
File "C:\Dokumente und Einstellungen\mein_login\Desktop\FreeCAD_Downloads\FreeCAD_0.16.6408_x86_dev_bin\bin\lib\site-packages\numpy\__init__.py", line 170, in <module>
from . import add_newdocs
File "C:\Dokumente und Einstellungen\mein_login\Desktop\FreeCAD_Downloads\FreeCAD_0.16.6408_x86_dev_bin\bin\lib\site-packages\numpy\add_newdocs.py", line 13, in <module>
from numpy.lib import add_newdoc
File "C:\Dokumente und Einstellungen\mein_login\Desktop\FreeCAD_Downloads\FreeCAD_0.16.6408_x86_dev_bin\bin\lib\site-packages\numpy\lib\__init__.py", line 8, in <module>
from .type_check import *
File "C:\Dokumente und Einstellungen\mein_login\Desktop\FreeCAD_Downloads\FreeCAD_0.16.6408_x86_dev_bin\bin\lib\site-packages\numpy\lib\type_check.py", line 11, in <module>
import numpy.core.numeric as _nx
File "C:\Dokumente und Einstellungen\mein_login\Desktop\FreeCAD_Downloads\FreeCAD_0.16.6408_x86_dev_bin\bin\lib\site-packages\numpy\core\__init__.py", line 6, in <module>
from . import multiarray
ImportError: DLL load failed: Diese Anwendung konnte nicht gestartet werden, weil die Anwenungskonfiguration nicht korrekt ist. Zur Problembehebung sollten Sie die Anwendung neu installieren.
>>>

Following the instruction (item 2.) of viewtopic.php?t=12839#p102933 fixes the numpy-issue and assembly2 workbench is able to start. What the real differences are within the site-package is not known to me.

[sgrogan]

The numpy package in the latest x86 builds is definitely corrupted. It should be the same as in the 0.15.4671 release. But I can confirm the error and replacing the numpy package from the 0.15 release fixes the problem. I will fix it on the next builds. Thanks for the heads up.

[easyw-fc]

OK, I even changed the placement of an object e.g. "Halter_fuer_Endschalter_01" to make sure that the solver does something. After pressing the solve button the object moved back to its original position as shown in the image 32bit.jpg. Then I saved the project under a new file name and re-opened it and the object is still at the correct position. I don't get the situation as shown in picture 64bit.jpg

This was tested with:
OS: Windows 7
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.16.6096 (Git)
Build type: Release
Branch: master
Hash: 38d90ab4c2341e91ce1408937e33f54ed33898ca
Python version: 2.7.6
Qt version: 4.8.5
Coin version: 4.0.0a
OCC version: 6.6.0

numpy version is 1.9.2

Hi @wmayer
it would be possible to have a copy of numpy 1.9.2 for FC 64b?
I cannot find a way to download an old release of FC 0.16.6096 64bit (if in that build numpy was the right one)
The actual FC distro in win has numpy 1.9.1

I discovered that numpy is for sure a part of the problem...
for example in this file:

ProfiliQuadro-assembly-aligned-2-normal.FCStd

(12 KiB) Downloaded 161 times

Assembly2 behaves different in win and in linux
these parts cannot be aligned in win but they can in linux
(I'm trying to align
ProfiloQuadro1_01 oblique face to ProfiloQuadro2_02 oblique face using assembly2 'add circular edge constraint' that now can support also faces, not only edges)
followed and old thread that I forgot, I changed in assembly2, arctan2 from numpy to atan2 from math
and that is solving this problem ... so at least numpy in win should be the wrong package...
I attached the two files I changed in assembly2

lib3D.py

(39.14 KiB) Downloaded 72 times

degreesOfFreedom.py

(9.97 KiB) Downloaded 69 times

and the file aligned

ProfiliQuadro-assembly-aligned-3.FCStd

(9.25 KiB) Downloaded 79 times

Unfortunately when I tested the example available in assembly2 (tests DIR) with these changes

testAssembly17-bspline_objects.fcstd

(585.84 KiB) Downloaded 73 times

the objects don't get oriented correctly as in linux..
so there are still some bug in these two releases of numpy...
thx
Maurice

PS some relevant data in here
viewtopic.php?f=28&t=19783

[r-frank]

the objects don't get oriented correctly as in linux..so there are still some bug in these two releases of numpy...

Please have a look at this tutorial starting minute 34:00.

I think the animation behaves "jumpy" because of a bug in numpy when calculating the needed positions.

[easyw-fc]

the objects don't get oriented correctly as in linux..so there are still some bug in these two releases of numpy...

Please have a look at this tutorial starting minute 34:00.

I think the animation behaves "jumpy" because of a bug in numpy when calculating the needed positions.

what I miss for a complete comparison is a 1.9.2 release of numpy for FC in win 64b