Hi, Thanks for the review :) I didn't manage to reproduce the error, do you think you could provide the tokens you are using, and the output path with the token written in it when you have the error ? And if it is possible, a copy of the error message from the console (the one you can show by going to "Window > Toggle System Console"). Thanks again !
Love the idea, perfect tool for pipelines. But...
I have multiple tags configured, such as: <scene> EXPRESSION bpy.context.scene.name <camera> EXPRESSION bpy.context.scene.camera.name <render> PATH RENDER_FILES <linetest> PATH LINETEST
If I use the following filename pattern: //<render>/<linetest>/<scene>_<camera>.#.
I get this result (with unresolved tags): <render>/LINETEST/<scene>_<camera>.#.
In other words, only the last tag, in this case <linetest>, gets resolved.
If I change the order in the Preferences' list, I always get the same result: only the last tag.
Not sure what I've made wrong.
Hi, Sorry for the answering so late, I just uploaded a new version that should fix your problem, let me know if it does not work.
I really like that addon, since it makes Output Paths behave like Maya and it should be Standard.
At first it worked. After Rendering an Animation in Evee it replaced the Token with the full output path.
Afterward it didn“t work anymore. I get the error message "could not open file for Rendering".
This workflow should be standard in Blender. I really hope the dev make it happen