DaHai8

just a wag, try: "material_print_temperature_layer_0" ...from the fdmprinter.def.json file...

I tried the Mac OS 15.x link on Windows/Chrome browser and it worked. Can you try a different browser under MacOS?

I played around with the Smooth Variable Layer Height (SVLH) feature. While it may seem off-topic on the Cura forum, I'd like to state some of my impressions of it here for the Cura developers - so they can do it better: First, its a decent first cut. It does what it says it will do with little effort on by the user (or the app ) But, in my opinion (and I might have missed something), it falls way short in a 'good' implementation: There is no analysis by the app on what parts would benefit from "SVLH", nor any suggestions by the app on what an appropriate layer height would be for any given section. There is no feedback on what you are 'smoothing' the layer height by. It's just a curve to the side with no numbers to tell you the new layer heights. Smoothing is done across the entire X/Y plane. If you object has 'towers' (or you have two objects), one curved and one straight, the smoothing is done on both, regardless. I'll shut up now.

Caveat Emptor - its beta: https://github.com/prusa3d/Slic3r/releases

Print Sequence is hidden if you have two extruders. You can get more information on what conditions are needed to unhide a specific setting by hovering over the 'i' icon next to that setting in the 'Settings Visibility' window. Hope this helps.

That's correct. You no longer need to press the first layer into the bed if you use something like PrintBite. It naturally sticks without special effort and comes off just as easy after the bed cools.

This is also known as 'VariSlice' from Autodesk. Nice to see a slicer with a version of that, but a bit disappointed that it must be set manually and not automatically detected and generated by the slicer.

PrintBite - I never print without it.

Cura 2.4.0 has a 'Save Project' feature that saves all the information about the model: stl/obj, printer, print settings, etc. Also, there are freeware and web based gcode viewers available so you can see what the model was and how it will print. Hope this helps.

Hey, I'm just making this stuff up as I go. That's just how I'd write it/understand it.

True. If it's a dome or a peak (or open) you can get a good finish with just 1 layer, otherwise it's a mess.

DId you try Special Modes -> Spiralize Outer Contour ? The yellow areas you are indicating is Cura setting up the top/bottom layer thicknesses on shallow overhangs. And the defects you are seeing are probably not heat related, but rather the 'jiggling' Cura does to set up these 'support' layers. If you don't wish use Spiralize Outer Contour. If you wish to not use that feature, set your Top/Bottom thickness to 1 layer height.

Your build area is 215x215 Your cube size is 24.3x24.3 Assuming your cube is centered on the build area, then the bottom left point of the cube would be at 95.35x, 95.35y Specifying X=0 and Y=100 puts that coordinate just 4.65mm north (Y) of the bottom left corner of your cube, but on the X axis. I believe Cura is favoring corners for Z-Seam alignments to minimize visibility, so the lower left corner of your cube is closest. Did you try 0x, 215y for the upper left corner? This would be the top left corner of your build area. That should put the z-seam at the top-left corner of your cube. Also try: 95x, 120y That will place your z-seam coordinate right next to the cubes upper-left corner. You cube is define as (from lower-left corner going clockwise): (95.35,95.35), (95.35,119.65),(119.65,119.65),(119.65,95.35) For more accurate z-seam placements, try these corrdinates: 95x, 95y = lower left corner. 95x, 120y = upper left corner 120x, 120y = upper right corner 120x, 95y = lower right corner Distance = sqrt((x2-x1)^2 * (y2-y1)^2)) Cura is finding the closet point (distance) to your specified z-seam location and if your points are way far away, it can give (seemingly) inconsistent results.

I have the same problem: https://ultimaker.com/en/community/38971-cant-run-cura-240?page=1&sort=#reply-172850 The only suggestion I've received so far is to rename the drive letter of the SD Card. I'm not about to mess with my system configuration for broken software. But I have not found any other solution. So, for now, I'm using S3D...

I sent you a personal message with my email address in it. I'd be happy to take a look at your model if you like.

That is strange. I tried it with Cura 15.x and got logical results: 5min for 30mm/s and 11mins for 10mm/s Unless the 'Cool -> Minimum Layer' time is set to something really large (or small), I can't explain it other than there is something wrong with Lulzbot's version of Cura.

Unless its really large, you can post it inside a message here using the 'code' tags from the menu >

