Hi WickedP, thanks for reaching us.

Can you please better explain the final intent of your request? Is the document displayed in viewport (which means it's the active document)? Or is it just a cloned document being hold in "memory"?

That said, supposing that you've your document displayed in the editor, beside the option to invoke CallCommand, there's no built-in function or method to invoke, but rather, as already depicted by @fwilleke80 you can think of doing something like:

for each object in all objects:
  get object bounding box center and radius
  evalute the bbox max and min and update the overall bbox

reposition the editor camera target in the center of the overall bbox 

for each overall bbox vertex:
  convert from world to screen space
  verify that's inside the frame of the editing camera 
  if not in frame:
   zoom out a little and recheck if vertex is now in frame

Hi mp5gosu, thanks for following up.

I see your point, but actually you can still initialize the member variables to a "reasonable" default value helping to identify cases when the class was instantiated without any explicit value.

A final, additional, side note about initialization: considering that constructors can't return any "evidence" of failure when allocating members we advise against initializing members directly in the constructor.
We rather suggest implementing an additional Init() method where the members' initialization takes place as shown in the code snippet in the Entity Creation section.

Best, Riccardo

Hi guys, thanks for your comments on the topic. We do appreciate your effort in trying to keep this place tidy and clean.

We've considered a few options and a better spam-prevention mechanism are now in place.

Cheers, R

Hi Rage thanks for reaching us.

With regard to your question, please consider that it was already discussed in the past in this thread.

Long story short you can set the scene scale simply using

def main():
    # check the current values for the currently active scene
    # for default scene it returns (1.0, 3) where scale is "1.0" and unit is "cm"
    print "current scale:", doc[c4d.DOCUMENT_DOCUNIT].GetUnitScale()

    # instantiate an UnitScaleData()
    sclData = c4d.UnitScaleData()
    # set the data accordingly to your needs
    # e.g. scale by 10x and set to mm units 
    sclData.SetUnitScale(10, c4d.DOCUMENT_UNIT_MM)
    # set the proper parameter in the active doc
    doc[c4d.DOCUMENT_DOCUNIT] = sclData
    # fire an EventAdd() 
    c4d.EventAdd()

    # check the new value
    print "new scale:", doc[c4d.DOCUMENT_DOCUNIT].GetUnitScale()

Finally, to speed up your issues' resolution, I warmly encourage making use of the search function.

Best, Riccardo

Hi Petros, sorry for getting late here.

I've tried to replicate the behavior you're reporting, but unfortunately I've succeeded in.
The way i usually handle buffer fill-up in VPData is :

...
VPBuffer* rgba = render->GetBuffer(VPBUFFER_RGBA, 0);
Int32 rgbaBufferCPP = NOTOK, rgbaBufferDepth = NOTOK, rgbaBufferWidth = NOTOK, rgbaBufferHeight = NOTOK;
if (rgba)
{
    rgbaBufferCPP = rgba->GetInfo(VPGETINFO::CPP);
    rgbaBufferDepth = rgba->GetInfo(VPGETINFO::BITDEPTH);
    rgbaBufferWidth = rgba->GetInfo(VPGETINFO::XRESOLUTION);
    rgbaBufferHeight = rgba->GetInfo(VPGETINFO::YRESOLUTION);
    DiagnosticOutput("rgbaBuffer: @ / @ / @ / @", rgbaBufferCPP, rgbaBufferDepth, rgbaBufferWidth, rgbaBufferHeight);
    
    if (rgbaBufferDepth == 32)
    {
        iferr (rgbaBuffer = NewMemClear(Float32, rgbaBufferWidth * rgbaBufferCPP))
        {
            CriticalOutput("Failed to allocate rgba 32-bit buffer");
            return RENDERRESULT::OUTOFMEMORY;
        };
    }
    else
    {
        iferr (rgbaBuffer = NewMemClear(UChar, rgbaBufferWidth * rgbaBufferCPP))
        {
            CriticalOutput("Failed to allocate rgba 8-bit buffer");
            return RENDERRESULT::OUTOFMEMORY;
        };
    }
}

Float percent = 0.0;
while (percent < 1.0)
{
    for (Int32 i = 0; i < rgbaBufferHeight; i++)
    {
        if (rgbaBuffer)
        {
            if (rgbaBufferDepth == 32)
                r_gigante::FillBufferWithRandomValues((Float32*)rgbaBuffer, rgbaBufferWidth, rgbaBufferCPP);
            else
                r_gigante::FillBufferWithRandomValues((UChar*)rgbaBuffer, rgbaBufferWidth, rgbaBufferCPP);
        
            rgba->SetLine(0, i, rgbaBufferWidth, rgbaBuffer, rgbaBufferDepth, true);
        }
        
        if (thread->TestBreak())
        {
            if (rgbaBuffer)
                DeleteMem(rgbaBuffer);
            return RENDERRESULT::USERBREAK;
        }
    }
} 
...

where FillBufferWithRandomValues is

void FillBufferWithRandomValues(Float32* buffer, UInt32 bufferSize, UInt32 channels/* = 4*/)
{
	Random rng;
	rng.Init(UInt32(rand()));
	if (channels == 4)
	{
		for (UInt32 i = 0; i < bufferSize; i++)
		{
			buffer[i * channels + 0] = Float32(rng.Get01());
			buffer[i * channels + 1] = Float32(rng.Get01());
			buffer[i * channels + 2] = Float32(rng.Get01());
			buffer[i * channels + 3] = Float32(0);
		}
		return;
	}
	
	if (channels == 3)
	{
		for (UInt32 i = 0; i < bufferSize; i++)
		{
			buffer[i * channels + 0] = Float32(rng.Get01());
			buffer[i * channels + 1] = Float32(rng.Get01());
			buffer[i * channels + 2] = Float32(rng.Get01());
		}
		return;
	}
	
	if (channels == 1)
	{
		for (UInt32 i = 0; i < bufferSize; i++)
		{
			buffer[i * channels + 0] = Float32(rng.Get01());
		}
		return;
	}
}

(NOTE - in my code the FillBufferWithRandomValues has definition for both 8-bit and 32-bit buffers)

If you can provide with a complete example showing your issue, I'd be glad to look into, but being blind to your code I really can't be more helpful.
With regard to the second question, I think the above code properly answers here.

In case you got your issue fixed, please mark this thread as solved.

Best, Riccardo

Hi Bentraje,

with regard to computing the area of a non self-intersecting planar polygon you can use:

# area of a polygon using 
# shoelace formula 
  
# (X[i], Y[i]) are coordinates of i'th point. 

def polygonArea(X, Y, n): 
    # Initialze area 
    area = 0.0

    # Calculate value of shoelace formula 
    j = n - 1
    for i in range(0,n): 
        area += (X[j] + X[i]) * (Y[j] - Y[i]) 
        j = i   # j is previous vertex to i
    # Return absolute ;
    return int(abs(area / 2.0)) 

Best, Riccardo

Hi Andi, first of all no need to apologize at all. My work IS to be interrupted and to be as much as possible helpful to our developers!

In order to port/migrate/adapt code pre-R20 to R20, I kindly recommend to read the Plugin Migration section in our documentation where it's properly explained how make this transition happen.

Do I have to create this file manually in all plugins folders?

Yes, projectdefinition.txt should be created for both the project and solutions. The SDK shipped with Cinema has a few projectdefinition.txt files which clearly show where and what to write in.

Do I have to run the project tool over these folders once the projectdefinition.txt file is there?

Yes, the projecttool should be run on the whole folder that contains the sdk where both frameworks and plugins are located.
The projecttool is indeed responsible to create both VisualStudio and Xcode project/solution files, so running once you get your IDE-required files properly created.

But in our R 19 plugin folders these files are already existing. Would it be enough to put an additional projectdefinition.txt into these folders?

My suggestion is to use a completely different folder for your R20 plugins and to structure it as follow:

<plugins folder>
    |-<project a>
    |-<project b>
    |-<project x>
    |   |-project
    |   |   |- projectdefinition.txt
    |   |-source
    |       |-source_1.cpp
    |       |-source_2.cpp
    |       |-...
    |       |-source_n.cpp

Then run the projecttool and you should be provided with all the needed files for VisualStudio.

Let me know if something is still unclear or missing.

Best, Riccardo

Hi mike, first of all thanks for providing feedback on the Python API.

1. GetPoint() isn't return accurate postion, just initial postion.please note or append another method(maybe already have?)

PointObject::GetPoint() is indeed accurate and it's supposed to return the position of a point regardless of the affine transformation operated by the global transformation matrix belonging to the BaseObject the PointObject inherits from. This grant a proper design where linear motion-blur doens't require the points to effectively move in space.

2. Matrix.mul(other) (matrix * matrix)
   ususlly computational order is 'left to right' , such as handwriting or Matlab, but here is 'right to left' ,could you make some changes?it is trouble to adapt.

Matrix::Mul() actually is used to left multiply a vector by a matrix

    transformed_vector = transformation_matrix.mul(original_vector)

To multiply matrices instead simply use the "*"operator

    matA = c4d.Matrix() 
    matA.v1 = c4d.Vector(3.0, 9.0, 27.0)
    matB = c4d.Matrix()
    matB.v3 = c4d.Vector(8.0, 4.0, 2.0)
    print matA * matB
    print matB * matA

3.maybe c4d.utils.QSlerp(q1,q2,alfa) is 'spherical interpolation' and c4d.utils.QBlend(q1, q2, r) is 'Linear interpolates '?

Yes, your guess it's right. c4d.utils.QSlerp is spherical interpolation for quaternions whilst c4d.utils.QBlend is the linear interpolation.

Last but not least, please mark your initial post as "Ask as a question" from the Topic Tools menù, and if the answer provide is correct don't forget to set the answering post as "Mark this post as correct answer" from the three-vertical dots menu.

Best, Riccardo

Hi ello, first of all thanks for getting back with the code fragment.

Analyzing the fragment provided I've ended up in a list of comments:

• why the "Dependency List" approach is used twice in your code to check children dirty status?

• why the "Dependency List" approach is used in combination with BaseObject::GetAndCheckHierarchyClone()? In the BaseObject Manual they are properly described and making them working in-cascade can actually lead to unexpected behaviors.

• most of your code completely lacks pointer validity check; I warmly suggest to extend such a type of check to the whole code snippet to be user that unallocated pointer's methods are not called resulting in a message like "CINEMA 4D.exe hat einen Haltepunkt ausgelöst."

• what does it mean when the debugger holds at a line like that,
  Vector rndoffset = bc->GetVector(RNDOFFSET);
  with a message "CINEMA 4D.exe hat einen Haltepunkt ausgelöst."

  it simply means that the bc pointer is likely to be invalid.

Last but not least, considering that in the very net days I'll be pretty busy for the DevKitchen 2018 preparation I can't engage longer discussion or provide thoughtful answers, but back from the event I'll be eager to assist further. One last question: what is the intended delivered functionality of your ObjectData?

Best, Riccardo

Hi Roger,

sorry come coming with a little bit of delay here, but actually the question was not that easy to address.

The "Deformers" flag enabled in the Advanced tab of Cinema Hair actually execute something like:

• create a dummy spline for each hair based on the hair definition
• deform the dummy spline by applying the modifier stack found under the hair object
• use the deformed spline data to overwrite the hair primitive

What is important to note is that in the end what is actually rendered is still an hair primitive and not the deformed spline.
As additional note the hairs are not represented in the scene as real geometry that's why you can't find any evidence in the Active Object Dialog since the hair renderer is not handling with 3D data but delivers a representation of hair in 2.5D space where geometry is not needed.
Finally the primitives which can be currently rendered are those satisfying the following expression (obj is the object being evaluated by the hair renderer)

obj->GetType() == HAIR_STYLE_OBJECT_ID || 
obj->IsInstanceOf(Opolygon) || 
obj->IsInstanceOf(Ospline) || 
obj->IsInstanceOf(Oline)) || 
obj->IsInstanceOf(Oparticle) || 
obj->GetType() == ID_TP_PARTICLEGEOMETRY

