RT GPU render compared to CPU RT and standard VRay

[Jiri.Matys]

Hi,

I tried my scene render with RT CPU and GPU. Its scene I used for testing new VRay and new Forest Pack 5, so you know, how its looking.
As you can see, CPU final render looks pretty close (only one thing - I think CPU support caustics, but its not there).
But what the hell is with GPU? Everything is bad and whole lighting is bad. Textures is sized down through VRay RT (I have only 3 GB of VRAM). But you added support for almost everything I always used in past two service pack. So where is the problem?
And one more thing - information window of VRay RT is not opening now. Is there a way how to open it? Its confusing, when you waiting to start rendering and dont know, what is happening.

[savage309]

For some reason the texture used for environment is not loaded properly and you are getting wrong lighting.
Can you share the scene so we can check why is that ?

[matanov]

That curved plane at the back is the source of all evil. So yes we will need that scene.

[Jiri.Matys]

Scene sent to support.

And I have two more big problems with RT GPU in new 3.3 version.

Sometimes happened that I hit render in active shade mode with RT GPU, it starts initializing and then stops. Log window dont appear now, so I dont know where is the problem. I restart whole max, load up a scene and it works, so its really weird and confusing. With this scene too.

And second, I render this scene in GPU, so it looks weird because of problems said previously, I just testing. Change camera angle and so on and whole image become green tint. Dont know what was that. But I cant get rid of so I have to restart max

[3LP]

here is how to show the log in RT production, should pop up automatically when a error is reported though


don't think it's possible in active shade.

Stan

[Jiri.Matys]

This is not what I mean. I mean the window which pop up every time with VRay RT rendering and showing all informations about initializing the scene, computing light cache, loading textures and so on. This is something different and only as production render. Iam using VRay RT as active shade to use a benefit of changing the scene as instantly rendering.

[yavor.rubenov]

Hello,

The window that popped for V-Ray RT was V-Ray Standalone. Now the whole renderer is integrated inside Max and there is no separate process for it. (The item (*) V-Ray RT: In-process RT engine (no separate command-line opens up); in the change log).

So now all the info that was previously there goes to the V-Ray log - can be seen with the "Show log" button or in the log file (%temp%\vraylog.txt by default).

Best regards,
Yavor

[savage309]

So where is the problem?

"Multiply color by opacity" for the V-Ray Light Mtl is not supported yet, thus the black curve and the darker render.
Sorry for that. I will put a note to fix it.

[3LP]

Hello,

The window that popped for V-Ray RT was V-Ray Standalone. Now the whole renderer is integrated inside Max and there is no separate process for it. (The item (*) V-Ray RT: In-process RT engine (no separate command-line opens up); in the change log).

So now all the info that was previously there goes to the V-Ray log - can be seen with the "Show log" button or in the log file (%temp%\vraylog.txt by default).

Best regards,
Yavor

That's right, although if you'd like to by pass that and for some reasons revert back to the old cmd window, you can do so by enabling the spawning, un-check use local machine, add your own machine ip adresse and start the vray RT server. (Little trick I learned while debugging with Peter and Vlado )
But that being said, vray log is way easier to manage

Stan

[Jiri.Matys]

Hello,

The window that popped for V-Ray RT was V-Ray Standalone. Now the whole renderer is integrated inside Max and there is no separate process for it. (The item (*) V-Ray RT: In-process RT engine (no separate command-line opens up); in the change log).

So now all the info that was previously there goes to the V-Ray log - can be seen with the "Show log" button or in the log file (%temp%\vraylog.txt by default).

Best regards,
Yavor

OK, I cant see all the info about light cache computing, bitmaps loading and so on in max log, which is opening. Iam using active shade, I have to do something to show me this informations?

[yavor.rubenov]

Hello,

If you are using Max 2016 - the max log window shows active shade messages in a separate tab. Also by default information messages are disabled and you have to enable them.



Best regards,
Yavor

[savage309]

As a result of your report we have fixed the issues in the scene and I'll try to merge the fixes into the 3.30.01 stable builds.
Keep in mind that raytraced(refract) mode and procedural maps for bump are not supported (so the pool will render differently) yet.
Best,
Blago.

[Jiri.Matys]

Hello,

If you are using Max 2016 - the max log window shows active shade messages in a separate tab. Also by default information messages are disabled and you have to enable them.

[ATTACH=CONFIG]27020[/ATTACH]

Best regards,
Yavor

Oh, I miss this option in roll out, thank you.

[Jiri.Matys]

As a result of your report we have fixed the issues in the scene and I'll try to merge the fixes into the 3.30.01 stable builds.
Keep in mind that raytraced(refract) mode and procedural maps for bump are not supported (so the pool will render differently) yet.
Best,
Blago.

Now Iam using one of the nightlies. Thanks.

And I find out that VRayLightMtl in Multi/Sub Material doesnt work in VRayRT, this is why lighting doesnt work.

I know about FastSSS2, but I think noise procedural map works through baking? Or it not work only as a bump? Is it possible to implement this?

So you change the Multi/Sub texture and disable Multiply color by opacity, ok? And enything else was wrong?

[savage309]

And I find out that VRayLightMtl in Multi/Sub Material doesnt work in VRayRT, this is why lighting doesnt work

I have fixed that. It will be soon in the nightlies and most likely in the official 3.30.01

So you change the Multi/Sub texture and disable Multiply color by opacity, ok? And enything else was wrong?

I have fixed that, too. Again it will be soon in the nightlies, possibly in the official 3.30.01, too.

With these fixes the scenes was rendering fine, I think.

For the noise - it is not baked. We do calculate it in a procedural way (just as in the production).
Procedural maps will not work for bump yet. It is possible to implement it, but we still haven't done it.