How to Install Blendluxcore for Blender on Google Colab
How to Install Blendluxcore for Blender on Google Colab
Someone just made it : https://youtu.be/sZus3-Mkxg0
Re: How to Install Blendluxcore for Blender on Google Colab
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:
https://drive.google.com/file/d/1c64NPb ... 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:
https://colab.research.google.com/drive ... 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:
https://drive.google.com/file/d/1jCLXN_ ... 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"
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:
Render will assume all settings done in file.
Point to file and render, like in last steps of the 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:
https://drive.google.com/file/d/1c64NPb ... 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:
https://colab.research.google.com/drive ... 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:
https://drive.google.com/file/d/1jCLXN_ ... 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"
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:
Render will assume all settings done in file.
Point to file and render, like in last steps of the Colab.
Re: How to Install Blendluxcore for Blender on Google Colab
Help me fix this. This is the same case with v3.0
Re: How to Install Blendluxcore for Blender on Google Colab
I fixed this I forgot to follow the automatic pack resources and output past now it is rendering, thanks alot.
Re: How to Install Blendluxcore for Blender on Google Colab
But the the render result is completely black. Any idea?
Re: How to Install Blendluxcore for Blender on Google Colab
It will output whatever and wherever is setup on file, by default is tmp directory, change that to a meanfull directory or keep it relative to file (//). Also change whatever layer passes and file format output you want, save and re upload file to Google Drive.
Re: How to Install Blendluxcore for Blender on Google Colab
Little update as I wanted to create a version without the need to load anything externally, I stumbled upon the fact that NVIDIA drivers wouldn't work with OCL , and couldnt find the exact way to set default render to CUDA, asked around and was mocked on Blender # code for using Chat GPT, turns out I used Chat GPT to find the exact proper sintax and...it delivered
Blender 4.0.2 using Blender alpha 2.8 (should be easy to translate to 4.1 when a working linux version of 2.9 is available)
https://colab.research.google.com/drive ... sp=sharing
The usual recommendations apply: Pack everything in file and set output in .blend file to //
I personally use EXR multilayer so outputs everything to same file.
As curiosity:
https://chatgpt.com/share/d3b9d220-4bba ... e0f0448014
Blender 4.0.2 using Blender alpha 2.8 (should be easy to translate to 4.1 when a working linux version of 2.9 is available)
https://colab.research.google.com/drive ... sp=sharing
The usual recommendations apply: Pack everything in file and set output in .blend file to //
I personally use EXR multilayer so outputs everything to same file.
As curiosity:
https://chatgpt.com/share/d3b9d220-4bba ... e0f0448014