Tweet
Hey,
I recently did a lot of projects with photographers who are used to light cars with Vred, which is a really fast realtime tool. So far, RT is nearly comparable in terms of speed, but a few things just don't work as expected. So here is my list of problems:
1: Proxies in RT are kind of useless, unless the materials are preserved. The background is this: When I have a cad model of a whole car provided by the manufacturer, I have about 15mio polies in the scene. The preparation time is extremely long when you click the active shade button. Waiting time is nearly 5 minutes before you can see anything. That is very annoying, especially when the photographer is sitting next to you, telling you that this is very fast in Vred... My solution would be Vray proxies, which makes the loading times very fast. But I cannot put all the parts into a single proxy, because the material assignments get lost. Exporting every single part as a proxy doesn't make sense, because I would have around 2000 proxies in the scene, which isn't very fast anymore. Is it possible to preserve the material assignments for the proxies. I don't request material export together with the Vray proxies, I just wish that Vray remembers which material in the scene is assigned to which parts inside the single proxy. By the way, attaching all the parts into an exisiting mesh with matching material ID's doesn't work, because Max just freezes on so many objects. Please see this thread for more information: http://forums.chaosgroup.com/showthr...erials-as-well
2: Interactivity can be very slow. The camera channges are very fast. Also lights are updated very fast. But when I create a simple plane next to the whole car, the update takes around 10 seconds. Too much in my eyes. Also, transformations to parts in the scene is very slow. For example, I select the bumper, move it up by 10cm. I wait 10 seconds... Creating and moving lights is blazing fast on the other hand.
3: Changes in the physcam are not updated. Let's say I want to see motion blur from the wheels. So I animate the wheels for some 100 frames, create a physcam and press active shade. I can see the wheel spinning. But let's say I want to make it spin faster: Go to the physical camera, change the shutter speed value, nothing happens. I have to close active shade and start it again to see the changes.
4: Directionality parameter in Vray lights doesn't show up in RT.
5: Camera moves update constantly, whereas light placement updated only when I release the mouse button. It would be nice to see a constant update when moving around light sources.
6: The tiling parameter of bitmaps doesn't work when used as texture in a Vray light.
7: Including/Excluding parts in Vray lights doesn't work.
If necessary, I can provide a scene file via ftp.
Regards
Oliver
I recently did a lot of projects with photographers who are used to light cars with Vred, which is a really fast realtime tool. So far, RT is nearly comparable in terms of speed, but a few things just don't work as expected. So here is my list of problems:
1: Proxies in RT are kind of useless, unless the materials are preserved. The background is this: When I have a cad model of a whole car provided by the manufacturer, I have about 15mio polies in the scene. The preparation time is extremely long when you click the active shade button. Waiting time is nearly 5 minutes before you can see anything. That is very annoying, especially when the photographer is sitting next to you, telling you that this is very fast in Vred... My solution would be Vray proxies, which makes the loading times very fast. But I cannot put all the parts into a single proxy, because the material assignments get lost. Exporting every single part as a proxy doesn't make sense, because I would have around 2000 proxies in the scene, which isn't very fast anymore. Is it possible to preserve the material assignments for the proxies. I don't request material export together with the Vray proxies, I just wish that Vray remembers which material in the scene is assigned to which parts inside the single proxy. By the way, attaching all the parts into an exisiting mesh with matching material ID's doesn't work, because Max just freezes on so many objects. Please see this thread for more information: http://forums.chaosgroup.com/showthr...erials-as-well
2: Interactivity can be very slow. The camera channges are very fast. Also lights are updated very fast. But when I create a simple plane next to the whole car, the update takes around 10 seconds. Too much in my eyes. Also, transformations to parts in the scene is very slow. For example, I select the bumper, move it up by 10cm. I wait 10 seconds... Creating and moving lights is blazing fast on the other hand.
3: Changes in the physcam are not updated. Let's say I want to see motion blur from the wheels. So I animate the wheels for some 100 frames, create a physcam and press active shade. I can see the wheel spinning. But let's say I want to make it spin faster: Go to the physical camera, change the shutter speed value, nothing happens. I have to close active shade and start it again to see the changes.
4: Directionality parameter in Vray lights doesn't show up in RT.
5: Camera moves update constantly, whereas light placement updated only when I release the mouse button. It would be nice to see a constant update when moving around light sources.
6: The tiling parameter of bitmaps doesn't work when used as texture in a Vray light.
7: Including/Excluding parts in Vray lights doesn't work.
If necessary, I can provide a scene file via ftp.
Regards
Oliver
Anisotropy parameter of the V-ray materials is not yet supported by the GPU engine. We have this in our "To do" list.
Comment