Hi @blastframe, I'm not sure what is your issue, does the draw method is called? Because since S22 to get the Draw method called you needed to register your TagData with the c4d.TAG_IMPLEMENTS_DRAW_FUNCTION flags.

Or does the Draw method is called but the result is not what you expected? If yes can you provide a screenshot of what you are aiming, or describe a bit more your issue?

Cheers,
Maxime.

Hi @nicholas_yue there is nothing builtin but the most optimized way I think will be

import c4d

def GetNodeListsAtCurrentLevel(bl2D):
    parent = bl2D.GetUp()
    if parent is None:
        parent = bl2D.GetListHead()

    return parent.GetChildren()

def main():
    print GetNodeListsAtCurrentLevel(doc.GetActiveTag())

# Execute main()
if __name__=='__main__':
    main()

Cheers,
Maxime.

Yes, all SDK team members are fine :D

I can only confirm the issue here, and it was introduced in S22 with the new ViewPort stuff just in case you want to do different codes for different versions.
The problem is that internally the new Viewport Render, is really just a mirror of what you see in the Viewport. And by default, the Viewport retrieves its data from the active BaseDraw of the document the Viewport is supposed to represent.
And by default (and here come the issue) this BaseDraw setting retrieves the active render setting when you ask for a render outside of the ViewPort windows.

So the current workaround is to set the render setting as active as bellow.

import c4d

def main():
    docClone = doc.GetClone()
    
    # Setup RenderData
    rdPreview = c4d.documents.RenderData()
    rdPreview[c4d.RDATA_RENDERENGINE] = c4d.RDATA_RENDERENGINE_PREVIEWHARDWARE
    rdPreview[c4d.RDATA_XRES] = 600
    rdPreview[c4d.RDATA_YRES] = 600
    
    # Uncomments those 2 lines to make it work
    # docClone.InsertRenderData(rdPreview)
    # docClone.SetActiveRenderData(rdPreview)
    
    # Setup Viewport Render
    vp = c4d.BaseList2D(c4d.RDATA_RENDERENGINE_PREVIEWHARDWARE)
    rdPreview.InsertVideoPostLast(vp)
    vp[c4d.VP_PREVIEWHARDWARE_ONLY_GEOMETRY] = True
    
    # Setup target BMP
    bmPreview = c4d.bitmaps.BaseBitmap()
    bmPreview.Init(rdPreview[c4d.RDATA_XRES], rdPreview[c4d.RDATA_YRES])
    
    # Render
    result = c4d.documents.RenderDocument(docClone, rdPreview.GetData(), bmPreview, c4d.RENDERFLAGS_EXTERNAL, th=None)
    if result == c4d.RENDERRESULT_OK:
        c4d.bitmaps.ShowBitmap(bmPreview)
        
if __name__=='__main__':
    main()

I've open a bug report about it.

Cheers,
Maxime.

@a_block said in Render filtered Hardware Preview:

But one has to be careful with testing. If the currently active scene has such flags set, too, then it may seems as if it works, while it actually is not working.

As always you are right, Im going to keep my research then :)

Hi @a_block I hope you are fine :)

In order to use the Preview Render you have to additionally pass RENDERFLAGS_PREVIEWRENDER

result = c4d.documents.RenderDocument(docClone, rdPreview.GetData(), bmPreview, c4d.RENDERFLAGS_PREVIEWRENDER | c4d.RENDERFLAGS_EXTERNAL, th=None)

Work as expected.

Cheers,
Maxime.

Hi @wob unfortunately this is not possible, c4dpy is a regular Cinema 4D executed as command line with the NoGui, and as all NoGui Cinema 4D execution, GeDialog is disabled.

So its a limitation, and as said by zipit there is no Tkinter shipped with Cinema 4D in order to force people to use Cinema 4D dialog.

So possible workarounds are:

• Install pip and install any 3rd party GUI module (but this is not officially supported by Cinema 4D so you may have some odd issues, but it should work).
• Execute a python script before from a system python installation that will create the Dialog and later execute c4dpy to do the Cinema 4D work.

Cheers,
Maxime.

Hi in C++ there is the BaseList2D.IsNodeBased method to check if a BaseList2D contains nodes and more interesting there is the NodeMaterial class that represents a Nodal Material, unfortunately, both are not available in Python.
Note also that any type of material can be evaluated to a NodeMaterial and this will add the MaterialData the ability to use NodeGraph.

So I confirm the only reliable way in Python to know if a material is a NodeBased one is to check the description.

If you want to explicitly create a NodeBaseMaterial the only way for you do to do so is via CallCommand with

c4d.CallCommand(202541) # New Node Material

Cheers,
Maxime.

Hi @wob there is noting built-in for that in Cinema 4D. but you can use the regular python way to kill the current process

import signal
import os

os.kill(os.getpid(), signal.SIGTERM)

But I just let you know, that it may be useless by nature python should be pretty good at not creating any memory leak, and should free the data as soon as possible, moreover your approach ( I don't know the whole pipeline) but may also be a big issue for a user since this will clause Cinema 4D without asking for saving. People may lose their work. So I really encourage you to be very careful with the use of this.

Cheers,
Maxime.

Hi @wob please make use of Q&A Functionaility and tagging system for the next time see How to post Question.
Moreover, the python_init.py is called before any plugin registration as stated in the documentation see pytohn_init.py
So your best bet is probably to have a PluginMessage and check for C4DPL_STARTACTIVITY.

Regarding your question, this means you open a scene(LoadFile does it) but in this file, there is one plugin called signal (https://greyscalegorilla.com/downloads/signal/) which is not installed on your Cinema 4D version, so Cinema 4D advertise you that the scene may not work as expected.

Cheers,
Maxime.

Hi @Cairyn, this also impacts C++, I don't see any workarounds, unfortunately, I've opened a Bugs report about it.

Cheers,
Maxime.