There is: Advanced -> Shell -> Z Seam Alignment = Back Not sure where 'back' is, I'm assuming its maximum positive Y position. You may need to set Visibility to ALL in Preferences -> Settings. Hope this helps

Use the Solid Inspector plugin in Sketchup to ensure there are no manifold issues.

Ok. The only thing I can figure is that Cura is making some Registry Change on the first launch of it. Is there a list somewhere of all the Windows Registry Entries Cura makes/changes on the install/first launch? The reason I say this is because: After the first run, I removed the AppData/cura folder and it still fails with the dialog box on the next run After installing Cura, but without running it, I copied the entire \Program Files\Cura folder (and subfolders) to a different location. Than ran Cura the first time, exited, and then replaced the \Program Files\Cura 2.4 contents with the virgin copy. Still failed on second launch So its nothing to do with the \AppData\cura folder or changes made in \Program Files\Cura 2.4 folder, so I has to be in the Registry. @nallath, can you point me in the direction of these registry entries? Thanks!

That .dll is part of "Visual C++ Redistributable for Visual Studio 2015" and was not installed as part of that update (I Googled it). Just do a search on the interwebs for that dll and you'll find instructions on how to fix it. Apparently Cura is not the only app that uses it, can't find it, and fails.

It all depends on what you're looking for in a Slicer. S3D gives you factory files, multiple processes by layer and/or object, direct printer control, custom support placement, and absolute tool head tracking in preview mode. Cura gives you fine detailed control over very many printing properties, like jerk, acceleration, speeds, etc. - most on a object by object basis. Its more flexible in setting up new printers and properties and its open to adding new functionality via plugins. Cura is open source and frequently updated. S3D is proprietary and not updated as quickly. I have both. I love them both. But for different reasons. The gaps between them are closing and it will be interesting to see where they end up by the end of this year.

I reinstalled Cura 2.3.0 beta along with wiping out the "C:\Users\[MyName]\AppData\Local" folder and it started with no issues. Doing the same routine with 2.4.0 give me those "There is No Disk..." dialogs. I'm gonna dig around some more.... P.S. Keep forgetting to mention: The first launch of Cura 2.4.0 after install goes without any issues. It's only after closing it and launching it again that those pesky dialogs appear.

Why does Cura try to open it in the first place? I renamed the drive from "USB Drive" to just "Goop" and it still throws that error box. I don't know of any way to change the Drive Letter short of going into the Hardware config and modifying it there - I'd prefer not to do that. Also, Cura 2.3.x never did this... P.S. More Info: After getting Cura started, I noticed that its 'Save' button is defaulting to 'Save to Removeable Drive'. I believe in previous versions it would default to the last drive and path you saved your gcode to. It doesn't appear to be doing that anymore. I can save the gcode to my HD and then exit and restart Cura, but it goes right back to 'Save to Removeable Drive'. The only way I've found to get around this is to a) put an SD card in the drive before booting Cura, or b) unplugging my SD Card reader. A workaround for now, but not a solution.

