The render in terminal only render the active scene #81063

Closed
opened 2020-09-22 17:46:03 +02:00 by zebus3d · 11 comments

Operating system: Darwin-19.4.0-x86_64-i386-64bit 64 Bits
Graphics card: NVIDIA GeForce GTX 780M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-14.0.32 355.11.11.10.10.143

Blender version: 2.90.0, branch: master, commit date: 2020-08-31 11:26, hash: 0330d1af29
Worked: (newest version of Blender that worked as expected)

When I make 2 scenes with different camera shots to render different view layers with different camera shots, when rendering by terminal only the active scene with which you save the .blend is rendered. It seems that it does not recognize the other scene specified with -S or --scene in either way.
When we finish the render we should have 4 renders in /tmp/ 2 for each scene called Cam01 and Cam02, but currently only render the active scene "Cam01".

Steps:
Download my .blend and edit/run this script (with your corresponding paths) and render with it.
testing_bug.blend

#!/bin/bash

echo "render Cam01"
/Applications/Blender_2.90.app/Contents/MacOS/Blender -b /path/to/the/scene/testing_bug.blend -f 1 --scene "Cam01"

echo "render Cam02"
/Applications/Blender_2.90.app/Contents/MacOS/Blender -b /path/to/the/scene/testing_bug.blend -f 1 --scene "Cam02"

Operating system: Darwin-19.4.0-x86_64-i386-64bit 64 Bits Graphics card: NVIDIA GeForce GTX 780M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-14.0.32 355.11.11.10.10.143 Blender version: 2.90.0, branch: master, commit date: 2020-08-31 11:26, hash: `0330d1af29` Worked: (newest version of Blender that worked as expected) When I make 2 scenes with different camera shots to render different view layers with different camera shots, when rendering by terminal only the active scene with which you save the .blend is rendered. It seems that it does not recognize the other scene specified with -S or --scene in either way. When we finish the render we should have 4 renders in /tmp/ 2 for each scene called Cam01 and Cam02, but currently only render the active scene "Cam01". Steps: Download my .blend and edit/run this script (with your corresponding paths) and render with it. [testing_bug.blend](https://archive.blender.org/developer/F8909533/testing_bug.blend) ``` #!/bin/bash echo "render Cam01" /Applications/Blender_2.90.app/Contents/MacOS/Blender -b /path/to/the/scene/testing_bug.blend -f 1 --scene "Cam01" echo "render Cam02" /Applications/Blender_2.90.app/Contents/MacOS/Blender -b /path/to/the/scene/testing_bug.blend -f 1 --scene "Cam02" ```
Author

Added subscriber: @zebus3dream

Added subscriber: @zebus3dream

Added subscriber: @rjg

Added subscriber: @rjg

While I haven't tested this yet, I think the order of CLI arguments is incorrect. Blender's CLI arguments are executed in order and -f starts the rendering before the scene is set. Placing --scene before -f will likely work.

While I haven't tested this yet, I think the order of CLI arguments is incorrect. [Blender's CLI arguments are executed in order ](https://docs.blender.org/manual/en/latest/advanced/command_line/arguments.html#argument-order) and `-f` starts the rendering before the scene is set. Placing `--scene` before `-f` will likely work.

Added subscriber: @StephenSwaney

Added subscriber: @StephenSwaney

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'

In Blender, the order of command line arguments matters. See the section Argument Order in the help text ( blender --help)

If you move the --scene in front of the -f , you should be golden.

In Blender, the order of command line arguments matters. See the section Argument Order in the help text ( blender --help) If you move the --scene in front of the -f , you should be golden.
Author

It seems that putting it in front of -f has worked!.
The fact is that the same script in previous versions of blender did work.

I have two other solutions to the problem:

1 One is to save one blender scene per Cam and render with several .blends.

2 The other option is to put all the composition nodes in the active scene.

It would be nice if blender warned you if you were putting the arguments in the wrong order!,

Thank you.

It seems that putting it in front of -f has worked!. The fact is that the same script in previous versions of blender did work. I have two other solutions to the problem: 1 One is to save one blender scene per Cam and render with several .blends. 2 The other option is to put all the composition nodes in the active scene. It would be nice if blender warned you if you were putting the arguments in the wrong order!, Thank you.

Changed status from 'Needs User Info' to: 'Archived'

Changed status from 'Needs User Info' to: 'Archived'
Robert Guetzkow self-assigned this 2020-09-22 19:53:07 +02:00

I'm closing this ticket because the correct order of CLI arguments allows to switch the scene before rendering.

/Applications/Blender_2.90.app/Contents/MacOS/Blender -b /path/to/the/scene/testing_bug.blend --scene "Cam01" -f 1

Please note that Blender does inform about the order of operations during execution. It prints Scene switch for render: 'Cam01' in file: '/path/to/the/scene/testing_bug.blend' to the terminal/console when the scene switch happens. In your original CLI arguments this was printed after the rendering.

The order of arguments isn't technically wrong, it's just not what you intended to do in this specific use case. If you would've wanted to switch the scene after rendering the first frame, it would've given you the intended result. Hence, Blender can't display a warning since it doesn't know your intentions.

I'm closing this ticket because the correct order of CLI arguments allows to switch the scene before rendering. `/Applications/Blender_2.90.app/Contents/MacOS/Blender -b /path/to/the/scene/testing_bug.blend --scene "Cam01" -f 1` Please note that Blender does inform about the order of operations during execution. It prints `Scene switch for render: 'Cam01' in file: '/path/to/the/scene/testing_bug.blend'` to the terminal/console when the scene switch happens. In your original CLI arguments this was printed after the rendering. The order of arguments isn't technically wrong, it's just not what you intended to do in this specific use case. If you would've wanted to switch the scene after rendering the first frame, it would've given you the intended result. Hence, Blender can't display a warning since it doesn't know your intentions.

The fact is that the same script in previous versions of blender did work.

@zebus3dream I've tested this with Blender 2.90 to 2.79, they all behave the same. If there was a previous version that ignored the order, this would have been a bug.

> The fact is that the same script in previous versions of blender did work. @zebus3dream I've tested this with Blender 2.90 to 2.79, they all behave the same. If there was a previous version that ignored the order, this would have been a bug.
Author

In #81063#1021212, @rjg wrote:

The fact is that the same script in previous versions of blender did work.

@zebus3dream I've tested this with Blender 2.90 to 2.79, they all behave the same. If there was a previous version that ignored the order, this would have been a bug.

Ok, thanks for everything anyway!!

> In #81063#1021212, @rjg wrote: >> The fact is that the same script in previous versions of blender did work. > > @zebus3dream I've tested this with Blender 2.90 to 2.79, they all behave the same. If there was a previous version that ignored the order, this would have been a bug. Ok, thanks for everything anyway!!
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#81063
No description provided.