Jump to content

titatovenaar

Dormant
  • Posts

    3
  • Joined

  • Last visited

Personal Information

  • Country
    BE

titatovenaar's Achievements

0

Reputation

  1. Hi, Here are the latest error logs 2016-05-14 21:38:55,594 - DEBUG - Attempting to kill the engine process 2016-05-14 21:38:55,594 - DEBUG - Killing engine process 2016-05-14 21:38:55,595 - DEBUG - Engine process is killed. Recieved return code 3221225477 2016-05-14 21:38:55,595 - ERROR - A socket error caused the connection to be reset 2016-05-14 21:38:55,601 - INFO - Started engine process: F:\Program Files\Cura 2.1\CuraEngine.exe 2016-05-14 21:38:55,623 - DEBUG - Backend connected on port 49674 2016-05-14 21:38:56,136 - DEBUG - Sending data to engine for slicing. 2016-05-14 21:38:56,136 - DEBUG - Sending data to engine is completed 2016-05-14 21:39:00,957 - WARNING - Arcus Error (6, native 10054): Receiving type failed 2016-05-14 21:39:01,059 - DEBUG - Attempting to kill the engine process 2016-05-14 21:39:01,059 - DEBUG - Killing engine process 2016-05-14 21:39:01,059 - DEBUG - Engine process is killed. Recieved return code 3221225477 2016-05-14 21:39:01,059 - ERROR - A socket error caused the connection to be reset 2016-05-14 21:39:01,065 - INFO - Started engine process: F:\Program Files\Cura 2.1\CuraEngine.exe 2016-05-14 21:39:01,086 - DEBUG - Backend connected on port 49674 2016-05-14 21:39:01,608 - DEBUG - Sending data to engine for slicing. 2016-05-14 21:39:01,609 - DEBUG - Sending data to engine is completed 2016-05-14 21:39:03,792 - WARNING - Arcus Error (6, native 10054): Could not receive data for message 2016-05-14 21:39:03,894 - DEBUG - Attempting to kill the engine process 2016-05-14 21:39:03,894 - DEBUG - Killing engine process 2016-05-14 21:39:03,894 - DEBUG - Engine process is killed. Recieved return code 3221225477 2016-05-14 21:39:03,895 - ERROR - A socket error caused the connection to be reset 2016-05-14 21:39:03,900 - INFO - Started engine process: F:\Program Files\Cura 2.1\CuraEngine.exe 2016-05-14 21:39:03,922 - DEBUG - Backend connected on port 49674 2016-05-14 21:39:04,433 - DEBUG - Sending data to engine for slicing. 2016-05-14 21:39:04,434 - DEBUG - Sending data to engine is completed
  2. Hi, I'm having this problem when I use a dual extruder with CURA 2.1. (x32/x64 tested) When setting extruder = 0 there's no problem. When setting extruder > 0 the CuraEngine crashes. I also tried all compatibility (for CURAEngine) modes available in Windows10 included administrator mode. But no succes. Any ideas how to solve this problem? Greets,
  3. I'm having exactly the same problem in Windows 10 in different compatibility modes of the CuraEngine. From the moment I raise the amount of extruders, CuraEngine crashes. Till now it happens with all STL files.
×
×
  • Create New...