-
Posts
675 -
Joined
-
Last visited
-
Days Won
18
Content Type
Forums
Events
3D Prints
Everything posted by Cuq
-
-
On my windows post I still have this problem with the new plugin: CuraEngineGradualFlow. Cura crashes and I have in the messages : CuraEngineGradualFlow\GradualFlowPlugin.py", line 41, in usePlugin return any([extr.getProperty(f"{constants.settings_prefix}_gradual_flow_enabled", "value") for extr in machine_manager.activeMachine.extruderList if extr.hasProperty(f"{constants.settings_prefix}_gradual_flow_enabled", "value")]) AttributeError: 'NoneType' object has no attribute 'extruderList' Am I the only one with this problem?
-
Could be an issue regarding the browser you use , With Google Chrome or Edge I don't have this result.
-
Yes a lot of old links have now switch to support.makerbot.com and old support.ultimaker.com redirects you to a salesforce page. The new updated link until the next mergers and acquisitions in 3D printing : https://support.makerbot.com/s/topic/0TO5b000000Q4w3GAC/cura-print-settings
-
Initial Layer Line Width : 150 % ???
-
Same problem as in this Github discussion : https://github.com/Ultimaker/Cura/issues/15056#issuecomment-1689206800 Should be partially solved in version 5.5. I say partial, because in this case, if the print order is better for the print, the wall print order is no longer respected, which will certainly lead to other comments. 5.X -> 5.4 5.5 or use the executable mentioned in the post
-
Would be also nice to update the Change_log.txt file ( Although I already have an idea about the update 😉 )
-
https://github.com/Ultimaker/Cura/releases/tag/nightly
-
@Gero: Read the first line of the @MariMakes answer : "There will indeed be an update on the wall ordering, one contributed by the community. You can find it here." The answer is here 😁 For the more adventurous, version 5.5 Alpha also solves this issue.
-
BreadthFirstIterator You mean DepthFirstIterator ? Is you use DepthFirstIterator you must check if the node "isSliceable" Me = CuraApplication.getInstance() for node in DepthFirstIterator(Me.getController().getScene().getRoot()): if node.callDecoration("isSliceable"): node.setPosition(Vector(position.x(), position.y(), position.z())) Note : setPosition should only "Move" the node so if you also copy there is something else in your code
-
-
Question Batch slicing stl files. Batch generating gcode files
Cuq replied to Murmur's topic in UltiMaker Cura
Yes in 5.X it's now : .\share\cura\resources Note form the CuraEngine Help message : In order to load machine definitions from custom locations, you need to create the environment variable CURA_ENGINE_SEARCH_PATH, which should contain all search paths delimited by a (semi-)colon. Other topic on this subject : -
Cura places supports in the wrong places that are not marked red
Cuq replied to Skas's topic in UltiMaker Cura
In Cura a support start from the builtplate to the supported area. So as you have define a support Expansion the support start from the Builtplate . Fix the support horizontal expansion value to 0 to get the right result : -
I don't think it's possible to do that with the standard functions of Cura. But you can use Ctrl+C / Ctrl+V to copy the Modifier. One issue the new instance is not linked with the Model so if you move the model the Modifer doesn't move. Via a plugin it would be possible, but the number of user would be limited on my point of view and as I don't use this function so many times this is not the think I will works on. For the previous release they where a plugin : SmartSlice ( Not free) which was supposed to calculate and define automaticaly different infill to enforce the strength of the part. But not sure it have been a lot of success in a opensource/free world. Anyway it doesn't seems to be still available.
-
Cura 5.4.0 not incorporating material print bed and extruder temps into gcode
Cuq replied to 13337's topic in UltiMaker Cura
There is many post concerning this issue. As soon as you define a temperature in your profile, this value overwrite the material datas. So if you are using a non standard profile most of the times you cuts the link between the material temperature and the parameter value of you current parameter value. To solved this problem you must install the Material Settings plugin from @fieldOfView (https://marketplace.ultimaker.com/app/cura/plugins/fieldofview/MaterialSettingsPlugin) and then you will have the possibility to access to a right clic button function (Use value from material) on the printing temperature and bed temperature to force the value from the material datas -
Custom Profile does not use Material Print Settings
Cuq replied to cygnyet's topic in UltiMaker Cura
You must use the material settings plugin to set the parameters to the material values (right clic on the parameter to access to the setting function) -
Error: there are no compatible profiles with this extruder configuration
Cuq replied to KoenP's topic in UltiMaker Cura
It's not only for the Ender 5 but for every Creality machine. In the Extruder definition for these machines there is no ASA configuration defined in standard. You can find some configuration for PLA / ABS/ PETG / TPU but No ASA , ToughPLA, PC, Nylon etc. If you want to use ASA definition you must add some Quality configuration for this material. base_0.4_ASA_standard.inst.cfg.zip -
Error: there are no compatible profiles with this extruder configuration
Cuq replied to KoenP's topic in UltiMaker Cura
Strange , When I load this material in Cura I have something totaly Different , The Default Color is Green and the Filament diameter 2.85 ( That's why why it shouldn't be compatible with your Ender-5 extruder) . But You have a different configuration, With a price , the name itself is different. Is it an old material configuration file ? Normaly you should event not see this material in the list if your Ender 5 is activated. -
Not a issue on the release, but a on the hardware. The graphics card is not compatible in the 5.4 case . Have you change your hardware ? or change the option of graphic compatibility ?
-
utiliser une imprimante générique , voir post :