algorithmic modeling for Rhino
There seems to be a bug where, while animating a slider in grasshopper, the screen will start flickering black before crashing completely. The file itself is not computationally heavy; it's only composed of about 1000 line objects and no surfaces. I've uploaded a screenshot of what the last frames look like right before the crash. They seem to start inverting. Some previous crashes showed frames that were not only inverted but also tiled. The frames are 1280x720, 5000 frames per animation (Is there a way for me to exceed 10000?). Graphics card is GTX 780 with latest drivers. On occasions I've seen a warning message pop up saying that Rhino is low on memory, even though the task manager clearly shows more than 10 gigs still available. How should I go about diagnosing the problem?
Tags:
Hi An,
memory warnings (and crashes) are usually due to 1 of 4 causes:
Since your images start going black before the crash, I'm tempted to think we're dealing with a #2 crash here. Maybe all these images we're saving out are hogging GDI handles and choking the system. If the handles or GDI objects assigned to Rhino keep going up and up as you write out these images, that'll be good supporting evidence. You can use the Windows 8 Task Manager to keep an eye on these values, or if you're running an older version of Windows I recommend installing Sysinternal Process Explorer in lieu of the Task Manager.
Welcome to
Grasshopper
Added by morteza khorsand 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
© 2024 Created by Scott Davidson. Powered by