Jeff Brogniet

Sry to ask Andrew, but why do you say AO would slow down 3DC ? As Sonk mentioned it, couldn't it be driven through CGfx (though I realize a bit late shaders don't have real interpretation of the mesh itself :s, i'm not advanced at all in that chapter, only asking ...), thus leaving the GPU dealing entirely with it. I must admit I was convinced the slow down was mainly due to highpoly mesh interpolation, so mainly RAM/Scratch concern isn't it ?

Hi all, and special "Hi, the 4 thumbs up !!! " for Andrew About these points Frankie mentioned, I'm REALLY waiting for any confirmation about potential updates on these before integration in our workflow. We're currently testing/choosing, for our environments (mostly huge rocks as in "Cars"), reversed Cam Mapping, also known as Termo Modeling. The main disadvantage of that technique being the stretching resulting from early modeling/extrusion of "mapped volumes", and thus making further treatment really heavy in order to tune up from different angles, the old-school way. So 3DC ISSSSSSSSS our solution, speaking of course about Texture/Photo imposing with dual viewport control for fast scale/orientation of both modelANDtexture. Unfortunately, as we're almost always mapping 4k, and sometimes 8k, it just kills all of the benefit and often freezes, forcing to close every other app. I guess this amazing tool can be considered as real companion for a "Paintless" Mudbox, mostly within regular VideoGame workflow, cause models and maps sizes still respond correctly in it. Pretty light, even with the often used 2k. On the other hand, it's a totally different concern for Movie Industry ... So please Andrew, will you develop any 64bits support, or is our dream almost ended ? Once again btw, kewl and pretty innovative on EVERy aspects (small "y" 'cause of the too conservative base workload ) Cheers, Andrew.