Posts made by r_gigante

Hi @mikegold10 thanks for reaching out us.

With regard to your request, you've to distinguish two cases:

• during a rendering process the public VolumeData member of the ChannelData (not of the BaseShader as shown in your code) is valid, you can retrieve the linked BaseTag and, from that, you can access you userdata attached to the TextureTag to find the color of interest
• outside a rendering process, you can use the ShaderData::Draw() to find the BaseTag and, from that, you can access you userdata attached to the TextureTag to find the color of interest.

Best, R

@zipit: I'm a bit confused of your remarks here as well
In my answer I see no reference to BaseObject::GetCache() here and looking at the documentation of both methods reported in the initial boolean expression, to answer first @mfersaoui's question, it results to be True if the cache is dirty or any object's parameter has become dirty.

Cheers, R

Hi @mfersaoui thanks for writing us.

The following line of code is supposed returning True only if parameters of the object changed?

That's partially true: the expression can be True also if the object's cache is dirty

But why it also returning True when my object selected and I Move / Scale / Zoom / rotate the perspective view.

That's weird and to answer here you've to show how you're using it with the rest of your ObjectData::GetVirtualObjects() method.

Best, R

Hi Daniel, after some investigation, it has been found that, as from your special case, having a completely empty dialog (ASYNC_POPUPEDIT) means there's nothing to layout. Therefore, the empty dialog content is centered in the window which means Local2Screen does account for that offset.
That's legacy behavior of the layouter and probably has been like that since the last century.
If the dialog presents items to display the Local2Screen and Local2Global behave correctly as from the tests we ran here.

Best, R

Hi @rsodre I'm sorry but I don't have any update on the bug resolution being it, as already stated, low-prio nor I can share bug-tracking information on a public forum.

Best, R

Hi @nicholas_yue , thanks for reaching out us.

With regard to your question please be aware that C4DAtom::SetParameter() has to be called with DESCFLAGS_SET_USERINTERACTION flag to set ID_CA_XREF_FILE.

Best, Riccardo

Hi @blastframe the NBIT_CKEY_ACTIVE is set when the animation path key is selected in the viewport (and not in the Timeline)

Cheers, R

Hi @blastframe, thanks for reaching out us.

I confirm that there's no handy way - considering how flexible the timeline is - to immediately identify which Timeline is currently active. However, given the consensus about the lack of this feature, I'll file an idea request to our development team.

Best, R

Hi @blastframe thanks for writing us.

Yes, as stated in your second post having unique ids for the different dialog is the safer way to prevent unexpected behavior like the one reported initially. Tested successfully (both main (async) dialog and modal dialog were correctly sized and placed on mac and windows) I also confirm there's no need to specify the subid.

Best, R

Hi @liushu thanks for reaching out us and sorry for the late answer.

