Announcement

Collapse
No announcement yet.

Someone published a tutorial somewhere!!!!!!!!!!!!yes, a tutorial, no I am not kiding

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Someone published a tutorial somewhere!!!!!!!!!!!!yes, a tutorial, no I am not kiding

    Posted even before whatching , so you tell me if helps, everyone.

    http://blog.motionmedia.com/3dean-oc...ing-phoenix-fd

  • #2
    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.
    ______________________________________________
    VRScans developer

    Comment


    • #3
      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.
      Last edited by lzmihich; 31-10-2013, 12:12 AM.

      Comment


      • #4
        btw we have tutorials made 2011 for phoenix 1.2, reading this thread someone may decide that we have no tutorials at all
        ______________________________________________
        VRScans developer

        Comment


        • #5
          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.

          Comment


          • #6
            yes, the service pack will be released with at least three tutorials
            ______________________________________________
            VRScans developer

            Comment


            • #7
              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


              • #8
                yes, we know that the lack of tutorials is our main drawback.
                ______________________________________________
                VRScans developer

                Comment

                Working...
                X