Jump to content

Crua 3.0.3 loads, displays drawing platform, then quits.


lahines100

Recommended Posts

Posted · Crua 3.0.3 loads, displays drawing platform, then quits.

I am trying to use Cura 3.0.3 on a Windows 7 platform. When Cura is selected, it goes through setup,loading software and machines. When I select "Other" and then select "FABtotum" the drawing platform loads, waits a couple of seconds, then the program quits. I have a fast video processor and 32 GB of computer memory.

  • Link to post
    Share on other sites

    Posted · Crua 3.0.3 loads, displays drawing platform, then quits.

    OK, the video chip is not the issue. Usually people seem to have an issue with the intel video chips.

    Definitely would seem to not be a VRAM issue. Just for kicks, have you tried to select a 'standard' machine to see if there is an issue with your selection of printers?

  • Link to post
    Share on other sites

    Posted · Crua 3.0.3 loads, displays drawing platform, then quits.

    one idea that i read here recently...: take a look at the log file: "%APPDATA%\cura\3.0\cura.log", if it reports a problem in "grid.shader", try to replace the file in the program folder (....Cura\resources\shaders) with the newer version from the GitHub repository: https://github.com/Ultimaker/Cura/tree/master/resources/shaders

  • Link to post
    Share on other sites

    Posted · Crua 3.0.3 loads, displays drawing platform, then quits.

    Thanks for your help. I have copied the last few lines from the log file with latest grid shader installed (still fails):

    2017-10-22 01:32:18,399 - INFO - FirmwareUpdateChecker.FirmwareUpdateChecker._onContainerAdded [38]: You have a 'FABtotum Personal Fabricator' in printer list. Let's check the firmware!

    2017-10-22 01:32:18,515 - WARNING - cura.Settings.ContainerManager.getContainerMetaDataEntry [184]: Could not get metadata of container because it was not found.

    2017-10-22 01:32:18,718 - WARNING - UM.Qt.Bindings.Theme.getIcon [109]: No icon tool_icon.svg defined in Theme

    2017-10-22 01:32:18,753 - WARNING - UM.Qt.Bindings.Theme.getIcon [109]: No icon tool_icon.svg defined in Theme

    2017-10-22 01:32:18,888 - DEBUG - UM.Mesh.MeshData.calculateNormalsFromVertices [425]: Calculating normals took 0.0009999275207519531 seconds

    2017-10-22 01:32:18,958 - DEBUG - STLReader.STLReader.read [79]: Loaded a mesh with 21378 vertices

    2017-10-22 01:32:19,334 - WARNING - cura.Settings.ContainerManager.getContainerMetaDataEntry [184]: Could not get metadata of container because it was not found.

    2017-10-22 01:32:19,661 - DEBUG - UM.View.GL.ShaderProgram.load [55]: Loading shader file [C:\Program Files\Cura 3.0\resources\shaders\default.shader]...

    2017-10-22 01:32:19,717 - DEBUG - UM.View.GL.ShaderProgram.load [55]: Loading shader file [C:\Program Files\Cura 3.0\resources\shaders\grid.shader]...

    2017-10-22 01:32:36,469 - CRITICAL - cura.CrashHandler.show [39]: An uncaught exception has occurred!

    2017-10-22 01:32:36,592 - CRITICAL - cura.CrashHandler.show [42]: Traceback (most recent call last):

    2017-10-22 01:32:36,628 - CRITICAL - cura.CrashHandler.show [42]: File "X:\3.0\build\inst\lib\python3.5\site-packages\UM\Qt\Bindings\MainWindow.py", line 183, in _render

    2017-10-22 01:32:36,661 - CRITICAL - cura.CrashHandler.show [42]: File "C:\Program Files\Cura 3.0\plugins\SolidView\SolidView.py", line 76, in beginRendering

    2017-10-22 01:32:36,695 - CRITICAL - cura.CrashHandler.show [42]: if not node.render(renderer):

    2017-10-22 01:32:36,729 - CRITICAL - cura.CrashHandler.show [42]: File "X:\3.0\build\inst\lib\python3.5\site-packages\cura\BuildVolume.py", line 179, in render

    2017-10-22 01:32:36,763 - CRITICAL - cura.CrashHandler.show [42]: File "X:\3.0\build\inst\lib\python3.5\site-packages\UM\View\GL\OpenGL.py", line 141, in createShaderProgram

    2017-10-22 01:32:36,797 - CRITICAL - cura.CrashHandler.show [42]: File "X:\3.0\build\inst\lib\python3.5\site-packages\UM\View\GL\ShaderProgram.py", line 64, in load

    2017-10-22 01:32:36,830 - CRITICAL - cura.CrashHandler.show [42]: File "configparser.py", line 696, in read

    2017-10-22 01:32:36,864 - CRITICAL - cura.CrashHandler.show [42]: File "configparser.py", line 1063, in _read

    2017-10-22 01:32:36,897 - CRITICAL - cura.CrashHandler.show [42]: configparser.DuplicateSectionError: While reading from 'C:\\Program Files\\Cura 3.0\\resources\\shaders\\grid.shader' [line 171]: section 'defaults' already exists

    2017-10-22 01:32:36,998 - DEBUG - UM.Mesh.MeshData.approximateConvexHull [392]: approximateConvexHull(target_count=1024) Calculating 3D convex hull took 0.06400346755981445 seconds. 78 input vertices. 78 output vertices.

    2017-10-22 01:32:37,253 - DEBUG - AutoSave.AutoSave._onTimeout [48]: Autosaving preferences, instances and profiles

    2017-10-22 01:32:37,512 - DEBUG - CuraEngineBackend.CuraEngineBackend._terminate [232]: Attempting to kill the engine process

    2017-10-22 01:32:37,530 - DEBUG - CuraEngineBackend.CuraEngineBackend._terminate [238]: Killing engine process

    2017-10-22 01:32:37,559 - DEBUG - CuraEngineBackend.CuraEngineBackend._terminate [241]: Engine process is killed. Received return code 1

    2017-10-22 01:32:37,608 - DEBUG - UM.Backend.Backend._createSocket [214]: Previous socket existed. Closing that first.

    2017-10-22 01:32:37,764 - CRITICAL - cura.CrashHandler.show [39]: An uncaught exception has occurred!

    2017-10-22 01:32:37,891 - CRITICAL - cura.CrashHandler.show [42]: Traceback (most recent call last):

    2017-10-22 01:32:37,929 - CRITICAL - cura.CrashHandler.show [42]: File "X:\3.0\build\inst\lib\python3.5\site-packages\UM\Qt\Bindings\MainWindow.py", line 184, in _render

    2017-10-22 01:32:37,966 - CRITICAL - cura.CrashHandler.show [42]: File "X:\3.0\build\inst\lib\python3.5\site-packages\UM\Qt\QtRenderer.py", line 138, in render

    2017-10-22 01:32:38,007 - CRITICAL - cura.CrashHandler.show [42]: File "X:\3.0\build\inst\lib\python3.5\site-packages\UM\View\DefaultPass.py", line 23, in render

    2017-10-22 01:32:38,042 - CRITICAL - cura.CrashHandler.show [42]: File "X:\3.0\build\inst\lib\python3.5\site-packages\UM\View\RenderBatch.py", line 164, in render

    2017-10-22 01:32:38,080 - CRITICAL - cura.CrashHandler.show [42]: AttributeError: 'NoneType' object has no attribute 'bind'

    2017-10-22 01:32:38,419 - DEBUG - UM.Backend.Backend._logSocketState [174]: Socket state changed to

  • Link to post
    Share on other sites

    Posted · Crua 3.0.3 loads, displays drawing platform, then quits.
    @lahines100 - You should report this as an issue at the GitHub repository (including the lines from the log file). Than there are much better chances that the developers get notice of it.
    • Like 1
    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
    • Our picks

      • UltiMaker Cura 5.7 stable released
        Cura 5.7 is here and it brings a handy new workflow improvement when using Thingiverse and Cura together, as well as additional capabilities for Method series printers, and a powerful way of sharing print settings using new printer-agnostic project files! Read on to find out about all of these improvements and more. 
         
          • Like
        • 18 replies
      • S-Line Firmware 8.3.0 was released Nov. 20th on the "Latest" firmware branch.
        (Sorry, was out of office when this released)

        This update is for...
        All UltiMaker S series  
        New features
         
        Temperature status. During print preparation, the temperatures of the print cores and build plate will be shown on the display. This gives a better indication of the progress and remaining wait time. Save log files in paused state. It is now possible to save the printer's log files to USB if the currently active print job is paused. Previously, the Dump logs to USB option was only enabled if the printer was in idle state. Confirm print removal via Digital Factory. If the printer is connected to the Digital Factory, it is now possible to confirm the removal of a previous print job via the Digital Factory interface. This is useful in situations where the build plate is clear, but the operator forgot to select Confirm removal on the printer’s display. Visit this page for more information about this feature.
          • Like
        • 0 replies
    ×
    ×
    • Create New...