Flame Fire doesn't show light on Render. #126805

Closed
opened 2024-08-27 00:59:14 +02:00 by Kent Davis · 25 comments

System Information
Operating system: macOS-14.6.1-arm64-arm-64bit 64 Bits
Graphics card: Metal API Apple M3 Pro 1.2

Blender Version
Broken: version: 4.3.0 Alpha, branch: main, commit date: 2024-08-25 03:57, hash: 6bd515e0d2a2
Worked: (newest version of Blender that worked as expected)

Short description of error
Flame fire doesn't show light

Exact steps for others to reproduce the error

MacBook Pro M3 Pro
image
Hardware Overview:

Model Name: MacBook Pro
Model Identifier: Mac15,7
Model Number: MRW43LL/A
Chip: Apple M3 Pro
Total Number of Cores: 12 (6 performance and 6 efficiency)
Memory: 18 GB
System Firmware Version: 10151.140.19
OS Loader Version: 10151.140.19
Serial Number (system): HPW7VKG2D9
Hardware UUID: 30E70298-022A-511D-A2F9-EF855835F739
Provisioning UDID: 00006030-001A051102D9001C
Activation Lock Status: Disabled

Apple M3 Pro:

Chipset Model: Apple M3 Pro
Type: GPU
Bus: Built-In
Total Number of Cores: 18
Vendor: Apple (0x106b)
Metal Support: Metal 3
Displays:
Color LCD:
Display Type: Built-in Liquid Retina XDR Display
Resolution: 3456 x 2234 Retina
Main Display: Yes
Mirror: Off
Online: Yes
Automatically Adjust Brightness: No
Connection Type: Internal


See some one work on flame fire youtube: https://youtu.be/mh9tyFnzSUw
for my Blender 4.3.0 not work for me
Flame fire doesn't show light

Youtube picture (You can see fire light)
image

My picture (Cannot light on fire)
image

**System Information** Operating system: macOS-14.6.1-arm64-arm-64bit 64 Bits Graphics card: Metal API Apple M3 Pro 1.2 **Blender Version** Broken: version: 4.3.0 Alpha, branch: main, commit date: 2024-08-25 03:57, hash: `6bd515e0d2a2` Worked: (newest version of Blender that worked as expected) **Short description of error** Flame fire doesn't show light **Exact steps for others to reproduce the error** MacBook Pro M3 Pro ![image](/attachments/44ffb294-9d25-408a-a00f-4f13ecbf55d0) Hardware Overview: Model Name: MacBook Pro Model Identifier: Mac15,7 Model Number: MRW43LL/A Chip: Apple M3 Pro Total Number of Cores: 12 (6 performance and 6 efficiency) Memory: 18 GB System Firmware Version: 10151.140.19 OS Loader Version: 10151.140.19 Serial Number (system): HPW7VKG2D9 Hardware UUID: 30E70298-022A-511D-A2F9-EF855835F739 Provisioning UDID: 00006030-001A051102D9001C Activation Lock Status: Disabled Apple M3 Pro: Chipset Model: Apple M3 Pro Type: GPU Bus: Built-In Total Number of Cores: 18 Vendor: Apple (0x106b) Metal Support: Metal 3 Displays: Color LCD: Display Type: Built-in Liquid Retina XDR Display Resolution: 3456 x 2234 Retina Main Display: Yes Mirror: Off Online: Yes Automatically Adjust Brightness: No Connection Type: Internal --- See some one work on flame fire youtube: https://youtu.be/mh9tyFnzSUw for my Blender 4.3.0 not work for me Flame fire doesn't show light Youtube picture (You can see fire light) ![image](/attachments/12373910-fa15-44dc-a7d0-f35b43ddd60f) My picture (Cannot light on fire) ![image](/attachments/8135963f-0034-405d-9c24-2637f3e3ad64)
Kent Davis added the
Severity
Normal
Type
Bug
Status
Needs Triage
labels 2024-08-27 00:59:15 +02:00
Author

Oh I see I just got free download (node preview version 1.20) it work and I am going show you picture.

Color Ramp on gradient not work.

image

Oh I see I just got free download (node preview version 1.20) it work and I am going show you picture. Color Ramp on gradient not work. ![image](/attachments/e5ef76c7-c7cd-414f-b528-6edf6e4765a5)
3.6 MiB
Author

Color Ramp is bug.
Gradient Texture is it worked.

Blender 4.2 and 4.3

image

