smoke sim glitch in solidmode #70678

Closed
opened 2019-10-09 18:00:21 +02:00 by Tobias Lijsen · 24 comments

System Information
Operating system: Windows-7-6.1.7601-SP1 64 Bits
Graphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.30

Blender Version
Broken: version: 2.81 (sub 14), branch: master, commit date: 2019-10-09 07:42, hash: 40a55be82c
Worked: (optional)

Short description of error
smoke sim with adaptive domain is sliding around in solid mode
see video for better explanation and showoff

Bugreport_Smoke_Glitch.mp4

domain is parented to a empty wich follows a curve per constraint
i tryed baking the constraint movement to an action and disable the constraint... this didnt help

Exact steps for others to reproduce the error
open the blend and just press play and see the error until frame 300

BLENDF FILE:
eevee_solid_smoke_bug.blend

sry for my english... :)

thx & have a nice day

**System Information** Operating system: Windows-7-6.1.7601-SP1 64 Bits Graphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.30 **Blender Version** Broken: version: 2.81 (sub 14), branch: master, commit date: 2019-10-09 07:42, hash: `40a55be82c` Worked: (optional) **Short description of error** smoke sim with adaptive domain is sliding around in solid mode see video for better explanation and showoff [Bugreport_Smoke_Glitch.mp4](https://archive.blender.org/developer/F7799172/Bugreport_Smoke_Glitch.mp4) domain is parented to a empty wich follows a curve per constraint i tryed baking the constraint movement to an action and disable the constraint... this didnt help **Exact steps for others to reproduce the error** open the blend and just press play and see the error until frame 300 BLENDF FILE: [eevee_solid_smoke_bug.blend](https://archive.blender.org/developer/F7799213/eevee_solid_smoke_bug.blend) sry for my english... :) thx & have a nice day
Author

Added subscriber: @blenderhilfe

Added subscriber: @blenderhilfe

#69870 was marked as duplicate of this issue

#69870 was marked as duplicate of this issue
Tobias Lijsen changed title from eevee smoke sim glitch to smoke sim glitch in solidmode 2019-10-09 18:08:50 +02:00

Added subscriber: @mano-wii

Added subscriber: @mano-wii
Jeroen Bakker was assigned by Germano Cavalcante 2019-10-09 21:53:40 +02:00

I can confirm.
The problem is only seen in Workbench.
Cycles and Eevee work well.

I can confirm. The problem is only seen in Workbench. Cycles and Eevee work well.
Author

This comment was removed by @blenderhilfe

*This comment was removed by @blenderhilfe*
Author

ive tested this further, and found more problems with moving (especially rotating) domains
also in eevee there is a problem - if the domain is ROTATING in the animation
in 2.7 this was not a problem as far as i remember

open this blend file and press play
test_smoke_curve.blend

you see 2 problems:
1.) the simulation is somehow rotating with the domain... this should not happen if "adaptive domain" is enabled
2.) on playback, the sim-frames gets added on top of any frames before - until you press stop... then just the "active" frame ist drawn again

question to problem #1 - is it allowed to rotate adaptive domains? as i remember in 2.7 and before this worked just fine
thx & have a great day