As pointed out by @Cairyn exporting a c4d scene from Cinema 4D to FBX format is indeed straightforward (see abc exporter example) on the contrary, Cineware SDK (which in any case doesn't come in a Python flavor) was not designed with this in mind and it's actually not possible without re-creating completely the whole FBX exporter.

Best, R

Hi @bentraje , thanks for pointing it out. We'll get it filled by a future documentation release.

Best, Riccardo

Hi @iluxa7k thanks for reaching out us.

With regard to your question, as already pointed out by @zipit , the Python del statement just is only responsible for decrementing the reference counter for the instance being "deleted" and not to actually free the memory used by the instance itself. This is clearly noted in the official Python documentation on the Note coming along with object.__del__(self) in Python 3 or object.__del__(self) in Python 2 .
Given that, also consider that the del app statement you've described in your first post might not actually deliver the "clean-up" action you're thinking about.

Best, Riccardo

Hi @iluxa7k thanks for following up.

At the moment, as told in the very first answer, there are no updates I can share about the adoption of Python 3 in C4D. Rest assured that this is still under our PMs' radar.

Best, Riccardo

Hi Frank, thanks for reaching out us.

I've played a bit with and I came to this other solution which make no use of BaseBitmap and should provide more coherent results UI-wise.

Looking forward checking how it compares with regard to performances.

maxon::Result<void> OptimizedDrawMultipleHUDText(const maxon::BaseArray<HUDTextEntry>& texts, BaseDraw* bd)
{
	if (!bd || texts.IsEmpty())
		return maxon::IllegalArgumentError(MAXON_SOURCE_LOCATION);

	AutoAlloc<GeClipMap> bgClipMap;
	if (!bgClipMap)
		return maxon::OutOfMemoryError(MAXON_SOURCE_LOCATION);

	AutoAlloc<GeClipMap> clipMap;
	if (!clipMap)
		return maxon::OutOfMemoryError(MAXON_SOURCE_LOCATION);
	
	// get the current view region
	Int32 cr, cl, cb, ct;
	bd->GetFrame(&cl, &ct, &cr, &cb);
	
	// calculate view sizes
	const Int32 viewW = (cr - cl + 1);
	const Int32 viewH = (cb - ct + 1);
	
	// set the BaseDraw matrix and lighting method
	bd->SetMatrix_Screen();
	bd->SetLightList(BDRAW_SETLIGHTLIST_NOLIGHTS);

	// Init HUD clipmap
	if (clipMap->Init(viewW, viewH, 32) != IMAGERESULT::OK)
		return maxon::UnexpectedError(MAXON_SOURCE_LOCATION);

	clipMap->BeginDraw();

	const Vector 	textColor = 255 * bd->GetParameterData(BASEDRAW_HUD_TEXTCOLOR).GetVector();
	const Vector 	bgColor = 255 * bd->GetParameterData(BASEDRAW_HUD_BACKCOLOR).GetVector();
	const Float 	bgTransparency = 255 * bd->GetParameterData(BASEDRAW_HUD_BACKOPACITY).GetFloat();
	
	const Int32 textH = clipMap->GetTextHeight();
	const Int32	drawH = textH + 10;
	const Int32 tX = 5;
	const Int32	tY = (drawH - textH) / 2;

	// set the complete image transparent
	clipMap->SetColor((Int32)bgColor.x, (Int32)bgColor.y, (Int32)bgColor.z, 0);
	clipMap->FillRect(cl, ct, cr, cb);

	for (const auto& it : texts)
	{
		// get text sizes
		const Int32 textW = clipMap->GetTextWidth(it._txt);
		const Int32 drawW = textW + 10;

		// init BG clip
		if (bgClipMap->Init(drawW, drawH, 32) != IMAGERESULT::OK)
			return maxon::UnexpectedError(MAXON_SOURCE_LOCATION);

		// create the BG
		bgClipMap->BeginDraw();
		bgClipMap->SetColor((Int32)bgColor.x, (Int32)bgColor.y, (Int32)bgColor.z, (Int32)bgTransparency);
		bgClipMap->FillRect(0, 0, drawW, drawH);
		bgClipMap->EndDraw();
		
		// blit BG
		clipMap->Blit((Int32)it._position.x, (Int32)it._position.y, *bgClipMap, 0, 0, drawW, drawH, GE_CM_BLIT::COL);
		
		// set text color
		clipMap->SetColor((Int32)textColor.x, (Int32)textColor.y, (Int32)textColor.z, 255);
		
		// draw Text
		clipMap->TextAt((Int32)it._position.x + tX, (Int32)it._position.y + tY, it._txt);
	}

	clipMap->EndDraw();
	
	// set the points coordinates
	const Vector 	pvText[4] = {
		Vector((Float)cl, (Float)ct, 0),
		Vector((Float)cl, (Float)ct, 0) + Vector(viewW, 0.0, 0.0),
		Vector((Float)cl, (Float)ct, 0) + Vector(viewW, viewH, 0.0),
		Vector((Float)cl, (Float)ct, 0) + Vector(0.0, viewH, 0.0)};
	
	// set the UVs coordinates
	const Vector 	pvUV[4] = {
		Vector(0, 0, 0),
		Vector(1, 0, 0),
		Vector(1, 1, 0),
		Vector(0, 1, 0)};

	// draw in Viewport
	bd->DrawTexture(clipMap->GetBitmap(), pvText, nullptr, nullptr, pvUV, 4, DRAW_ALPHA::NORMAL, DRAW_TEXTUREFLAGS::INTERPOLATION_NEAREST | DRAW_TEXTUREFLAGS::TEMPORARY);

	return maxon::OK;
}

Best, R

@zipit said in Isoparm in Deformer plugin:

I might be misunderstanding the quote:
@r_gigante said in Isoparm in Deformer plugin:

Bevel Deformer does nothing with regard to iso-params representation since being it applicable only to polygon objects iso-param representation coincides exactly with the edges representation.

Sorry for the lack of clarity. Let me put it differently: deformers have nothing to do with iso-params creation or deletion: a bend-deformer, to mention one, doesn't create or destroy the LineObject used in the deformed generator to represent the iso-param, but rather applies the deformation to that data as well.

@Danchyg1337: a deformer, when the iso-params visualization is active, is provided with a PolygonObject (the generator's cache) and with a LineObject (the generator's iso-params). In your code you never check the type of object you pass to DeformPlugin::Disconnect and this lead to indeed unpredictable results especially considering the operations you're executing there.

Last but not least, I warmly invite you to have a look at the examples (deformers and generators) shipped with the cinema4dsdk to getter a better understanding on how generators and deformers behave. As a rule of thumb whilst generators are supposed to create new BaseObject (or SplineObject) instances, deformers are instead supposed to modify the data of the generator without destroying those instance.

Best, Riccardo

Hi @Swinn, thanks for reaching out us.

With regard to your question, once you've retrieved the root from the GvNodeMaster, you can traverse the shader graph and considering that a GvNode inherits from a BaseList2D and consequently from GeListNode you can delete it by calling GeListNode::Remove().

Assuming this graph the code below deletes the noise node just by looking, for the sake of simplicity, at its name.

...
    activeMat = doc.GetActiveMaterial()
    
    if activeMat is not None and activeMat.GetType() != 1036224:
        print "Active material is not a RedShift one"
        return
    
    outputNode = activeMat[c4d.REDSHIFT_GRAPH_NODES]
    if outputNode is None:
        print "Output node is not valid"
        return
    
    gvMaster = outputNode.GetNodeMaster()
    if gvMaster is None:
        print "NodeMaster is not valid"
        return
    
    gvRoot = gvMaster.GetRoot()
    if gvRoot is None:
        print "Root node is invalid"
        return
    
    currentNode = gvRoot.GetDown()
    while currentNode is not None:
        if currentNode.GetName() = "RS Noise":
            currentNode.Remove()
            break
        
        currentNode = currentNode.GetNext()
    
    print "Node removed"
...

Best, Riccardo

Hi @Danchyg1337, thanks for reaching out us.

With regard to your question, I'm a bit confused because iso-parametrics are actually lightweight representations of geometrical elements which being governed by parameters can be drawn using curves defined by the driving parameters having the same value.
This usually applies to rational and non-rational surfaces where the s and t parameters can represent s and t iso-parametric curves defined by the locus of points characterized by the same parameter value.

In the case of a generator, this is meaningful because, depending on the math behind the generator, you could take advantage of the iso-params representation but for a modifier I really don't get it. Usually modifiers when applied in a representation where iso-params are shown, automatically deform the isoparametric curves (check for example applying the bend deformer to a sphere represented via iso-params)

Assuming that the code you've posted is running in a BaseObject::ModifyObject() method then BaseObject::SetIsoparm() can not be called from there.
Finally, to my knowledge, deformers like the Bevel Deformer does nothing with regard to iso-params representation since being it applicable only to polygon objects iso-param representation coincides exactly with the edges representation.

Cheers, R

@zipit said in Change a rendering parameter in python xpresso node:

Hi,
I am a bit confused. If you have the plugin id, I do not quite understand what exactly the problem is.

You're right @zipit, nothing to get confused about it was just me taking a different mind path. Your proposed approach is indeed correct and also more effective. Thanks for pointing it out!

Hi @Passion3D, thanks for reaching out us.

With regard to your request, please consider that you can access the currently active document using the doc instance already existing in the Xpresso Python node. From this instance you can retrive the active RenderData using BaseDocument::GetActiveRenderData and from here retrieve the first BaseVideoPost using RenderData::GetFirstVideoPost().
Given the first BaseVideoPost, you can iterate over the videoposts until you find the right one and then change the parameter by accessing by reference its BaseContainer via BaseList2D::GetDataInstance().

The code below attempts to modify the Filter Size of the ProRender videopost given the FilterDriver as Float parameter of the Xpresso Python Node.

import c4d

def main():
    # check doc
    if doc is None:
        return

    # get the active RenderData
    activeRD = doc.GetActiveRenderData()
    if activeRD is None:
        return

    # get the first BaseVideoPost
    firstVP = activeRD.GetFirstVideoPost()

    # check and eventually make the change
    if firstVP.IsInstanceOf(1037639):
        firstVP.GetDataInstance()[c4d.VP_GPURENDERER_FILTERSIZE_OFFLINE] = FilterDriver

Hi @SolarPH, thanks for reaching out us.

With regard to your question, actually initializing the InExcludeData has nothing to do with having the list not including duplicates.
The v parameter pointed out in the documentation is used to fill the to-be-created InExcludeData with the values found in the passed InExcludeData as @zipit has shown in line 48.
To avoid duplication instead you've to manually browse the items in the lists and pickup from the second only those not found in the first. Again @zippit code perfectly shows this.

Cheers, R