Hi folks,
I have created a simple addon which will help to automate codes for command line render in Blender. So that artists and sysadmins can relax for a while.
I can’t recreate the error. Can you please take a snap shot of your render settings> output directory? That would be helpful.
The error is most likely your output path for render images…
This idea gives me the chance to remember an old project that has never been realized, but that would be nice e useful. To create a custom linux distribution that contains the following features :
A list of questions to understand what kind of user will use blender like these :
do you want to use the most stable blender version or the development version ?
in which part of blender do you want to focus today ? (modelling,texturing,rigging,animation,etc) ?
depending on the answer,a standard blender installation will start and it will contains a series of settings and plugins,that can be modified later
a system to keep updated the plugins and blender
a series of script to optimize the rendering stage and the various blender functions…
I’m not a python programmer,so I don’t know how to do that,but I can give some ideas…
It can be done as an external standalone application, but I afraid it will break Blender release cycle rules, plugin dependency and overall blender infrastructure…Cause plugins of one version of Blender may not be compatible with another one.
I am in vacation right now. Will test it after a week or so. But tested it in win, Fedora and Mint before release through standard tarball and msi blender installation.
Hi thanks for the feedback. I have updated the bl info…
Have you saved the Blender project and specified the render file directory and render file name? What does it create after pressing the generate button?
Hi, I was updating the addon today. Although I have not understood your problem entirely, have fixed some relative path issues and auto directory creation we needed for our server.
Tested with Win 10 and LNX. Seems working fine. If there are any error shows in the prompt please copy- paste that. It’s easier to understand in this way.
Thanks.
When you change a path with cd “X:\Some Path” you change the path on X: but you don’t find yourself on drive X: afterwards. You still have to switch to X: by typing “X:” after that. Otherwise you aren’t in the same directory as blender.exe.
The other issue is that there are two “” in front of the “cd”-path in the batch file. There should only be one ".
Here are the two lines of the batch file that the addon created. As you can see, the first line has two “” in front of the path.
Hi thanks for the feedback, I have fixed the typo for windows. But I am not sure why you need to change the path.
Our workflow with WINDOWS is:
1. Save the blender file with everything setup (timeframe, render engine, render file path).
2. Generate the script.
3. Go to that folder where the script is and just double click it.
(It should be in the render path you have set)
4. Command promt will open up and render starts
For LINUX and MAC everything is same, just instead of double clicking you need to cd to that render folder and do sh yourrenderscript.sh
The blender.exe location is already attached in the script in your case: “F:\Programme_Fix\Blender Foundation\blender-2.80-windows64_ecycles”
Let me know your intended workflow please and will see.
Thanks