If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
New! You can now log in to the forums with your chaos.com account as well as your forum account.
When one tries to achieve the kind of accuracy we are used to with VRay, it falls apart (literally: oversample and it crashes.).
Long live hardware-independent raytracers, thanks a lot.
Edit: from the demo i had, it seems they moved it from GPUs to CPUs.
The issues remain, though.
Check in the aerospace gallery image 4 and 7.
Where sharp corners meet (fuselage and top compartments in number 4, vertical panles and ground in 7) you will notice streaks.
I could not let them go away, no matter how hard i tried.
It seems to be due to shadows and GI sampling.
Raising the quality kills the app, memory-wise, and leads to crashes. EVERY time.
nono, they had a demo a while back (three months or so?).
I simply tried it on the models of a chair and few other small demo things they had.
Still, the contact GI shadows were bad, and streaked, exhibiting the issues you can see in the aerospace images (which i checked because of your post ).
I have no idea where they got the models from, tbh.
the default image as i load it and let it render (quickly by all means!). no matter how much i let it refine, it won't clean up those issues through the interactive renderer.
so i turn to the final renderer, after having upped the shadow quality for the interactive one.
with these settings, this i s what i get on xp 64 with 2 gb of ram:
And this:
and finally this. Notice how upping the shadow quality in the interactive renderer only leads to smaller "dots", not to a better interpolation (as seen in the zoomed bit).
As i said previously, it sure is quick.
As i said WRONGLY before, it's CPU, NOT GPU based.
Do not pretend VRay's flexibility or precision from it yet, though.
Comment