There are no PC, HIPS, TPU, PC, BVOH materials for makerbot series and the references used point to Generic 175 material GUIDs which is blocked for the makerbot/sketch series.
Since both of them where a different render type (solid versus transparent) the sorting didn't work. Make them both transparent. (Though no changes where made there, see also UM/Scene/Platform -- which is not to be confused with UM/Platform.)
should fix CURA-12188
Previously, this was only checked on 'load all' leading to some weird edge-ish cases where loading an any-color material on a printer that does support it, briefly also made it available on printers that (otherwise would, but) don't -- but only for that session.
part of CURA-12159 (also refer to CURA-11634)
Otherwise you have to wait until the access token refreshes, and are in a weird state in between that time where you _are_ logged in, and we even have the subscription-level, but the permission-list are empty. Now you just have to wait until the permissions return from the server after login, which shouldn't be a problem unless our users are speedrunners.
fixes internal ticket CURA-12076
Changed setting support_infill_density_multiplier_layer_0 to support_infill_density_multiplier_initial_layer.
Added Tough PLA to the MaterialOutputModel.py so it is recognised by Cura.
PP-475
Since the permissions can only change with a token, we only need to
check what the permissions at that moment (instead of every 60 seconds)
Fixes CURA-11870
Otherwise the behavior of the model changes depending on what stack you
have active. I think that this was caused by some code duplication where one
copy of the code was updated but not the other one. This bug was here for quite
some time, but strangely enough, it was never found...
CURA-11854
A new function has been added to the MachineManager class to check for core compatibility in the Factor4 machine. This function ensures the selected core is compatible for use with the Factor4 machine and if not, it displays a warning icon with an appropriate message.
CURA-11851
Although this is rare scenario.This allows for metadata retrieval from the container directly if one is provided, otherwise metadata is fetched using the container_id from the ContainerRegistry. Updated the MaterialNode creation in the VariantNode class(only one scenario) to pass the container.
CURA-11748
