Originally posted by Donfarese
View Post
Announcement
Collapse
No announcement yet.
vray and corona
Collapse
X
-
Originally posted by Morbid Angel View PostMan you're old...Actually I did the same exact thing. I caught final render at its end of day same as brazil. Actually final render is still around......no one hears about it anymore though but apparently its still being used.
Sorry for OT btwMartin
http://www.pixelbox.cz
Comment
-
Originally posted by Morbid Angel View PostMan you're old...Actually I did the same exact thing. I caught final render at its end of day same as brazil. Actually final render is still around......no one hears about it anymore though but apparently its still being used.
Comment
-
Originally posted by Donfarese View PostWouldn't that only be because the lack of ram on the 970. I use RT CPU & GPU, GPU is faster by like 10x.
- Cycles is not V-Ray GPU. So experience may vary there.
- I am comparing CPU and GPU of the equal price bought at same time and at a time both were latest tech, so it's a good base for comparison. If you have say 4core i7 2600k and comparing it to Titan Z, then indeed GPU will be vastly faster, but it was also more expensive and eats a lot more power
- AFAIK when Cycles runs out of GPU memory, it doesn't start to out-of-core, it simply refuses to render with error message, so I would have noticed that.
- And as I mentioned, it heavily depends on scene complexity. Teapot on a plane kind of scene (a simple car exterior/studio scene for example) will indeed render a lot faster, but try some complex scene with forestpack foliage or something like that Something that pushes GPU to its limit in terms of memory and performance
- And lastly, yes, I did not deny that actual rendering performance will likely be significantly better than the CPU version, just that feedback speed (update latency) won't be magically better on GPU. If you compare V-Ray RT CPU vs GPU - yes, the noise will clean faster - but no, the camera/object transformation/material/environment change updates won't be any faster.
TL;DR: How much is the renderer interactive has nothing to do with GPU at all. CPU is as good for rendering interactivity (updating scene on the fly) as the GPU. But if you have hybrid renderer, like V-Ray, that has both CPU and GPU options, then CPU is a lot more suitable choice, because it allows for 1:1 feature parity. And when rendering interactively, knowing that what you are tweaking will be exactly 1:1 to final production render frame is IMHO a lot more important than performance.Last edited by LudvikKoutny; 06-05-2016, 12:54 AM.
Comment
-
Oh yeah the good old days I found an image from the last millenium. Povray anyone ? This is the second image I rendered after playing half a year with cubes, spheres, various modellers like moray and render settings.The first one was a spaceship. I can´t find this image anymore. but I remember it was pretty terrible At that time I didn´t even think of making 3D my profession.
Those are two images comparing Brazil alpha with Final Render. Those "lighting around the corner" images were nearly as popular as the "I can render 10 gazillion instances" images, these days.
First I went with Final Render. While Brazil was capable of the more detailed GI, Final Render was faster. Brazil without a big Render Farm was pretty much a pain. Than Vray hit the stage. I was still with Final Render for quite some time. The main reason for me to test Vray was one missing feature in FR. Light through Glas without caustics. While testing I discovered the incredible speed advantage. So from that day I never used FR again. Vray at that time in general had a lot less features compared to FR.
Now back to Vray vs. Corona. I think it´s a pretty esoteric discussion. And we had similar discussions before. I remember Maxwell and those Flashlight images. Something that no one ever would consider to sell to an archviz customer. That´s why it probabely never was done before in Vray. But people very all about how realistic Maxwell can render. Once a renderer uses an algorithm that relies on physical light distributions it´s purely up to the artist. No matter if it´s Metropolis Light Transport, Pathtracing Brute Force and any other imaginable method. Even way before those renderers existed people made damn realistic pictures with Lightscape. The discussion should focus more on speed, usability, flexibility, feature range and support ! Now let me come back to the Car comparission from some pages before. I agree that Corona is a Lexus but Vray is not a tank. Vray Is a Mercedes S-Class. It was there way before the Lexus. You can clearly see where the Lexus got it´s design from. The costs are nearly the same, they have similar features. But if I had the choice I would always go with the S-Class. Now let´s wait and see if there comes a renderer stepping up as a Tesla....
Comment
-
Originally posted by PIXELBOX_SRO View Posti have one area which i would be curious to ask Vlado about when it comes to comparing the two engines as described here:
http://forums.ronenbekerman.com/show...t=2641&page=17
i ve read the whole thread there and it seem there is a difference in how Corona handles the translucency/glossies when rendering tree leaves.
This is, for me, is the area I struggle with most with Vray. Didn't Vlado once whisper sweet nothings about a specific MTL just for leaves? Might have been a dream....
Comment
-
Originally posted by Pixelcon View PostThis is, for me, is the area I struggle with most with Vray.
Also, I don't think that any real-world tree looks like in that picture... leaves are not *that* translucent. I specifically took the time to take a lot of pictures and compare.
Best regards,
VladoLast edited by vlado; 06-05-2016, 04:44 AM.I only act like I know everything, Rogers.
Comment
-
Originally posted by vlado View PostThere are no technical differences in how the two engines handle thin translucency as far as lighting calculations go, but there is a slight difference in the way the BRDFs are layered. In 3ds Max 2017, you can try the Physical Material, which is supported by V-Ray and has a "thin translucency" option. If that works for you, we may consider adding it to the VRayMtl material.
Also, I don't think that any real-world tree looks like in that picture... leaves are not *that* translucent. I specifically took the time to take a lot of pictures and compare.
Best regards,
Vlado
http://thumbs.dreamstime.com/z/apple...n-57589650.jpg
https://runningmad.files.wordpress.c...5/p1010784.jpg
http://imgc.allpostersimages.com/ima...ous-leaves.jpg
https://wallpaperscraft.com/image/su..._2560x1600.jpg
That being said, I agree that there's not that much different with the actual translucency component in VRayMTL. The problem I think is mainly the reflection conservation issue and generally clumsy two material workflow
EDIT: BTW I would love to try Physical Material in 2017 with V-Ray. I even sent you a mail, but no reply :/Last edited by LudvikKoutny; 06-05-2016, 05:07 AM.
Comment
-
-
Originally posted by Recon442 View PostThe problem I think is mainly the reflection conservation issue
Comment
-
Originally posted by Recon442 View PostThat would be a very unfortunate way of solving it
Comment
Comment