Topics created by peterakos

hello,

without further addition on your part, this thread will be considered as solved tomorrow.

Cheers,
Manuel.

Thank you for your help !

Hello,

I tested it with the Gradient Shader example from the cinema4dsdk and it works fine as far as I can tell.

I just removed the check for ASSETDATA_FLAG::TEXTURESONLY:

Bool SDKGradientClass::Message(GeListNode* node, Int32 type, void* data) { switch (type) { case MSG_GETALLASSETS: { AssetData* const assetData = static_cast<AssetData*>(data); // checks if only texture assets should be added if (assetData == nullptr) return true; BaseList2D* const baseList2D = static_cast<BaseList2D*>(node); if (baseList2D != nullptr) { // get the file name const Filename path = baseList2D->GetData().GetFilename(GRAD_FILE); // check if the file name is set if (path.IsPopulated()) { // add the file name assetData->Add(path, nullptr); } } break; } } return SUPER::Message(node, type, data); };

Regarding Shader hierarchies: I guess you can send the message to your child-shaders yourself, to make sure they receives the message.

best wishes,
Sebastian

Shouldn't STEP be used to set this precision?
Or is there a limit for STEP?

Hello.

The problem was that I didn't add the definitions.

iferr_scope;
signal = maxon::ConditionVariableRef::Create() iferr_return;

Thank you for your time and sorry for that 😞

Hello.

Thank you very much for your clarification on this.
I have a button in MaterialData that saves the material in a specific format in the disk.
I doesn't change anything in the material but the MSG_UPDATE is sent anyway.
So, since I don't want to run the MSG_UPDATE handler, I have to set a flag to true in order to skip it.

Thank you.

Thank you very much for your support !

Hi Petros, glad that you get it fixed.

With regard to buffer allocation via AllocateBuffer, being those buffer handled by Cinema, they are automatically released as soon as the multipass bitmap containing such buffers are passed to the PictureViewer.

Best, Riccardo

Hello.

I have solved it by using SpecialEventAdd and sending a message to dialog's CoreMessage.

Thank you.

Hi Petros, in order to have the MATPREVIEW_PREPARE_SCENE being dispatched, you've to set MatPreviewObjectInfo::bNeedsOwnScene to true. At the same time also MatPreviewObjectInfo::bHandlePreview needs to be set to true when the host object is responsible for the rendering.

Finally I think that looking at MATPREVIEW enums can be helpful as well.

Best, Riccardo

Hello,

LoadDialogResource() and LayoutFlushGroup() should work perfectly fine together. Typically LayoutFlushGroup() is called in reaction to some user interaction or in InitValues():

Bool CreateLayout() { if (!GeDialog::CreateLayout()) return false; if (!LoadDialogResource(11000, nullptr, 0)) return false; return true; } Bool InitValues() { LayoutFlushGroup(11003); AddButton(100, BFH_SCALEFIT, 0, 10, "Button"_s); LayoutChanged(11003); return true; }

best wishes,
Sebastian