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.
Exciting News: Chaos acquires EvolveLAB = AI-Powered Design.
To learn more, please visit this page!
New! You can now log in to the forums with your chaos.com account as well as your forum account.
Announcement
Collapse
No announcement yet.
Someone published a tutorial somewhere!!!!!!!!!!!!yes, a tutorial, no I am not kiding
unfortunately this tutorial skips a very important point, by default the vray displacement clamps the texture to 0-1, and if you put the phoenix ocean texture it will be clamped.
this is very confusing for the new users, and they even can't realise that something is wrong.
until now we have found four similar points where the default vray settings are in conflict with some phoenix feature, and we decided to detect them and to display a warning message box or even to offer automatic setting
here is the list:
1. The max transp levels (global switches) conflicts with the geometry mode rendering, it must be much more, for example 1000
2. The transp. cutoff (global switches) conflicts with the under water foam rendering, when the fog color (vray mtl) is too dense. VRay skips the refraction rays and the underwater foam disappears. To avoid this the proper value is zero.
3. The above mentioned clamping values in the vray displacement mod, beside the vector displacement option, which is by default enabled in the ocean texture and disabled in the mod.
4. The default geometry (vray system settings) is by default "auto", that conflicts with our ocean option of the mesher. It must be "static"
We have implemented warnings for all these situations except the transp. cutoff parameter, still considering at which point to display the message for it.
I was surprised it doesn't even go trough Phoenix settings !To good to be true right ?
Seems those warnings are really necessary, Good luck(and expertise) with the new service pack and
the task to make Phoenix FD 2.* more user friendly.
yes Yvaylo.
The basics are there, but they are almost deprecated.
There are new features, my bad, I am concentrating only on the new features, particularly Ocean, should made it clear.
Just got excited that I found one, pity it is not suitable.
but I've understood that a service pack will be released whenever it is ready and tutorials will be updated then , yes ?
No intent to rush or stress anyone, as you already explained there are bugs being adressed ,and the team is working hard.
Perhaps we could set up a system where users can make tutorials, but run them by the developers for comments. Even if the user could not redo the tutorial other users watching the tutorials could get the benefit of the developers' feedback by posting the comments with the video.
I think Phoenix is great, and in many ways better than the competition, but, MAN, there are hundred of tutorials for the other guys, and we need more user generated stuff for Phoenix. I keep meaning to do some, but haven't had a chance.
I think Chaos should also emphasize the free render node aspect of Phoenix, as the competition chargers per node.
Comment