Posts made by r_gigante

The issue has been recently investigated and it should have been just fixed.

Please confirm the links are correct now on your side.

Dear PluginCafé user,

on Thursday, May 27th 2021, from 06:00 to 07:00 CEST, due to planned maintenance activity, the services will be down and unreachable during this period.

Maxon SDK Team

Thanks @C4DS for reporting the recent positive experience.

Unless you experience the issue again in the future, we can consider the case closed.

Hi Daniel, sorry for coming back only now. I think it's a bug that has been introduced with the theme switch we've done but I'm a little bit puzzled because I can't reproduce it consistently.
If you click any of the top-right circle that appears in the notification drop-down, does the bell shows the counter?
Have you tried to clean-up the cookies, or using a browser in private-mode, to reproduce the issue?

Cheers, R

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

hi @Boony2000 , these are Visual Studio Intellisense errors which you can safely ignore. If they bother you switch the filter from "Build + Intellisense" to "Build".

Cheers, R

Hi @Boony2000, thanks for reaching out to us.

From R20 to R21, as expectable, changes took place in the API which led to adapt R20 examples to be compiled against the newer API. I recommend having a look at Changes in R21 in our documentation and adapt your code or the demo examples consequently if you copied them straightly from R20.

I'm also a bit puzzled by your last reply where you stated that errors were all fixed but you confirm that warnings are still around. Can you clarify what warnings look like? Can you also provide a little bit of context in your code where the warning it's likely to take place?

Thanks, Riccardo

Hi Thomas, I'm sad to confirm that at the moment there is no updated version of ResEdit for R23.

Cheers, Riccardo

@kbar said in Plugin compiled on macOS Catalina for R23, not working on Big Sur?:

@fwilleke80 I think setting the hardened runtime when you code sign solves the timestamp issue. I don’t set a timestamp.

codesign --force --options runtime --sign 'Developer ID Application: YOURCOMPANYNAME' 'sdk/plugins/yourplugin/yourplugin.xlib'

Thanks a lot Kent, for pointing this out!
The one below is the string I use which, as said by Kent, doesn't need the timestamp because of the hardened runtime.
codesign -f -s "Developer ID Application: <YOUR DEV ID>" --options runtime <binary file>.xlib

Documentation updated accordingly

Hi @JohnThomas, thanks for reaching out us.

With regard to your question, I confirm that what you see is correct since the deformer provided data is the tessellated representation of the original spline.

Best, Riccardo

Hi @chuanzhen thanks for reaching out us.

With regard to your question, I warmly recommend also thinking of using FindUniqueID and looking at the section BaseList2D Manual::Unique ID or to make good use of BaseLink.

Finally with regard to get the object, either you traverse and compare again the unique ID or, by keeping your BaseLink list updated when add/deletion operations take place, you can look into the list and retrieve desired C4DAtom.

Cheers, R