Mirage 3.7 is out now

It’s been a while, has­n’t it? Life has been real­ly, real­ly hec­tic. But there’s always some time to work on Mirage! This new ver­sion comes with a com­plete revamp of the dis­tri­b­u­tion sys­tem, now using Geometry Nodes. Also M1 macs are sup­port­ed now. The first thing you will notice is that changes are applied inmedi­ate­ly. Vertex groups or 

Render+ 2.5 released

It’s that time of the year again! A new Render+ release is out with some new fea­tures, some life qual­i­ty improve­ments and a bunch of bug fix­es. Verison 2.5 brings mul­ti­ple cus­tom frames, frame jump con­trol for ani­ma­tions, bet­ter tools for trou­bleshoot­ing, sup­port for Blendfiles com­pressed with Zstd (Blender 3), and a new option to run a python script (from

Render+ 2.4 out today

Today is release day! Render+ 2.4 is out. Also known as the spit and pol­ish release. The pre­vi­ous refac­tor in 2.3 unfor­tu­nate­ly intro­duced a num­ber of regres­sions and oth­er ran­dom bugs. There’s also a cou­ple of improve­ments to make the UI less con­fus­ing and some ini­tial work on Blender 3.0. Take a look at the list of fixes 

Mirage 3.6 is out

No video this time, because a lot of the improve­ments are basi­cal­ly iter­a­tive or under the hood (also had no time to make a full video TBH). This release comes with much need­ed per­for­mance work, bet­ter mate­ri­als a new mod­i­fi­er. I also did some jan­i­tor work remov­ing dead code and improv­ing sev­er­al parts of the ter­rain mod­ule with the recent 

This week(s) in Mirage #7

Welcome to anoth­er pro­duc­tive week for Mirage! This time I focused on fix­ing seam­less ter­rains. Seamless ter­rains have match­ing edges and can be tiled and repeat­ed.  I had this work­ing a while ago at the noise gen­er­a­tion lev­el. The Perlin func­tion I’m using is peri­od­ic, so it’s pos­si­ble to grab coor­di­nates out­side of the ter­rain and interpolate 

This week(s) in Mirage #6

Whoa, how long has it been? Wasn’t I sup­posed to do this every week? These last few weeks have been crazy with work, life, the release of Blender 2.80, Mirage 3.2 and Render+ 2. But that’s all done now. Time to get back on the horse! The good news is that I still man­aged to put some 

This week in Mirage #5

Time for the usu­al week­ly devel­op­ment news. This week I worked some more on the water ero­sion mod­i­fi­er. I start­ed by fix­ing the ran­dom­ness of the rain. Every iter­a­tion 100 drops fall at ran­dom places in the ter­rain. The prob­lem was that I was­n’t keep­ing the seeds for the ran­dom val­ues around so every­time a set­ting changed it 

This week(s) in Mirage #4

These last two weeks have been pret­ty busy, both in work/life and Mirage. On the mirage side, I port­ed the last mod­i­fi­er: flu­vial ero­sion. I spent the first week writ­ing the ini­tial imple­men­ta­tion and this week mak­ing it actu­al­ly work. Many moons ago I wrote a pure Python imple­men­ta­tion of the vir­tu­al pipes hydraulic ero­sion algo­rithm. It was crazy slow. 

This week in Mirage #3

Thermal ero­sion is now ful­ly port­ed! There isn’t a very notice­able dif­fer­ence this time around, I think it looks a bit bet­ter though (but maybe I’m biased!). I also changed the set­ting names to make them eas­i­er to under­stand: Repose Angle is now Threshold Iterations is now Time They are also short­er too, so they work nice­ly in 

This week in Mirage #2

This week went bet­ter than expect­ed in many ways. I end­ed up get­ting the mod­i­fi­er work done fair­ly quick­ly and man­aged to squeeze a small refac­tor, break­ing a ~1300 lines file into 3 files. I still have som­re more refac­tor­ing to do to make things more flex­i­ble. Hopefully I can get to that too in the fol­low­ing weeks.  Porting went smoothly 

This week in mirage

In this series of posts I’m going to talk about the new hot stuff I’m work­ing on for Mirage. This will be my first time doing a devlog, so bear with me 🙂 Our first stop is what I’ve doing for the past few months: the Rust port. Port to Rust Rust is a pro­gram­ming lan­guage focus­ing on safe­ty, per­for­mance and 

A look at security in Blender

A few moons ago secu­ri­ty researchers at Cisco made waves in the Blender com­mu­ni­ty after dis­clos­ing a num­ber of vul­ner­a­bil­i­ties that could allow an attack­er to run arbi­trary code. All the of them were fixed by 2.79a but it’s still pos­si­ble to make Blender run arbi­trary code.