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

    Compiled C.O.F.F.E.E. plugin doesn't works on R12

    Scheduled Pinned Locked Moved SDK Help
    5 Posts 0 Posters 426 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 17/05/2011 at 14:05, xxxxxxxx wrote:

      User Information:
      Cinema 4D Version:   11.5&12 
      Platform:    Mac  ;  Mac OSX  ; 
      Language(s) :   C.O.F.F.E.E  ;

      ---------
      Hi all !

      One of my C.O.F.F.E.E plugins doesn't works only on R12.043 on OSX.
      It has been checked on windows 11.5 & 12 / x86 & x64. It also works well on older than R12 versions on Mac.

      I wonder how a C.O.F.F.E.E based plugin can be non-working only on R12.043 on mac.

      Console reports :

      "COFFEE ERROR!
      (124) Syntax error
      File: EasyArea.cob
      Line: 1
      Row: ~1"

      As it blocks on the 1st char could it be a compilation reading problem on R12 on mac ? I used the 9.5 SDK's C.O.F.F.E.E compiler.

      I tried changing the 1st row and it leads to the same error.

      Tomorrow I'll try directly with .COF file instead of .COB.

      Thanks

      M!ke

      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 18/05/2011 at 01:00, xxxxxxxx wrote:

        I had the same issue sometimes.
        Ah damn, I just can't remember how I could solve the problem ~.~
        I will tell you as soon as I remember it !!

        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 18/05/2011 at 01:02, xxxxxxxx wrote:

          It's not a compilation error, If it's the exactly same problem as I had.
          But I had this problem on Windows. hm..

          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 20/05/2011 at 13:07, xxxxxxxx wrote:

            I got it !

            The problem came from the fact that I refered to a vrayobject ID.

            2 weird things :

            1 - The error was detected at line 1 row 1, although the wrong line was far away from that.

            2 - The line was :

            if (op->GetType() == XXXXX)   
                {  
                do sth;  
                 }
            

            Where XXXXX refers to the ID of a VrayForC4D Object. I taught that this line would return false if the object wasn't known, instead of this it returned an error :s.

            Mike

            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 20/05/2011 at 14:14, xxxxxxxx wrote:

              Are you using the number or the enumation name?  If you use the latter, define the name and associate it with the number.  Then it won't error if VrayForC4D isn't installed.

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