Freestyle rendering not in sync with camera move #59581

Closed
opened 2018-12-18 20:13:52 +01:00 by Lars Bunch · 9 comments

System Information
Operating system: OSX 10.13.4
Graphics card: Radeon Pro 580 8192 MB

Blender Version
Broken:
Date: 2018-12-18 12:08
Hash: c92cffb56d
Branch: blender2.8

Worked: The problem does not exist in Blender 2.79

Short description of error
Freestyle lines are rendered from a static camera position while objects render normally from the moving camera's position.

Exact steps for others to reproduce the error
The problems occurs consistently in all versions of Blender 2.8 (alphas through current beta) that i have tried on OSX. This has been tested and the error is consistent on two different imacs and a Mac Pro trashcan. I have not been able to try it on Windows or Linux.

Create a cube.
Enable Freestyle
Animate the camera to move so that the position of the object moves across the screen
Render in Cycles

When the camera is animated and the object is static, the freestyle lines will remain in the same place as if shot from a static camera while the 3D solid is seen properly from the camera's view. If the camera is static but the object moves, the freestyle lines move appropriately. In a situation where the object AND the camera are animated, the freestyle lines seem to move properly based on the object movement, but go out of sync with the camera movement.

When the camera is animated, if I do a single frame render (F12) the freestyle lines will line up with the object properly, but once I do a sequence render (Crtl-F12) the freestyle lines will be seen from the camera position where I did the single frame render, but will remain static (if the object isn't animated).

The error occurs whether "View Map Cache" is checked or not. I have not been able to reproduce the error in Blender 2.79

Camera move only
Freestyle_Animation_Error_20181218_Camera_Move_Only.jpg

Object Move only
Freestyle_Animation_Error_20181218_Object_Move_Only.jpg

Camera and Object move
Freestyle_Animation_Error_20181218_Camera_and_Object_Move.jpg

Freestyle_Animation_Error_20181218_Camera_and_Object_Move.blend

Freestyle_Animation_Error_20181218_Camera_Move_Only.blend

Freestyle_Animation_Error_20181218_Object_Move_Only.blend

system-info.txt

Based on the default startup or an attached .blend file (as simple as possible).

**System Information** Operating system: OSX 10.13.4 Graphics card: Radeon Pro 580 8192 MB **Blender Version** Broken: Date: 2018-12-18 12:08 Hash: c92cffb56d5 Branch: blender2.8 Worked: The problem does not exist in Blender 2.79 **Short description of error** Freestyle lines are rendered from a static camera position while objects render normally from the moving camera's position. **Exact steps for others to reproduce the error** The problems occurs consistently in all versions of Blender 2.8 (alphas through current beta) that i have tried on OSX. This has been tested and the error is consistent on two different imacs and a Mac Pro trashcan. I have not been able to try it on Windows or Linux. Create a cube. Enable Freestyle Animate the camera to move so that the position of the object moves across the screen Render in Cycles When the camera is animated and the object is static, the freestyle lines will remain in the same place as if shot from a static camera while the 3D solid is seen properly from the camera's view. If the camera is static but the object moves, the freestyle lines move appropriately. In a situation where the object AND the camera are animated, the freestyle lines seem to move properly based on the object movement, but go out of sync with the camera movement. When the camera is animated, if I do a single frame render (F12) the freestyle lines will line up with the object properly, but once I do a sequence render (Crtl-F12) the freestyle lines will be seen from the camera position where I did the single frame render, but will remain static (if the object isn't animated). The error occurs whether "View Map Cache" is checked or not. I have not been able to reproduce the error in Blender 2.79 Camera move only ![Freestyle_Animation_Error_20181218_Camera_Move_Only.jpg](https://archive.blender.org/developer/F5995616/Freestyle_Animation_Error_20181218_Camera_Move_Only.jpg) Object Move only ![Freestyle_Animation_Error_20181218_Object_Move_Only.jpg](https://archive.blender.org/developer/F5995620/Freestyle_Animation_Error_20181218_Object_Move_Only.jpg) Camera and Object move ![Freestyle_Animation_Error_20181218_Camera_and_Object_Move.jpg](https://archive.blender.org/developer/F5995623/Freestyle_Animation_Error_20181218_Camera_and_Object_Move.jpg) [Freestyle_Animation_Error_20181218_Camera_and_Object_Move.blend](https://archive.blender.org/developer/F5995629/Freestyle_Animation_Error_20181218_Camera_and_Object_Move.blend) [Freestyle_Animation_Error_20181218_Camera_Move_Only.blend](https://archive.blender.org/developer/F5995630/Freestyle_Animation_Error_20181218_Camera_Move_Only.blend) [Freestyle_Animation_Error_20181218_Object_Move_Only.blend](https://archive.blender.org/developer/F5995631/Freestyle_Animation_Error_20181218_Object_Move_Only.blend) [system-info.txt](https://archive.blender.org/developer/F5995682/system-info.txt) Based on the default startup or an attached .blend file (as simple as possible).
Author

Added subscriber: @LarsBunch

Added subscriber: @LarsBunch

Added subscriber: @ZedDB

Added subscriber: @ZedDB

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Sebastian Parborg self-assigned this 2019-02-01 15:01:32 +01:00

I can not reproduce this with the latest blender beta. So this must have been solved at some point.

I can not reproduce this with the latest blender beta. So this must have been solved at some point.

Added subscriber: @xanegraphics

Added subscriber: @xanegraphics

Changed status from 'Resolved' to: 'Archived'

Changed status from 'Resolved' to: 'Archived'

Having the same problem. Rendering from static camera position. Changed focal length of camera but it's using the first keyframed camera focal length

Edit >
It's using the camera state of the position where the cursor on the timeline is placed before rendering.
e.g If I place my cursor on frame 300 before hitting render, it would use the camera state at frame 300, even if the range is from 1 - 500.
So I have to render each frame and place my cursor a frame forward after rendering each frame. Tedious, but it's the only way at the moment

Having the same problem. Rendering from static camera position. Changed focal length of camera but it's using the first keyframed camera focal length Edit > It's using the camera state of the position where the cursor on the timeline is placed before rendering. e.g If I place my cursor on frame 300 before hitting render, it would use the camera state at frame 300, even if the range is from 1 - 500. So I have to render each frame and place my cursor a frame forward after rendering each frame. Tedious, but it's the only way at the moment

Added subscriber: @sif

Added subscriber: @sif

I have the same issue as Xane described it. Freestyle assumes the current focal length to be constant over the course of an animation in Cycles.

Reproduce bug:
focal-freestyle-issue.blend
Render this blend as animation, which will render a single frame different from the current time frame and with different focal length. Tested in 2.81-2.83 .
focal-freestyle-issue.png

A temporary workaround is to render Freestyle as separate pass in 2.83 with Eevee and compose it back to the Cycles render. (thanks to 4minus1d for the hint)

I have the same issue as Xane described it. Freestyle assumes the current focal length to be constant over the course of an animation in Cycles. **Reproduce bug:** [focal-freestyle-issue.blend](https://archive.blender.org/developer/F8374545/focal-freestyle-issue.blend) Render this blend as animation, which will render a single frame different from the current time frame and with different focal length. Tested in 2.81-2.83 . ![focal-freestyle-issue.png](https://archive.blender.org/developer/F8374552/focal-freestyle-issue.png) A temporary workaround is to render Freestyle as separate pass in 2.83 with Eevee and compose it back to the Cycles render. (thanks to 4minus1d for the hint)
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
4 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#59581
No description provided.