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
    • Login

    Melange: CreatePhongNormals - wrong results

    Scheduled Pinned Locked Moved SDK Help
    2 Posts 0 Posters 175 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/10/2011 at 01:32, xxxxxxxx wrote:

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

      ---------
      Hi!

      Sorry to bring this up again. But when i do the following:

      Create a Cube in C4D
      Export it for Melange
      Load it in my external Melange app

      and do CreatePhongNormals (valid tag) the output is some values, but they're not the normals i should get.

      As far as i understood this, they're all just per index, means i don't have a normal per vertex, but per polygon index coming out of this array.

      e.g.: 8 vertices, 24 indices -> 24 normals.

      Strange thing is, some are even 0/0/0.

      This is really nagging me, any ideas?

      Thanks for your help...

      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 24/10/2011 at 05:23, xxxxxxxx wrote:

        I can confirm this strange behaviour. The Cinema API version works fine though. I will report it as a bug.

        cheers,
        Matthias

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