Jump to content

baltic

Member
  • Posts

    26
  • Joined

  • Last visited

Everything posted by baltic

  1. But the artifacts are not at triangles intersections. I think ill find time to file the bug with all the info. Maybe other luckers, who also have it, could add something to it. And so we find how to reproduce it. It's definitely a Cura problem, since it doesn't happen with 4.7 Only 4.8 and upwards.
  2. It doesn't happen on smaller ones. Even if i scale that model down, it stops happening.
  3. I found that 4.7.1 doesn't have it. 4.8 and 4.9 do. Maybe i should file a bug, but without an easy way to reproduce it, it's gonna be futile.
  4. Note how the BC line isn't even derived from the original stl, as it is obvious from the wireframe. QED. It has nothing to do with rounding.
  5. Only? Dude the dimensions in the STL are in mm. So the 0.1mm is waay too huge to be a rounding error.
  6. Yeah but if it works on the other machine, how does it prove the point that this is exactly the rounding issue, rather then something else? Btw i don't believe its the rounding. It's waay too off
  7. 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.
  8. Did you mean plane? Plane intersects triangles and gets 2 segments, which don't have a common point? If you already take tolerances into account, when comparing floats, i don't believe the rounding errors alone are going to be huge enough to cause problems. I did it differently, when i wrote a foam cutter software very long ago. As far as i remember, I had a soup of tri edges, and a way to map an edge to a tri. So a slice in my case was list of edges. And I went from a first one, through the triangles it belongs to, to the next. It was working fine, though I didn't have a huge .stl test base, and those stls i had were seemingly well formed. Also, you can implement a simple check, if an edge belongs only to one triangle, then something is wrong in the model.
  9. Ok. I have downloaded the fresh appimage, created a new profile, not derived from Ender 3, to be able to use full printing area. Result is still the same. Is there some sort of log Cura writes which i can check?
  10. It's just for some weird reason Cura started to include "disallowed area" into ender 3 profile. I had to remove them. That's really strange.
  11. Dude it's clearly has nothing to do with the video. Since it's in the .gcode file. It's slicing issue. Ok that explains the inferences. The only weird thing about it, is why this bug feature is not reproducible with another Cura of the same version? Did you try to slice it? Did it produce the same result as for me? Linux x64, it is.
  12. Do you believe the slicing code works somehow different on different OS? 😉 I'm afraid its not that much platform specific. I have suspicion that it's some setting, which leads to this. Especially coz you clearly have different settings then mine, per your screenshot. So .3mf doesn't seem to save them at all, or maybe just doesn't save all of them. Besides, what makes you so sure its the .stl error? No software had reported one on the .stl so far. Yet you quickly jumped to the conclusion that it's .stl error merely based on the fact, that some web service returned you a different .stl. And the fact that you can't reproduce it on your slicer, with the same "erroneous" .stl doesn't bother you.
  13. But apparently yours doesn't Thats what i was talking about. No matter how you have tried, you wasn't able to reproduce it. Thats rather strange.
  14. Solidworks 2014 Strange that it's not 100% reproducible on other machine though, even with 3mf. Model problem suppose to cause the same effect on any slicer instance.
  15. True, but the point was to try to reproduce it. Does the 3mf store all the parameters? Or only the model configuration? Or does it make sense to reproduce it? Are they going to fix it, even if the problem is in stl?
  16. You don't get it. The point is not in the adaptive layers. The point is you were trying to reproduce it with different layer size, and that's the likely reason you didn't hit the bug. Change it to something like 0.01 and you will get tonns of them all around
  17. A-ha! I have changed the layer thickness to the ridiculous 0.01 and i now enjoy a bunch of them, even on the fixed model!
  18. Huh, apparently when i check "use adaptive layers" the problem reappears even on the fixed model. Maybe its just luck that you didn't hit it, because you have used different layer thickness, and so the slicer didn't hit the sweet spot while was cutting it to layers?
  19. Yeah thnx for the fix. But its weird that the bug is not reproducible. Its 100% reproducible for me. At exactly the same layer. I have 4.8.0 under linux P.S. Prusa slicer eats the original stl just fine.
  20. Nah, it's not a preview. I have checked the gcode. The fixed model doesn't have it Here are the settings i am using petg.curaprofile
×
×
  • Create New...