Closed Rojetto closed 5 years ago
I just happened to stumble upon the changelog of v2.53 which says
A memory leak and antialiasing artifacts in the 3D rendering engine were fixed.
which made me try out v2.52. Result: the error I described does not occur using v2.52, so the changes to the rendering engine probably introduced this bug in v2.53
Thank you for the bug report. I was able to reproduce it and am happy to report that the problem is fixed in version 2.54, which I have just released.
I have a 3D figure that I need to render using rasterization. Using
-render 0
(vectorizing it) everything works fine, apart from 3D paths and surfaces not intersecting correctly. This is fixed by using-render 2
, which gives the correct, albeit a little pixely result. When I try to raise the resolution using-render 4
, Asymptote crashes and printsSuspendThread failed
into the console.There seems to be some kind of limit to the resolution of the rasterized bitmap, because this problem appeared with multiple combinations of
render
parameters,size()
settings and even camera perspectives that change the picture size. I even had this happen in the interactive 3D viewer, which succesfully opened but crashed at some point with the same message while I was rotating the camera.I'm running Asymptote 2.53 on Windows 10 and an Intel HD 520 integrated graphics chip. The command line arguments I use are
Here is the code for reproducing the problem. I could not figure out a minimal example that has the same problem, so you'll have to endure this small mess.
test.asy
:heli.asy
: