"Cubemap Size" affects procedural texture's scale in the reflections #61739

Closed
opened 2019-02-20 09:47:20 +01:00 by Marcin Twarowski · 7 comments

Win 10, GTX 1080
Blender 2.80 2019-02-19 23:18 855b3e68ef

When you bake a cubemap at lower resolutions like 128px, procedural textures have incorrect scale in reflections:

cubemap_texture_size_bug_02.png
cubemap_texture_size_bug_01.png
cubemap_texture_size_bug_03.png

See attached blend file:texture_bake_scale_bug.blend

Win 10, GTX 1080 Blender 2.80 2019-02-19 23:18 855b3e68ef27 When you bake a cubemap at lower resolutions like 128px, procedural textures have incorrect scale in reflections: ![cubemap_texture_size_bug_02.png](https://archive.blender.org/developer/F6668290/cubemap_texture_size_bug_02.png) ![cubemap_texture_size_bug_01.png](https://archive.blender.org/developer/F6668293/cubemap_texture_size_bug_01.png) ![cubemap_texture_size_bug_03.png](https://archive.blender.org/developer/F6668296/cubemap_texture_size_bug_03.png) See attached blend file:[texture_bake_scale_bug.blend](https://archive.blender.org/developer/F6668286/texture_bake_scale_bug.blend)

Added subscriber: @MarcinTwarowski

Added subscriber: @MarcinTwarowski

Added subscriber: @moisessalvador

Added subscriber: @moisessalvador

What you see is a combination of a moire effect, due to small scale of the texture and the low cubemap resolution. Another way of putting it, the texture is so small than when it's captured on the cubemap filtered at a lower res, it just happens to look like a large scale version of the same texture, an optical illusion. But if you use any other procedural texture, or the texture at a larger size, you see that lowres cubemaps don't change their scale. Like in this image with the lowest cubemap resolution possible.

image.png

texture_bake_scale_bug.blend

What you see is a combination of a moire effect, due to small scale of the texture and the low cubemap resolution. Another way of putting it, the texture is so small than when it's captured on the cubemap filtered at a lower res, it just happens to look like a large scale version of the same texture, an optical illusion. But if you use any other procedural texture, or the texture at a larger size, you see that lowres cubemaps don't change their scale. Like in this image with the lowest cubemap resolution possible. ![image.png](https://archive.blender.org/developer/F6670236/image.png) [texture_bake_scale_bug.blend](https://archive.blender.org/developer/F6670249/texture_bake_scale_bug.blend)

Moire effect doesn't explain this:

noise_texture_cubemap.PNG

It's a simple noise texture with a scale of 100. texture_bake_scale_bug_noise.blend

If it's indeed a moire effect then i guess it needs better filtering.

Moire effect doesn't explain this: ![noise_texture_cubemap.PNG](https://archive.blender.org/developer/F6670356/noise_texture_cubemap.PNG) It's a simple noise texture with a scale of 100. [texture_bake_scale_bug_noise.blend](https://archive.blender.org/developer/F6670386/texture_bake_scale_bug_noise.blend) If it's indeed a moire effect then i guess it needs better filtering.

The noise is smaller than the size of a pixel in the cubemap, and thus the small noise disappears in the downscale process while the few ones that appear look big because that's how big the pixels are. It's like downsampling a picture of stars in photoshop, that's what happens, and no filtering algorithm would solve that 100%. It's definitely NOT procedural textures changing scale, because then it would change scale even with big textures like in the imaged I used above

The noise is smaller than the size of a pixel in the cubemap, and thus the small noise disappears in the downscale process while the few ones that appear look big because that's how big the pixels are. It's like downsampling a picture of stars in photoshop, that's what happens, and no filtering algorithm would solve that 100%. It's definitely NOT procedural textures changing scale, because then it would change scale even with big textures like in the imaged I used above

Ok then, If there's nothing to be done about it.

Ok then, If there's nothing to be done about it.

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Marcin Twarowski self-assigned this 2019-02-21 11:21:49 +01:00
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#61739
No description provided.