Using emixer files at MXI Batch Processing tool makes other changes to be ignored.
Noise procedural texture doesn’t use the seed.
If a texture is blended with a procedural texture and tiling is used, procedural texture uses squared tiling.
Selecting a folder on UI sets the path without a final slash.
Dropping a file on a path UI sets the file path wrong.
Crash when closing app if any field has focus.
Bad illumination patterns with high values of blur in spotlights.
Random crash using denoiser.
Switching between GPU and CPU engines at render time can make some emitters to stop working.
Slow render using custom alpha channel on 2 socket machines.
If an instance of an object has a material but the original object uses the default one, both of them use the default material.
Deleting BSDFs with FIRE-GPU “on”, makes other objects to change their material.
Object opacity clipmaps fail in some scenarios.
Ghost BSDF in combination with other BSDFs doesn’t behave as expected.
Some scenes have noisy caustics where draft CPU engine doesn’t.
Some monochrome images (i.e. TIF format) do not work properly in monochromatic maps (i.e. opacity).
“No tiling” feature on textures does not work.
Render Booleans are not interacting properly with indirect lighting rays.
Black emitter + BSDF makes FIRE to crash at stop.
FIRE-GPU can crash at material change.
Monochrome textures not being sampled properly.
Textures for opacity layers not working in emitters.
Re-enable a disabled material layer with FIRE running may crash.
Moving an emitter with FIRE running may crash.
Materials with roughness between 90 and 100 may not behave as intended.
Repeated textures are repeated on GPU memory too.
CPU memory peak on GPU copy.
Moving instances on FIRE-GPU may crash.
Changing resolution between renders may make GPU render to crash.
Multistep motion blur may have triangles disappearing