Linux version

I’ve been using S3D so far, adjusting setting compared to the Cura download. During the brief time I have my dual solenoid working, S3D changed the tools when requested.

Well I don't have experience with AppImage but I do compiling programs. I gave it a try but I failed too =P.

This was my experience, also this will get technical fast:

For anyone who wanna try there are 3 public repositories of Cura. One is the software. Cura-build repository is to make the images. And finally a repository to set up your environment. I tried to compile cura-build but I really didn't want to use the environment setup code, I downloaded it but I have no idea how to use it with the other repositories plus I don't like running those kind of scripts in my computer. So I began the quest to install the dependencies by myself and I think I used all of my skills; getting needed packages for ubuntu from reviewing the repohistory of the readme file; installing newer packages with python pip; solving extra dependencies; Installing Appimage(this was really complex by its own)and copying to /usr/bin/ AppImage runner and tools executable with the names that cura-build use. I think I'm really close to compile it without errors but now I get a error in cmake of "get_filename_component unknown component CACHE" , looking further in the logs seems like a problem with compile command option -lpthread. Here I was going to break my rule of not modifying the repositories files( the compilations files) but I failed after analyzing several files; I knew what to do but couldn't find the place; But mayney It is just a dead end. That is how far I got, I think that after solving the cmake errors I will only need to run a command to make the app image.

Maybe I could try it later in a virtual machine if I found more free time. If anyone want me to detail my steps I could elaborate them, I was planning to but since at this point I think I failed too then I will wait.

Nice to hear that you are behind it. So they gave me an apple computer at work so I'm slicing with that computer now, finally got my first print =D. But definitely waiting to do it in Linux hehe.

Hello,

I have been playing around with cura build environment repository this days but still no luck. It a dependencies hell in ubuntu. I have been trying with the last 3 LTS releases (as appimagetool supposedly has a hard requirement of using really old packages) using virtual machines but still no luck and I got different results in each release. Appimage tools keep being a problem and a blank in my knowledge.

Now I'm learning docker and trying this way, probably the smartest move.

Whoever write all this guide is probably not using an debian based Linux, probably using CentOs as the docker image. Also someone updated the linux instructions some days ago in cura-build repo for ubuntu https://github.com/Ultimaker/cura-build/commit/254f8435c049ac4dc08ccb558fd51a6d80e5bc12 and in cura-build-environment https://github.com/Ultimaker/cura-build-environment/commit/dd910d83e98fd2fe02c1d441c4671726bcfe5757 in case someone wanna try.

I got good news! the cura version you made for windows works perfectly great using wine hahaha xD. Also is impossible to download a installer for Mac from your webpage(both download links point to the same windows .exe)

I gave it a try to docker to compile cura but somethings seems wrong, I think i couldn't make the image run after configuring it. Why you choose cura version 3.6 instead of ?

Anyways, I'm back to melting plastic! but I will like to have an update about the pull request progress, and for the simplify 3d profiles

Works nicely and gives a Linux AppImage with ProForge goodness.

Would you be OK if I included the Makertech custom resources in a github repository with the repacker script? Are the Makertech custom resources under any license I need to note? Happy to accept PRs for any other needed changes too :)

Edit: the Makertech resources are just the printer/nozzle/material/etc definitions - none of your logo work or imagery.

Thats great Molotov!!! Lets wait for

So we don't have a word, then we should proceed and ask for forgiveness after!

There should be no problem as they are only configurations of cura, the rights are of cura, as long as we keep the makertech and Proforge name but declaring that it is not yours. The only part that could a conflict will be the images but you said you will not include that, as they aren't necessary. I don't know if there is a separate configuration for the printer and for the materials used.

Thanks for letting me know about the MAC link for CURA - it's been updated now.

As for the modifications to CURA feel free to use/edit anything you like (including our logo/artwork), it's all opensource. Everything that's integral should be in the resources folder.

Simplify3D profiles are on our to do list - just very busy at the moment!!

In the meantime you should be able to setup Simplify3D with the build volume (20x30x30cm for single and 20x30x25 for DSE) and default print values, the DSE doesn't need any special gcode from the slicer (switching is handled by firmware). It's just the nozzle offsets for tuning - but these will be unique for everyone.