Yes, Blender is free
(but what does it really mean?)

A 3D mod­eller, ani­ma­tion suite and not one but two ren­der engines. Blender’s code­base is full of insane­ly com­plex work and math. So, how can it be free? We’re talk­ing about one of the most math inten­sive prob­lem domains in soft­ware. It’s no won­der that in all these years there have been very few open source 

Mirage 3.5 Beta

Oh hey, it’s been a while! As you might guess what was to be a short, self-con­­tained, rea­son­able release turned into a chaot­ic avalanche of fea­tures. Typical. You fix one thing and then you get an idea to make some­thing bet­ter. You get on it since it’s a small change, and when you snap out of it weeks have 

Easy batch rendering with Render+ 2.2

Watch out! A new ver­sion of Render+ is out. We final­ly take the first step towards net­work ren­der­ing and many improve­ments all around. Network ren­der­ing The batch serv­er can now be run in a sep­a­rate com­put­er. For now, the serv­er also does the ren­der­ing. I will be work­ing on dis­trib­uted ren­der­ing over future releas­es. Please refer to the 

A quick peek at Mirage 3.5

I’ve been work­ing on Mirage 3.5 for a while now and have some neat new fea­tures to show; includ­ing a new move/rotation tool, new ter­rain type, new mod­i­fiers sys­tem, new set­tings for mod­i­fiers, rewrit­ten mod­i­fiers, dis­tri­b­u­tion sys­tem maps and more. This is still heavy work in progress so many things can still change.

Mirage 3.4 is out today!

The time has final­ly come. Mirage 3.4 is out today! The high­light of this release is the new ter­rain engine. It’s been a while, has­n’t it? This has prob­a­bly been the longest time between releas­es, but there’s a good rea­son for the delay! Mirage 3.4 comes with a new ter­rain engine com­plete­ly rewrit­ten in Rust for top-per­­for­­mance. I’ve codenamed 

Render+ 2.1 is out

It’s release time! Render+ 2.1 is now out. This ver­sion comes with sev­er­al small qual­i­ty of life improve­ments. I’m try­ing to small­er, more fre­quent releas­es mov­ing for­ward. This way you can get bug fix­es and small improve­ments faster instead of wait­ing until I imple­ment some big fea­ture. Let’s look at the changes in this ver­sion Debug messages 

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 

Render+ 2 released

After a long time Render+ 2 is final­ly out. I start­ed work­ing on this ver­sion on September last year, and went into beta around January until now. But the plan­ning for these changes goes back years. I’m real­ly hap­py with this release, the code base and the whole sys­tem have tak­en a leap for­ward in qual­i­ty. These changes pave 

Mirage 3.3 out for Blender 2.80

New Blender, new Mirage. Or so I’d like to say. This is bor­ing release actu­al­ly. The only news is com­pat­i­bil­i­ty with Blender 2.80. Note that from this point onward, Mirage will require at least Blender 2.80. All the new fea­tures I’ve been blog­ging about will come in the next ver­sion: 3.4. Join the mail­ing list 

Blender 2.80 released!

Blender 2.80 is out today after almost a year and a half in devel­op­ment. Time to cel­e­brate! This is one of the largest and most impor­tant releas­es of Blender. As big as 2.5 back in the day.  So, what’s the big deal? Don’t be fooled by the ver­sion num­ber. 2.80 isn’t just 0.01 bet­ter than 2.79, it’s 100x times 

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