Command line rendering wrong on first rendered frame #37797

Closed
opened 2013-12-13 01:35:45 +01:00 by Stephen Hamacek · 8 comments

System Information
Mac 10.7.5
Blender Version
Broken: Blender 2.69 r60991

Short description of error

Complex animation scene renders correctly from GUI, but on first frame of command line rendering, linked characters do not have actions applied.

Exact steps for others to reproduce the error

Haven't been able to recreate with a simple .blend yet.

My scene is an animation with a number of linked assets, so difficult to share, but all seems healthy otherwise.

Proxified character rigs seem to not have their actions correctly applied on first render frame when rendering from command line. Have tried with local renders on two machines, as well as using Qmaster as render manager. With Qmaster the first frame of each chunk (it breaks render into 10 frame ranges) also renders incorrectly.

So whatever frame I start rendering from always comes out incorrectly.

Here is an example command line:

/Applications/Blender2.69/blender.app/Contents/MacOS/blender -b -y /Users/stephenhamacek/Documents/Quandamooka/Projects/YunganMunnee/scenes/Scene06/YM-06-08-01.blend -o /Users/stephenhamacek/Documents/Quandamooka/Projects/YunganMunnee/renders/quick/06-08/ -s 1 -e 170 -a

Example incorrect frame (no pose/action applied)

Screen_Shot_2013-12-13_at_10.25.32_AM.png

Next frame renders correctly:

Screen_Shot_2013-12-13_at_10.26.00_AM.png

Here's example terminal output:
Term.rtf

**System Information** Mac 10.7.5 **Blender Version** Broken: Blender 2.69 r60991 **Short description of error** Complex animation scene renders correctly from GUI, but on first frame of command line rendering, linked characters do not have actions applied. **Exact steps for others to reproduce the error** Haven't been able to recreate with a simple .blend yet. My scene is an animation with a number of linked assets, so difficult to share, but all seems healthy otherwise. Proxified character rigs seem to not have their actions correctly applied on first render frame when rendering from command line. Have tried with local renders on two machines, as well as using Qmaster as render manager. With Qmaster the first frame of each chunk (it breaks render into 10 frame ranges) also renders incorrectly. So whatever frame I start rendering from always comes out incorrectly. Here is an example command line: /Applications/Blender2.69/blender.app/Contents/MacOS/blender -b -y /Users/stephenhamacek/Documents/Quandamooka/Projects/YunganMunnee/scenes/Scene06/YM-06-08-01.blend -o /Users/stephenhamacek/Documents/Quandamooka/Projects/YunganMunnee/renders/quick/06-08/ -s 1 -e 170 -a Example incorrect frame (no pose/action applied) ![Screen_Shot_2013-12-13_at_10.25.32_AM.png](https://archive.blender.org/developer/F39266/Screen_Shot_2013-12-13_at_10.25.32_AM.png) Next frame renders correctly: ![Screen_Shot_2013-12-13_at_10.26.00_AM.png](https://archive.blender.org/developer/F39268/Screen_Shot_2013-12-13_at_10.26.00_AM.png) Here's example terminal output: [Term.rtf](https://archive.blender.org/developer/F39272/Term.rtf)

Changed status to: 'Open'

Changed status to: 'Open'

Added subscriber: @StephenHamacek

Added subscriber: @StephenHamacek

Added subscriber: @brecht

Added subscriber: @brecht

Can you test the latest build from here?
http://developer.blender.org/buildbot/

I just did a fix yesterday for a problem like this: {522f17daa105a5c640950e74ece7aab2f83dd485}

Can you test the latest build from here? http://developer.blender.org/buildbot/ I just did a fix yesterday for a problem like this: {522f17daa105a5c640950e74ece7aab2f83dd485}

Thanks Brecht, sorry I missed that update! Testing now.

Thanks Brecht, sorry I missed that update! Testing now.

You're a legend - all good now! Only thing better than having bugs fixed just after you report them: having them fixed just before ;)

Many thanks again.

You're a legend - all good now! Only thing better than having bugs fixed just after you report them: having them fixed just before ;) Many thanks again.

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Brecht Van Lommel self-assigned this 2013-12-13 02:36:24 +01:00

Thanks for testing, closing report.

Thanks for testing, closing report.
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
2 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#37797
No description provided.