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

    Wrong editor preview of material plugins with TextureTag repetitions

    Cinema 4D SDK
    s22 c++
    2
    4
    631
    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.
    • D
      Deyan
      last edited by Deyan

      Hi,

      In short - when material plugins are assigned on object and have non-zero Repetitions U or Repetitions V in their texture tag assignment, the editor preview does not clip the preview image at all. I noticed this only for Cinema 4D S22 and above.

      Some details - I have a material plugin deriving from the MaterialData class, with an override for MaterialData::InitGLImage(..) to generate a generic preview for the material in the editor. Until S22, the editor preview correctly showed the material with the specified repetitions in the TextureTag. After that only the native materials seem to show this correctly.

      Is there a flag that we missed adding for S22 or something else that was introduced and is missing on our side, or this is a problem in Cinema 4D?

      Thanks,
      Deyan

      1 Reply Last reply Reply Quote 0
      • ManuelM
        Manuel
        last edited by

        Hi,

        I did reproduced the issue, with the s22 we changed the viewport and many changes have been introduce.

        I have contacted the devs to have some feedback about that.

        Cheers,
        Manuel

        MAXON SDK Specialist

        MAXON Registered Developer

        1 Reply Last reply Reply Quote 0
        • ManuelM
          Manuel
          last edited by

          hi,

          This is a bug and will be fix in a futur release.
          Unfortunately, there's no workaround.

          Cheers,
          Manuel

          MAXON SDK Specialist

          MAXON Registered Developer

          1 Reply Last reply Reply Quote 0
          • D
            Deyan
            last edited by

            Thanks for the investigation. At least now we are aware the problem is not on our side.

            Cheers,
            Deyan

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