3D printing forums
-
General
-
- 3.5k
- posts
-
- 3.8k
- posts
-
-
Ultimaker products
-
- 56.3k
- posts
-
- 66.8k
- posts
-
- 8.7k
- posts
-
- 413
- posts
-
- 22.9k
- posts
-
-
3D print Questions
-
- 24.7k
- posts
-
- 2.1k
- posts
-
- 855
- posts
-
-
Ultimaker Academy e-learning
-
- 14
- posts
-
- 7
- posts
-
- 10
- posts
-
-
User Lounge
-
- 7.8k
- posts
-
- 19.2k
- posts
-
- 5.4k
- posts
-
-
Languages
-
- 2.2k
- posts
-
- 23k
- posts
-
- 693
- posts
-
- 30.3k
- posts
-
- 593
- posts
-
- 14
- posts
-
- 252
- posts
-
-
Posts
-
And how to check this theory? The fact that it slices well on another machine doesn't mean that the problem is exactly in this. -
By GregValiant · Posted
"Like if you had the old pentium from years ago where sometimes the floating point processor returned the wrong answer?" It goes back a bit further. Intel was having trouble getting the floating point side of the 486's to work consistently. Their fix was simple. If the floating point side of a chip didn't work when tested, they totally disabled the floating point side and renamed that particular chip a 486SX and were able to sell their scrap (slightly discounted of course). It was a brilliant solution. If the floating point side worked it was a 486DX. -
By Nicko_Airbus · Posted
Did you get better results ? I have the same issues with Aquasys and my printer (ultimaker S5 Pro Bundle). I wonder what we should change to get better prints. Any Feedback ? @willryan3 @SandervG -
By Nicko_Airbus · Posted
I have the same equipment you have and the same issue occured... Don't know why. I fill like the solution given by Dim3nsioneer should help! Good luck! Give us some news about your results! -
Yes that's what I mean but the common point is not in the STL directly - there should be one line that the common point is on at the height of the current slice. Those "common lines" have a point at each end to define them. Those points are in two different triangles that should have a common edge (the common edge is the 3d line). It's hard to explain in words. Anyway I don't think that's the problem. I think the calculation of all the line segments has some kind of floating point error. Like if you had the old pentium from years ago where sometimes the floating point processor returned the wrong answer? I'm not sure.
-
-
Topics
-
