PDA

View Full Version : I thought VPR and F9 were the same in 2018.



Tim Parsons
07-23-2018, 09:10 PM
I'm baffled by this. I was under the impression that VPR and F9 were the same in LW2018 - no matter what. Is this not a true statement? What are the circumstances where they would be different? With 2015 and 11.6, glass was always an issue and never rendered as VPR, but as to what's going on here makes my head ache. :) There is a considerable brightness difference. BTW - I'm not in draft mode. Any ideas?

142356

vncnt
07-23-2018, 10:17 PM
Looks like a Color Space issue to me.

JohnMarchant
07-24-2018, 08:40 AM
As Vincent said it must be a colour space problem, also you are right VPR and the render engine are one in the same thing.

MSherak
07-24-2018, 11:27 AM
Looks like a Color Space issue to me.

Also check if VPR is in DRAFT mode. Draft mode has some fixed numbers like bounces.

Tim Parsons
07-24-2018, 11:38 AM
Also check if VPR is in DRAFT mode. Draft mode has some fixed numbers like bounces.


BTW - I'm not in draft mode. :)

Everything seems to be right. I will keep experimenting with other objects and scenes. - Thanks guys!

jwiede
07-24-2018, 02:43 PM
Are you getting identical results for a single-frame f10 image and the f9 image?

Tim Parsons
07-25-2018, 09:13 PM
Same scene, different day = looks fine. :confused: Some minor differences, but nothing that would ruin your day.
142377

VermilionCat
07-25-2018, 10:02 PM
It seems VPR render duration makes difference here.

vncnt
07-25-2018, 10:36 PM
Same scene, different day = looks fine. :confused: Some minor differences, but nothing that would ruin your day.
142377
Do you have a config path definition in a shortcut to the executable?

In that case that config path definition is not used if you open a LWS from Explorer, only when using that shortcut.
I noticed this myself when Ive lost certain shortcuts and other (Color Space?) settings.