Contents3 sections
Choose a dust material
[look] material = "soil" uses the median colour of 40 soils from ECOSTRESS and USGS splib07a. "masonry" uses red brick.
Each preset fills dust, spread, lumpiness, smoke fade, turbulence, drag and colours. Any key you set wins. Values other than colour are not fitted to footage.
In [look], presets fill missing smoke and dust colours. In [solver], they fill fade, drag, turbulence strength and turbulence size. Each emitter inherits missing dust, lumpiness, lump_size_m, jitter and spread_deg.
An explicit value in the spec or in --set wins, including zero. The report records material.name and material.overridden.
Kick-up soil
# A short puff of cold dust rising from the ground.
[look]
material = "soil"
[domain]
size_m = [3.2, 2.4, 3.2]
voxel_m = 0.05
duration_s = 1.5
[[emitters]]
shape = "disc"
position_m = [0, 0.15, 0]
size_m = 0.32
thickness_m = 0.10
end_s = 0.10
fuel = 0
temperature_k = 293
direction = "up"
velocity_mps = 3
[solver]
turbulence_where = "moving"
[[views]]
pitch_deg = 15
[export]
grid = [4, 4]
tile_px = 64
supersample = 1
pacing = "front"
channels = ["six_way", "motion", "depth"]Both kick-up examples report ENDS_VISIBLE; masonry also reports DOMAIN_CLIPPING. Check the warning list when choosing the domain and duration.
Questions
What do the soil and masonry dust presets configure in pyrofx?
They fill missing smoke and dust colours, fade, drag, turbulence settings and emitter defaults like lumpiness and spread.
Can I override values from a pyrofx dust material preset?
Yes, any key you set explicitly in the spec or on the command line wins over the preset, including zero.
Where does pyrofx record which dust preset was used and what changed?
The compile report records material.name and material.overridden so you can verify which preset values were applied or replaced.