Wrong texture mapping in render preview #40581

Closed
opened 2014-06-11 17:38:28 +02:00 by Fabian Emmes · 13 comments

Blender Version
Broken: current master e53c00a

Short description of error
Rotating the view (middle-click and drag) in a 3D viewport, while the "Viewport Shading" is set to "Rendered" yields wrong texture coordinates if the texture slot uses "Object" coordinate mapping.

Exact steps for others to reproduce the error
Open mapping_bug_object.blend.
Change "Viewport Shading" to "Rendered".
Notice that texture mapping on object "Plane" is wrong.
Press F12 to render scene.
Notice that texture mapping is correct in rendered image.
Press Escape.
Notice that viewport is now updated to correct texture coordinates.

**Blender Version** Broken: current master e53c00a **Short description of error** Rotating the view (middle-click and drag) in a 3D viewport, while the "Viewport Shading" is set to "Rendered" yields wrong texture coordinates if the texture slot uses "Object" coordinate mapping. **Exact steps for others to reproduce the error** Open [mapping_bug_object.blend](https://archive.blender.org/developer/F93911/mapping_bug_object.blend). Change "Viewport Shading" to "Rendered". Notice that texture mapping on object "Plane" is wrong. Press F12 to render scene. Notice that texture mapping is correct in rendered image. Press Escape. Notice that viewport is now updated to correct texture coordinates.
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @der_fab

Added subscriber: @der_fab

Added subscriber: @Sergey

Added subscriber: @Sergey

I don't really see an issue with the mapping. And there's no difference in the viewport before and after the render.

What exactly do you mean "wrong"? Maybe some screenshots will help here.

I don't really see an issue with the mapping. And there's no difference in the viewport before and after the render. What exactly do you mean "wrong"? Maybe some screenshots will help here.
Author

I'm sorry, the steps to reproduce this bug weren't clear.

It happens while rotating the view in the 3D viewport, while "Viewport Shading" is set to "Rendered".

Before rotation: correct_mapping.png

After rotation: wrong_mapping.png

I'm sorry, the steps to reproduce this bug weren't clear. It happens while rotating the view in the 3D viewport, while "Viewport Shading" is set to "Rendered". Before rotation: ![correct_mapping.png](https://archive.blender.org/developer/F94001/correct_mapping.png) After rotation: ![wrong_mapping.png](https://archive.blender.org/developer/F94003/wrong_mapping.png)

Added subscriber: @mont29

Added subscriber: @mont29

Added subscriber: @Harvester

Added subscriber: @Harvester

Hello. I checked this bug report with the current official 2.71 Win64bit version and the attached test file works as expected in both Blender Internal and Cycles.
Regards

Hello. I checked this bug report with the current official 2.71 Win64bit version and the attached test file works as expected in both Blender Internal and Cycles. Regards
Sergey Sharybin self-assigned this 2014-06-30 09:38:46 +02:00

That's weird, because don't remember fixes in that area.. Would have a closer look. Also, do you mind checking latest builds from builder.blender.org?

That's weird, because don't remember fixes in that area.. Would have a closer look. Also, do you mind checking latest builds from builder.blender.org?

Sergey, I downloaded the latest build from b.b.o., Blender 2.71.0 (Hash: 5588e45 dated 2014-06-30 01:55) Win64bit (blender-2.71-5588e45-win64.zip) and I can confirm that the behaviour is correct in both BI and Cycles. The issue raised by der_fab happened only in BI because I forgot initially to assign a target Object in the Texture|Mapping|Object field (which is the Plane itself).

I have also downloaded the currently available 32bit verions (Hash: ea3c2eb dated 2014-06-30 00:42) and as far I can see it works fine also here.

Sergey, I downloaded the latest build from b.b.o., Blender 2.71.0 (Hash: 5588e45 dated 2014-06-30 01:55) Win64bit (blender-2.71-5588e45-win64.zip) and I can confirm that the behaviour is correct in both BI and Cycles. The issue raised by der_fab happened only in BI because I forgot initially to assign a target Object in the Texture|Mapping|Object field (which is the Plane itself). I have also downloaded the currently available 32bit verions (Hash: ea3c2eb dated 2014-06-30 00:42) and as far I can see it works fine also here.
Author

Indeed, the bug seems to be fixed. I tried bd777ff dated 2014-06-27.

Indeed, the bug seems to be fixed. I tried bd777ff dated 2014-06-27.

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'

Closing then, no need to keep invalid bug reports open! :)

Closing then, no need to keep invalid bug reports open! :)
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#40581
No description provided.