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

    adding a new illumination model

    Scheduled Pinned Locked Moved SDK Help
    5 Posts 0 Posters 474 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 24/09/2007 at 12:50, xxxxxxxx wrote:

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

      ---------
      Hi!
      I want to add a new illumination model to the standard material of cinema 4d. If you create a new material and you select "Illumination" in the material editor, you can select a model like phong or blinn.
      I just want to add a new model and if this model is selected, there should be an additional button to load a file.
      Is this possible or do I have to create a complete new class of materials?
      Thank you very much for your reply.

      Nice greetings from Germany,
      Manuel

      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/09/2007 at 07:48, xxxxxxxx wrote:

        You have to create your own material class.

        cheers,
        Matthias

        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 27/09/2007 at 06:22, xxxxxxxx wrote:

          Another, perhaps easier, alternative is to create a channelshader that can be plugged into the luminance channel of the standard cinema4d material. Like the "lumas" shader.

          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 27/09/2007 at 07:24, xxxxxxxx wrote:

            Thank you for your answers.

            I am not really sure how difficult it is, to create my own material with all the default settings from a standard material.

            The other idea sounds great. I just write my own shader for the luminance channel and then I have do deactivate my color channel because I don't want phong shading, right?

            Many thanks,
            Manuel

            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 27/09/2007 at 20:30, xxxxxxxx wrote:

              I agree with FilipM. A plugin material does not include the stock material channels (as one cannot extend existing C4D types, gaddangit). You'll have to experiment with what provides the best illumination model, but the luminance channel is probably the best bet. You really should not have to disable the color channel - but try both and see the results.

              To go abit off-topic, I really wish that Maxon would allow extension of stock types. Okay, it is a bit perilous since they might change at any time - but aren't we already required to change plugins for new SDKs as the interface changes? This would allow for much, much, much simpler plugins as one could have the existing power of the stock type and accentuate it. Currently, we have to recreate any of this existing power ourselves - and with the mantric "we cannot divulge the underlying algorithms" just to make it a billion times more difficult. The things that I could do with such ability would cut my development time by years (YEARS!!!!). TYVM...

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