Thanks for all the tips @ferdinand The solution was Catalina + XCode 12.4

Thanks @ferdinand, I think that clarifies my issue. I'll what I can do here.

hi, I don't see how we could do it with the Draw Method in a efficient way. Cheers, Manuel

Thanks, seems to be working now, thanks.

Thanks, @zipit that's very clarifying.

We found another AA option on Settings, Viewport Hardware, that performs much better than the View Settings Supersampling, probably using a different technique. Thanks.

Hi, without further feedback, we will consider this thread as solved by tomorrow and flag it accordingly. Cheers, Ferdinand

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

@rsodre please refrain from discussing NDA-protected topics.

@r_gigante good to know, thanks!

@m_magalhaes No hurry, for now there's just one place where I need this, I get it using the BaseContainer. But I will probably use it more often, so if the DOTS example is updated I can replicate the solution to my own type and remove this workaround. Thanks!

Hi @m_magalhaes This was research for a feature I'll start implementing soon, and possible refactor. I'll mark as solved and if there's anything else I need I'll open it again. Thanks.

hi sorry it wasn't clear enough. yes sure, doing documentInfoData->doc->GetDocumentName() is the same as doc->GetDocumentName() I've updated the documentation with Save Project with Assets to be a bit more clear. Cheers, Manuel

@m_adam got it! it's working now. The final code for my float sdf exporter is here.

There is no relationship between BaseContainer IDs and plugin IDs. All you need is a unique ID, that you can use as a BaseContainer ID. This forum (the plugin ID page) provides such IDs.

@r_gigante Thanks, I used an inverse scale matrix wen calculating my gizmo points.

@r_gigante ok thanks! I managed a workaround by filling my dummy spline with two zero length segments at the claculated bounding box limits.

@m_adam , AddEventNotification was exactly what I needed. I created a notification to NOTIFY_EVENT_UNDO, and then add my object to it. Now if I delete anything from my object after a polygon is deleted, it will be restored with Undo. Thanks! case MSG_NOTIFY_EVENT: { CHECK_BREAK( data != nullptr ); const auto eventData = static_cast<NotifyEventData*>( data ); if( eventData->eventid == NOTIFY_EVENT_UNDO ) { NotifyEventMsg* notifyMessage = static_cast<NotifyEventMsg*>( eventData->event_data ); CHECK_BREAK( notifyMessage != nullptr ); if( notifyMessage->msg_id == Int32( UNDOTYPE_DELETE ) ) { eventData->doc->AddUndo( UNDOTYPE_CHANGE, Get() ); } } break; }

@m_adam Hi Maxime, Thanks for this workaround, indeed puts the polygon on the right place. Best, roger

@m_magalhaes Based on the hair_shader.cpp example, I implemented a workaround with a custom shader on the Texture attribute, using calc_sample to sample per segment. Works fine!