How to Install Blendluxcore for Blender on Google Colab

Links and discussions related to tutorials, tips and tricks.
Post Reply
User avatar
Posts: 2996
Joined: Mon Dec 04, 2017 10:11 pm
Location: Ivory Coast

How to Install Blendluxcore for Blender on Google Colab

Post by Sharlybg » Tue Aug 31, 2021 10:58 am

Someone just made it :
Support LuxCoreRender project with salts and bounties

Portfolio :

Posts: 21
Joined: Sun May 09, 2021 5:28 pm

Re: How to Install Blendluxcore for Blender on Google Colab

Post by MCurto » Fri Jan 07, 2022 6:40 pm

Unfortunately Colab runs on Ubuntu 18 and newer versions of BlendLuxCore (2.6 and 2.6.1) for linux need something called GLIBC version 2.29 and Ubuntu 18 uses 2.27, so you can't really take the linux add-on from Github and put it in Colab.

I've compiled (my son actually did it for me) the 2.6.1 (from yesterday i think) on Uubunu 18 that you can run on Colab in Blender 3.0.

2.6.1 Latest with GLIBC 2.27: ... sp=sharing

I dont have the communication skills required to make an engaging video so just gonna describe here how to use Colab:

First and foremost you need a Google Drive, that's where all the permanent files will reside, communicates with Colab as permanent storage and will also save the renders there, Colab its allways the same machine sotware wise nut its nor permanent,every reconnect you'll be presented with same initial state machine, it changes somewhat hardware according to if you're using free or paid versions, paid versions unlock higher tier GPUs : P100/T4 16 GB on paid and K80's on free.

This is my notebook I use for render, anyone can copy as their own and modify if they like: ... sp=sharing

The Colab contents are as follows:

The preferences file (one might need to edit the path inside fileto installer if placed on a diferent folder) that points to installer,chooses CUDA and exits Blender saving preferences: ... sp=sharing

The usage is quite simple, I recommend you keep everything in the same folder in Google Drive, mine is Blender but feel free to customize.
For simplicity and ease of use the best way is to set EVERYTHING on file so:
-Pack resources and keep the Automatic
-Keep path relative
-Keep outputs relative ("//" or "//Renders" for instance if you want to have them in a folder Renders place above file.blend directory)
-Same for simulations, keep a folder ins same file.blend directory named "sim" or whathever and point path to "//sim"
Screenshot 2022-01-07 at 18.33.38.jpg

I think the rest is self-evident, but will explain anything further if needed.

This is my hierarchy, all files to be rendered in Blender main directory:
Screenshot 2022-01-07 at 18.44.30.jpg
Screenshot 2022-01-07 at 18.47.40.jpg

Render will assume all settings done in file.

Point to file and render, like in last steps of the Colab.

Post Reply