![]() ![]() It is hard to believe this is likely caused by ‘plug-in or hardware, or a combination’ without further elaboration.īelow is the Systeminfo result when I open Rhino as a baseline: ![]() That being said, the true problem reported here is not only the file crashed, which can be partly recovered by digging into the autosave versions, but this time my custom settings have all gone disappeared for some reason. It is obviously not the correct solution since the problem persists even to the most recent release today. I had reported this multiple times and the simple answer I get is to update my Rhino. This is a habit I built since the very early days of using Rhino and now it has become a trigger to crash ever since the shift to Rhino7. Just an example, because of my modeling tendencies, I am used to editing a polysurface by selectively moving control points to adjust the size of an enclosed geometry, or doing similar things on curves and hatches for drafting. However, it has nothing to do with the issues I run into when I focus exclusively on modeling. When I crash out with plugins open I understand that the issue is likely on the capacity of the graphic card or the issue of the plugin. What I know is that most of the time I don’t have Vray or Enscape running actively when I am working in the model space. I am not 100% sure if I should consciously disable those plugins every time I open Rhino to make the software work properly. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |