Modification of Slicing Strategies
Quote from Simon BD on 2021-08-18, 09:58Hi Guys,
i am trying to modify the Slicing Strategies, and am haveing a few issues with this:
When i am Dublicating a Profile, i am just getting an empty Profile without any Overrides.
This is not a Dublication for me, it would be just a "new" Profile. (Having the Option to create a New one would be good anyway.)
My intention of a Dublicated Profile would be to have a Copy of all the included Overrides that can bemodified without destroying the original one.
Adding a new Override - Selecting the Toothed Wheel - Activating Box "Area Type":
Results in an Error Message (Logfile says: [error] Unhandled exception caught by QApplication::notify(): Bad any_cast")
So it is impossible to create an Override for any Kind of Area Type for me.
Is there a way to Export the Strategies or at least the complete Configuration ?
Or where are these files saved ?
Hi Guys,
i am trying to modify the Slicing Strategies, and am haveing a few issues with this:
When i am Dublicating a Profile, i am just getting an empty Profile without any Overrides.
This is not a Dublication for me, it would be just a "new" Profile. (Having the Option to create a New one would be good anyway.)
My intention of a Dublicated Profile would be to have a Copy of all the included Overrides that can bemodified without destroying the original one.
Adding a new Override - Selecting the Toothed Wheel - Activating Box "Area Type":
Results in an Error Message (Logfile says: [error] Unhandled exception caught by QApplication::notify(): Bad any_cast")
So it is impossible to create an Override for any Kind of Area Type for me.
Is there a way to Export the Strategies or at least the complete Configuration ?
Or where are these files saved ?
Quote from dartrax on 2021-08-18, 10:33Welcome to the community 🙂
The error message when adding a new override might be related to (or the same as) this one.
Welcome to the community 🙂
The error message when adding a new override might be related to (or the same as) this one.
Quote from Simon BD on 2021-08-18, 11:05Hi dartrax,
thx. for this Info.
I have also seen that Export/Import will be included in the Future, this would be good.
Is the empty Dublication also a known Bug ?
I just recognized that the Dublication works if i just Quit and Save. After the restart the dublicated Strategy is filled with all the copied Overrides.
Hi dartrax,
thx. for this Info.
I have also seen that Export/Import will be included in the Future, this would be good.
Is the empty Dublication also a known Bug ?
I just recognized that the Dublication works if i just Quit and Save. After the restart the dublicated Strategy is filled with all the copied Overrides.
Quote from Norbert Fekete on 2021-08-18, 14:47Hi Simon,
Yes, the slicing Strategy duplication bug is known, and it will work in the next release.
Along with the new Override addition problem.We're sorry that you need to wait for the fixes!
There are several things being added and reorganized in the code, so we had to make the decision of holding back the release for a longer period of time after 1.0.0.154.
Thank you for your patience!
We'd like to get back to the two/three-week scheduled releases as soon as we can.
Regards,
Norbert
Hi Simon,
Yes, the slicing Strategy duplication bug is known, and it will work in the next release.
Along with the new Override addition problem.
We're sorry that you need to wait for the fixes!
There are several things being added and reorganized in the code, so we had to make the decision of holding back the release for a longer period of time after 1.0.0.154.
Thank you for your patience!
We'd like to get back to the two/three-week scheduled releases as soon as we can.
Regards,
Norbert
Quote from Simon BD on 2021-08-19, 09:33Hi Norbert,
that is good to know.
Will it be possible to remove added Overrides from a Strategy ?
How can multiple Parameters be combined in one Override Topic ?
e.G. the existing ones like Topic "Perimeter" in default Strategy including EW / Feed Rate ... etc. ?
I have tried using a Skirt, and the Loop seems to have no effect on the length of the Skirt.
How can this length be changed, or is it also a Bug ?
For the Overview or optimization to read the Configuration it would be nice to have a small Letterbox with the really used Parameter next to the Modifier.
e.G. in Default Strategy - > Base parameter the EW is a percentage related to the Nozzle Diameter,
and in the Perimeter the EW is a percentage related to the calculated EW. It would be good to see the resulting used Parameter next to this for a better understanding.
Hi Norbert,
that is good to know.
Will it be possible to remove added Overrides from a Strategy ?
How can multiple Parameters be combined in one Override Topic ?
e.G. the existing ones like Topic "Perimeter" in default Strategy including EW / Feed Rate ... etc. ?
I have tried using a Skirt, and the Loop seems to have no effect on the length of the Skirt.
How can this length be changed, or is it also a Bug ?
For the Overview or optimization to read the Configuration it would be nice to have a small Letterbox with the really used Parameter next to the Modifier.
e.G. in Default Strategy - > Base parameter the EW is a percentage related to the Nozzle Diameter,
and in the Perimeter the EW is a percentage related to the calculated EW. It would be good to see the resulting used Parameter next to this for a better understanding.
Quote from Simon BD on 2021-08-19, 11:45By now i have found out that it is possible to combine multiple Parameter by choosing multiple Boxes in the Drop Down Menu.
How should the integration of Scripts be working ?
For Example i want to use a start Script. What should be written in the Field "GCode Start Script" ?
Should there be the Code or a Link to Script File ?
Whatever i have been trying leads to Error "[error] Unhandled string exception caught by QApplication::notify(): This object has no properties class craft::CraftValueBase * __ptr64"
Is there some Kind of How To or Advanced Manual for the Craftware Pro available ? Try and Error is not the best way to use this Software.
By now i have found out that it is possible to combine multiple Parameter by choosing multiple Boxes in the Drop Down Menu.
How should the integration of Scripts be working ?
For Example i want to use a start Script. What should be written in the Field "GCode Start Script" ?
Should there be the Code or a Link to Script File ?
Whatever i have been trying leads to Error "[error] Unhandled string exception caught by QApplication::notify(): This object has no properties class craft::CraftValueBase * __ptr64"
Is there some Kind of How To or Advanced Manual for the Craftware Pro available ? Try and Error is not the best way to use this Software.
Quote from Norbert Fekete on 2021-09-02, 14:02Hi Simon,
Sorry for the long delay!
Yes, you can remove Overrides, the trash icon is in the Condition manager popup, which you can open with the gear icon.
Built-in Overrides cannot be removed, just the ones you add as extra.As you've found out, the Binding manager popup which lists all the available parameters is a big multiple "on/off" switch for them with the checkboxes. The ones checked will be affected by the Override.
The Skirt is generated the following way:
- Calculate where the Skirt's outer perimeter should be
- Fill from this outer perimeter with concentric fill the number of times "Loop count" is set to.
- Run a Cut Area Post-Processor on it, which cuts this generated toolpath at the given length.The cut length is not a plain property, this is why it is not on the same level as the "Loop count" property, but it is inside the Are Post-Processors.
And now that I've looked at it in the latest release, there are some bugs. I'll add them to the bug tracking.
Until then you can still work your way around it:
- The Cut Area Processor should by default be visible in the "Skirt" Override. We'll look into this.
You can however override the default values for it by adding your own Cut Area Processor there. In the Binding manager of the Skirt Override, you can search for "processor", and you'll see the Cut Area Processor there, simply check its box, and it will be added.
- Next bug is, it should only contain two parameters, the "Front cut position" and "Back cut position". We'll get rid of the other two.
- Now that you have the processor there, set both "Actual front cut position" and "Front cut position" to "0", and the "Actual back cut position" and "Back cut position" to the maximal Skirt length you need. If you need all of it, just set "10000" or something there. 10 meters maximal Skirt length should be enough. 🙂
- An additional bug I realized just now: The Skirt actually get one loop less than the value set in "Loop count". Will check on this too.Okay, moving on:
"For the Overview or optimization to read the Configuration it would be nice to have a small Letterbox with the really used Parameter next to the Modifier.e.G. in Default Strategy - > Base parameter the EW is a percentage related to the Nozzle Diameter"
What do you mean by the "Letterbox"?
I agree that readability of the parameters, especially the bound ones are a bit hard, and it would be very good to have a design which could imply what they mean. In this way that you wrote: "Extrusion Width is 100% of currently used Nozzle Diameter"
If you have any suggestions, we are open to them.
Expert settings work in a complex way, and we would like to show them through an intuitive user interface. We know it won't work at first, this will be an iterative process to find out how it should be presented."and in the Perimeter the EW is a percentage related to the calculated EW. It would be good to see the resulting used Parameter next to this for a better understanding."
Yes, this is something which is in our backlog.
We want to put in the tooltip a hint about where the current parameter is coming from, which Overrides have bindings for it.
Also, in a separate part: Which parameters will be affected by this.Nice job finding out this by yourself! 🙂
We're also working on how to explain this property mechanism in a user manual the best we can.
It gives high flexibility, but also high complexity.
The GCode scripts will be multi-line input fields, and even will get a separate edit script popup, as you will be able to use properties in the scripts as well.
For now, you can add the GCode script binding, and type text there. If you press enter, you can type multiple lines there.
Just don't put in comments at the end of the lines there yet. Parameters don't have explicit positions, and a comment is considered as a parameter, so if you have a scipt with this:
"G1 E0 ;My comment"
Can result in this:
"G1 ;My comment E0"The reason for this is that GCode script texts are parsed and the GCode is regenerated from them. This will be the base for the script pre-processing.
For now it doesn't always keep the parameter.
It is a known bug, and we're working on it.
As you can see, the public beta release made us readjust things. This was the goal of releasing an early public beta, so we can still change course in development right before giving a final release.
This is why it does not have a manual yet as well. Needs to adjust with the software, and when it is solidified, then the manual can reflect properly what is in the software.
Regards,
Norbert
Hi Simon,
Sorry for the long delay!
Yes, you can remove Overrides, the trash icon is in the Condition manager popup, which you can open with the gear icon.
Built-in Overrides cannot be removed, just the ones you add as extra.
As you've found out, the Binding manager popup which lists all the available parameters is a big multiple "on/off" switch for them with the checkboxes. The ones checked will be affected by the Override.
The Skirt is generated the following way:
- Calculate where the Skirt's outer perimeter should be
- Fill from this outer perimeter with concentric fill the number of times "Loop count" is set to.
- Run a Cut Area Post-Processor on it, which cuts this generated toolpath at the given length.
The cut length is not a plain property, this is why it is not on the same level as the "Loop count" property, but it is inside the Are Post-Processors.
And now that I've looked at it in the latest release, there are some bugs. I'll add them to the bug tracking.
Until then you can still work your way around it:
- The Cut Area Processor should by default be visible in the "Skirt" Override. We'll look into this.
You can however override the default values for it by adding your own Cut Area Processor there. In the Binding manager of the Skirt Override, you can search for "processor", and you'll see the Cut Area Processor there, simply check its box, and it will be added.
- Next bug is, it should only contain two parameters, the "Front cut position" and "Back cut position". We'll get rid of the other two.
- Now that you have the processor there, set both "Actual front cut position" and "Front cut position" to "0", and the "Actual back cut position" and "Back cut position" to the maximal Skirt length you need. If you need all of it, just set "10000" or something there. 10 meters maximal Skirt length should be enough. 🙂
- An additional bug I realized just now: The Skirt actually get one loop less than the value set in "Loop count". Will check on this too.
Okay, moving on:
"For the Overview or optimization to read the Configuration it would be nice to have a small Letterbox with the really used Parameter next to the Modifier.
e.G. in Default Strategy - > Base parameter the EW is a percentage related to the Nozzle Diameter"
What do you mean by the "Letterbox"?
I agree that readability of the parameters, especially the bound ones are a bit hard, and it would be very good to have a design which could imply what they mean. In this way that you wrote: "Extrusion Width is 100% of currently used Nozzle Diameter"
If you have any suggestions, we are open to them.
Expert settings work in a complex way, and we would like to show them through an intuitive user interface. We know it won't work at first, this will be an iterative process to find out how it should be presented.
"and in the Perimeter the EW is a percentage related to the calculated EW. It would be good to see the resulting used Parameter next to this for a better understanding."
Yes, this is something which is in our backlog.
We want to put in the tooltip a hint about where the current parameter is coming from, which Overrides have bindings for it.
Also, in a separate part: Which parameters will be affected by this.
Nice job finding out this by yourself! 🙂
We're also working on how to explain this property mechanism in a user manual the best we can.
It gives high flexibility, but also high complexity.
The GCode scripts will be multi-line input fields, and even will get a separate edit script popup, as you will be able to use properties in the scripts as well.
For now, you can add the GCode script binding, and type text there. If you press enter, you can type multiple lines there.
Just don't put in comments at the end of the lines there yet. Parameters don't have explicit positions, and a comment is considered as a parameter, so if you have a scipt with this:
"G1 E0 ;My comment"
Can result in this:
"G1 ;My comment E0"
The reason for this is that GCode script texts are parsed and the GCode is regenerated from them. This will be the base for the script pre-processing.
For now it doesn't always keep the parameter.
It is a known bug, and we're working on it.
As you can see, the public beta release made us readjust things. This was the goal of releasing an early public beta, so we can still change course in development right before giving a final release.
This is why it does not have a manual yet as well. Needs to adjust with the software, and when it is solidified, then the manual can reflect properly what is in the software.
Regards,
Norbert
- You need to login to have access to uploads.
Quote from Simon BD on 2021-09-20, 07:56Hi Norbert,
thx for this detailed reply. The Workaround for the Skirt is nice to know.
I prefer a simple "Wipe" at the edge of the Buildplate anyway, that i tried to integrate with the GCode start Script.
But in the Moment i am finished writing something in the "GCode start Script" Field the Software crashes with the "unhandled String exception" Error.
With the "Letterbox" i just meant a field next to the modifier that shows the resulting Parameter.
Maybe this Result can also just been shown when you are hovering long enough with the Mouse over the Modifier,
but for readability the first suggestion would be better.
Hi Norbert,
thx for this detailed reply. The Workaround for the Skirt is nice to know.
I prefer a simple "Wipe" at the edge of the Buildplate anyway, that i tried to integrate with the GCode start Script.
But in the Moment i am finished writing something in the "GCode start Script" Field the Software crashes with the "unhandled String exception" Error.
With the "Letterbox" i just meant a field next to the modifier that shows the resulting Parameter.
Maybe this Result can also just been shown when you are hovering long enough with the Mouse over the Modifier,
but for readability the first suggestion would be better.