Jump to content
Ultimaker Community of 3D Printing Experts

ghostkeeper

Team Ultimaker
  • Content Count

    152
  • Joined

  • Last visited

  • Days Won

    2

ghostkeeper last won the day on March 7 2018

ghostkeeper had the most liked content!

Community Reputation

72 Excellent

1 Follower

About ghostkeeper

  • Birthday 01/01/2015

Personal Information

  • Country
    NL

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Changing support settings for an object will change how that object is supported. So if you change the Support X/Y/Z Distance for a custom support block, you're changing how that block would be supported but the block itself isn't supported so it has no effect. The block causes the model to be supported. The support X/Y/Z distance can't be changed for just parts of your model. I'm sorry. You'd need to change it everywhere or nowhere, or indeed model the support yourself in CAD.
  2. You need to look at the following four settings: Support X/Y Distance Support Z Distance Support Distance Priority (normal support only, not Tree support) Support Min X/Y Distance (normal support only, Z overrides X/Y only) I would expect that reducing the X/Y Distance has a lot of effect for you, but don't reduce it to below 0.3mm or so because then your support will stay too close to your model sideways.
  3. ghostkeeper

    Introducing Ultimaker Cura 3.5 | Beta

    We did some things to improve that, which should be released in 4.0.
  4. ghostkeeper

    Introducing Ultimaker Cura 3.6 | Beta

    PETG and HIPS are not supported for the Ultimaker printers. You can download that profile, and it'll show up for some other printers, but we disabled it for the Ultimaker printers.
  5. ghostkeeper

    Introducing Ultimaker Cura 3.5 | Beta

    I did a performance test on that 3.5 file using Callgrind and got this result: http://dulek.net/work/3.5-beta-callgrind.out.3886 This seems to point to this change: https://github.com/Ultimaker/CuraEngine/pull/791 We'll continue discussion there.
  6. ghostkeeper

    Introducing Ultimaker Cura 3.5 | Beta

    We expect that 1 or 2 lines of code need to change for most plug-ins. It's not much, but the developer needs to figure out the stuff that is broken, test it, package it and re-submit it which could be an hour or two of work. Also, some people have loads of plug-ins up there which could be quite a significant amount of work to do for all.
  7. ghostkeeper

    Introducing Ultimaker Cura 3.5 | Beta

    A more complete list of features is in the great blog post, written up by my friend Matt: https://ultimaker.com/en/blog/52715-whats-new-in-ultimaker-cura-35-beta An even more complete list (that includes the most significant bug fixes as well) is in Cura itself. You can read that list from Cura's source code here: https://github.com/Ultimaker/Cura/blob/master/plugins/ChangeLogPlugin/ChangeLog.txt
  8. ghostkeeper

    Cura 3.4.1 crash problem

    What's that error traceback that you see in the first textbox?
  9. ghostkeeper

    dual extruder / chimera settings

    There can only be one bed temperature. Bed temperature is a global setting, so shared between extruders. Cura indicates these sort of settings by displaying a chain link icon next to the setting. Each extruder has its own defaults for most settings. Like the print temperature and such, these can be different for each extruder. That is a problem for Chimaera-style nozzles because Cura will try to set the temperatures for both extruders to different temperatures but on your nozzle only one of them can win. There is no real solution for that yet (and no priority from Ultimaker to make one) but you can work around it by removing some temperature commands using the Search-and-Replace post-processing script. Some default settings that are global can still be set by the material profiles per extruder. This is kind of a complex system, but necessary for things like the bed temperature. For these, there is a resolve function that Cura defines per setting. For instance, for the heated bed temperature, Cura chooses the highest of the temperatures of all nozzles. Make sure you check "Enable Prime Blob" or use a skirt/brim/raft for the extruders that need priming at the beginning of a print. Use a prime tower if you need them primed after each extruder switch (strongly advisable for Chimaera!) Don't bother with the ooze shield in my opinion. Use a prime tower for your Chimaera printer though.
  10. ghostkeeper

    cura not showing menu items

    Did you try updating your graphics drivers? Cura indicates in the log that you support OpenGL 3.3, which is pretty old (released in 2010). They are at version 4.7 right now.
  11. ghostkeeper

    cura not showing menu items

    That is the correct log file ? Only there is nothing in the log that indicates that Cura finds something wrong on your computer. Technical background: I suspect, also from your pictures, that it's some redrawing bug in Qt. We aren't seeing it on our computers though. I can't find that it has been reported on QtBugs anywhere either, so the chance that it'll get fixed in Qt 5.10 is small. In the next Cura release we've updated to a newer version of Cura's GUI framework, Qt. There is some chance that that fixes things but don't keep your hope up. I looked through the Cura code that generates these comboboxes and the application menu but there is nothing to indicate that the opacity of these menus get set to 0% or anything... ?
  12. ghostkeeper

    cura not showing menu items

    That log file is from September 2017. At some point we moved the log file into the folder of the specific version you're using. Could you look into the /3.4 folder for another log file? Sorry for the confusion.
  13. ghostkeeper

    problem with print size

    Cura stuff around your print and forbids you from slicing if that extra stuff would move outside the build volume (since that could damage your printer). Some of the stuff that's added around your print includes: Brim Skirt Raft Avoid Objects when Travelling Draft Shield With default settings, setting the brim size to 0 and disabling Avoid Objects When Travelling will allow you to print stuff using the maximum volume of your printer.
  14. ghostkeeper

    cura not showing menu items

    We haven't seen this on our testing computers. That makes it a bit hard to fix the problem. Maybe there is something in your Cura log? Could you post that here?
  15. ghostkeeper

    Cura 3.4.1 will not start

    Looking at the log file again. I fixed a broken colour that I found because of that log, so thanks already ? So in the log it appears to be crashing right after it initializes the shaders and right before or during initialization of the main window. The most likely culprit is these lines: 2018-07-22 05:06:55,824 - WARNING - [MainThread] UM.Qt.QtApplication.__onQmlWarning [301]: file:///C:/Program Files/Ultimaker Cura 3.4/resources/qml/Topbar.qml:19: TypeError: Cannot read property 'stageId' of null 2018-07-22 05:06:55,826 - WARNING - [MainThread] UM.Qt.QtApplication.__onQmlWarning [301]: file:///C:/Program Files/Ultimaker Cura 3.4/resources/qml/Topbar.qml:104: TypeError: Cannot read property 'stageId' of null 2018-07-22 05:06:55,829 - WARNING - [MainThread] UM.Qt.QtApplication.__onQmlWarning [301]: file:///C:/Program Files/Ultimaker Cura 3.4/resources/qml/Topbar.qml:175: TypeError: Cannot read property 'stageId' of null 2018-07-22 05:06:55,831 - WARNING - [MainThread] UM.Qt.QtApplication.__onQmlWarning [301]: file:///C:/Program Files/Ultimaker Cura 3.4/resources/qml/Cura.qml:433: TypeError: Cannot read property 'mainComponent' of null 2018-07-22 05:06:55,834 - WARNING - [MainThread] UM.Qt.QtApplication.__onQmlWarning [301]: file:///C:/Program Files/Ultimaker Cura 3.4/resources/qml/Cura.qml:427: TypeError: Cannot read property 'mainComponent' of null 2018-07-22 05:06:55,836 - WARNING - [MainThread] UM.Qt.QtApplication.__onQmlWarning [301]: file:///C:/Program Files/Ultimaker Cura 3.4/resources/qml/Cura.qml:465: TypeError: Cannot read property 'sidebarComponent' of null 2018-07-22 05:06:55,839 - WARNING - [MainThread] UM.Qt.QtApplication.__onQmlWarning [301]: file:///C:/Program Files/Ultimaker Cura 3.4/resources/qml/Cura.qml:497: TypeError: Cannot read property 'sidebarComponent' of null From this it appears that `activeStage` is null at that time which is weird to me. Also strange is this line: 2018-07-22 05:06:37,560 - INFO - [MainThread] UM.VersionUpgradeManager._getUpgradeTasks [272]: Config file [.\cura.cfg] is of version [6000000], which is different from the defined version [2000000], no upgrade task for it from type [preferences]. There it looks like someone mixed up two of the version numbers that we have in Cura.
×

Important Information

Welcome to the Ultimaker Community of 3D printing experts. Visit the following links to read more about our Terms of Use or our Privacy Policy. Thank you!