Kronologic81

Here my files... load it on shared/cura/resources and on your AppData/Roaming/Cura 5.6... directory... Cura 5.6 - files to make FLSUN V400 work .zip

Finally I could slice successfully, but I had to do a lot of handcrafting with all the configuration files. Cura 5.4 was working flawesly but 5.5 and 5.6 has been a nightmare. First, there are no variants so any profile that you try to set goes to a empty variant. I've loaded the variants, qualities with some prebuild configurations, intents, extruder, and the problem with the definition finally, if you take the FLSUN SR definition, and the FLSUN V400 set the same amount of overrides, that means, nothing... The Slicer fiflsun_v400.def.zipnally executes, the problem here is that the precalculation of the speeds, and other stuff are lost. I've attached my deffinition file and a prove that the process has finished, after weeks of fighting against that.

Hi, There is some implementation of a 2-tier for CURA? We have two computers, 1 a standard laptop where we run the CURA Gui where we do the stuff related to the positioning on the building area and so one. And a second server that have a 32 vCPU cores, but has not possibility of interactive session. But I would put over this server the load corresponding to the slicing process. That's the "uranium" component if I'm not wrong, that is started by the gui and accessed using a loopback tcp/ip connection thru a socket created ad-hoc for the engine execution. It's possible to segregate the Backend process to an external server that could process faster the slicing load? Thanks.

Hi, There is another concept of remote server. We have two computers, 1 a standard laptop where we run the CURA Gui where we do the stuff related to the positioning on the building area and so one. And a second server that have a 32 vCPU cores, but has not possibility of interactive session. But I would put over this server the load corresponding to the slicing process. That's the "uranium" component if I'm not wrong, that is started by the gui and accessed using a loopback tcp/ip connection thru a socket created ad-hoc for the engine execution. It's possible to segregate the Backend process to an external server that could process faster the slicing load? Thanks.