ive tested this further, and found more problems with moving (especially rotating) domains also in eevee there is a problem - if the domain is ROTATING in the animation in 2.7 this was not a problem as far as i remember open this blend file and press play [test_smoke_curve.blend](https://archive.blender.org/developer/F7802848/test_smoke_curve.blend) you see 2 problems: 1.) the simulation is somehow rotating with the domain... this should not happen if "adaptive domain" is enabled 2.) on playback, the sim-frames gets added on top of any frames before - until you press stop... then just the "active" frame ist drawn again question to problem #1 - is it allowed to rotate adaptive domains? as i remember in 2.7 and before this worked just fine thx & have a great day
Author

maybe this helps to nail it
test_smoke_curve_workaround.blend

in this blend i worked around all (!!!) the errors... by leaving out rotation (see contraint in blend)
now it is clear: its definitly a rotation problem with adaptive domains
is this by design - or is it a error?

never before ive got this problem with adaptive domains...

maybe this helps to nail it [test_smoke_curve_workaround.blend](https://archive.blender.org/developer/F7802894/test_smoke_curve_workaround.blend) in this blend i worked around all (!!!) the errors... by leaving out rotation (see contraint in blend) now it is clear: its definitly a rotation problem with adaptive domains is this by design - or is it a error? never before ive got this problem with adaptive domains...
Author

NOW THE CONCLUSION: if we dont be able to rotate the adaptive domain with the flow... the cache gets to over 200 GB instead of 15 GB.... totaly not usable!

and for workarounds it looks like this:
in eevee particle info and point density is not implemented... so i have to go with good old alpha-plane-particles for my smoke... but wait... we dont have billboards functioning in cycles and eevee.
so mmmm crap... nothing works really

i understand that the new smoke/fluid system is coming and nobody wants to waste time on fixing the "old" smoke-system... but
can someone maybe fix the billboard-particles-funktion & particle-info-nodes for eevee???
so at least we can have alpha particles that look to the camera and fade out properly in eevee?

i try to find a solution for over a week now... i think i have to leave this tutorial from my new 2.8 tutorial series... no smoke for my steam train.... didnt expect THAT mass of problems :(

thank you anyways devs ;) 2.8 is overall great... but if i dig deeper... many bugs.
but ok, 2.8 is a new software overall, i understand this :)
thx & have a great day

NOW THE CONCLUSION: if we dont be able to rotate the adaptive domain with the flow... the cache gets to over 200 GB instead of 15 GB.... totaly not usable! and for workarounds it looks like this: in eevee particle info and point density is not implemented... so i have to go with good old alpha-plane-particles for my smoke... but wait... we dont have billboards functioning in cycles and eevee. so mmmm crap... nothing works really i understand that the new smoke/fluid system is coming and nobody wants to waste time on fixing the "old" smoke-system... but can someone maybe fix the billboard-particles-funktion & particle-info-nodes for eevee??? so at least we can have alpha particles that look to the camera and fade out properly in eevee? i try to find a solution for over a week now... i think i have to leave this tutorial from my new 2.8 tutorial series... no smoke for my steam train.... didnt expect THAT mass of problems :( thank you anyways devs ;) 2.8 is overall great... but if i dig deeper... many bugs. but ok, 2.8 is a new software overall, i understand this :) thx & have a great day
Member

Hi @blenderhilfe!

That is totally not the case; drawing and simulating are two separate things. I am happy to look at this issue and find a solution for it.

Hi @blenderhilfe! That is totally not the case; drawing and simulating are two separate things. I am happy to look at this issue and find a solution for it.
Member

I made the scene simpler so it is easier for developers to debug.

#70678.blend

20191015_smoke.webm

To reproduce:

  • Domain needs to be rotated and adaptive.

As you see the smoke will be rendered correctly when the adaptive domain reaches the size of the simulation domain. Also notice the cube that is showing the voxel size. It just seems to work reversed.

