Of cause you need the 3G.. It would be like, bring-your-own-internet-day type of thing, letting them know what you think about them and their firewall
session ended - hopefully it was OK
Well done Ian!
BTW, Team viewer is not the best IMO.
nice info about octane workflow Ian ! It is crazy fast And responseve too
If they will implement support for bitmap real scale + displacement maps + proxies, i will also buy it as a max plug-in!
As a side note:
As far as i know, gpu rendering is not make use of the proxies memory advantage (iray suport`s mentalray proxiy objects, but it treat them as all at once mesh objects, so not an advantage for video memory in iray, yet). A proxy, is a container of a mesh (like 1 squaremeter of modelled grass), that is placed in the scene, on your site, by instanciating it in many copies without eating your video memory for every instance (only for some instances at the render time for the spot of the image where the cpu is working...so a few of the instances are loaded/unloaded in memory at render time to preserve a constant memory load). This give you the advantage to have a lot of vegetation, with millions of poligons, that don`t eat your limited video memory. Curently the proxies are suported by vray and mentalray.
For me, the main ideea is to have archi vis gpu rendering, with nice vegetation around . The vegetation is the only thing that keep me away from gpu rendering. I like and I love to have phisicaly accurate light algorithms but if there is not physical geometry vegetation around there is not a "natural" scene I know you can put a limited amount modeled meshes (trees, maybe somea real grass)
For interiors scenes (where there is not vegetation ),and in general for the process of defining new materials in realtime, I think it is a very atractive path to follow
Last edited by gaby424; January 24th, 2012 at 12:03 AM.