FAQ for when worker cannot find Blender executable #104232

Merged
Sybren A. Stüvel merged 5 commits from michael-2/flamenco:faq_worker_not_finding_blender into main 2023-08-23 15:15:39 +02:00
Showing only changes of commit 120d1e4654 - Show all commits

View File

@ -70,7 +70,7 @@ the Worker cannot find Blender.
WRN Blender could not be found. Flamenco Manager will have to supply the full path to Blender when Tasks are sent to this Worker. For more help see https://flamenco.blender.org/usage/variables/blender/
```
If Flamenco cannot locate Blender on the system it is possible to use a [two-way variable named `blender`][blendervar] for each platform (eg: Windows, Linux or MacOS). The Flamenco Worker will still show the same WRN message on startup when you use the two-way `blender` variable. The path specified by the `blender` variable is sent with the render job is enqueued.
If Flamenco cannot locate Blender on the system it is possible to use a [two-way variable named `blender`][blendervar] for each platform (eg: Windows, Linux, or MacOS). This path to Blender is then sent to the Worker for each render task. Note that the Worker will still show the warning at startup, as it cannot find Blender by itself; this is fine, because you now have configured the Manager to provide this path.

Windows, Linux or MacOS

Please use the Oxford comma.

The Flamenco Worker will still show the same WRN message on startup when you use the two-way blender variable. The path specified by the blender variable is sent with the render job is enqueued.

I think this can be reworded for more clarity, something like this:

This path to Blender is then sent to the Worker for each render task. Note that the Worker will still show the warning at startup, as it cannot find Blender by itself; this is fine, because you now have configured the Manager to provide this path.

> Windows, Linux or MacOS Please use the Oxford comma. > The Flamenco Worker will still show the same WRN message on startup when you use the two-way `blender` variable. The path specified by the `blender` variable is sent with the render job is enqueued. I think this can be reworded for more clarity, something like this: This path to Blender is then sent to the Worker for each render task. Note that the Worker will still show the warning at startup, as it cannot find Blender by itself; this is fine, because you now have configured the Manager to provide this path.
[blendervar]: {{< ref "usage/variables/blender" >}}
michael-2 marked this conversation as resolved

This can be written more positively. It's just a warning, not a "problem". Something like "There are two ways to address this" would be better.

This can be written more positively. It's just a warning, not a "problem". Something like "There are two ways to address this" would be better.