I made the scene simpler so it is easier for developers to debug. [#70678.blend](https://archive.blender.org/developer/F7825182/T70678.blend) [20191015_smoke.webm](https://archive.blender.org/developer/F7825186/20191015_smoke.webm) To reproduce: * Domain needs to be rotated and adaptive. As you see the smoke will be rendered correctly when the adaptive domain reaches the size of the simulation domain. Also notice the cube that is showing the voxel size. It just seems to work reversed.

Added subscriber: @sebbas

Added subscriber: @sebbas

Can confirm this drawing issue in the fluid-mantaflow branch too.

Can confirm this drawing issue in the fluid-mantaflow branch too.
Jeroen Bakker removed their assignment 2019-10-16 12:51:18 +02:00
Clément Foucault was assigned by Jeroen Bakker 2019-10-16 12:51:18 +02:00
Member

Added subscriber: @Jeroen-Bakker

Added subscriber: @Jeroen-Bakker
Member

After researching it seems to be that the workbench_volume_frag does not take into account rotation/offset of the texture.

@fclem can you have a look at this?

After researching it seems to be that the workbench_volume_frag does not take into account rotation/offset of the texture. @fclem can you have a look at this?

Added subscriber: @marks-4

Added subscriber: @marks-4

Hello all, FYI I managed to get the problem with the 29th Sept build in a completely static domain, will try to find the blend file to send to this thread.

Hello all, FYI I managed to get the problem with the 29th Sept build in a completely static domain, will try to find the blend file to send to this thread.

Typically: when I re-baked the old scene I couldn't see anything much wrong- until I removed the 2 Turbulence fields I was using to make the smoke look interesting, after which I was rewarded with an absolute corker of an example of the issue (TC 06:21 to 06:22)-

https://www.youtube.com/watch?v=OWt1Yp9IrRc&feature=youtu.be
SmokeTwitch.mp4

You can also see something suspicious happening at TC 00:17 to 00:18 from the overhead camera.

Here's the scene file-
MantaflowSmokeTwitch.blend

Something I have noticed, don't know if it's related but- adaptive domain doesn't seem to give a toss about the domain size & position once baked: i.e. in the attached scene the bottom of the domain goes way below where the domain was originally defined, and had it's scale applied, before baking.
Like so-
pre-bake
PreAdaptiveBake.JPG

post-bake
PostAdaptiveBake.JPG

Also I've noticed when baking the noise, there seem to be instances of 2-3 frames baking way faster than the rest (observed while watching the timeline play head whilst baking), I couldn't swear to it, but I think it's around when the twitches occur.
Additionally the twitch coincides with the time the wee box in the bottom corner of the domain moves in x,y,or z, which doesn't happen without adaptive domain being enabled.

Here's my current system info-
System Information
Operating system: Windows-10-10.0.18362 64 Bits
Graphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.48

Blender Version
Broken: version: 2.81 (sub 12), branch: fluid-mantaflow, commit date: 2019-09-27 09:45, hash: 114783000d

IMHO my issue is totally to do with adaptive domain, not with the domain being moved. I've never used a non-static domain so far (nice idea though, shall do in future!).

Cheers!
Mark

Typically: when I re-baked the old scene I couldn't see anything much wrong- until I removed the 2 Turbulence fields I was using to make the smoke look interesting, after which I was rewarded with an absolute corker of an example of the issue (TC 06:21 to 06:22)- https://www.youtube.com/watch?v=OWt1Yp9IrRc&feature=youtu.be [SmokeTwitch.mp4](https://archive.blender.org/developer/F7828283/SmokeTwitch.mp4) You can also see something suspicious happening at TC 00:17 to 00:18 from the overhead camera. Here's the scene file- [MantaflowSmokeTwitch.blend](https://archive.blender.org/developer/F7828214/MantaflowSmokeTwitch.blend) Something I have noticed, don't know if it's related but- adaptive domain doesn't seem to give a toss about the domain size & position once baked: i.e. in the attached scene the bottom of the domain goes way below where the domain was originally defined, and had it's scale applied, before baking. Like so- pre-bake ![PreAdaptiveBake.JPG](https://archive.blender.org/developer/F7828241/PreAdaptiveBake.JPG) post-bake ![PostAdaptiveBake.JPG](https://archive.blender.org/developer/F7828244/PostAdaptiveBake.JPG) Also I've noticed when baking the noise, there seem to be instances of 2-3 frames baking way faster than the rest (observed while watching the timeline play head whilst baking), I couldn't swear to it, but I think it's around when the twitches occur. Additionally the twitch coincides with the time the wee box in the bottom corner of the domain moves in x,y,or z, which doesn't happen without adaptive domain being enabled. Here's my current system info- **System Information** Operating system: Windows-10-10.0.18362 64 Bits Graphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.48 **Blender Version** Broken: version: 2.81 (sub 12), branch: fluid-mantaflow, commit date: 2019-09-27 09:45, hash: `114783000d` IMHO my issue is totally to do with adaptive domain, not with the domain being moved. I've never used a non-static domain so far (nice idea though, shall do in future!). Cheers! Mark
Member

Added subscriber: @marksda

Added subscriber: @marksda
Member

Hi @marks-4
Sorry for the confusion, but your ticket was marked as a duplicate of this task, but seems to be addressing two totally different issues.
Could you add your feedback to your original ticket?

Thanks

Hi @marks-4 Sorry for the confusion, but your ticket was marked as a duplicate of this task, but seems to be addressing two totally different issues. Could you add your feedback to your original ticket? Thanks
Member

Removed subscriber: @marksda

Removed subscriber: @marksda

This issue was referenced by 382e7ce9ec

This issue was referenced by 382e7ce9ecfbdc80853a250a57c0d8f25cf258fa

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

Have copied my above to the original task as requested.

Have copied my above to the original task as requested.
Author

thank you!
but its not totally fixed... now we have another problem!

i made a new bug report for this - https://developer.blender.org/T70943

thank you! but its not totally fixed... now we have another problem! i made a new bug report for this - https://developer.blender.org/T70943
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
7 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#70678
No description provided.