generative modeling for Rhino
Grasshopper (and indeed Rhino) can be performance critical applications since both potentially deal with large amounts of data and computations. Although we aim to make our software runnable on low-end, over-the-counter computers, you may still run into serious performance issues. We have no strict recommendation or requirements, but here are the basic rules when it comes to picking hardware for Rhino and Grasshopper:
Some further points to take into account:
* This may change in the future, but not the foreseeable future.
Tags: RAM, card, graphics, hardware, memory, processor, requirements, video
Permalink Reply by Mirza Ali on August 26, 2012 at 9:29pm Thanks! That helped! I bought the hp envy 6 sleekbook last night, (8 hrs back!!!) with 64bit and an 8GB memory and 2 GB graphics card :) everything seems to be working at a much faster speed as compared to my old vaio! Thank you both, again! :)
Permalink Reply by Hans Hubers on February 7, 2013 at 9:12am What should one do, when Rhino gets slow? I noticed that even if you disconnect a Grasshopper component that caused the problem, the machine stays slow. Only a restart helps. Is there a command that frees unused memory?
Permalink Reply by Diego Xavier on February 7, 2013 at 11:08am Although we aim to make our software runnable on low-end, over-the-counter computers
I must admit that you really did it, for almost 6 years my work machine was a 2004 PC with an AMD Semprom 1.6Ghz, 2GB RAM and a GeForce 4 mx 4000 128MB (and I suspect is not working for Rhino or Gh, because in my openGL preferences Rhine says I have only 64mb of video memory), and still within a couple of months I was able to do my entire graduation thesis, modeled 95% in Gh.. So a basic pc is not an excuse thanks to you guys :D
© 2013 Created by Scott Davidson.
Powered by