Maxon Developers Maxon Developers
    • Documentation
      • Cinema 4D Python API
      • Cinema 4D C++ API
      • Cineware API
      • ZBrush Python API
      • ZBrush GoZ API
      • Code Examples on Github
    • Forum
    • Downloads
    • Support
      • Support Procedures
      • Registered Developer Program
      • Plugin IDs
      • Contact Us
    • Categories
      • Overview
      • News & Information
      • Cinema 4D SDK Support
      • Cineware SDK Support
      • ZBrush 4D SDK Support
      • Bugs
      • General Talk
    • Unread
    • Recent
    • Tags
    • Users
    • Login

    TexData and TextureTag.

    SDK Help
    0
    4
    388
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • H
      Helper
      last edited by

      THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

      On 27/06/2003 at 20:17, xxxxxxxx wrote:

      User Information:
      Cinema 4D Version:   8.100 
      Platform:   Windows  ;   
      Language(s) :   C.O.F.F.E.E  ;  C++  ;

      ---------
      Hi all.
      I want my material plugin to act like the c4d standard material about UVW Coordinates,But there is a problem about a TexData.
      TexData is not influenced by TextureTag, Even if I get it from vd->GetTexData().
      Please tell me what I should do for this.
      void CelMaterial::CalcSurface(PluginMaterial *mat, VolumeData *vd)
      {
        /*  Although vd->tex->lenx and ox changes by TextureTag's Projection setting, It does not change by some TextureTag's Length and Offset value.*/
      Vector col;
       vd->ProjectPoint( vd->tex, vd->lhit, vd->p, vd->n, &uv) );
       col = MyBaseChannel->Sample( vd, &vd->uvw, vd->delta, &vd->n,
                                                          vd->time, vd->tex->texflag, 0.0, 0.0 );
       vd->col = col;
       return;
      }

      1 Reply Last reply Reply Quote 0
      • H
        Helper
        last edited by

        THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

        On 28/06/2003 at 02:05, xxxxxxxx wrote:

        Confirmed, though there's a vague explanation at the top of TexData in the docs that might explain this as a "precalculated raytracer representation". I'll ask the programmers...

        1 Reply Last reply Reply Quote 0
        • H
          Helper
          last edited by

          THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

          On 02/07/2003 at 12:35, xxxxxxxx wrote:

          Materials (except for the C4D material) always get the projection P_VOLUMESHADER assigned. In that case the values for offset/length are not defined.
          For C4D materials the ox/oy values and matrix are modified (precalculated values for the renderer). They do not represent the original offset/length values.
          So this is not optimal right now, and will hopefully be changed in the future.

          1 Reply Last reply Reply Quote 0
          • H
            Helper
            last edited by

            THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

            On 02/07/2003 at 17:31, xxxxxxxx wrote:

            Thanks for your reply.
            I will try another solution.
            Some shader( for expamle, Earth or Marble ) does not work correctly in My Matrerial Plugin, Is it also same reason?

            1 Reply Last reply Reply Quote 0
            • First post
              Last post