Extra info! While I had set this topic as solved, without an actual WORKING solution being provided, I simply wanted to point out for future reference that R16 - R19 has a slight different behaviour. As with R20 and R21 the first time the dialog is opened it gets positioned centered on the current mouse position. On all subsequent opening it gets positioned with its upper left corner at 0,0. Something got "fixed" between R19 and R20, but not "fixed enough".

Hi Cayring this is indeed a bug I'm going to report them and fix them (both for BaseMaterial and shader) as soon as possible :) If you have other cases like that please report them. I set the topic as solved, I will bump this topic once the fix will be available. Cheers, Maxime.

Hi, thanks a lot. I've opened a bug entry for that one. It will be fixed in a futur release. Cheers, Manuel

Thanks for the response, that's exactly what I needed. John Thomas

Great, thank you.

Yes, Thanks. :)

@m_magalhaes, thanks

You're welcome, Manuel. Actually, I usually prepare all the textures and mapping to be in UVW mapping, when texturing is required. But, mainly, what I need is exporting geometry that is animated.

@r_gigante Thanks. This is what I assumed.

Hi, This is solved in the last documentation update. Cheers, Maxime.

@m_adam Thanks, Maxime, for the temporary workaround and for bumping it to the development team. I hope this is fixed soon!

Hi, This is solved in the last documentation update, see BaseBitmap.ScaleIt. Cheers, Maxime.

@r_gigante Thank you for checking in and updating! I'll keep a keen eye on the thread, if you need me to test anything just shout.

This bug is now resolved in R21 sp2. Cheers, Maxime

Yes your code could be optimized but we agree with you here this is not really the point, a R20 code is expected to have the same performance with R21 and here this is not the case. And @C4DS I agree using GeIsMainThread() == false I would say partially fix the issue (sometimes it works as R20, sometimes not) We keep investigating it. Cheers, Maxime.

Hello, We've talked about this issue in our morning meeting. Contrary to what I've said, it's Core related and not API related. (limitation of cinema4D itself in fact) You have to open a ticket in our support. Tell them you are coming from our forum and it's not related to the API and it's a Core Problem. Sorry for wasting a bit of your time but we need to keep organized. Cheers, Manuel

Hello Sorry for the delay, Christmas time didn't helped. I've opened a bug entry for that issue. I'll be back when i'll have more information. I've added the "Bug report" tag to this thread Cheers, Manuel

Still not I will update you as soon as I have some news. Cheers, Maxime.

This bug is now resolved in R21 sp2. Cheers, Maxime

@r_gigante Hi Riccardo, Thanks for the explanation. I wasn't sure that a "Solved" thread would still get revisited by SDK team members. As Manuel mentioned "I'll come back when I got more information", but the thread was set to solved, I wasn't sure the thread would get an update. Also, others visiting the forum (now or in future) might be misleaded by the state of the thread, thinking that the bug has been fixed, while it actually isn't. But now I understand a "bug fixed" tag is being added. Seems I need to pay more attention to the tags, as I assumed these tags were added by the creator of the thread. As such, I never really paid any attention later on, as I assumed the tags I added were the only ones to be available for that thread, and only the unsolved/solved state would change as a result of a resolution. Thanks for clarifying.