first impression: very nice, quite fast…impressive integration for a standalone app.
the demo limitations are a bit annoying.
after playing with it for 10 minutes, it seems very solid (can’t test DR with the demo), but it also isn’t quite ready yet.
IMO every aspect of vray should be supported, including displacement and proxies…
i guess it will come with later updates.
a few quirks/bugs i noticed so far:
-) layer visiblility is ignored. since i organize everything with layers, it is crucial for me to be able to turn them on/off quickly, especially for realtime tests. a must for architectual scenes.
-) tiles map doesn’t support color variation.
-) vray edges tex doesn’t work in bump slot, for rounded corners.
Actually you can use one additional machine for DR (total of 2 machines for DR, one doesn’t have to be your local machine).
-) layer visiblility is ignored. since i organize everything with layers, it is crucial for me to be able to turn them on/off quickly, especially for realtime tests. a must for architectual scenes.This seems to be a limitation of the 3ds Max SDK for now (V-Ray RT does not receive notification when layer visibility changes). There might be a way around it, but we’ll have to research a bit.
For the other things, they will be added in an update.
after playing with it for 10 minutes, it seems very solid (can’t test DR with the demo), but it also isn’t quite ready yet.
IMO every aspect of vray should be supported, including displacement and proxies…I completely agree that these need support, but disagree that the release should be held off for all of them. There are workarounds for both of these things that do the trick, and basic material and light support for standard geometry is still hugely useful.
Spend some more time with RT and I think you will change your mind - the time savings it represents for material development alone make it worth it IMO. Setting up lighting for complex objects (particularly refractive materials) is also significantly faster, and therefore capable of much greater refinement in reasonable times.
Yes, there appears to be a way to capture the layer visibility change; it just didn’t occur to me at the time… (there are like 3 ways to get such notifications and they all work for different cases).
I am only running 1 machine (quad core) was very interested to see if it could handle Vray RT.
But with the demo being soooo limited, I have no way of knowing.
So the demo is abit pointless as most scenes have a tad more then 15 objects.
Would prefer a demo that could open a scene I would be using in a work situation.
So not sure if would be worth my while purchasing it, if I cant tell if I can run it.
I tested with a scene that had more than 15 objects… the way around it is to merge everything into a single poly. That’s of course if your computer can handle it
“Store with irradiance map” on vray light doesn’t seem to quite work, with the setting on the light is a lot darker. I can’t see this on the “Unsupported features” list, so I guess there is a bug or something.
And with “store with irradiance map” on the render result and the result in Vray RT is not the same.
You’ll get the same effect if you set the primary GI engine to “Brute force” in the standard V-Ray renderer (which is the method that the RT always uses). However you are right that it is somewhat unexpected and should be corrected.
Me again… “vray object properties” also isn’t working, tested send and receive GI and “visible to gi”, I couldn’t see it on the list of “Unsupported features”.
Please help me,
just download VRay RT. Make a simple scene with one object, VRay Sun, VRay Phys cam, test render ok. Then start VRay RT, but Its black without showing anything :(((
They do work; what does not work is the interactive change of these properties - you need to restart the ActiveShade view. To fix this I will have to modify the standard V-Ray though.
