Flamenco 3.0 Beta - The worker doesn't run the Blender version configured in the Manager but the one registered in Windows #100226

New Issue

Riccardo Giovanetti · 2022-08-05T17:31:35+02:00

2022-08-05 17:31:35 +02:00

System Information
Operating system: Windows-10-10.0.19043-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.93

Blender Version: 3.2.2, branch: master, commit date: 2022-08-02 18:15, hash: blender/blender@bcfdb14560

Short description of error
The worker runs the Blender version registered in Windows instead of the specific version configured in the Manager

Exact steps for others to reproduce the error
I was testing Flamenco 3 Beta on my laptop where I do have several versions of Blender Portable within dedicated directories, and configured to be completely self contained and independent from eachother.

Currently, for production reasons, I do have Blender version 2.83.20 registered in Windows Registry so that, when I double click on a .blend file, it opens with this specific version. Other versions of Blender are installed on my laptop: 2.93.10 LTS, 3.2.2, 3.3beta, and 3.4alpha. All these versions are installed on the secondary HDD mapped as D:\ as follows (while the OS and Programs are located in the SDD C:):

D:\Blender_2.83_stable
D:\Blender_2.93_stable
D:\Blender_3.2_stable
D:\Blender_3.3_dev
D:\Blender_3.4_dev\

I followed Sybren's instructions in the video and created a D:\Flamenco directory with three subdir (\projects, \renders, and \software). At the first run of the Flamenco Manager I specified to do not use the registered version 2.83, which was found (first option), but instead to run Blender from the absolute path D:\Blender_3.2_stable, where the add-on was also installed in this version, and configured correctly.

I created a .blend project file using Blender 3.2.2, saved it inside D:\Flamenco\projects as per Sybren's video, and sent the job to the Manager. After running the Worker application I noticed that in the Worker's console the registered 2.83 version was found, the job was created to run the 3.2 version, but instead version 2.83 was executed which raised an error and job cancellation.

Find attached the .yaml file, the content of the Manager's and Worker's console messages for debugging.

flamenco-manager.yaml
manager_console_msgs.txt
worker_console_msgs.txt

**System Information** Operating system: Windows-10-10.0.19043-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.93 Blender Version: 3.2.2, branch: master, commit date: 2022-08-02 18:15, hash: `blender/blender@bcfdb14560` **Short description of error** The worker runs the Blender version registered in Windows instead of the specific version configured in the Manager **Exact steps for others to reproduce the error** I was testing Flamenco 3 Beta on my laptop where I do have several versions of Blender Portable within dedicated directories, and configured to be completely self contained and independent from eachother. Currently, for production reasons, I do have Blender version 2.83.20 registered in Windows Registry so that, when I double click on a .blend file, it opens with this specific version. Other versions of Blender are installed on my laptop: 2.93.10 LTS, 3.2.2, 3.3beta, and 3.4alpha. All these versions are installed on the secondary HDD mapped as D:\ as follows (while the OS and Programs are located in the SDD C:\): D:\Blender_2.83_stable\ D:\Blender_2.93_stable\ D:\Blender_3.2_stable\ D:\Blender_3.3_dev\ D:\Blender_3.4_dev\ I followed Sybren's instructions in the video and created a D:\Flamenco directory with three subdir (\projects, \renders, and \software). At the first run of the Flamenco Manager I specified to do not use the registered version 2.83, which was found (first option), but instead to run Blender from the absolute path D:\Blender_3.2_stable\, where the add-on was also installed in this version, and configured correctly. I created a .blend project file using Blender 3.2.2, saved it inside D:\Flamenco\projects as per Sybren's video, and sent the job to the Manager. After running the Worker application I noticed that in the Worker's console the registered 2.83 version was found, the job was created to run the 3.2 version, but instead version 2.83 was executed which raised an error and job cancellation. Find attached the .yaml file, the content of the Manager's and Worker's console messages for debugging. [flamenco-manager.yaml](https://archive.blender.org/developer/F13337875/flamenco-manager.yaml) [manager_console_msgs.txt](https://archive.blender.org/developer/F13337876/manager_console_msgs.txt) [worker_console_msgs.txt](https://archive.blender.org/developer/F13337877/worker_console_msgs.txt)

Riccardo Giovanetti commented

2022-08-05 17:31:35 +02:00

Added subscriber: @Harvester

blender-admin commented

2022-08-30 10:36:04 +02:00

This issue was referenced by e5a20425c4

This issue was referenced by e5a20425c474ec93edbe03d2667ec5184f32d3ef

Sybren A. Stüvel self-assigned this 2022-08-30 11:06:16 +02:00

Sybren A. Stüvel commented

2022-08-30 17:29:37 +02:00

Changed status from 'Needs Triage' to: 'Resolved'

Sybren A. Stüvel closed this issue

2022-08-30 17:29:37 +02:00

Sybren A. Stüvel commented

2022-08-30 17:29:37 +02:00

This should be fixed by e5a20425c4, which will be part of the soon-to-be-released 2nd beta.

Note that that change is backward-incompatible, and it'll make it impossible to re-render old jobs. You'll have to resubmit them to Flamenco after upgrading to beta2.

This should be fixed by e5a20425c4, which will be part of the soon-to-be-released 2nd beta. Note that that change is backward-incompatible, and it'll make it impossible to re-render old jobs. You'll have to resubmit them to Flamenco after upgrading to beta2.

Sign in to join this conversation.