Color Ramp is bug. Gradient Texture is it worked. Blender 4.2 and 4.3 ![image](/attachments/dbe2b70e-a5f7-4eeb-a4a8-662c5be6f30d)
186 KiB
Member

So just to make sure I understood this correctly, you found that the color ramp node does not work under Apple M3 Metal right?

So just to make sure I understood this correctly, you found that the color ramp node does not work under Apple M3 Metal right?
Member

The file provided (Flame Fire 1.0.0 Blender 4.3.0 by Kent Davis.zip) doesn't show a flame because you're using a blank attribute. Setting the attribute name to heat like the tutorial fixes this issue. Does this fix the issue for you?

Set to heat attribute.jpg


Color Ramp is bug.
Gradient Texture is it worked.

Blender 4.2 and 4.3

image

The color ramp is working as expected in this situation. The color ramp takes a value as a input (This is the Fac input), then remaps it with the color ramp setup you created. Because the Fac is 0.5, the preview will show you a solid color from the centre of the color ramp setup you've created.

The file provided (`Flame Fire 1.0.0 Blender 4.3.0 by Kent Davis.zip`) doesn't show a flame because you're using a blank attribute. Setting the attribute name to heat like the tutorial fixes this issue. Does this fix the issue for you? ![Set to heat attribute.jpg](/attachments/31493604-a9f0-47ed-b62a-9855963e65a6) --- > Color Ramp is bug. > Gradient Texture is it worked. > > Blender 4.2 and 4.3 > > ![image](/attachments/dbe2b70e-a5f7-4eeb-a4a8-662c5be6f30d) The color ramp is working as expected in this situation. The color ramp takes a value as a input (This is the `Fac` input), then remaps it with the color ramp setup you created. Because the `Fac` is 0.5, the preview will show you a solid color from the centre of the color ramp setup you've created.
Alaska added
Status
Needs Information from User
and removed
Status
Needs Triage
labels 2024-08-27 07:35:24 +02:00
Author

@ChengduLittleA
Yes correct Colorramp and I haven't check iMac intel because I give to my wife complete and I can't use her's iMac.
I do use M3 Pro right now.

@Alaska

How did you do that flame fire there but not work for me black one.
Can you fix and send me 1 document .blend and I will check?

@ChengduLittleA Yes correct Colorramp and I haven't check iMac intel because I give to my wife complete and I can't use her's iMac. I do use M3 Pro right now. @Alaska How did you do that flame fire there but not work for me black one. Can you fix and send me 1 document .blend and I will check?
Member

Here's the adjusted file. You may need to free and rebake the smoke/fire simulation data as I did not include it with the file

Here's the adjusted file. You may need to free and rebake the smoke/fire simulation data as I did not include it with the file
Author

Click Free Bake button then click rebake button complete and 3D Viewport render still not work for me not see light.

image

Only for MacOS and do not use Windows. Thanks.

Click Free Bake button then click rebake button complete and 3D Viewport render still not work for me not see light. ![image](/attachments/eebf9104-8e85-497f-a95d-72b6d539720b) Only for MacOS and do not use Windows. Thanks.
Member

Something's not right. When you rebaked the simulation, it didn't actually make anything (no fire and no smoke). So that's why you can't see it. I'll take a look at this issue seperately and I might file a bug report for it.

Does this work for you?
This time I've sent both the .blend file, and the simulation so you don't need to rebake it (as rebaking it seems to be having issues at the moment).

Something's not right. When you rebaked the simulation, it didn't actually make anything (no fire and no smoke). So that's why you can't see it. I'll take a look at this issue seperately and I might file a bug report for it. Does this work for you? This time I've sent both the .blend file, and the simulation so you don't need to rebake it (as rebaking it seems to be having issues at the moment).
Author

Alaska thank you for send me Updated Fire Simulation on zip and I show you my youtube screen record and can tell problem.
https://youtu.be/aUQElA1NDrY
Something's not right. When me rebake the simulation that bug.

Alaska thank you for send me Updated Fire Simulation on zip and I show you my youtube screen record and can tell problem. https://youtu.be/aUQElA1NDrY Something's not right. When me rebake the simulation that bug.
Author

Now another one
Rename on folder "4.3" to "4.3 hold 2"
check other youtube
https://youtu.be/G7OOCOfYJic

Now another one Rename on folder "4.3" to "4.3 hold 2" check other youtube https://youtu.be/G7OOCOfYJic
Member

I've taken a look at it. The reason why it's not baking properly is because Blender can't find the texture attached to the fire emitter. This thing: Unable to find flame fire texture.jpg

