Assembly3 preview

[realthunder]

Could we somehow help on this? One way is to serve as a rubberduck (as http://rubberduckdebugging.com suggests) at least. IMO, the solution will shine once you (could?) explained the problem to me (us). (In other words, I won't do anything other than listening )

Haha, there is actually a website for this. And it does work. I always think that is why Holmes needs Watson.

About the problem, I have already found a potential solution. Still need some test, though.

[OakLD]

Haha, I'll have to borrow one of these rubber mentors from my kids next time I'm stuck

I was thinking about the misplaced parts and one strange thing that that baffle my mind why (some) of the parts (or their dejavu copies) are placed in such an odd angle. I then remembered, that my assembly was aligned wit GCS until some very late stage of assembling, when it got somehow misplaced. I think I tried to hide and show some parts around that time.
Just a thought, I'm not sure if it's important.

I still experience extremely long times when using Move tool, I guess it recalculates all assembly solution after any move/rotation even when auto recalc is off (is it?). With such assemblies, you can nearly go have a tea (even with Hi-spec PC) even with simple move of one un-constrained (!) part. As reported months ago, it's same on W7, W10 and OpenSuSE Linux. If above assumption is correct, it would be great if (yet) unconstrained parts can be removed from recalculate trigger and if it was sensitive to setting of auto-recompile button.
The hiding was a result of those desperate low speeds, but it didn't help anyway.

Sorry for not being more specific then this, console doesn't show anything interesting, so it's just what I see.

[realthunder]

I still experience extremely long times when using Move tool, I guess it recalculates all assembly solution after any move/rotation even when auto recalc is off (is it?).

There are a few performance related improvements thanks to ceremcem's report. I will try my best to make a release this month.

[fosselius]

I will try my best to make a release this month.

\o/ yey! Awesome!

[m.cavallerin]

Hi all,

just a question about link & elements.
As for the wiki page, the author suggests to define elements before starting assembling operations and also tell us to use prior entities on the design stage(phase) as for reduce the impact of topology(?) name modifications due to modelling operations; for this reason he truly suggests to use sketches as it is possible to see in the "Large assembly tutorial".

In any case, is it possible to add a modification to the link "path" inside the element object to redefine it in case of design process modifications? Is it manageable?

[realthunder]

In any case, is it possible to add a modification to the link "path" inside the element object to redefine it in case of design process modifications? Is it manageable?

You can select the new geometry in 3D view, and then drag the corresponding tree item and drop it to an existing 'Element' object item. This will modify the 'Element' to point to the new geometry.

[m.cavallerin]

Easier than expected!

I'm facing another issue about the freezing operation:
When I freeze an assembly, the freezed configuration shows me Parts in other position, what am I missing?

Thx.

[realthunder]

I'm facing another issue about the freezing operation:
When I freeze an assembly, the freezed configuration shows me Parts in other position, what am I missing?

There is a bug in shape combining that has been fixed. I'll try to make a release in this month. Can you please attach your model file and let me test it?

[m.cavallerin]

Sure, no problem!

I created a .7z file with the 3 components.

Let me know if you face problems.

Thx.

[realthunder]

Sure, no problem!

I created a .7z file with the 3 components.

Let me know if you face problems.

Thx.

The shape combining works fine now. BTW, when you distribute your file with external links, you must preserve the exact layout of all files, because FC uses relative file path for external linking.