Hi Vlado.
I think i have a problem with my new RT cpu 2.00.02. I upgrade my THREE licenses and have the same problem.
Problem 1 : the image from RT is different from Vray render. Vray render is “lighter” now. With old vray i had no this problem. In the screenshot you can see my settings. I have only one sun and GI environment. the render is BF+LC.
Problem 2 : Very often , when i press activeshade button, RT start a “non gamma correction” render. When i press the button again, the activeshade close the window for a new one , but this time “gamma correct”. Old version didn’t have this problem.
I found RT very usefull in my works but i’m trying to have coherence.
ciao,
I had a similar problem because that was exactly my legacy workflow until VR 2.00 but; after the update, I realized that probably chaos had changed something with the gamma management.
So I have switched to a different workflow, try this:
output gamma 2.2
don’t affect colors checked
sRGB checked
I still have some minor issue with the image sampler settings but VR and RT are more “similar”
I thought it was the best way to use LWF because when you are using the “don’t affect color” checkbox, vray will sample in 2.2 and not in 1, that way, you will have less noise and quicker render for the same results.
If I’m mistaken, please let me know and tell me what’s the other difference between that one and the one you where using before
Hope I will one day understand all thoses settings that’s giving the same results but with differents way to process it
If you are using the light cache for the production renderer, then this would explain the difference. The RT engine only uses a limited number of bounces (three by default) so the image tends to be somewhat darker. If you increase the number of GI bounces for the RT engine, you will closer results to the production renderer.
3LP
probably right now it is the only viable option but I’m still fighting with a lot of issue migrating from 1.5 to 2.0.
I am not able to elaborate exactly what doesn’t work with my legacy workflow but actually I’m forcing myself to change it because it doesn’t work anymore as expected.
In the past years my general setup was:
max preferences
- gamma correction enabled
- affect color selectors and affect material editor checked
- input gamma 2.2
- output gamma 1
material and light subd
- more or less all defaults
render settings
- more or less all defaults (gi on of course)
only few exceptions
color correction reinhard
burn 1 (linear)
gamma 2.2
no aa filters
adaptive dmc sampler
With these settings I was used to let the image sampler do the most of the job (playing with its own settings, of course)
It was maybe not exact from a “perfect compositing” viewpoint but good enough to get my job done.
Migrating to 2.0 I’ve a lot of problems cleaning my images, but I have to investigate better what’s happening and I still have to try the “use old sampler” system variable mentioned into the help file.
Right now it could be only an impression but for me it appears that it’s happened something strange.
I’ve just read a post from Vlado mentioning a bug with color mapping but it doesn’t seem releted to my issues, who know? maybe another one
Yeah this happens to me all of the time, well a lot of time at least. It’s easy to fix it by just starting a new activeshade render but it is annoying.
Yeah this happens to me all of the time, well a lot of time at least. It’s easy to fix it by just starting a new activeshade render but it is annoying.