Maxon Developers Maxon Developers
    • Documentation
      • Cinema 4D Python API
      • Cinema 4D C++ API
      • Cineware 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

    Custom lens and renderers

    Cinema 4D SDK
    c++
    2
    4
    833
    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.
    • rsodreR
      rsodre
      last edited by rsodre

      Hi,

      I have a custom lens plugin (VIDEOPOSTINFO_CUSTOMLENS) that works only with the Standard and Physical renderers. What do I need to do to make it work with the ProRender, Hardware and Software renderers?

      Thanks.

      1 Reply Last reply Reply Quote 0
      • a_blockA
        a_block
        last edited by

        Hi,

        by now we are tossing coins, who has to be the messenger of bad news to you. Somehow it's always me...

        I'm sorry, but there's no way to make it work with the other renderers. The renderer would have to explicitly support it.

        Bye,
        Andreas

        rsodreR 1 Reply Last reply Reply Quote 2
        • rsodreR
          rsodre @a_block
          last edited by

          It sounds strange to me that the built-in renderers do not support all the features.
          Well, ok then, thanks.

          1 Reply Last reply Reply Quote 0
          • a_blockA
            a_block
            last edited by

            Hi Roger,

            yes, you are right, this seems a bit strange on first sight. But the entire concept of VideoPostData providing C++ functions to extend the render pipeline does not hold for a GPU renderer nor the viewport display (which in the end is used for the preview renderers). This doesn't make it any better, but may at least explain the current inconsistency on our side. I'm confident at least for ProRender this is being looked into, but I can't say anything nor make any promises about future developments.

            Cheers,
            Andreas

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