Skip to first unread message
Maze Mietner
Dec 5, 2015, 6:11:42 AM12/5/15
to IceSL
Hi
sometimes the File -> Export -> Meshed slices (.stl) just works too fast - not actually slicing anything and not saving anything.
The preview isn't affected and works normally.
When this is the case the status info in the bottom says "Exporting...", the progress bar stays empty and the "Save as..." dialog pops up. The dialog will close on "Save", but there's not even a file created on disk.
If I then exit the program there's an error dialog saying it just crashed.
(Happens when rending object with lots of faces and/or changing the preview)
Maze
sometimes the File -> Export -> Meshed slices (.stl) just works too fast - not actually slicing anything and not saving anything.
The preview isn't affected and works normally.
When this is the case the status info in the bottom says "Exporting...", the progress bar stays empty and the "Save as..." dialog pops up. The dialog will close on "Save", but there's not even a file created on disk.
If I then exit the program there's an error dialog saying it just crashed.
(Happens when rending object with lots of faces and/or changing the preview)
Maze
sylefeb
Dec 5, 2015, 12:31:50 PM12/5/15
to IceSL
Hi Maze, this is most likely due to the GPU running out of memory during mesh generation, which interrupts the process. Could you please send me the file? (feel free to use direct email). I can test on my side to verify this.
Btw, there is one known issue with meshed slices where, in rare cases, it can generate a mesh that is not fully closed (lacking some top/bottom slice faces).
I am working on getting rid of these memory issues, but it will take some development time.
Btw, there is one known issue with meshed slices where, in rare cases, it can generate a mesh that is not fully closed (lacking some top/bottom slice faces).
I am working on getting rid of these memory issues, but it will take some development time.
Maze Mietner
Dec 6, 2015, 4:29:37 PM12/6/15
to IceSL
Hi Sylvain
just put a file on github: https://github.com/maze1980/chaintrack/blob/master/chaintrack_003
I can export .stl with scaling to 50% ("sc=1/2", first line).
If I increase the scaling to "sc=1" it will preview or not (depending on the viewing angle), and if I try to save it'll trigger the bug. Changing back to "sc=1/2" after having the bug won't let me export. Maze
Maze
just put a file on github: https://github.com/maze1980/chaintrack/blob/master/chaintrack_003
I can export .stl with scaling to 50% ("sc=1/2", first line).
If I increase the scaling to "sc=1" it will preview or not (depending on the viewing angle), and if I try to save it'll trigger the bug. Changing back to "sc=1/2" after having the bug won't let me export. Maze
Maze
sylefeb
Dec 17, 2015, 4:26:39 AM12/17/15
to IceSL
Hi Maze,
I just looked into this. The problem with the STL export is that it runs out of GPU memory. This is currently the biggest limitation of IceSL regarding models having large extent (nothing to do with 'complexity' but rather the XY-area of the models).
This is a very high priority item on my TODO but it requires some time to revise the engine in several places.
I fixed the code to remove the silent error - in the next release an error will be correctly triggered and the save dialog will no longer appear.
About the object disappearing from view: This is a different issue. The rendering algorithm can currently only work when the camera is outside of the primitives. If you get too close, it shuts down to avoid displaying a wrong result. In the 'vanilla' version a dialog appears but not in the new UI. I'll fix this. I'll also look into removing this limitation, its annoying.
I just looked into this. The problem with the STL export is that it runs out of GPU memory. This is currently the biggest limitation of IceSL regarding models having large extent (nothing to do with 'complexity' but rather the XY-area of the models).
This is a very high priority item on my TODO but it requires some time to revise the engine in several places.
I fixed the code to remove the silent error - in the next release an error will be correctly triggered and the save dialog will no longer appear.
About the object disappearing from view: This is a different issue. The rendering algorithm can currently only work when the camera is outside of the primitives. If you get too close, it shuts down to avoid displaying a wrong result. In the 'vanilla' version a dialog appears but not in the new UI. I'll fix this. I'll also look into removing this limitation, its annoying.
Maze Mietner
Dec 22, 2015, 11:25:35 AM12/22/15
to IceSL
Great news.
I tried to implement the gears with OpenJSCad as well - it's having the same issue for the ring wheel or a planetary gear: out of memory. And of course it takes ages to process, before giving that error.
I tried to implement the gears with OpenJSCad as well - it's having the same issue for the ring wheel or a planetary gear: out of memory. And of course it takes ages to process, before giving that error.
sylefeb
Dec 23, 2015, 2:40:41 PM12/23/15
to IceSL
Good to know, thanks! Hopefully these memory issues in IceSL will go away sometime next year.
Happy holidays!
Sylvain
PS: btw, we'll be opening R&D engineer positions for working on IceSL, I'll post more info soon but if anyone is interested here please contact me!
Happy holidays!
Sylvain
PS: btw, we'll be opening R&D engineer positions for working on IceSL, I'll post more info soon but if anyone is interested here please contact me!
Reply all
Reply to author
Forward
0 new messages