Otherwise it should theoretically default to int, which is wrong. However with some graphics drivers it just seems to result in a failure to compile and concluding with a crash and crescendo.
Fixes#9692.
* Create s3d_std1.0_ABS_D.inst.cfg
* Create s3d_std1.0_ABS_E.inst.cfg
* Create s3d_std1.0_ABS_F.inst.cfg
* Create s3d_std1.0_ASA-X_D.inst.cfg
* Publication des profiles betas 1mm et 1.2mm
J'ai mis les fichiers quality à la bonne setting version pour Cura, j'ai mis l'indication Beta sur les labels de profiles.
* Update s3d_std1.0_ASA-X_E.inst.cfg
Tes
* Update s3d_std1.0_ASA-X_E.inst.cfg
* Correction 'No New Line'
* Update s3d_std1.0_ABS_D.inst.cfg
* Incrementation à setting version 16
* Update s3d_std1.0_ABS_D.inst.cfg
* Ajout Profiles COPA B04, B06 et B08
* Ajout Profiles PLA HR870 B0.4, B0.6 et B0.8
* Modification of profiles for 1.0mm and 1.2mm nozzles
-Renaming the variants to include 'Experimental' in the title
* Modification of Variants files for 1.0mm and 1.2mm nozzles
* Update s3d_std0.6_PLA_HT_C.inst.cfg
* Addition of profiles for polycarbonate for 0.4, 0.6 and 0.8mm nozzles
* Delete rename.sh
Remove rename.sh
* Changes: ASA-X points to ASA-X
Co-authored-by: AButler31 <alexander@emotion-tech.com>
It's also used as the speed at which layer changes are made, so technically it should be kept visible since the setting does indeed affect the g-code.
In practice, it won't affect the print though. Using a reasonable Z hop speed of 10mm/s and the default acceleration of 100mm/s/s, it would take 0.1s to reach the Z hop speed. With the formula for acceleration, 1/2att+vt+c, you can see that it needs 0.5mm to get up to speed, and another 0.5mm to get back to 0. So this speed is only attained with layer heights of more than 1mm which is very unrealistic. For this reason we won't document this in the setting description or its name. The Z hop speed is only used for layer changes because it needs a sensible default for extreme cases, not because it needs to be configurable as such.
But we'll keep it visible to give a less-than-expert user a feeling of control, a placebo effect that they are actually making print quality improvements even if their firmware forbids it from making an actual difference.
FixesUltimaker/CuraEngine#1446.
Some ultimakers tend to choke if you try and send a lot of materials in one go.
Previously we would also always send the materials on the main thread, which would also make
the interface freeze a bit. That should no longer happen.
The implementation of this is not really great, but since this is a hotfix i've opted to change
as little as possible.
CURA-8224
This was done as part of merging the printer. Since the issue is so small
I decided to fix it right away instead of bouncing it back & forth with the
original author
CURA-8221
Not all printers support a firmware configuration here. Wouldn't want to ruin some people's old prints by adding unsupported commands in there, nor change the tried-and-true old parameters people already tested with.
Contributes to issue CURA-8219.
Previously, Arcus, Savitar, and pynest2d were being build with a missing sip flag. This led to Cura
getting `ValueError: PyCapsule_GetPointer called with incorrect name`, if those libraries were not
imported (even if they were unused).
This flag was added in the following commits:
* 83393f989c
* e9e530d963
* bd440b50ad
Since the issue seems to be gone now, the unused imports should be removed from Cura.
All credits go to Rex Dieter for figuring that this missing flag was the issue.
https://src.fedoraproject.org/rpms/libarcus/pull-request/1#request_diff
CURA-8146
