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
    • Recent
    • Tags
    • Users
    • Register
    • Login

    ray->vv and ray->pp?

    Scheduled Pinned Locked Moved SDK Help
    7 Posts 0 Posters 665 Views
    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 Offline
      Helper
      last edited by

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

      On 22/03/2005 at 07:36, xxxxxxxx wrote:

      User Information:
      Cinema 4D Version:   9.1 
      Platform:   Windows  ; Mac  ;  Mac OSX  ; 
      Language(s) :     C++  ;

      ---------
      Hi,

      why are the vd->ray->vv and vd->ray->pp vectors never filled? Do I need to fill them myself? If so, how are they filled?

      Thanks
      Katachi

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

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

        On 25/03/2005 at 06:20, xxxxxxxx wrote:

        Do you have MIP-mapping enabled for the shader? Where are you accessing these vectors? Are ->v and ->p filled?

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

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

          On 25/03/2005 at 06:24, xxxxxxxx wrote:

          I did so, but it doesn´t help. However, I believe it may be may fault. I am accessing them from within a volume shader with no surface calculation (it´s an environment shader).

          I guess that´s why they are not filled? ->v and ->p are filled.

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

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

            On 25/03/2005 at 12:51, xxxxxxxx wrote:

            I guess I should have been more explicit, but did you set SHADER_MIPSAT in MaterialData::GetRenderInfo()?

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

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

              On 25/03/2005 at 12:53, xxxxxxxx wrote:

              If you did that, then your explanation sounds likely.

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

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

                On 25/03/2005 at 13:49, xxxxxxxx wrote:

                yes, I did set SHADER_MIPSAT. If I´d like to fill them, is there a general rule of thumb what they should look like?

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

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

                  On 25/03/2005 at 13:50, xxxxxxxx wrote:

                  just to add: spot size etc. are of course not accessible either (resp. not filled)

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