That said since I see no reason to deny deformed splines to be rendered by the hair renderer, I'm going to file a bug report on this regard.

Best, Riccardo

Hi Daniel, thanks for reporting.
We've not reported by others about this issue, nor we've seen this happening on our profiles. However I'll research next week to see what could be the cause.

Can you confirm which notification is missing? Email notification, forum notification or both?

Cheers, R

The updated version of the projecttool is available at this link.

Hi @mp5gosu, thanks for pointing it out but we prefer to stay consistent with the company new color palette.

Best, Riccardo

Fixed in S24

Hi community,

with the PluginCafè UI refresh from yesterday we are now shipping also on a dark-skin.

You can switch it by going to your profile settings and at the bottom of the page switch to Dark in Select skin for theme. Be sure to refresh your browser cache and you should be good to go!

Cheers, R

@Cairyn: thanks to nodeBB folks, the issue of infinite scrolling / infinite flickering should be resolved now.

Please let me know if it persists on your side, R

Hi @Cairyn, I've tested on different OS (macOS, Windows, Linux) and different browsers (Safari, Edge, Firefox) and, although I've spotted some other issues, I'm capable to dynamically scroll down like in an infinite scrolling mode.

The infinite scrolling mechanism although has a little lag that is "physiological" and can't be avoided: once reached the end of the scroll give the browser a little to refresh and load further pages.

