Jump to content

Msuurmond

Dormant
  • Posts

    192
  • Joined

  • Last visited

Posts posted by Msuurmond

  1. On 6/26/2018 at 11:18 AM, RocketScientistJan said:

    I saw the license of Cura was changed in github for Cura and _most_ of the dependencies were updated. However, _CuraEngine_ still is under AGPL, which to my understanding overwrites the LGPL that is used for _Cura_. 

    No the engine is a separate program so the AGPL doesn't 'infect' programs that use it. For Cura every contributor but 1 agreed on our proposal to move from AGPL to LGPL. Once this was done, we didn't need to change the license of the Engine anymore because plugins work together with Cura and not the engine.

     

  2. 10 hours ago, Croy9000 said:

    I am attaching a file that has the section of my cura.log that captures the moment I click to select my configuration.

     

    This area looks notable (but maybe not related?)

     

    2018-05-25 15:42:53,215 - INFO - [MainThread] cura.Settings.MachineManager._updateQualityWithMaterial [1144]: No available quality types found, setting all qualities to empty (Not Supported).
    2018-05-25 15:42:53,217 - DEBUG - [MainThread] cura.Machines.Models.CustomQualityProfilesDropDownMenuModel._update [15]: Updating CustomQualityProfilesDropDownMenuModel.
    2018-05-25 15:42:53,219 - INFO - [MainThread] cura.Machines.QualityManager.getQualityChangesGroups [186]: Cannot find node for machine def [ultimaker3] in QualityChanges lookup table

    cura.log

    Could you share your whole config folder as a zip-file? Than we can use that to reproduce it on our development machines.

  3. 1 minute ago, XYZDesignPro said:

     

    Thanks for the feedback.  I have been playing with the Max Resolution setting, and sometimes it depends on the shape of the part.  Sometimes .01 (apparently the default in 3.2.1) works best, but other times, in 3.3.1, I have gone as far as .005 to get the desired results.

     

    Whar's the down side to setting it to .005?

    That Cura has to work harder to show (render) the model and gets more laggy and that you might have tiny lines of GCode that might cause buffer-underruns in you printer. This might be the case when the line of GCode can be executed faster than a new line can be put into to buffer.

  4. On 5/1/2018 at 8:07 PM, XYZDesignPro said:

    I don't have an account at Github to post to.  Perhaps someone on the forum with the Ultimaker team will see the conversation we have exchanged and jump in here. This is definitely a bug in this new release.  I think I still have 3.3 beta on my laptop.  I'm going to see if the same problem is in the beta.  I'll just continue to use 3.2.1 for now.

     

    Thanks for you help just the same . . .

    We investigated this issue and it was indeed the maximum resolution setting. To make it work please change the 'Maximum Resolution' to 0.01 and than it will work. We use the default of 0.04 which helps on less powerfull hardware and is prevents buffer underruns on the printer.

  5. @Drdave That is the correct content! I used it to run Cura 3.3.1 and it works here (on my MacBook). I also see you have some plugins installed, it might be that your Octoprint plugin needs an update.

    To get Cura running again you could try to delete the folder OctoPrintPlugin:

    1948183739_ScreenShot2018-05-02at07_49_46.thumb.png.b74e62217608aa793ceccf0e9ad179fb.png

     

    When Cura runs again you can redownload it from the plugin browser.

  6. 15 hours ago, Drdave said:

    Elle 

    Sorry, I removed the 3.3 folders as you suggested then reran the install and still the IDENTICAL issue.  No profiles no printers

    I get it that 3D is designed for techies but most of us aren't and this has been going on since late version 1.x but surely since 2.x

    The install asks to remove the older version if you say NO then it freaks out and refuses to install properly.

    I can't won't remove the older version honestly because I don't trust the new version as has been demonstrated by still another not ready for the release version

    I tried to upload the zipped folder the software won't allow it be included help me to help you, please

    Dr. Dave

    We can only help you further if you can give us the complete config folder. With that we can extract it on our development machines and create the exact same situation as you have. If anything goes wrong we can than see it and fix it.

  7. 1 hour ago, ninjapigeon said:

    So, fixed this myself.

     

    Seems the programmers on 3.3 took an assumption that didn't fit my profile. I have a smallish SSD to run Windows, and launch my apps from a RAID1 HDD setup.

    After 3.3 released today, and i removed every config/install/appData file for my previous Cura installs, i had the same error.

    This time the log said something along the lines of "file not found on expected drive".

    Uninstall it all again, reinstall on the default C: drive.. lo and behold it works, and i'm printing now from 3.3.

    :(

     

    TL;DR - fixed, only if i installed on my default C: drive. Lame Ultimaker, lame.

    Yes we just found out of this bug after the release and are working on a fix. Sorry!

    • Like 1
×
×
  • Create New...