Tweet
Hi again, one more time with a bug or point to improve.
This time appears I have encountered myself with a vray-wasting-memory-way.
I've been three days testing a few hours, trying to discover what is doing this, but still no lucky, with the exception of the "bug" is an issue of render with the Maya subivision system.
I've tested materials, GI lightning ways, etc, but how I said, no more hints that the own subdivision itself.
In the scene you'll find, in the outliner, two groups, one for leave it without touch, and another one whose object you should try so subdivide. I'd like you make this test, looking at the memory consumption:
Render with the surfaces as are (without subdivision). Memory consumption will be normal. In my machine, almost 3 gb.
Render with subdivided surfaces (select all surfaces in the group selecting it and pushing "3". It will be subdivided as usually does Maya, 2 levels. This render should consume at least between two-three times the first render. (7 gb)
Last render would be switching back the selected meshes to not-subdivided (pushing "1"), and smooth the surface two times (this time with Mesh>Smooth).
This memory consumtption, back to the first result, but haves the detail of the second one. (Almost 3gb again)
So, if this behaviour is normal... Are not the same, subdivision is not the same that smooth for Vray?. Obviously, I would prefer use subdivision in sufraces where I could, for maintain scene fast, flexible and with a light weight... and I've been smoothing and adjusting surfaces a pair of days to avoid reach my 16 gb limit (seeing I can't discover why I can't use subdivided surfaces), and in theory should be enough with push "3" in just a moment, but...
Errr.. yes, I was to forget it: Win 7 64, Maya 2012 Suscription Advantage Pack, Vray 2.0 last september stable version.
Humm, scene zip compressed weights 160kb, so I'll send you at vraymaya@chaosgroup.com
This time appears I have encountered myself with a vray-wasting-memory-way.
I've been three days testing a few hours, trying to discover what is doing this, but still no lucky, with the exception of the "bug" is an issue of render with the Maya subivision system.
I've tested materials, GI lightning ways, etc, but how I said, no more hints that the own subdivision itself.
In the scene you'll find, in the outliner, two groups, one for leave it without touch, and another one whose object you should try so subdivide. I'd like you make this test, looking at the memory consumption:
Render with the surfaces as are (without subdivision). Memory consumption will be normal. In my machine, almost 3 gb.
Render with subdivided surfaces (select all surfaces in the group selecting it and pushing "3". It will be subdivided as usually does Maya, 2 levels. This render should consume at least between two-three times the first render. (7 gb)
Last render would be switching back the selected meshes to not-subdivided (pushing "1"), and smooth the surface two times (this time with Mesh>Smooth).
This memory consumtption, back to the first result, but haves the detail of the second one. (Almost 3gb again)
So, if this behaviour is normal... Are not the same, subdivision is not the same that smooth for Vray?. Obviously, I would prefer use subdivision in sufraces where I could, for maintain scene fast, flexible and with a light weight... and I've been smoothing and adjusting surfaces a pair of days to avoid reach my 16 gb limit (seeing I can't discover why I can't use subdivided surfaces), and in theory should be enough with push "3" in just a moment, but...
Errr.. yes, I was to forget it: Win 7 64, Maya 2012 Suscription Advantage Pack, Vray 2.0 last september stable version.
Humm, scene zip compressed weights 160kb, so I'll send you at vraymaya@chaosgroup.com
Comment