Thank you for the tutorial. I am trying to learn this assembly module and it seems more complicated to use than it needs to be. Also, how many times did Freecad crash while trying to do this?? :)
Boy, this is excellent work. Thank you so much, I've watched a couple of times, and I'm beginning to understand and can start to assemble. I sent a small thank you via paypal... A question: Do I understand correctly that the In context design practices you are demonstrating here will conflict with the main FreeCad build, regarding the Topo naming situation, and requires adopting realthunder's build to accomplish in context modeling? I'm reading on freecad's wiki about this. So if we used the main build, the names of assembly parts may change, and the planes and points that are referenced in the assembly for instance may break and cause the parts to disconnect undesirable ways, is this correct? I watched your two interviews with realthunder, they are very helpful. It seems that realthunders branch is pretty stable, and he's actively merging the upstream with his changes and trying to get his improvements upstream. Are assemblies made in link able to be exported to upstream builds? Have you had any difficulties with utilizing the realthunder builds? Our needs are fairly small, not too worried, but would appreciate your input... Thanks
Thank you so much ... your contribution was so welcomed that I already spent it on linear bearings so consider it a investment in the future of freecad education regarding the path workbench :) Atm it is advised against mismatching the Linkstage3 branch and master files. Linkstage3 has tools that help with the in context modelling that have not yet landed in master. Especially tools for cross body referencing that are a must when designing in context . The topo naming algo is actively merging as we speak, in fact Realthunder has had few releases lately because of that. We will see soon a release of a master branch with the algo included. That being said, I use Linkstage3 on some fairly complex projects and I had close to none segmentation faults. There is the occasional bug that is being reported and Realthunder is highly active at squashing them. If you haven't already seen it I would recommend also this video ruclips.net/video/JZUsNR2ys1I/видео.html Cheers and thank you again
@@OficineRobotica Excellent! RealThunder is amazing, the work and talent he is putting into this project is incredibly generous, I think I'll donate to him as well. For our purposes I think it's safe enough to switch to the link3 branch, I don't have anything so complex that it would be a problem even if there was backwards compatibility that caused me to have to recreate assemblies or something. It is comforting that you are finding only minor concerns, and they are addressed quickly. Also, until I watched your interviews with realthunder, I wasn't aware of the very helpful UI changes, although I did wonder what settings you were using for instance to get the transparent toolbars. I've been interested 2d drafting since the earliest days of page layout programs, and I recently became aware of all the 3rd party services where you can send for cutting, milling 3d printing. I care for a small suite of Italian stone working machines, and often run into problems with availability or cost of parts, and now I can design my own parts and enhancements, and have them made for me for a reasonable cost. After a few trys to have blender make cam files, I discovered freecad, and I'm obsessed ever since. Since I found your videos, I've been able to take engineering files from SKF, McMaster, Eurodrive, and design fixes that there is no ready-made solution for. For instance, my big stone saw has a belt roller with a drive, and since it's a wet environment, and there are no seals, the shaft corrodes so fiercely to the hollow shaft after a few years that a 100 ton press can't separate them, requiring thousands of dollars and a week of downtime to fix. Now I'm designing and preparing to have made a system to retrofit seals to the system that should help prevent or at least postpone this problem. So thank you again, Sir, you are a fine communicator, very generous with your time.
@@zincfive FIY I live in Turin Italy ;) .... you can find my email in the channel info page, who knows, with a bit of publicity you could cut granite for cnc machines lol
@@OficineRobotica Ah, the stone machines are made in Marinello, not too far from Turin... You mentioned gaining Italian citizenship in one video, I took your accent to be Italian. What's your nationality? Did your application go well?
Is using Part container mandatory, or is using subassemblies in Assembly 3 also and option. Isn't part container a remnant of old freecad's assembly aspiration?
Yes, "Part" was originally created as a base building block for assemblies. It is still around because it has some really useful properties. Most notably, it gives a common coordinate system for a group of objects and this is what we are interested in when modelling in context. Also it gives a common visibility toggle for the said group other than permitting to group under it's tree branch datums, reference images etc etc You could easily follow this tut wibought creating the Part001 but you would loose the ability to move everything as a group as I am doing towards the end of the video. I tend to always wrap designs in Part containers.
@@OficineRobotica But I see you are using subshapebinder witin part container and with bodies. Is it possible and if yes how can you transfer features with for example shape binder, between assembled parts? Either I have cycling dependency error or if using links I need to actibate a body and links wont be activated
Not even if you search in the "Type to search field" of the "Customize" panel? If I search it in the last Linkstage3 release i get as one of the results "Refresh (Std_Refresh) (F5)" . You can then add it to the pie menu
![[LinkStage3] FreeCAD in context modelling. Simplified version.](http://i.ytimg.com/vi/JZUsNR2ys1I/mqdefault.jpg)
![[LinkStage3] FreeCAD in context modelling. Simplified version.](/img/tr.png)
![[LinkStage3] FreeCAD in context modelling using assemblies. Part1 assembly3.](http://i.ytimg.com/vi/K0ATkxFhLFc/mqdefault.jpg)
Thank you very much, your tutorial makes freecad more useful.
Please, continue. Like your videos 😉
Thank you a lot. It is one of the best tutorials I saw!!! I encourage you to do videos like this one
Great tutorial as always
Very Interesting, thanks for publishing this...
sono impressionato, grazie mille
Ti ringrazio tantissimo :)
Lots to take in but fabulous tutorial again thanks 😀
Great job, so many possibilities with linkstage3, perhaps better than creo top down skeleton modeling
Nice work 👍👏
Valeu!
Thank you for the tutorial. I am trying to learn this assembly module and it seems more complicated to use than it needs to be. Also, how many times did Freecad crash while trying to do this?? :)
Boy, this is excellent work. Thank you so much, I've watched a couple of times, and I'm beginning to understand and can start to assemble. I sent a small thank you via paypal...
A question: Do I understand correctly that the In context design practices you are demonstrating here will conflict with the main FreeCad build, regarding the Topo naming situation, and requires adopting realthunder's build to accomplish in context modeling? I'm reading on freecad's wiki about this. So if we used the main build, the names of assembly parts may change, and the planes and points that are referenced in the assembly for instance may break and cause the parts to disconnect undesirable ways, is this correct?
I watched your two interviews with realthunder, they are very helpful. It seems that realthunders branch is pretty stable, and he's actively merging the upstream with his changes and trying to get his improvements upstream. Are assemblies made in link able to be exported to upstream builds? Have you had any difficulties with utilizing the realthunder builds? Our needs are fairly small, not too worried, but would appreciate your input...
Thanks
Thank you so much ... your contribution was so welcomed that I already spent it on linear bearings so consider it a investment in the future of freecad education regarding the path workbench :)
Atm it is advised against mismatching the Linkstage3 branch and master files. Linkstage3 has tools that help with the in context modelling that have not yet landed in master. Especially tools for cross body referencing that are a must when designing in context . The topo naming algo is actively merging as we speak, in fact Realthunder has had few releases lately because of that. We will see soon a release of a master branch with the algo included.
That being said, I use Linkstage3 on some fairly complex projects and I had close to none segmentation faults. There is the occasional bug that is being reported and Realthunder is highly active at squashing them.
If you haven't already seen it I would recommend also this video ruclips.net/video/JZUsNR2ys1I/видео.html
Cheers and thank you again
@@OficineRobotica Excellent! RealThunder is amazing, the work and talent he is putting into this project is incredibly generous, I think I'll donate to him as well. For our purposes I think it's safe enough to switch to the link3 branch, I don't have anything so complex that it would be a problem even if there was backwards compatibility that caused me to have to recreate assemblies or something. It is comforting that you are finding only minor concerns, and they are addressed quickly. Also, until I watched your interviews with realthunder, I wasn't aware of the very helpful UI changes, although I did wonder what settings you were using for instance to get the transparent toolbars.
I've been interested 2d drafting since the earliest days of page layout programs, and I recently became aware of all the 3rd party services where you can send for cutting, milling 3d printing. I care for a small suite of Italian stone working machines, and often run into problems with availability or cost of parts, and now I can design my own parts and enhancements, and have them made for me for a reasonable cost. After a few trys to have blender make cam files, I discovered freecad, and I'm obsessed ever since. Since I found your videos, I've been able to take engineering files from SKF, McMaster, Eurodrive, and design fixes that there is no ready-made solution for.
For instance, my big stone saw has a belt roller with a drive, and since it's a wet environment, and there are no seals, the shaft corrodes so fiercely to the hollow shaft after a few years that a 100 ton press can't separate them, requiring thousands of dollars and a week of downtime to fix. Now I'm designing and preparing to have made a system to retrofit seals to the system that should help prevent or at least postpone this problem.
So thank you again, Sir, you are a fine communicator, very generous with your time.
Just watched you In Context modeling tutorial. Very powerful! Thanks Again!
@@zincfive FIY I live in Turin Italy ;) .... you can find my email in the channel info page, who knows, with a bit of publicity you could cut granite for cnc machines lol
@@OficineRobotica Ah, the stone machines are made in Marinello, not too far from Turin... You mentioned gaining Italian citizenship in one video, I took your accent to be Italian. What's your nationality? Did your application go well?
Is using Part container mandatory, or is using subassemblies in Assembly 3 also and option. Isn't part container a remnant of old freecad's assembly aspiration?
Yes, "Part" was originally created as a base building block for assemblies. It is still around because it has some really useful properties. Most notably, it gives a common coordinate system for a group of objects and this is what we are interested in when modelling in context. Also it gives a common visibility toggle for the said group other than permitting to group under it's tree branch datums, reference images etc etc
You could easily follow this tut wibought creating the Part001 but you would loose the ability to move everything as a group as I am doing towards the end of the video. I tend to always wrap designs in Part containers.
@@OficineRobotica But I see you are using subshapebinder witin part container and with bodies. Is it possible and if yes how can you transfer features with for example shape binder, between assembled parts? Either I have cycling dependency error or if using links I need to actibate a body and links wont be activated
Thank you. How can I insert "Refresh (F5)" in the Pie-Menu. Cannot find "Refresh".
Not even if you search in the "Type to search field" of the "Customize" panel?
If I search it in the last Linkstage3 release i get as one of the results "Refresh (Std_Refresh) (F5)" . You can then add it to the pie menu
I love the Realthunder branch, too bad it constantly crashes on my machine.
Have you tried the release from here? github.com/realthunder/FreeCAD/releases
What os are you on?