Hi @Leo_Saramago thanks for reaching out to us.
With regard to execution priority, as you've already spotted, the scene nodes are evaluated after generator because classic Cinema items can indeed be used as entry point for the node graph. With regard instead to nodes graph execution priority, nodes are executed left-to-right, or better said, a node is evaluated when its input ports have received the needed data from the “preceding" nodes!
Hope it answers your question.
Riccardo
@ECHekman said in Compiling material nodegraph to shaders:
I take it this also means its not possible to manually convert node ourselves?
Right.
Thanks @ceen for reaching out to us.
I'll make aware Maxon ppl responsible for the animation area about your request and leave it, for the time being, to community on offering support.
Best, Riccardo
Hi @ECHekman, thanks for reaching out to us.
With regard to your question, at the moment with current API, is not possible to traverse a node-based material shader graph and consequently to convert to other convenient datasets.
As said already in other threads, it's under our radar and we hope to share soon updates on this regard.
Cheers, R
Hi @delizade, thanks for reaching out to us.
The PythonTag associated to an object is evaluated, by default, every time Cinema 4D evaluates the scene and this can happen even if the object has not changed at all.
Finally, without more details on the PythonTag code, its design and the ultimate goal, I can only think about of the simple solution of caching the last userdata value in the PythonTag's container and compare, before running your tag's business logic, it against the value found in the userdata.
Cheers, R
Hi @delizade, thanks for reaching out to us.
With regard to your question I've a few considerations to share:
%APPDATA%/MAXON/{cinemaversion}/python37/libs, if they are referred only to a specific Cinema version or in %APPDATA%/MAXON/python37/libs if they are supposed to be seen by all Cinema(s) installed on your machine (see here for further info);c4d.EventAdd() adds an event to the Cinema 4D events queue, and it's not responsible for the tag to not be executed "infinitely". Consider that a Python tag is executed every time the scene is evaluated so the behaviour your mention is consistent with the code posted.Given said that and with regard to
@delizade said in How to use/import another script file in Python tag correctly?:
've solved the issue
c4d.EventAdd() was added end of my external function script. I removed it and used it in tag script. I think after that line python tag was triggered again.
I can't see, guessing your code I've reported below, how you stopped the PythonTag to be executed "infinitely".
import c4d
import test
def main():
print ("test")
customCode.myFunction(op)
Cheers, Riccardo
@fwilleke80 Thanks for the follow-up Frank! In all the previous cases I always notarized without specifying the timestamp. I'll again and in case update the guide.
Cheers, r
@fwilleke80 said in Plugin compiled on macOS Catalina for R23, not working on Big Sur?:
- Can you ask your customer what "usual" security questions he answered?
- Can you ask your customer before unpacking the zip archive, that maybe he has downloaded from an email or a website, to run
$ xattr -d "com.apple.quarantine <zip archive to your plugin>"Ah, thanks, I'll ask him to try that!
So, to make the plugin run on my beta testers' Macs with Bir Sur without warnings, I not only need to sign the binary, I also need to send the binary to Apple to have it notarised? Every single time I release a beta version to my testers??
Cheers,
Frank
This is actually what we do in our building pipeline. My suggestion is to automate the process which, being completely terminal based, should be far from being rocket science.
Cheers, R
Thanks @kbar it's clear to me, I just wanted to know what actually @fwilleke80 was meaning. And for those listening you can sign a plugin during or after the building process.
Cheers, R
Hi @fwilleke80, looking at our code base this statement is no more active in recent versions of Cinema.
What accompanies the code is Change to WarningOutput as Installer needs to run without objects module but, honestly, given the vague description is hard to further comment and being it R20 it doesn't allows us to invest more time on it.
Cheers, R
Hi @JohnThomas, consider that spline generators using children as input are not officially supported and the solution offered, although can show from case to case performance penalties, it's the sole way to go.
Forgive my ignorance, but do native Cinema objects face this sort of overhead?
Yes, they do.
Would this amount of overhead be a limiting factor?
It heavily depends on the implementation, but I'm pretty confident to see it as a little overhead.
Cheers, R
Hi @fwilleke80, I'm using 11.3 and I've no issue on running the plugin BigSur.
With regard having the code running on your customers' machine I think you need to notarise (is it what you mean by sign my plugins?) the plugins before giving them otherwise the security mechanism found in BigSur might easily have block them.
He has answered the usual security question that macOS shows him (as I don't sign my plugins yet), but no success.
$ xattr -d "com.apple.quarantine <zip archive to your plugin>"Cheers, R
Hi @JohnThomas, sorry for the delay in getting back to you.
This topic was throughly discussed in a few threads already which I warmly recommend to look for.
The first was back in 2016 with GetVirtualObjects v GetContour for Spline Gen which ended up in the creation of the Offset-Y Spline example available on @dskeithbuck / @dskeith GitHub repo.
The second came on 2019 with GetRealSpline() not returning a result where @m_adam also come in to refine the Offset-Y Spline code in this post.
Reading it and dissecting the code will answer all your answers.
Last but not least, the spline example is registered passing the OBJECT_INPUT flag which as throughly discussed on OBJECT_INPUT Child Updating doesn't work in combination with Dynamic Tags.
Cheers, R
Hi @ResolveDZN,
being the issue reported not directly connected to Cinema 4D development, please submit it to the Maxon Support Portal.
Cheers, R
Hin @lasselauch, with regard to the issue mentioned it looks like it's somehow similar to what has been already reported on this thread and based on customers feedback, it seems that wiping out and reinstalling Cinema solved the issue.
However it's important to note that Cinema 4D R23 is supported on macOS 10.14.6+ or higher, and in this case the minimum requirements are not matched.
Cheers, R
Hi @JohnThomas, first and foremost I sincerely apologise for getting back to this thread so lately.
A few notes on your code that are very likely to prevent your cubes to disappear:
ObjectData::GetVirtualObjects() is not supposed to return a nullptr but rather return a BaseObject::Alloc(Onull);BaseObject::AddDependence()BaseObject::GetHierarchyClone() without storing its results in somewhere and I also have doubts on the combination of HIERARCHYCLONEFLAGS you used.poly->GetMg()) calling any method belonging to the instance it points to or accessing its data ( see accessing posArray values)I recommend to have a look at the Generating section of the BaseObject Manual where fundamental concepts about BaseObject generation are explained.
Cheers, R.
As already told by @zipit, I'm terribly sorry for coming so late here.
I've prepared a full example showing how to fill a VertexColorTag in the ObjectData::GetVirtualObjects() and use this values to color the triangles shown up in the ObjectData::Draw() method. My code actually uses the VertexColorTag::SetColor()/GetColor().
The VertexColorTag in this case is not specify to each vertex of the triangle but specifies the color for the whole triangle: this is because the tag is created in the ObjectData::GetVirtualObjects() and store color for each point of the cloud, but then it's used in the ObjectData::Draw() method to specify the ObjectColorProperty used to color the drawn PolygonObject. As far as I know the BaseDraw::DrawPolygonObject() ignores any VertexColorTag assigned to the PolygonObject to be drawn.
BaseObject* PC_12974::GetVirtualObjects(BaseObject* op, HierarchyHelp* hh)
{
// check cache before continue
BaseObject* cache = op->GetCache();
if (cache)
return cache;
// init the random gen and get a arbitrary number of tris
_rndGen.Init(GeGetTimer());
_randomTrisCnt = (SAFEINT32(_rndGen.Get01() * (1 + _max - _min)) + _min);
// allocate a PolygonObject and fill it with points randomly
PolygonObject* po = PolygonObject::Alloc(_randomTrisCnt, 0);
if (!po)
return BaseObject::Alloc(Onull);
// fill the points array with random positions
Vector* points = po->GetPointW();
for (Int32 i = 0; i < _randomTrisCnt; i++)
points[i] = Vector (100.0 * _rndGen.Get11(), 100.0 * _rndGen.Get11(), 100.0 * _rndGen.Get11());
// look for VertexColor tag
BaseTag* tag = po->GetTag(Tvertexcolor);
// if not existing just create a new one
VertexColorTag* vcTag = nullptr;
if (!tag)
{
tag = VertexColorTag::Alloc(_randomTrisCnt);
po->InsertTag(tag);
}
vcTag = static_cast<VertexColorTag*>(tag);
vcTag->SetPerPointMode(true);
VertexColorHandle handle = vcTag->GetDataAddressW();
// fill the vertexcolor tag with random values
for (Int32 i = 0; handle && i < _randomTrisCnt; i++)
VertexColorTag::SetColor(handle, nullptr, nullptr, i, maxon::Color32(_rndGen.Get01(), _rndGen.Get01(), _rndGen.Get01()));
// update host object
po->Message(MSG_UPDATE);
return po;
}
Bool PC_12974::TriangleOnPoint(const Vector &pos, PolygonObject& po)
{
// given a point create a triangle centered over there.
Vector* points = po.GetPointW();
const Matrix poMG = po.GetMg();
const Vector posMG = poMG * pos;
if (!points)
return false;
// set vertexes positions for the triangle.
points[0] = Vector(0, 0, _triangleRad) + posMG;
points[1] = Vector(_triangleRad * Cos(-PI / 6), 0, _triangleRad * Sin(-PI / 6)) + posMG;
points[2] = Vector(_triangleRad * Cos(-PI * 5 / 6), 0, _triangleRad * Sin(-PI * 5 / 6)) + posMG;
// create the polygon
CPolygon* polys = po.GetPolygonW();
if (!polys)
return false;
polys[0] = CPolygon(0, 1, 2);
return true;
}
DRAWRESULT PC_12974::Draw (BaseObject *op, DRAWPASS drawpass, BaseDraw *bd, BaseDrawHelp *bh)
{
// skip anything but OBJECT drawpass
if (drawpass != DRAWPASS::OBJECT)
return DRAWRESULT::SKIP;
// check for the object and its cache
if (op && op->GetCache())
{
// get the PolygonObject from the cache
PolygonObject* opPO = static_cast<PolygonObject*>(op->GetCache());
// look for the attached VertexColor Tag
BaseTag* const tag = opPO->GetTag(Tvertexcolor);
if (!tag)
return DRAWRESULT::SKIP;
VertexColorTag* const vcTag = static_cast<VertexColorTag*>(tag);
// retrieve the read-only handle
ConstVertexColorHandle vcTagHandleR = vcTag->GetDataAddressR();
// get the points and iterate over the VertexColor to set the color
// of each triangle drawn
maxon::Int pointCnt = opPO->GetPointCount();
Vector const *points = opPO->GetPointR();
for (maxon::Int i = 0; i < pointCnt; i++)
{
maxon::Color32 vtxCol(0.0);
// get the color
if (vcTagHandleR && vcTag->IsPerPointColor())
vtxCol = VertexColorTag::GetColor(vcTagHandleR, nullptr, nullptr, (Int32)i);
// set the color in the ObjectColorProperties
ObjectColorProperties colProp;
colProp.usecolor = ID_BASEOBJECT_USECOLOR_ALWAYS;
colProp.color.x = vtxCol.r;
colProp.color.y = vtxCol.g;
colProp.color.z = vtxCol.b;
colProp.xray = false;
// allocate the temp triangle
PolygonObject* tri = PolygonObject::Alloc(3, 1);
// set the color prop, create the tri and draw!
tri->SetColorProperties(&colProp);
if (TriangleOnPoint(op->GetMg() * points[i], *tri))
bd->DrawPolygonObject(bh, tri, DRAWOBJECT::NONE, nullptr);
// free the tri
PolygonObject::Free(tri);
}
}
return DRAWRESULT::OK;
}
Feel free to comment and again sorry for the silence.
Riccardo
Hi @MUR-弑疑, we don't have any date to share at the moment. Rest assured that you'll be promptly notified via the standard channels.
Best, Riccardo
@rsodre please refrain from discussing NDA-protected topics.