What instead I'm still trying to fix is a sort of "infinite flickering" issue as visible below

I'll try digging down and for the time being as suggested by @ferdinand the best way to avoid this UX flaw is to active pagination under the User Settings

Downtime timeframe updated

Hi @rsodre, a quick update from Pixar that hopefully shall address your issue

From: Ivan Kolev [email protected]
Subject: Re: [PixarAnimationStudios/USD] Deadlock loading usd (#1341)
Date: 22 March 2021 at 11:53:37 CET

We resolved this by switching our plugin to refer to the copy of libtbb.dylib included with C4D's USD module, using install_name_tool -change

As our plugin runs on 3 platforms and on 3 hosts (3dsMax/Maya/C4D), our approach to TBB usage is to rely on its full backward compatibility: we compile/link against the oldest version that does the job for us (4.4) and expect that the hosts provide newer versions.
In case of C4D we didn't do that because C4D doesn't include TBB in its main application, though some of its external modules do include their own copy of TBB. Similar to the other modules, we included our (old 4.4) copy of TBB.

But this was no problem until now, the copies of TBB carried by C4D's modules haven't interfered in any harmful way. And the new USD module in R23 didn't change that.

The source of the problem here is probably the fact that our plugin links to our own static copy of USD, which causes USD to be loaded twice, along with two different copies of TBB (and maybe the version mismatch is not important).
So, linking against C4D's copy of TBB resolved the TBB deadlock problem, but we have now a new duplicate symbol problem, which I opened a new issue about: #1479

Cheers, R

Hi Lars, thanks for reaching out to us.

At the moment the latest version of Cineware SDK is 22 and it does not come with arm64 support.

Next version is instead going to support it.

Best, Riccardo