Jump to content
UltiMaker Community of 3D Printing Experts

Cura 2.7 | Beta


SandervG

Recommended Posts

Posted · Cura 2.7 | Beta

I installed on MacOS 10.11.2, and Cura wouldn't start. Double-click, get the warning about downloaded apps, then nothing. Nothing in the security settings on the control panel either. Any attempt to open the application after that does nothing that I can see.

  • Link to post
    Share on other sites

    • Replies 126
    • Created
    • Last Reply

    Top Posters In This Topic

    Posted · Cura 2.7 | Beta

    I have noticed a bug in 2.7

    If I add this to the start code of a machine only the 3 last lines are saved when I start the program again.

    ;Slice at: {day} {date} {time}

    ;Adhesion type: {adhesion_type}

    ;Layer height: {layer_height}

    ;First layer height: {layer_height_0}

    ;Retraction amount: {retraction_amount}

    ;Support enable: {support_enable}

    ;Wall thickness: {wall_thickness}

    ;Speed print: {speed_print}

    ;Top thickness: {top_thickness}

    ;Bed temperature: {material_bed_temperature}

    ;Min infill area: {min_infill_area}

    ;Infill density: {infill_sparse_density}

    ;Print temperature: {material_print_temperature}

    ;Fan Speed: {cool_fan_speed}

    M190 S{material_bed_temperature} ;Sets Bed to correct temperature and wait

    M104 S{material_print_temperature} ;Sets extruder to correct temperature

    M109 S{material_print_temperature} ;Sets extruder to correct temperature and wait

  • Link to post
    Share on other sites

    Posted · Cura 2.7 | Beta

    is it working on 2.6.2 too? my 2.7 crashes always at startup :-(

    i had the same problem on mac but i fixed it by simply clicking show package content and then /contents/MacOS/ and just open Cura. i had to do that one time and now i can open it normally.(i am guessing it should also work similar on windows)

  • Link to post
    Share on other sites

    Posted · Cura 2.7 | Beta
    I'm running it on 10.11.12 and it works OK' date=' but crashes on Exit every time.[/quote']

    We fixed this for the stable release. Thanks for the report.

  • Link to post
    Share on other sites

    Posted · Cura 2.7 | Beta

    I'd like to tell you about the new Doodle3D WiFi-Box plugin we made for Cura. It's now available in the Cura 2.7's new Plugin Browser.

    The plugin uploads the GCODE produced by Cura to a secured server from where your Doodle3D WiFi-Box (if you have one) will fetch the file and prints it on your Ultimaker or other open-source printer. It works for all Ultimaker models except the UM3 but that one is already wireless :-)

    doodle3d-cura.png

    • Like 2
    Link to post
    Share on other sites

    Posted (edited) · Cura 2.7 | Beta

    Works great, no issues!! I wish you can add manual supports function to the software!

    Edited by Guest
  • Link to post
    Share on other sites

    Posted · Cura 2.7 | Beta

    When I try to import Solidwork files using the plugin on Windows 10, the program just hangs... Otherwise, I like the black theme!

    • Like 1
    Link to post
    Share on other sites

    Posted · Cura 2.7 | Beta

    Looks great! But for some odd reason, Cura refuses to import Solidworks files using the Solidworks plugin. Using Solidworks 2016 on a modern Windows 10 laptop.

  • Link to post
    Share on other sites

    Posted · Cura 2.7 | Beta

    Cura 2.7 beta crashes when I add TweakatZ-Plugin.

  • Link to post
    Share on other sites

    Posted · Cura 2.7 | Beta

    I noticed a problem when trying to slice a model only with core 2 (for model, brim and support) on a UM3: the available space is no longer extended to the right after the model is loaded and assigned to core 2. It still works for core 1.

  • Link to post
    Share on other sites

    Posted · Cura 2.7 | Beta

    I have noticed a bug in 2.7

    If I add this to the start code of a machine only the 3 last lines are saved when I start the program again.

    This is a known issue; lines that start with a semi-colon are properly saved into configuration files, but ignored when loading them back in. There's a fix for it in theory, but it is kind of an extreme meassure which may impact other areas of configurations.

  • Link to post
    Share on other sites

    Posted · Cura 2.7 | Beta

     

    I have noticed a bug in 2.7

    If I add this to the start code of a machine only the 3 last lines are saved when I start the program again.

     

    This is a known issue; lines that start with a semi-colon are properly saved into configuration files, but ignored when loading them back in. There's a fix for it in theory, but it is kind of an extreme meassure which may impact other areas of configurations.

     

    Okay, Just I like to have this data in my gcode file. Is there another way?

  • Link to post
    Share on other sites

    Posted · Cura 2.7 | Beta

    Okay, Just I like  to have this data in my gcode file. Is there another way?

     

    Well, you could try prepending each line with a harmless gcode command, such as G21 (which sets the units to MM, which they should already be).

  • Link to post
    Share on other sites

    Posted · Cura 2.7 | Beta

    There's a problem between the two windows5a333e84a21fd_Capturedcran2017-08-2218_55_51.thumb.jpg.61ee89e1c38daf6d40a080e22fbb71d7.jpg

  • Link to post
    Share on other sites

    Posted · Cura 2.7 | Beta

    There's a problem between the two windows5a333e84a21fd_Capturedcran2017-08-2218_55_51.thumb.jpg.61ee89e1c38daf6d40a080e22fbb71d7.jpg

     

    Thx! We will have a look!

  • Link to post
    Share on other sites

    Posted · Cura 2.7 | Beta

    Trying to find a setting that would make cura 2.7 look for a non-existent D:\ drive on load. Every time I launch I have to press continue over 20 times to get the app to run.

    Thanks,

    kj

  • Link to post
    Share on other sites

    Posted · Cura 2.7 | Beta

    Trying to find a setting that would make cura 2.7 look for a non-existent D:\ drive on load.  Every time I launch I have to press continue over 20 times to get the app to run.

    Thanks,

    kj

    Damnit. I thought I fixed that.

    If you disable the WindowsRemovableDrive plugin you shouldn't have the problem anymore.

  • Link to post
    Share on other sites

    Posted · Cura 2.7 | Beta

    No Nallath, 2.7 still has the problem. :( My solution is to actually keep an SD card in the drive that it's complaining about. In my case it is the D drive, which is in fact a removable drive in the multi card reader on the front panel of my computer tower.

  • Link to post
    Share on other sites

    Posted (edited) · Cura 2.7 | Beta

    While I found this same error in current release (not beta) my work around has been to make sure  I do not let it close with "Save to Removable". The odd part is that even when ejecting the drive properly through windows, it does not revert back to "Save to File." It sees the drive going in but not going out.

    Edited by Guest
  • Link to post
    Share on other sites

    Posted (edited) · Cura 2.7 | Beta

    If you disable the WindowsRemovableDrive plugin you shouldn't have the problem anymore.

    When asked people with affected systems to entirely remove the WindowsRemovableDrive plugin folder, the issue still did not go away.

    Using the ProcessActivityView utility (from that webbrowser module thread) I can see that the actual problem is that Cura.exe tries to open files from d:\env and d:\2.6 (ie: remnants from the build-system). I know I suggested this before, but with the utility I now have the prove:

    d-drive.thumb.png.afb4d44d716496ecf7cc3d353e822ff9.png

    Because my D-drive is a standard windows 10 recovery drive, the calls fail silently. If you have an empty removable drive, you can imagine how it is logical for Windows to ask you to insert a disk.

    The recent fix in WindowsRemovableDrive may have silenced some of the messages (though apparently not all), but the actual issue is not with that plugin but with the build system / Py2Exe.

    Edited by Guest
  • Link to post
    Share on other sites

    Posted · Cura 2.7 | Beta

    If its not to late, I would like to make a feature request.

    When importing projects, for me, I just use it for print parameters, and object placements. I only have one printer, and I have custom G-code for beginning and ending.

    When I import a project from a while ago, its possible I made a few changes to my printer by then, and some of the custom settings have been tweaked. Well when the import happens, I have an option to update current printer, or create a new one.

    Well I dont really want a new one because new printers stack up as Printer #1, #2, #3, etc....and I dont really want to update my current one because its been tweaked a bit since the last time I created this old project.

    Instead, an option to possibly "Ignore" printer settings in the project file, and just load object placement and other non printer specific settings?

  • Link to post
    Share on other sites

    Posted · Cura 2.7 | Beta

    Just to add to that, Has the annoying problem of projects importing and creating additional machines been taken care of? It even happens when I bring in a project created from scratch in the current version.

    Or tell it to just use the current machine?

  • Link to post
    Share on other sites

    Posted · Cura 2.7 | Beta

    Instead, an option to possibly "Ignore" printer settings in the project file, and just load object placement and other non printer specific settings?

    If you open a project file, you should get a question if you want to open it as a project, or if you want to import the models. If you don't, please check the "Opening and savinf files" section in the General settings.

  • Link to post
    Share on other sites

    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now
     Share


    • Our picks

      • Here it is. The new UltiMaker S7
        The UltiMaker S7 is built on the success of the UltiMaker S5 and its design decisions were heavily based on feedback from customers.
         
         
        So what’s new?
        The obvious change is the S7’s height. It now includes an integrated Air Manager. This filters the exhaust air of every print and also improves build temperature stability. To further enclose the build chamber the S7 only has one magnetically latched door.
         
        The build stack has also been completely redesigned. A PEI-coated flexible steel build plate makes a big difference to productivity. Not only do you not need tools to pop a printed part off. But we also don’t recommend using or adhesion structures for UltiMaker materials (except PC, because...it’s PC). Along with that, 4 pins and 25 magnets make it easy to replace the flex plate perfectly – even with one hand.
         
        The re-engineered print head has an inductive sensor which reduces noise when probing the build plate. This effectively makes it much harder to not achieve a perfect first layer, improving overall print success. We also reversed the front fan direction (fewer plastic hairs, less maintenance), made the print core door magnets stronger, and add a sensor that helps avoid flooding.
         

         
        The UltiMaker S7 also includes quality of life improvements:
        Reliable bed tilt compensation (no more thumbscrews) 2.4 and 5 GHz Wi-Fi A 1080p camera (mounted higher for a better view) Compatibility with 280+ Marketplace materials Compatibility with S5 project files (no reslicing needed) And a whole lot more  
        Curious to see the S7 in action?
        We’re hosting a free tech demo on February 7.
        It will be live and you can ask any questions to our CTO, Miguel Calvo.
        Register here for the Webinar
          • Like
        • 10 replies
      • UltiMaker Cura 5.3.0-Alpha 🎄 Tree Support Spotlight 🎄
        Are you a fan of tree support, but dislike the removal process and the amount of filament it uses? Then we would like to invite you to try this special release of UltiMaker Cura. Brought to you by our special community contributor @thomasrahm
         
        We generated a special version of Cura 5.2 called 5.3.0 Alpha + Xmas. The only changes we introduced compared to UltiMaker Cura 5.2.1 are those which are needed for the new supports. So keep in mind, this is not a sneak peek for Cura 5.3 (there are some really cool new features coming up) but a spotlight release highlighting this new version of tree supports.  
          • Like
        • 16 replies
      • New here? Get ahead with a free onboarding course
        Hi,
         
        Often getting started is the most difficult part of any process. A good start sets you up for success and saves you time and energy that could be spent elsewhere. That is why we have a onboarding course ready for
        Ultimaker S5 Pro Bundle, Ultimaker S5, Ultimaker S3 Ultimaker 2+ Connect.   
        They're ready for you on the Ultimaker Academy platform. All you need to do to gain access is to register your product to gain free access. 
        Ready? Register your product here in just 60 seconds.
          • Like
        • 14 replies
    ×
    ×
    • Create New...