Eevee: ludicrous high value fireflys AO+Bent normals #65118
Labels
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
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#65118
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Windows-7-6.1.7601-SP1 64 Bits
Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 417.35
Blender Version
Broken: version: 2.80 (sub 72), branch: master, commit date: 2019-05-24 18:32, hash:
a629c74c9c
Worked: (optional)
Short description of error
Seems that in that angle from the camera those objects align in order to generate the fire flies in the object "AA-Rojo_Interior" the SSS spread the firefly all around thats why i leave SSS to 1 in all the objects in the sample.
Turning off bent normals in the AO options or removing the normal map from the material "GrisPlastico" seems to "fix" or avoid the issue.
Exact steps for others to reproduce the error
[Please describe the exact steps needed to reproduce the issue]
Firefly bug.blend
1-Switch to viewport render
2-scrub the timeline, around frames 220 - 230
Added subscriber: @NahuelBelich
Added subscriber: @moisessalvador
I can replicate it in the sense that they happened to me in some frames of an animation but I couldn't pinpoint what angles point of view caused it. All that I can confirm is that they happened with AO+Bent normal + Subsurface. It was force to fix this using the Compositor to clamp the high values, erase the alpha and use the Inpaint filter.
My system is Nvidia 1060 6gb, Windows 10 64bit
I cannot reproduce it here on my setup (linux + AMD Radeon Pro + mesa).
Maybe it's a driver bug on windows 7? Can anyone confirm that?
Added subscriber: @Jeroen-Bakker
We tried to reproduce this issue but were not able to.
Could you try to update your graphical drivers and test with the latest blender?
ok, ill try to test this further, ill try to do it as soon as i can
Ok i have done more tests.
in my main machine (i7 win7 gtx 1070 ), updated drivers (430) an last blender version and the bug its consistently appearing always there. 2019-06-04_23-49-56.mp4
Then i undust my old secondary machine a q9300, win7, nvidia 460 (updated drivers 354), and there the bug didn't appear. . . . nothing, works fine as it should.
So there is a problem i can see it in my main machine but i totally understand if this report its closed as "not enough info" or "not able to reproduce" since im with both machines same file in front of me, i can't get consistent behavior.
Ill keep an eye open in case i find any other clue to reproduce the error more consistently.
Can you pack the normal map inside the file?
DANG! ok im feeling really really stupid right now, i though i had paked, and i was sure when was moving a file that weight more than an 1mb with only that little mesh data. . . . anyways, ill test this again in my secondary machine later to check this version.
Its kind a bit big but this is the file with the normal map.
Firefly bug_packed.blend
This issue was referenced by
8fa65ed31b
Changed status from 'Open' to: 'Resolved'
I tested the fix with
8fa65ed31b
and8b2b79c210
and the viewport looks great and mainly worked but. .https://youtu.be/FUpuVy0LRTU
The problem seem to persist but in a different frame and a lot fewer, one more difficult thing its that its not possible or at least i wasn't able to reproduce with the demo .blend i uploaded later, so im going to disect the scene again to try to prepare another demo file to test it.
I was just commenting here to let you know.
By the way, what should i do if i can pin point a demo .blend reproduce the error? should i added here or create a new bug report?
Thanks
Changed status from 'Resolved' to: 'Open'
Yes just attach the blend file here.
Fireflybug_03.blend
In this file i got a consistent result
1 open
2 render
Changing anything makes the firefly don't appear.
For example:
Tested with builds
8b2b79c210
andaa003c7324
Unfortunately I cannot reproduce this time. I tried a blind guess and maybe it will fix the issue.
Hi, i have test with
4fb4415172
, rendered that problematic shot a few times with different sizes and also other cameras, that blind guess seems to be working i didn't see any fire fly, this scene shots are rendering properly now.Thanks
Changed status from 'Open' to: 'Resolved'