Hi @litao ,

Sure, for the end-user questions you can always reach out our Support Center.

Cheers,
Ilia

@Dunhou Thanks, I'm having a lot of fun making TP run like a train, I'm trying to optimize the code by vectorizing some functions and gain new FPS. I will keep this post updated on developments as much as possible

@kbar
I am interested in c4d (also cg) plugin development.
But your requirements are a little bit high for me, especially "Strong proficiency in C++ programming language".
I can use c++ for programming but not strongly. But I can also make a c++ plugin like this:
Set View.gif
A part of my code:
A part of my code.png

Entschuldigung. Vielen Dank.

Hello @conductor,

thank you for reaching out to us. You can certainly post a job posting here, but it should happen in the General Talk forum. It can contain everything which is not directly related to one of our APIs but loosely related to CGI or development.

The same applies to this thread of yours, I have moved it to 'General Talk' .

Cheers,
Ferdinand

Hi,

There is the EffectorData class that could help you to create your own effector. This class is only available on c++. With python the only option is to use the python effector. And that could be tricky because you need to retrieve the size of all clones. Doable but tricky imo.

I hope that you will find a developer to do it, this might look easy to do but is harder than you might thought.

Cheers,
Manuel

Hi;

if you're looking for Python development - I'd have some time on my hands. Long-time C4D user and developer (currently creating a Python-for-C4D course actually). Not in the UK though (mainland Europe).

If you want to talk about some details, drop me a mail under cairyn (at) tigress (dot) com.

@JasenLux said in Automate Turbosquid uploading with Python script:

Even if in the morning I've got a bunch or renders done over night - and it's all automated - I'd be very happy.

A more or less automated rendering could be achieved by using the native Render Queue if you create your files with some rigid discipline.

Start out by creating a base C4D file that contains the necessary cameras and render settings with some appropriate naming. The render settings should be hierarchically ordered, with the basic setting on top and all the different resolutions as children of that setting, with only the necessary settings overwritten.

If there are TurboSquid requirements that you cannot achieve with render settings, you can create some takes that offer the necessary changes (this might be the most difficult part, as you may need to overwrite parameters in tags that you don't have in the basic file, but only create with your project, but that very much depends on what you really need to change, I am not familiar with the TurboSquid requirements.

Once that file is set up, you only need to copy your master data into that, save it under the appropriate name, and in the evening add it a few times to the render queue. As you can select the take, rendersetting, and camera for each job, the prepared file can be rendered out without saving multiple versions of it first.

(That sounds like some script would make it easier, too, but I just fleetingly looked at the Python and C++ documents about BatchRender, and it doesn't look as if you can control the job settings individually?)

I recognize that this would only be good for the rendering part, but... if TurboSquid doesn't offer an official, supported web interface for uploading, then as @zipit said, "hacking" into the protocols would be just one gigantic mess that you don't really want to spend money on as it is very likely to break at the first opportunity.

Thanks for mentioning me 😉