Container IDs for RenderData



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 04/08/2009 at 14:10, xxxxxxxx wrote:

    User Information:
    Cinema 4D Version:    
    Platform:      
    Language(s) :

    ---------
    In may COFFEE script many of the container ids for RenderData are not defined (like RDATA_NAME). Do I need some include directive?

    RDATA_ALPHACHANNEL is defined though, so

    > `

      
    \>  renderdata()->GetContainer()->GetData(RDATA_VOLUMETRICLIGHTING)  
    \>  
    

    `

    works. But

    > `

      
    \>  renderdata()->GetContainer()->GetData(RDATA_NAME)  
    \>  
    

    `

    works not. Any ideas?



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 04/08/2009 at 14:22, xxxxxxxx wrote:

    The following

    > `

      
    \>  MyMenuPlugin::Execute(scene)  
    \>  {  
    \>      var rd = scene->GetFirstRenderData();  
    \>      println(rd);   
    \>      scene->SetActiveRenderData(rd); // this fails  
    \>  }  
    \>  
    

    `

    also fails with an runtime error:

    (9) Member not found

    Not sure if this is somehow related.

    I'm using Cinema 4d R11 on Windows (!). Any ideas?



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 05/08/2009 at 02:29, xxxxxxxx wrote:

    RDATA_NAME is not defined anymore. Please use renderdata->GetName().

    To set the active render data you set its bit BIT_ACTIVERENDERDATA, rdata->SetBit(BIT_ACTIVERENDERDATA).

    Unfortunatly there seem to be some bugs for the COFFEE class. Setting the bit doesn't work always as expected. Also it's currently only a 2D list not a hierarchy. You can't step through a whole render settings hierarchy.

    I have reported this to the CINEMA 4D developers.

    cheers,
    Matthias



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 05/08/2009 at 03:00, xxxxxxxx wrote:

    So is C.O.F.F.E.E. suggested for plug-in development or should I prefer the C++ API? I chose COFFEE because:

    * I do not need a compiler (yes, I'm developing on a virtualized windows box from my linux host, so this is a point)

    * I guessed it will speed up my code-test-debug cycle

    What I see so far is, that the documentation is not in sync with the C.O.F.F.E.E. API (or did I miss something).

    Will I be happy with C.O.F.F.E.E. in the long term? Is there a way to tell what is in the API and what not (like I could do by looking up in C/C++-Header files?).

    Cheers;)



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 05/08/2009 at 03:06, xxxxxxxx wrote:

    It really depends on the type of plugin you are developing. In general the C++ API is much more complete and powerful. Also you can't create COFFEE plugins with a Attribute Manager interface.

    Personally I only use COFFEE to write some scripts and do prototyping (testing algorithms etc.).

    cheers,
    Matthias



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 05/08/2009 at 04:31, xxxxxxxx wrote:

    Quote: Originally posted by Matthias Bober on 05 August 2009
    >
    > * * *
    >
    > Unfortunatly there seem to be some bugs for the COFFEE class. Setting the bit doesn't work always as expected. Also it's currently only a 2D list not a hierarchy. You can't step through a whole render settings hierarchy.
    >
    >
    > * * *

    What I tried worked so far, only the "Render Settings" dialog does not get updated in real-time. What did not work for you?


Log in to reply