You are not logged in.
Pages: 1
1. Every STL I send for slicing ends up having corrupt triangles. This includes STLs that sliced with absolutely no issues on the previous version.
2. I use a remote slicer. A lot of STLs finish slicing on the remote slicer (192.168.0.97) with the error message "Network issue write tcp 192.168.0.97:8080->192.168.0.96:42670: i/o timeout" and they then slice locally on the RPi
Is there any way I can go back to the previous build, as that one worked correctly for me.
Offline
1. Are you sure they did not had any corrupted triangles before?
2. Let me check.
Do you remember last version that was working correctly?
Offline
1. Are you sure they did not had any corrupted triangles before?
Yup. I run all of my STLs through Netfabb and repair them before sending them for slicing. Like I said, STLs that sliced perfectly prior to the upgrade are now coming back with with a warning message saying "Source file contains faulty triangles."
Do you remember last version that was working correctly?
Sorry, no. I upgraded yesterday, last upgrade was (I think) a week or two ago
Offline
1. I could not reproduce it.
2. Not much changed here. It is working correctly but due to changes make sure both side you are using latest version see if the issue goes away or not.
Offline
I am using the same version on both.
Now almost every plate I slice, I get "This plate is corrupt"
Now I know you can't reproduce, but it is real, it is happening, and I need to go back to the previous version. Can you please provide advice on how to do so, as I've wasted an entire 24 hours trying to get a print out.
Offline
Try latest beta, corruption issue has been resolved.
But still could not reproduce the issue 2
About issue 1, a bug prevent reporting triangle issue when remote slicing being used. So it is working correctly now.
Offline
I missed your post until today, but upgraded to build 2555 and all seems good. I think I may have got to the bottom of issue 2, although why it only started when I wen to build 25436 is strange - I only have the issue when my WiFi access is set up in the OS AND in nanoDLP for the nanoDLP instance directly connected to the printer (The remote slicer is cabled), and disappears as well when I connect the printer instance to the switch via cable.
Offline
Pages: 1