I guess, you are using Linux, right?
PS: The bug fix works for you?
Edited by thopiekarI guess, you are using Linux, right?
PS: The bug fix works for you?
Edited by thopiekar@thopiekar In Freecad It seems the ActiveObject is the last created one (may be a bug) You can check it in Pyton Console with >>> App.ActiveDocument.ActiveObject.Name after create more body/object
But it is not a problem: I think you have just to know that if you have more object/body ( say a cube and a cylinder) you must do a fusion as last step.
3 hours ago, thopiekar said:I guess, you are using Linux, right?
PS: The bug fix works for you?
I'm sorry, yes, I'm using Linux.
And I don't know if the bugfix works, because I have not installed FreeCAD-stable only for the plugin. This is not an acceptable solution for me (I am a morbid perfectionist...).
4 hours ago, RobyRob said:@thopiekar In Freecad It seems the ActiveObject is the last created one (may be a bug) You can check it in Pyton Console with >>> App.ActiveDocument.ActiveObject.Name after create more body/object
But it is not a problem: I think you have just to know that if you have more object/body ( say a cube and a cylinder) you must do a fusion as last step.
Hmm, so there could be two ways of importing something into Cura, right? Once by using an active object, as I do now, or by looking for visible bodies.
I guess the method with the visible bodies could get interesting when printing with multiple extruders.
2 hours ago, UbuntuBirdy said:I'm sorry, yes, I'm using Linux.
And I don't know if the bugfix works, because I have not installed FreeCAD-stable only for the plugin. This is not an acceptable solution for me (I am a morbid perfectionist...).
Well, if it is not too difficult for you, then add the binary directory of your installation to the $PATH environment variable.
Or (as I do) upgrade FreeCAD using the FreeCAD PPA. Currently, they deliver version 0.18.0 in it.
25 minutes ago, thopiekar said:Well, if it is not too difficult for you, then add the binary directory of your installation to the $PATH environment variable.
Or (as I do) upgrade FreeCAD using the FreeCAD PPA. Currently, they deliver version 0.18.0 in it.
I am using the FreeCAD PPA, but the daily builds...
Well, I believe it would not be too difficult to add the binary directory, if I would know where to find the $PATH environment variable...
@UbuntuBirdy Personally, I prefer the second answer (modifying .bashrc):
https://askubuntu.com/questions/60218/how-to-add-a-directory-to-the-path
PS: The new version is on its way:
hmmm ... either my faith in my ability was too strong, or it is not because of the missing path...
Can the reason be that the daili builds is started not with the command "freecad" but with "freecad-daily"???
Could be. I'm using the stable PPA. Does an "freecadcmd-daily" exist, too?
The plugin is using the freecadcmd command line application to do the conversion from FCstd to STL automatically.
If another name is used, then it won't be recognized.
That's it! I changed the "FreeCADcmd" to "FreeCADcmd-Daily" and now it works perfect! Thank you so much for your plugin and your support!!!
7 minutes ago, UbuntuBirdy said:That's it! I changed the "FreeCADcmd" to "FreeCADcmd-Daily" and now it works perfect! Thank you so much for your plugin and your support!!!
Haha, no problem. I think I need to think about adding a window for overwriting the path to the executable and overwriting the executable name 😅
2 minutes ago, thopiekar said:Haha, no problem. I think I need to think about adding a window for overwriting the path to the executable and overwriting the executable name 😅
Would it not be easier to query the two or three options and execute them accordingly?
1 minute ago, UbuntuBirdy said:Would it not be easier to query the two or three options and execute them accordingly?
Yes, would save them in the settings storage and recover them on each load of a file. Within a settings window in the menu, they could get changed or reset. Think that might be something interesting for all commandline-based plugins (Blender and OpenSCAD), too.
I am happy with every solution, even if I have to rewrite from hand to daily like now...
Could someone with an Apple laptop do me a favour and test the unreleased plugin above?
Thanks!
Found the bug. Made the changes on the script with FreeCAD 0.18, but some functions are not backwards compatible to 0.17. Made it working for both now.
New testing release:
https://thopiekar.eu:5443/cura-cad-integration/CuraFreeCadPlugin/-/jobs/1300/artifacts/browse
I just touched some minor things when working on the SolidWorks and Inventor plugin.
Would be great if you could give it a try.
Thanks!
Made my FreeCAD-Daily adaptation and it works like a dream! Thanks again!
Hey guys, where should I post issues for Freecad Plugin?
I am running Cura 4.2.1 with Freecad Integration plugin 0.3.1. It can't open my FCStd files from Freecad 0.18.3.
Please, can someone reference me where this plugin is being developed?
As I could verify, It works with Frecad <= 0.18.2 only.
Hello Leo,
there are problems uploading a new release with corrections for FreeCAD >= 0.18.0.
Hope I'll manage to resolve the issue together with Ultimaker soon.
Hello thopiekar, thanks for the reply. Is there any thing that I can do to help you?
Edited by leoheckI am still investigating this issue. Now, I have cura 4.3.0 with FreeCAD integration 0.3.2.
The macro runs flawlessly from the command line but I was not able to run it with Cura.
I am thinking the issue is in the CommonCLIReader.py but it is just a guess.
Maybe it is a bug on executeCommand. I am discarding this one. It looks good.
Cura just say "Invalid File, Failed to load"
Recommended Posts
UbuntuBirdy 56
I'm working with FreeCAD-dailybuilds. Is there another possibility to get working the plugin than installing the stable version of FreeCAD?
Link to post
Share on other sites