@Roy_Berntsen, Cycles should run in the “Raytraced Viewport” without the plugin. Note that if you make “Cycles for Rhino” the current renderer, it will crash the current WIP once you invoke _Render.
@nathanletwory, are you planning to include commands like _RenderWindow or _RenderInWindow to use cycles as well ? I think this would be a huge timesaver when it works like the renderborder in blender.
The thing is I don’t have the option of choosing cycles as current render. This is because I didn’t install the plugin. It raytraces in the wievport as it should so I don’t see the point in the plugin anyways.
@Roy_Berntsen, the plugin currently was required to render larger than the viewport size and it would allow for a few optimisations too. Eg. you’ll not need the progressive refinement when you are not doing realtime rendering. There is also (hopefully) an option to change the tilesize which can potentially double the render speed using AMD GPUs.
Note that in it’s current state, rendering using the _Render command seems to work again, however, closing the render window brings up an endless running dialog over here with “Abort” and “Retry” buttons which do nothing yet.
@nathanletwory, can you please try to reproduce / add this to the buglist ?
Yes, it applies to all GPUs according to this. (scroll down to see the chart about tile sizes). For my GPU (AMD) , i’ve found that i can render fastest in blender if i set it to 640x400 which is a very large tile.