Blender being unable to find the texture is related to the linked data blocks are missing error message you're getting when you open the file. (The texture is from a linked file, and Blender can't seem to find it now).

So to fix this issue you either need to change or turn off the texture on the emitter object, or relink the file to the texture.

I've taken a look at it. The reason why it's not baking properly is because Blender can't find the texture attached to the fire emitter. This thing: [Unable to find flame fire texture.jpg](/attachments/f4cbd803-d89a-4552-9ce2-662cba7138d6) Blender being unable to find the texture is related to the `linked data blocks are missing` error message you're getting when you open the file. (The texture is from a linked file, and Blender can't seem to find it now). So to fix this issue you either need to change or turn off the texture on the emitter object, or relink the file to the texture.
Author

You said "Texture" is miss linked and I found reason. Blender 4.3.0 is not show miss Properties Texture tab
#126306
Blender 4.2.1 it worked already Properties Texture tab but 4.3.0 is miss not there on Properties Texture tab.

This Blender 4.2.1 Outliet
image

Blender 4.3.0
image

You said "Texture" is miss linked and I found reason. Blender 4.3.0 is not show miss Properties Texture tab https://projects.blender.org/blender/blender/issues/126306 Blender 4.2.1 it worked already Properties Texture tab but 4.3.0 is miss not there on Properties Texture tab. This Blender 4.2.1 Outliet ![image](/attachments/948d4e8a-7048-4710-901d-21f0433dd842) Blender 4.3.0 ![image](/attachments/cfea09b5-c54d-45ff-a2bc-0a871fa6a4d4)
1.5 MiB
2.5 MiB
Member

In my testing the missing texture tab in 4.3 isn't causing the issue.

The issue seems to be that the texture you were using has been deleted and Blender can't find it. Here's a quick explaination on what I think happened and why:

  • What we know right now.
    • Blender is complaining that a linked texture is missing.
    • The texture is Flame fire cloud and it is being linked from /Applications/Blender 4.3.0.app/Contents/Resource/4.3/datafiles/assets/brushes/essential_brushes.blend
    • Based on the error messages you're getting, it seems that Blender can find essential_brushes.blend, but can't find the Flame fire cloud texture inside that file.
    • When I look at essential_brushes.blend on my computer, there doesn't appear to be a Flame fire cloud texture in the file.
  • What I think happened:
    • I believe you created Flame fire cloud and somehow added it to essential_brushes.blend.
    • I believe you then updated Blender 4.3.0 to a newer version, which replaced essential_brushes.blend and deleted your Flame fire cloud.
In my testing the missing texture tab in 4.3 isn't causing the issue. The issue seems to be that the texture you were using has been deleted and Blender can't find it. Here's a quick explaination on what I think happened and why: - What we know right now. - Blender is complaining that a linked texture is missing. - The texture is `Flame fire cloud` and it is being linked from `/Applications/Blender 4.3.0.app/Contents/Resource/4.3/datafiles/assets/brushes/essential_brushes.blend` - Based on the error messages you're getting, it seems that Blender can find `essential_brushes.blend`, but can't find the `Flame fire cloud` texture inside that file. - When I look at `essential_brushes.blend` on my computer, there doesn't appear to be a `Flame fire cloud` texture in the file. - What I think happened: - I believe you created `Flame fire cloud` and somehow added it to `essential_brushes.blend`. - I believe you then updated Blender 4.3.0 to a newer version, which replaced `essential_brushes.blend` and deleted your `Flame fire cloud`.
Author

Ok I got download last night latest 4.3.0 Alpha

https://youtu.be/LYy_YaoMTck
Why look different? few years ago like Blender 2.8 to 2.9 look match but new latest version they change mess up.
iMac Intel and M1, M2, M3 same problem on flame fire not match through youtube.

image

Fuel change from 1.0 to 2.0
There really wrong!
image

See youtube picture
image

Ok I got download last night latest 4.3.0 Alpha https://youtu.be/LYy_YaoMTck Why look different? few years ago like Blender 2.8 to 2.9 look match but new latest version they change mess up. iMac Intel and M1, M2, M3 same problem on flame fire not match through youtube. ![image](/attachments/af7272cb-0225-46bf-b84a-ba0ad1dd5291) Fuel change from 1.0 to 2.0 There really wrong! ![image](/attachments/bd6c5a84-bdc4-4cb6-811e-77b331ef6f87) See youtube picture ![image](/attachments/2511fa4f-696e-4ad0-b845-16a5ce86d18e)
Member

@mac4kent The reason it's different is because the default settings for the fire simulation changed in 4.2, leading to differences compared to the tutorial, which was created in 4.0.

The setting that changed was the CFL number. Increasing it to 4 (the value used in Blender 4.0) resolves the issue.

Location of CFL number.jpg


We like to keep reports at "one issue per bug". I will close this report. This report now as all the issues are expected, or being handled by a different report.

I will open a new report about the change in default settings and see how the developers feel about it.

@mac4kent The reason it's different is because the default settings for the fire simulation changed in 4.2, leading to differences compared to the tutorial, which was created in 4.0. The setting that changed was the CFL number. Increasing it to 4 (the value used in Blender 4.0) resolves the issue. ![Location of CFL number.jpg](/attachments/64f5bf97-34ec-4b5c-bb4e-2ae3f7eb8dde) --- We like to keep reports at "one issue per bug". I will close this report. This report now as all the issues are expected, or being handled by a different report. I will open a new report about the change in default settings and see how the developers feel about it.
Blender Bot added
Status
Archived
and removed
Status
Needs Information from User
labels 2024-08-29 11:05:04 +02:00
Author

@Alaska
Ok just change from 2 to 4 and still not right see picture.
image

@Alaska Ok just change from 2 to 4 and still not right see picture. ![image](/attachments/78ef037a-8e9f-4e1b-b36b-e417565b13a5)
4.2 MiB
Member

The tutorial was using resolution divisions of 32 in the beginning while you're using resolutiono divisions of 64. This will have a impact on the simulation and you may need to increase the CFL number even higher (E.g. 6)

The tutorial was using resolution divisions of 32 in the beginning while you're using resolutiono divisions of 64. This will have a impact on the simulation and you may need to increase the CFL number even higher (E.g. 6)
Author

From 64 to 32
from 4.000 to 6.000
image

From 64 to 32 from 4.000 to 6.000 ![image](/attachments/5e2a5d64-e568-4e38-90fd-b0a88e58f598)
1.4 MiB
Author

do you have your own MacOS ?

do you have your own MacOS ?
Member

Yes, I have been testing everything here on a M1 Pro Mac.

I'm sorry, there are a lot of settings in fire and smoke simulations, mainly to let users define the quality they want for the time and computer speed they have.

When these settings are configured incorrectly (For example, CFL Number is too low), then they can cause the simulation to behave in unexpected ways.

The main thing I see contributing to this issue is that the surface emisison value is too low for the current configuration of fuel.

So either reduce the fuel or increase the surface emission value, or do both, to bring back some stability to your simulation.

These settings can be found in the Pyshics properties panel when your icosphere is selected.

Yes, I have been testing everything here on a M1 Pro Mac. I'm sorry, there are a lot of settings in fire and smoke simulations, mainly to let users define the quality they want for the time and computer speed they have. When these settings are configured incorrectly (For example, CFL Number is too low), then they can cause the simulation to behave in unexpected ways. The main thing I see contributing to this issue is that the `surface emisison` value is too low for the current configuration of `fuel`. So either reduce the fuel or increase the surface emission value, or do both, to bring back some stability to your simulation. These settings can be found in the Pyshics properties panel when your icosphere is selected.
Author

that is good you have.
yes icosphere.
Where is properties panel?

that is good you have. yes icosphere. Where is properties panel?
Member
No description provided.
Author

Me
Flow Behavior: Flow change to Geometry
Fuel: from 2 change to 1
Surface Emission from 1.0 to 1.5
https://youtu.be/Ua7LIT21KZE

You
Flow Behavior: Geometry

Me Flow Behavior: Flow change to Geometry Fuel: from 2 change to 1 Surface Emission from 1.0 to 1.5 https://youtu.be/Ua7LIT21KZE You Flow Behavior: Geometry
Member

Sorry, the flow behaviour should be set to inflow if you want the sphere to continuously be on fire. I made a mistake in my previous image and didn't realize it was set to geometry.

Sorry, the flow behaviour should be set to inflow if you want the sphere to continuously be on fire. I made a mistake in my previous image and didn't realize it was set to geometry.
Author

Oh really hehe no problem
image
image

Oh really hehe no problem ![image](/attachments/4686e200-da55-414c-b382-9dec91445705) ![image](/attachments/a2cfadd8-ead1-4191-9f87-e9058f0a1720)
1.2 MiB
4.2 MiB
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Code Documentation
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
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
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
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
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
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
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#126805
No description provided.