Moderator: face_off
It looks like TheFoundry has "fixed" a previous bug in the render cache, which has now changed (broken?) the instances functionality. I reported the problem to TheFoundry and they are saying it is "Not a bug", so I will need to see if there is a way around the problem.I use Modo 10.1v2
I have investigated the render cache issue some more, and the changes put through in Modo10.2v1 completely break the render cache, and it is no longer viable as a way to obtain Modo scene geometry. Regretfully I will need to remove render cache support in the next release of the plugin.I don't no what to say ... As long as I can remember Modo crashes at least once a day (At least for me). Its a good modeler which also has some nice features and bugs too. I feel sorry for you ... that you choose this application as plugin developer ... as much as I love Modo ... I hate it (Sometimes). But with the new plugin ... I don't need to enable the option "Use Render Cache" since the displacement map renders now nicely.
I agree too, I also think memory management for out of core needs to be reworked by otoy, when used with different cards gives me error 700.face_off wrote:I have investigated the render cache issue some more, and the changes put through in Modo10.2v1 completely break the render cache, and it is no longer viable as a way to obtain Modo scene geometry. Regretfully I will need to remove render cache support in the next release of the plugin.I don't no what to say ... As long as I can remember Modo crashes at least once a day (At least for me). Its a good modeler which also has some nice features and bugs too. I feel sorry for you ... that you choose this application as plugin developer ... as much as I love Modo ... I hate it (Sometimes). But with the new plugin ... I don't need to enable the option "Use Render Cache" since the displacement map renders now nicely.
Paul
