Animated image texture in cycles material view buggy and extremely finicky; almost unusable #43479

Closed
opened 2015-01-29 23:43:11 +01:00 by Harrison Nordby · 12 comments

Tested on:
windows 7
geforce gtx 660 ti

Also tested:
windows 7
geforce gtx 670

Broken: Blender 2.73a official

Animated image textures in cycles material viewport mode are buggy and extremely finicky to the point of being almost unusable.

Here's a zip with a .blend and 5 clearly numbered images to demonstrate:
image_plane_anim.zip

There are multiple problems, and they may originate from the same bug. Here's what I've found so far:

  • Pressing play does not update the image, only scrubbing the timeline or alt-scroll up/down affects it.

  • Repeatedly scrubbing the timeline from frame 0 to frame 5 will eventually cause a permanent pink image in the viewport.

  • Using alt-scroll up/down in the viewport will often show the incorrect image. For example, sometimes going to the previous frame will show the next frame's image. (Viewport not being redrawn after frame change?)

Tested on: windows 7 geforce gtx 660 ti Also tested: windows 7 geforce gtx 670 Broken: Blender 2.73a official Animated image textures in cycles material viewport mode are buggy and extremely finicky to the point of being almost unusable. Here's a zip with a .blend and 5 clearly numbered images to demonstrate: [image_plane_anim.zip](https://archive.blender.org/developer/F139854/image_plane_anim.zip) There are multiple problems, and they may originate from the same bug. Here's what I've found so far: - Pressing play does not update the image, only scrubbing the timeline or alt-scroll up/down affects it. - Repeatedly scrubbing the timeline from frame 0 to frame 5 will eventually cause a permanent pink image in the viewport. - Using alt-scroll up/down in the viewport will often show the incorrect image. For example, sometimes going to the previous frame will show the next frame's image. (Viewport not being redrawn after frame change?)

Changed status to: 'Open'

Changed status to: 'Open'

Added subscriber: @Squashwell

Added subscriber: @Squashwell

This comment was removed by @Squashwell

*This comment was removed by @Squashwell*

If everything was working properly, the number on the plane in the 3d viewport should be the current frame number.

If everything was working properly, the number on the plane in the 3d viewport should be the current frame number.

Added subscriber: @FloridaJo

Added subscriber: @FloridaJo

Yes, material method is buggy, works fine in render mode.
Also, if the number is not displayed correctly, if one clicks on the texture node, it updates correctly.
Maybe autorefresh timing is off?

OSX 10.2

Yes, material method is buggy, works fine in render mode. Also, if the number is not displayed correctly, if one clicks on the texture node, it updates correctly. Maybe autorefresh timing is off? OSX 10.2

Added subscribers: @Psy-Fi, @mont29

Added subscribers: @Psy-Fi, @mont29

Antony, could it be an OpenGL issue?

Would have thought of a missing update event, but the fact texture remains invalid (pink state) even when editing its settings makes me eye to OGL…

Antony, could it be an OpenGL issue? Would have thought of a missing update event, but the fact texture remains invalid (pink state) even when editing its settings makes me eye to OGL…

Generally animation of values + GLSL + play real-time animation is not working so well. It forces recompilation of shaders and we avoid that for speed. That said, it's weird that we get pink images so I'll take a look here later.

Generally animation of values + GLSL + play real-time animation is not working so well. It forces recompilation of shaders and we avoid that for speed. That said, it's weird that we get pink images so I'll take a look here later.
Antonis Ryakiotakis self-assigned this 2015-01-30 10:32:55 +01:00

This issue was referenced by 46fe39ff31

This issue was referenced by 46fe39ff312cd13e3a8955a7244e7bd4c8cf6dac

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

Closed by commit 46fe39ff31.

Closed by commit 46fe39ff31.
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
5 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#43479
No description provided.