Jump to content

thopiekar

Dormant
  • Posts

    323
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by thopiekar

  1. Nope, replace it with the script in the macro folder of the plugin.

    You know where I mean?

     

    Something like:

    /home/<your user id>/.config/cura/4.8/plugins/CuraFreeCadPlugin/macro/

     

    My plugin is running a macro from inside the plugin folder using "freecadcmd" btw. 🙂

  2. I improved the export script to convert all volumetric and shaped objects. Wasn't happy with the results some time ago when I was working on something in FreeCAD, so I gave it another try. One thing that definitely needs improvement is that I can check the objects' visibility. This is not available within FreeCAD's headless mode, because people might have thought: "Why caring about visibility, if you have no UI and can't see anything anyways."

    Well, good point, but stupid if I would like to convert all visible objects (because theoretically you could have made some invisible because something is temporarily not needed) into mesh(es).

     

    Anyway, I could deliver a new package for this, but I think it won't be a big deal for you to replace the following FreeCAD macro:

     

    https://git.thopiekar.eu/Cura/CAD/CuraFreeCADPlugin/-/blob/master-improving-macro-to-export-volumetric-and-shaped-objects/CuraFreeCADPlugin/macro/conversion.py

     

    Good luck and if you need any kind of help, let me know!

    Looking forward for your feedback 🙂

  3. Hey!

     

    After a longer time I got FreeCAD into my hands again and probably faced the same issue as you do!

    If you are using Ubuntu* (likely affects Debian, too) there is a problem with the "headless mode" of FreeCAD.

    The only way to make it work is to use the stable PPA of FreeCAD, which comes with the fix, which will make the plugin work again, too!

    https://wiki.freecadweb.org/Install_on_Unix#Stable_PPA_through_the_graphical_interface

  4. @Khamul2000: If you are interested to dig deeper, you can take a look into the plugin's source files.

    The file called "SolidWorksReader" has the parameters, which you would normally set via "Custom" mode:
    https://git.thopiekar.eu/Cura/CAD/CuraSolidworksPlugin/-/blob/master/CuraSolidWorksPlugin/SolidWorksReader.py#L656

    As I said before, if you find other settings (or one of the two) too coarse for e.g. "fine", then argue and let's discuss here. We can adjust the parameters then, so everyone can benefit from our findings 😉

  5. Great to hear! The settings are finer than in the SolidWorks ones. If you are using SolidWorks only you choose between three profiles:
    * Fine

    * Coarse
    * Custom

    These fine and coarse profiles are the SolidWorks' ones you see in the plugin. I can imagine SolidWorks tweaked the parameters behind these profiles for industrial printers with larger build volumes and therefore if you print on an Ultimaker (having an Ultimaker 2 or 3 primary in mind) then you will get something that is too coarse still. E.g. the rounding won't be nice.
    Just to suite everyone using the plugin, I decided to keep the access to SolidWorks' presettings - for those who are used to them.

    Btw., if you find the parameters in our fine profile still too coarse, just let me know! 🙂

  6. Hmm, looks like the registry keys are missing on your computer. That can be either because there is no support for external access via Windows Automation on your version or there is something special about your installation still.

    Maybe some old conventions to register, I don't know of??

     

    Which version of Windows are you using? 🙂

  7. The service checker is only to test the functionality of the connection to SolidWorks. Actually, I'm surprised that there are so many leftovers on your computer. Every entry in service checker indicates that some installation has been found on your computer.

    However, the executable (.exe file) to your installation could not be found. Normally, it should be known by your registry for Windows' automation interface.

    Could you be so kind and send me your log file? I should tell me more precise why the executable has not been found. I can imagine of either a malformed path or missing entry in your registry 🙂

    If you need any further help or instructions, please let me know!

  8. Heard the same from other people in the meantime, too.

    The macro is written in VBA and contributed by Ultimaker years ago as they wanted to see this feature as part of the plugin.

    However, it seems that they changed something to Cura's installer, so registry entries are written differently and thus the macro can't find it. The last time that happened was when "Cura" got renamed to "Ultimaker Cura", that's why I guess it must be something similar.

×
×
  • Create New...