Thank you for the kind help! @m_adam: The plug-in you have linked is very useful. I could fix some problems with the "Select polygons by normal direction" function. Working with badly constructed meshes is no fun job either way. Kind regards, Julien.

Thank you! In future I will set the tags.

@mp5gosu Thank you, that is a good tip. I see that Onull=5140 is listed and it looks like all others are in there too! Thom

Thanks very much. (There is so much information to be read!). -Pim

Hi, just want to ask, if can consider this topic as solved. Bye, Andreas

Hello, I'm not really sure I understand what you are doing. Are you operating in a command line version of Cinema? Or is you code reacting to some command line arguments? Are you operating on the currently active BaseDocument? As I said, I don't have Indigo Renderer so I can't test this specific scenario. But when you "change" the renderer, you also have to "create" that renderer video post when operating in a new document. So it is not enough just to change the RDATA_RENDERENGINE parameter. This example shows how to set and create the "Hardware" renderer: renderData = doc.GetActiveRenderData() if renderData is None: return # set Hardware as active renderer bc = renderData.GetDataInstance() bc[c4d.RDATA_RENDERENGINE] = c4d.RDATA_RENDERENGINE_PREVIEWHARDWARE # add Hardware post effect # in Python a BaseList2D object must be created videoPost = c4d.BaseList2D(c4d.RDATA_RENDERENGINE_PREVIEWHARDWARE) renderData.InsertVideoPost(videoPost) c4d.EventAdd() You find general information on RenderData also in the C++ documentation: RenderData Manual. best wishes, Sebastian

That's it! :) Thank you so much, mp5gosu! Cheers, Mark.

@a_block Thank You so much Andreas ! I would like to try all the suggested approaches and hopefully I'll get my issue resolved (except second option is out of my context as I can't use another application). Third potion seems to be the best suited option and I would like to give it a try. Thanks Again...!

Hi, just a small request from our side: Please do not cross post to different forums (this topic on CGSociety). Chances are, you'll make people work for you redundantly. Cheers, Andreas

I already guessed so. Thanks, I think we can close this post. -Pim

"actually, you can still multiply in one line. You just have to multiply a matrix with a vector:..." D'oh! I'm surprised that I didn't try that - tho it doesn't seem as intuitive ("vector = some other vector, being modified by some operations" vs. "vector = a matrix, imposing/operating on some vector", etc.)... do you know why the Vector lost so many direct operators (* other Vector (Dot()), * Matrix, % other Vector (Cross()) - there may be others)? Apparently, you can still '!v' to normalize it (yay), even tho there's a v.Normalize() call... and I can understand why the "Identity Matrix" operator might have changed from '!' to '~'... some of the other changes just seem a bit arbitrary. I've already made all the changes at this point, but thanks for the tip/reply - I'll keep that in mind for future reference. Cheers.

thank you sebastian, this is a really helpful overview!

Now Work Thanks Andreas

I am with the OP. Can we please have an option in future updates where this color picker can be hidden (Python and C++ SDK please). Thanks

This worked. Thank you.

damn. totally didn't look there. sorry. Alfie

Hi Gigante, Thanks a lot for your reply. I'll analyze that and will update you on the results. Thanks again !

Hi, thanks but i managed to fix it. It wasnt a Cinema4d related error. Apparently a bad argument to one of python methods was causing it to return the filepath of the script instead.

Thanks for the solution and explanation Yannick. It's working perfectly now and I can finish converting my scripts.

Thanks dskeith, that code worked perfectly. Thanks for that!