You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a scene in blender 2.93.5
I am running blendluxcore v2.6, github 78ed64744d60f28f03e4a735254b637f2b32973d from Dec 27, 2021
I am on Linux Ubuntu 20.04.4 LTS (focal)
I run Python 3.8
PySide is not installed
The scene renders fine in the blender window in "render preview" mode
It also renders fine when I press F12
However, when I save it to a .bcf file (via LuxCore FileSaver in binary mode) and try to render from the command line using the following command:
To try and understand what happens, I straced the pyluxcoretools command.
Turns out after each Loading serialized image map: message is printed, a crapload of data is indeed read from the bcf file (lotsa read and brk syscalls) , but there are neither an open or a write syscall anywhere to be seen in the log.
It eventually gets to a stat("/tmp/tmptd9ucxy7.jpg", 0x7ffcfdb47e80) system call which - unsurprisingly - fails.
Hello,
I have a scene in blender 2.93.5
I am running blendluxcore v2.6, github 78ed64744d60f28f03e4a735254b637f2b32973d from Dec 27, 2021
I am on Linux Ubuntu 20.04.4 LTS (focal)
I run Python 3.8
PySide is not installed
The scene renders fine in the blender window in "render preview" mode
It also renders fine when I press F12
However, when I save it to a .bcf file (via LuxCore FileSaver in binary mode) and try to render from the command line using the following command:
python3 pyluxcoretools.zip console /tmp/luxcore/rampe.lampes_LuxCore/00001.bcf
I get the error shown below at the end.
It looks like it is deserializing the textures fine but fails to find them after deserialization ...
The BCF file is 220 megs, so I'm not even going to try and attach it to this issue, but you can download it here:
(220 megs) 00001.bcf
or alternatively : curl 'http://95.217.220.241/00001.bcf' > 0001.bcf
Here's the error message:
`
...
`
The text was updated successfully, but these errors were encountered: