Major update from 0.16 to 0.19: Migrating problems

Discussion about the development of the Assembly workbench.
Forum rules
Be nice to others! Respect the FreeCAD code of conduct!
kbwbe
Veteran
Posts: 1052
Joined: Tue Apr 10, 2018 3:12 pm
Location: Germany, near Köln (Cologne)

Re: Major update from 0.16 to 0.19: Migrating problems

Post by kbwbe »

Hi Koemi,
i can import both versions of Slotbout-M10x80 without problems to an assembly file.

The error message in the reportview looks strange. Do you try to get a relative path from a server to a local drive ?
Maybe this creates some trouble.

See screenshot. Both of my imports are inside and correct. Your old import is missing all sourcefile imformation.
import-problem.png
import-problem.png (159.05 KiB) Viewed 818 times
Greetings, Klaus

My system

Code: Select all

OS: Linux Mint 20.3 (X-Cinnamon/cinnamon)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.Unknown
Build type: Unknown
Python version: 3.8.5
Qt version: 5.12.8
Coin version: 4.0.0
OCC version: 7.5.1
Locale: German/Germany (de_DE)

KBWBE

https://github.com/kbwbe/A2plus
latest release: v0.4.56, installable via FreeCAD's addon manager
Tutorial: gripper assembly https://www.youtube.com/watch?v=QMxcQ5tssWk
Documentation: https://www.freecadweb.org/wiki/A2plus_Workbench
Koemi
Posts: 150
Joined: Thu Dec 28, 2017 11:13 am
Location: The Netherlands

Re: Major update from 0.16 to 0.19: Migrating problems

Post by Koemi »

Hi kbwbe, thanks for your reply

This morning I started my PC and FC. Opened the assembly, tried to add the same parts and...

It worked 100%!! Flabbergasted!! :shock: :shock:
The error message in the reportview looks strange. Do you try to get a relative path from a server to a local drive ?
I do not know exactly what you mean, but all created files are saved on a server (Z-drive) for backup purposes obviously. The FreeCAD software is saved on my local C-Drive.
Maybe this creates some trouble.
I think you're right, but why is this a problem since I went to V0.19 (and A2Plus)? With V0.16 (and Assembly2) I never had any problems like this?

And very, very, much more important: how to solve this? :?

Another strange thing (maybe related): when I have an assembly (made with A2Plus) and I click on a part, normally I can check the path of the part (Combo View > Property > import part > source file) but sometimes I do not get the path as it should but this one: C:\Program Files\FreeCAD 0.19\bin

My system

Code: Select all

OS: Windows 10 Version 2009
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.24267 +99 (Git)
Build type: Release
Branch: Branch_0.19.3
Hash: 6530e364184ce05ccff39501e175cf2237e6ee4b
Python version: 3.8.6+
Qt version: 5.15.2
Coin version: 4.0.1
OCC version: 7.5.3
Locale: Dutch/Belgium (nl_BE)
Koemi
Posts: 150
Joined: Thu Dec 28, 2017 11:13 am
Location: The Netherlands

Re: Major update from 0.16 to 0.19: Migrating problems

Post by Koemi »

And it goes on and on...

New part, created with V0.19. Saved this part locally on c-drive (check attachement).

Tried to import it in the assembly. And it fails. Same sh*t as described earlier. What the hell is going wrong? Am I the only person in the world with this problem?

I definately need help, because now It is 99% impossible to do my work.

Fusion360 is knocking on my door and I do not want that to happen... :(

Update:
Saved the assembly locally on c:, then tried to import the part >>> This actually works! :D

I guess I got to have some chat with the server-guy here. If someone has tips according to this subject or has had also these kind of problems, would be great to read what the solution could be.
Attachments
019_5baans weg.FCStd
(41.12 KiB) Downloaded 24 times
Post Reply