Correction: Clicking on 'Cancel' 158 times finally gets Cura up and running. When closing Cura, I get the same dialog box and must click on 'Cancel' 2x to quit. Here's that log file: 2017-02-22 13:34:19,783 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin FileLogger2017-02-22 13:34:20,671 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin GCodeProfileReader2017-02-22 13:34:21,567 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin GCodeWriter2017-02-22 13:34:22,432 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin ImageReader2017-02-22 13:34:23,209 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin LayerView2017-02-22 13:34:24,320 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin LegacyProfileReader2017-02-22 13:34:25,209 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin LocalFileOutputDevice2017-02-22 13:34:26,104 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin MachineSettingsAction2017-02-22 13:34:26,896 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin PerObjectSettingsTool2017-02-22 13:34:27,745 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin PostProcessingPlugin2017-02-22 13:34:28,664 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin RemovableDriveOutputDevice2017-02-22 13:34:29,593 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin SliceInfoPlugin2017-02-22 13:34:30,497 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin SolidView2017-02-22 13:34:31,441 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin CameraTool2017-02-22 13:34:32,474 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin MirrorTool2017-02-22 13:34:33,690 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin RotateTool2017-02-22 13:34:34,593 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin ScaleTool2017-02-22 13:34:35,521 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin SelectionTool2017-02-22 13:34:36,474 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin TranslateTool2017-02-22 13:34:37,393 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin UltimakerMachineActions2017-02-22 13:34:38,521 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin UM3NetworkPrinting2017-02-22 13:34:38,666 - INFO - UpdateChecker.UpdateChecker.run [40]: Checking for new version of cura2017-02-22 13:34:39,602 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin UpdateChecker2017-02-22 13:34:40,545 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin USBPrinting2017-02-22 13:34:41,530 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin VersionUpgrade21to222017-02-22 13:34:42,730 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin VersionUpgrade22to242017-02-22 13:34:43,794 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin SimpleView2017-02-22 13:34:44,834 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin WireframeView2017-02-22 13:34:45,754 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin X3DReader2017-02-22 13:34:46,754 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin XmlMaterialProfile2017-02-22 13:34:47,635 - INFO - UM.PluginRegistry.loadPlugin [100]: Loaded plugin XRayView2017-02-22 13:34:48,619 - INFO - UM.Qt.QtApplication.__init__ [90]: Command line arguments: {'disable-textures': False, 'file': [], 'external-backend': False}2017-02-22 13:34:49,595 - INFO - UM.VersionUpgradeManager.upgrade [100]: Looking for old configuration files to upgrade.2017-02-22 13:34:50,515 - DEBUG - UM.Backend.Backend._logSocketState [167]: Socket state changed to Listening2017-02-22 13:34:51,476 - INFO - UM.Backend.Backend.startEngine [71]: Started engine process: C:\Program Files\Cura 2.4\CuraEngine.exe2017-02-22 13:34:52,452 - DEBUG - UM.Backend.Backend._backendLog [89]: [backend] Calling engine with: ['C:\\Program Files\\Cura 2.4\\CuraEngine.exe', 'connect', '127.0.0.1:49674', '-j', 'C:\\Program Files\\Cura 2.4\\resources\\definitions\\fdmprinter.def.json', '']2017-02-22 13:34:54,347 - DEBUG - UM.Backend.Backend._backendLog [89]: [backend] 2017-02-22 13:34:54,747 - DEBUG - UM.Backend.Backend._logSocketState [171]: Socket state changed to Connected2017-02-22 13:34:56,027 - DEBUG - UM.Backend.Backend._backendLog [89]: [backend] Cura_SteamEngine version DEV2017-02-22 13:34:56,475 - DEBUG - UM.Backend.Backend._onSocketStateChanged [161]: Backend connected on port 496742017-02-22 13:34:56,589 - DEBUG - MachineSettingsAction.MachineSettingsAction._onContainerAdded [69]: Not attaching MachineSettingsAction to ultimaker3; Multi-extrusion printers are not supported2017-02-22 13:34:57,382 - DEBUG - UM.Backend.Backend._backendLog [89]: [backend] Copyright © 2014 David Braam2017-02-22 13:34:58,314 - DEBUG - UM.Backend.Backend._backendLog [89]: [backend] 2017-02-22 13:34:58,554 - DEBUG - MachineSettingsAction.MachineSettingsAction._onContainerAdded [69]: Not attaching MachineSettingsAction to ultimaker_original_dual; Multi-extrusion printers are not supported2017-02-22 13:34:58,953 - DEBUG - MachineSettingsAction.MachineSettingsAction._onContainerAdded [69]: Not attaching MachineSettingsAction to punchtec_connect_xl; Multi-extrusion printers are not supported2017-02-22 13:34:59,183 - DEBUG - MachineSettingsAction.MachineSettingsAction._onContainerAdded [69]: Not attaching MachineSettingsAction to ord; Multi-extrusion printers are not supported2017-02-22 13:34:59,405 - DEBUG - UM.Backend.Backend._backendLog [89]: [backend] This program is free software: you can redistribute it and/or modify2017-02-22 13:34:59,557 - DEBUG - MachineSettingsAction.MachineSettingsAction._onContainerAdded [69]: Not attaching MachineSettingsAction to ultimaker3_extended; Multi-extrusion printers are not supported2017-02-22 13:35:00,588 - DEBUG - UM.Backend.Backend._backendLog [89]: [backend] it under the terms of the GNU Affero General Public License as published by2017-02-22 13:35:01,676 - DEBUG - UM.Backend.Backend._backendLog [89]: [backend] the Free Software Foundation, either version 3 of the License, or2017-02-22 13:35:02,632 - DEBUG - UM.Backend.Backend._backendLog [89]: [backend] (at your option) any later version.2017-02-22 13:35:03,568 - DEBUG - UM.Backend.Backend._backendLog [89]: [backend] 2017-02-22 13:35:04,521 - DEBUG - UM.Backend.Backend._backendLog [89]: [backend] This program is distributed in the hope that it will be useful,2017-02-22 13:35:05,559 - DEBUG - UM.Backend.Backend._backendLog [89]: [backend] but WITHOUT ANY WARRANTY; without even the implied warranty of2017-02-22 13:35:06,552 - DEBUG - UM.Backend.Backend._backendLog [89]: [backend] MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the2017-02-22 13:35:07,469 - DEBUG - UM.Backend.Backend._backendLog [89]: [backend] GNU Affero General Public License for more details.2017-02-22 13:35:08,529 - DEBUG - UM.Backend.Backend._backendLog [89]: [backend] 2017-02-22 13:35:09,496 - DEBUG - UM.Backend.Backend._backendLog [89]: [backend] You should have received a copy of the GNU Affero General Public License2017-02-22 13:35:10,490 - DEBUG - UM.Backend.Backend._backendLog [89]: [backend] along with this program. If not, see .2017-02-22 13:35:11,468 - DEBUG - UM.Controller.setActiveView [81]: Setting active view to SolidView2017-02-22 13:35:12,468 - WARNING - cura.Settings.ExtruderManager.getMachineExtruders [375]: Tried to get the extruder trains for machine Prusa i3 Mk2, which doesn't exist.2017-02-22 13:35:13,402 - WARNING - cura.Settings.ExtruderManager.getMachineExtruders [375]: Tried to get the extruder trains for machine Prusa i3 Mk2, which doesn't exist.2017-02-22 13:35:15,707 - DEBUG - UM.Mesh.MeshData.calculateNormalsFromVertices [379]: Calculating normals took 0.006003618240356445 seconds2017-02-22 13:35:15,709 - DEBUG - STLReader.STLReader.read [63]: Loaded a mesh with 8052 vertices2017-02-22 13:35:16,274 - DEBUG - UM.Qt.Bindings.Theme.load [126]: Loading theme file: C:\Program Files\Cura 2.4\resources\themes\cura\theme.json2017-02-22 13:35:17,427 - DEBUG - UM.Qt.Bindings.Theme.load [186]: Loaded theme C:\Program Files\Cura 2.4\resources\themes\cura2017-02-22 13:35:18,073 - DEBUG - UM3NetworkPrinting.DiscoverUM3Action._createAdditionalComponentsView [134]: Creating additional ui components for UM3.2017-02-22 13:35:19,735 - DEBUG - UM.Mesh.MeshData.approximateConvexHull [347]: approximateConvexHull(target_count=1024) Calculating 3D convex hull took 0.004003047943115234 seconds. 36 input vertices. 36 output vertices.2017-02-22 13:35:19,742 - DEBUG - CuraEngineBackend.CuraEngineBackend.slice [152]: Starting slice job...2017-02-22 13:35:21,503 - DEBUG - UM.Qt.GL.QtOpenGL.__init__ [57]: Initialized OpenGL subsystems.2017-02-22 13:35:22,824 - DEBUG - UM.Qt.GL.QtOpenGL.__init__ [58]: OpenGL Version: 4.0.0 - Build 10.18.10.43582017-02-22 13:35:24,327 - DEBUG - UM.Qt.GL.QtOpenGL.__init__ [59]: OpenGL Vendor: Intel2017-02-22 13:35:25,641 - DEBUG - UM.Qt.GL.QtOpenGL.__init__ [60]: OpenGL Renderer: Intel® HD Graphics 40002017-02-22 13:35:35,768 - DEBUG - AutoSave.AutoSave._onTimeout [48]: Autosaving preferences, instances and profiles2017-02-22 13:37:34,415 - DEBUG - UM.Qt.QtApplication.windowClosed [198]: Shutting down cura2017-02-22 13:37:34,730 - DEBUG - CuraEngineBackend.CuraEngineBackend._terminate [197]: Attempting to kill the engine process2017-02-22 13:37:34,731 - DEBUG - CuraEngineBackend.CuraEngineBackend._terminate [203]: Killing engine process2017-02-22 13:37:34,735 - DEBUG - CuraEngineBackend.CuraEngineBackend._terminate [206]: Engine process is killed. Received return code 1