Re: Softimage to Modo

[Jason S]

To post details on a sheer poly-count (only) test, involving  subdividing a 600k poly head scan twice (to a 15 million poly head) and instancing it as many times as possible. (using instances to load poly display without loading memory) ________________________ With Modo subdividing (twice to 15 mil. polys) took 1m30sec, and I was able to make 36 instances, (limited by memory.. and stability) saving (15 mil. polys) took 1 min and Loading took 2m10sec. at least (many) long operations show a reliable progress bar showing it's not just frozen. I would save at every third head instance copy, because it would crash at every couple of newly created ones Saving took a while, but autosaves became very irritating taking longer than regular saves (3min) for some reasion, while still not being a good idea to turn it off. doing things like switching (certain) tools would involve a whopping 30 seconds each time, switching 'Modules' wasn't bad (3 sec) but the need to constantly switch back and forth to completely different views, (some with no timeline.. wanting to change something at a particular frame) then having to relocate every time, I didn't find particularly fun.  It would also seemingly randomly process something for 10-20 sec every few minutes, and doing a few things would quickly further push up (the already very heafty 10 gb) memory consumption t'il I had to restart once my 16gig were filled (if that happended before crashing) with 36 instances navigation was 1 FPS in certain modules, to 0.3 FPS (3 sec per frame) in other modules (or with certain tools selected ) (with selection outlines and everything off) __________________________________  While c4d had the fastest processing (15 sec for subivisions) & saving/loading time (20 sec each)  (I know many operations became multithreaded in R15) C4D could barely go beyond 4-5 instances (limited by performance), it would take 10 second refresh to basically do anything in the viewport and even in bounding box display mode (or having stuff out of view?) had barely any effect on performance, which I couldn't beleive, (I hope I was missing something) Program used 4gb ____________________ XSI  Subdividing twice to 15 million took the longest at 3m30sec, Saving was 30 sec , and  1m20sec for loading But while XSI would sort of get hot, it would very much keep on going smooth..  1, all the way to 50 (x15mil polys) instance copies (I could go further), made (any) viewport nav/intraction/transforms, linearly go from 60fps to a usable 1.6 FPS, with a cool 1.9 gb memory consumption with a partcularity of having all Interface (non viewport) interactions remain completly unnaffected by whatever was in the scene. _________________________________ Some of that in  a grid..  Subdividing twice to 15mil       Saving 15mil polys                  Loading                  Nav FPS                                       Mem C4D           15sec                                   20sec                                20sec          10sec/frame  (4x 15 mil polys)             4.3gb MODO      1m40sec                1 min (sometimes 3min)             2m10sec     1 to 3sec/frame (36x 15 mil poly)     9 to 14gb SI               3m30sec                              30sec                                 1m20sec      1.6 fps (50x 15mil polys)                         1.9 gb __________ This is of course but a narrow polycount only test (and maybe I was missing stuff), but I know SI continues to shine with deformations and stuff going-on, and things are far from being all about FPS (ie; the 'depth' of Houdini, where SI also shines(again) except with the simplicity of C4D) But with these results after all this time,  I think the next XSI (or Maya) would more likely be a Vodoo or an Apollo (if released) than either Modo or C4d, But who knows when a truely 'limitless' while super-friendly app (contradictory in terms by default) would rersurface once again.. On 08/07/14 12:54, Paulo Cesar Duarte wrote: Great. Softimage is still my main software, and probably will still remain for the next 3-5 years, and I also believe that in the next 1-2 years the evolution of Modo will be great, and in this time I will be doing a smooth transition, I'm also learning Houdini little by little for simulation and particles.  I once saw a survey showing more satisfied user with their dcc, and the first 3 was Modo users, Blender and Houdini. 2014-08-07 13:33 GMT-03:00 Eric Mootz <e...@mootzoid.com>: PS (@Paulo): I am not "transfering" the plugins to Modo, I am "porting" them. What I mean is that all plugins will remain available for Softimage|XSI, too. In fact I develop in Softimage only and then port them ;) The Modo SDK is still tough to handle, at least that is my opinion. The SDKs of Softimage, Maya and Cinema - just to name a few - are far simpler to use. But the Modo team is aware of the lack of documentation and examples and they are working on it! Pretty sure things will improve greatly in the next 1-2 years!