Smoke adaptive Domain (Volume render + z-mask layer) #33480

Closed
opened 2012-12-11 14:42:27 +01:00 by samran abed alsalam · 15 comments

%%%smoke adaptive domain interactive with mask layer ,should be not ! !
There is a problem in this aspect !

in test file lock to
frame 106
frame 120

thanks
samran abed alsalam
%%%

%%%smoke adaptive domain interactive with mask layer ,should be not ! ! There is a problem in this aspect ! in test file lock to frame 106 frame 120 thanks samran abed alsalam %%%

Changed status to: 'Open'

Changed status to: 'Open'

%%%blender 2.65 _windows Ver

%%%

%%%blender 2.65 _windows Ver %%%

%%%Hey,

Could you make a minimalistic .blend file where this issue happens without any unrelated objects etc. Or at least explain what exactly should happen and when?%%%

%%%Hey, Could you make a minimalistic .blend file where this issue happens without any unrelated objects etc. Or at least explain what exactly should happen and when?%%%

%%%new test file
What I'm trying to do is delete the layer containing smoke domain and keep the smoke over the other elements using mask layer
i have right render if the camera outside the adaptive domain
if the camera inside adaptive domain i don't have render 100% alpha !%%%

%%%new test file What I'm trying to do is delete the layer containing smoke domain and keep the smoke over the other elements using mask layer i have right render if the camera outside the adaptive domain if the camera inside adaptive domain i don't have render 100% alpha !%%%

%%%sorry right render if camera inside adaptive domain
100% if camera outside the adaptive domain
This means adaptive domain working as Box and have Zpass .. so he cut everything Behind it !!
%%%

%%%sorry right render if camera inside adaptive domain 100% if camera outside the adaptive domain This means adaptive domain working as Box and have Zpass .. so he cut everything Behind it !! %%%

%%%Do not forget BAKE the smoke !
I think should be excluded adaptive domain and domain from Z buffer
sorry for bad EN %%%

%%%Do not forget BAKE the smoke ! I think should be excluded adaptive domain and domain from Z buffer sorry for bad EN %%%

%%%Okay, I can see two possible issues there:

  1. Smoke flows don't work if they're not on same scene layer with domain. There seems to be code specifically limiting this. Dunno why.

  2. Smoke doesn't render if camera is outside the volume when render layer masking is enabled. This seems to be related to other bug and volume renderer TODO item:
    http://projects.blender.org/tracker/index.php?func=detail&aid=28849&group_id=9&atid=498

I'll ask brecht if he can explain why this doesn't work. :)%%%

%%%Okay, I can see two possible issues there: 1) Smoke flows don't work if they're not on same scene layer with domain. There seems to be code specifically limiting this. Dunno why. 2) Smoke doesn't render if camera is outside the volume when render layer masking is enabled. This seems to be related to other bug and volume renderer TODO item: http://projects.blender.org/tracker/index.php?func=detail&aid=28849&group_id=9&atid=498 I'll ask brecht if he can explain why this doesn't work. :)%%%

%%%Problem no 1. is now "fixed" in r52898. Smoke flows don't have to be in same scene layer as domain anymore to bake. (Even though it wasn't really part of this report. :)

That render mask issue is still there, though.%%%

%%%Problem no 1. is now "fixed" in r52898. Smoke flows don't have to be in same scene layer as domain anymore to bake. (Even though it wasn't really part of this report. :) That render mask issue is still there, though.%%%

%%%and smoke collision have same issues :)
%%%

%%%and smoke collision have same issues :) %%%

%%%As I understand it, all collisions in Blender only interacts if the collision objects are on the same layer, that's a feature. In fact for smoke flows it might have been intentional too, seems consistent with collision then. There's always the smoke flow / collision groups that you can set if you don't want to use layers this way.%%%

%%%As I understand it, all collisions in Blender only interacts if the collision objects are on the same layer, that's a feature. In fact for smoke flows it might have been intentional too, seems consistent with collision then. There's always the smoke flow / collision groups that you can set if you don't want to use layers this way.%%%

%%%I think the way the mask layers are set up here isn't quite working the way that feature was intended. Basically if you put an object on the mask layer, it will not be rendered, so putting the smoke domain on the mask layers means the smoke will not be rendered. However it happens to render anyway when the camera is inside the volume, and it's that which might actually be considered a bug.

The fact that the domain bounding box affects the mask is also somewhat unexpected, but disabling that wouldn't fix your case, the smoke still would not be visible then because it's on the mask layer.

Anyway, I think the correct way to set this up would be to put the red box on the mask layer, and enable the Zmask option, though I may not understand entirely what you're trying to do.%%%

%%%I think the way the mask layers are set up here isn't quite working the way that feature was intended. Basically if you put an object on the mask layer, it will not be rendered, so putting the smoke domain on the mask layers means the smoke will not be rendered. However it happens to render anyway when the camera is inside the volume, and it's that which might actually be considered a bug. The fact that the domain bounding box affects the mask is also somewhat unexpected, but disabling that wouldn't fix your case, the smoke still would not be visible then because it's on the mask layer. Anyway, I think the correct way to set this up would be to put the red box on the mask layer, and enable the Zmask option, though I may not understand entirely what you're trying to do.%%%

%%%I committed a fix now for an issue with the setup I described, using the Zmask option, frame 67 was rendering wrong then without any smoke.%%%

%%%I committed a fix now for an issue with the setup I described, using the Zmask option, frame 67 was rendering wrong then without any smoke.%%%

%%%I work on drama VFX project using blender (In this shot I try to break down the wall and use smoke to dust simulation)
It is difficult to explain what I'm trying to do and complex , but I found another solution to get what I want
new attach photo from the project "FOR FUN" :)
%%%

%%%I work on drama VFX project using blender (In this shot I try to break down the wall and use smoke to dust simulation) It is difficult to explain what I'm trying to do and complex , but I found another solution to get what I want new attach photo from the project "FOR FUN" :) %%%

%%%Awesome, always great to see people putting Blender to good use :)

I've added this to the todo list of volume rendering issues now. It could handle this smarter, but I would suggest to use the Zmask option as that seems to be designed more for what you'd want to do.
http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Render#Volume_Rendering

The collision only interacting on layers is not a bug as mentioned, so I think this report can be closed.%%%

%%%Awesome, always great to see people putting Blender to good use :) I've added this to the todo list of volume rendering issues now. It could handle this smarter, but I would suggest to use the Zmask option as that seems to be designed more for what you'd want to do. http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Render#Volume_Rendering The collision only interacting on layers is not a bug as mentioned, so I think this report can be closed.%%%

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
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
3 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#33480
No description provided.