I can confirm that with a fresh enblend build from yesterday (enblend-4.2.0-993) this bug is fixed! :) Big thanks from me Mikolaj!
I can confirm that with a fresh enblend build from yesterday (enblend-4.2.0-993) this bug is fixed! :)
Big thanks from me Mikolaj!