LuxCoreRender Forums

New LuxCoreRender v2.0alpha3 release is available at: https://luxcorerender.org/download/

v2.0 release notes are available here: https://wiki.luxcorerender.org/LuxCoreR ... Notes_v2.0

The complete list of changes between alpha2 and alpha3 in Luxcore API is available here (76 commits): https://github.com/LuxCoreRender/LuxCor ... v2.0alpha3

The complete list of changes between alpha2 and alpha3 in BlendLuxCore is available here (75 commits): https://github.com/LuxCoreRender/BlendL ... v2.0alpha3

Congrats to next step

Understanding question: is pyluxcoremerge working like former luxmerger ?
Aka ./pyluxcoremerge <optional args> filmfile1 filmfile2 ?
This is not fully clear to me. The helppage does not really imply i can merge
films here.

Jens

Thank you!

jensverwiebe wrote: ↑Sat Feb 03, 2018 10:09 pm Understanding question: is pyluxcoremerge working like former luxmerger ?
Aka ./pyluxcoremerge <optional args> filmfile1 filmfile2 ?
This is not fully clear to me. The helppage does not really imply i can merge
films here.

Yes and it is quite more powerful with the possibility to create custom films from .cfg files and to merge sub-regions of films (for instance to compose 4 tiles of a rendering in a new complete film). I wrote some information here: https://wiki.luxcorerender.org/Pyluxcoremerge

Dade wrote: ↑Sun Feb 04, 2018 1:12 pm

jensverwiebe wrote: ↑Sat Feb 03, 2018 10:09 pm Understanding question: is pyluxcoremerge working like former luxmerger ?
Aka ./pyluxcoremerge <optional args> filmfile1 filmfile2 ?
This is not fully clear to me. The helppage does not really imply i can merge
films here.

Yes and it is quite more powerful with the possibility to create custom films from .cfg files and to merge sub-regions of films (for instance to compose 4 tiles of a rendering in a new complete film). I wrote some information here: https://wiki.luxcorerender.org/Pyluxcoremerge

Ah okay, fantastic.
Btw: I wrote a bashscript that allows to setup all cmd-line tools from there in one action, so i needed that information.
For me has the advantage the uncompressed package is only 90MB cause i don't need full 30MB ( total 220MB ) binary for every function.

Jens

jensverwiebe wrote: ↑Sun Feb 04, 2018 1:26 pm Btw: I wrote a bashscript that allows to setup all cmd-line tools from there in one action, so i needed that information.
For me has the advantage the uncompressed package is only 90MB cause i don't need full 30MB ( total 220MB ) binary for every function.

The problem is that PyInstaller is currently packing a copy of everything required in each single pyluxcoretool executable (python, pyluxcore.so, all required libraries, pyluxcoretools, etc.). The exe are just auto-extracting .zip.

It is handy to move/copy each excitable around without any problem but they are LARGE.

If you keep the components in a single place (python, pyluxcore.so, all required libraries, pyluxcoretools.zip, etc.), the command itself is just few kbytes.

P.S. I could somewhat solve this problem by packing all pyluxcoretools in a single command like Git to have something like:

- pyluxcoretools merge <options>
- pyluxcoretools console <options>
- pyluxcoretools netconsole <options>
- pyluxcoretools netnode <options>

Dade wrote: ↑Sun Feb 04, 2018 1:35 pm P.S. I could somewhat solve this problem by packing all pyluxcoretools in a single command like Git to have something like:

- pyluxcoretools merge <options>
- pyluxcoretools console <options>
- pyluxcoretools netconsole <options>
- pyluxcoretools netnode <options>

Yeah, thats what my bashscrpt does kinda. Also it allows to again launch any binary until all wanted actions are done.
For example launch pyluxcorenetnode, then launch pyluxcorneteconsole to fire a renderjob.

@ just realized, lets go dev forum with this topic better. Willl post followups in networking thread.

Jens