Linux OctaneServer / Alembic Camera / ACES CM issues
Posted: Thu Apr 27, 2017 5:21 pm
CentOS 7 (3.10.0-514.10.2.el7.x86_64)
2x1070 8gb
32gb system ram
375.39
OctaneRender™ for Blender 3.05.3 - 11.24 [STABLE]
OctaneServer runs quiet unstable, eats up a lot of memory and transfers data quiet slow.
First of all: I tested the maya demo plugin and the scene transfers much faster, but maybe no bug at all.
Biggest issue is the memory usage. I have a scene in blender that cannot be rendered directly in the app but uses only 3gb VRAM in the standalone. Also BlenderOctane/OctaneServer seems to not clean empty memory after rendering a couple of times the memory is full and i have to KILL and restart the OctaneServer.
Thats really annoying because i cannot light my scene in blender anymore since it uses too much VRAM in blender. Even if i let blender stay open and use Octane Standalone on another virtual desktop it works...so its not the blender guy that eats up all the VRAM.
Another thing i just recognized: If i have a alembic cam in blender and write the whole scene out to .orbx the camera has messed up transforms. Maybe Euler rotations? If i import the same cam i used in blender to the standalone, the camera works well.
ACES files are not found. I'm using a global profile (OCIO EnvVar). Blender(not BlenderOctane) picks up the color profiles perfectly while BlenderOctane gives me errors:
Color management: using fallback mode for management
Color management: display "ACES" used by scene not found, setting to default ("sRGB").
Color management: scene view "sRGB" not found, setting default "Default".
Color management: sequencer colorspace "ACES - ACEScg" not found, will use default instead.
Thanks.
2x1070 8gb
32gb system ram
375.39
OctaneRender™ for Blender 3.05.3 - 11.24 [STABLE]
OctaneServer runs quiet unstable, eats up a lot of memory and transfers data quiet slow.
First of all: I tested the maya demo plugin and the scene transfers much faster, but maybe no bug at all.
Biggest issue is the memory usage. I have a scene in blender that cannot be rendered directly in the app but uses only 3gb VRAM in the standalone. Also BlenderOctane/OctaneServer seems to not clean empty memory after rendering a couple of times the memory is full and i have to KILL and restart the OctaneServer.
Thats really annoying because i cannot light my scene in blender anymore since it uses too much VRAM in blender. Even if i let blender stay open and use Octane Standalone on another virtual desktop it works...so its not the blender guy that eats up all the VRAM.
Another thing i just recognized: If i have a alembic cam in blender and write the whole scene out to .orbx the camera has messed up transforms. Maybe Euler rotations? If i import the same cam i used in blender to the standalone, the camera works well.
ACES files are not found. I'm using a global profile (OCIO EnvVar). Blender(not BlenderOctane) picks up the color profiles perfectly while BlenderOctane gives me errors:
Color management: using fallback mode for management
Color management: display "ACES" used by scene not found, setting to default ("sRGB").
Color management: scene view "sRGB" not found, setting default "Default".
Color management: sequencer colorspace "ACES - ACEScg" not found, will use default instead.
Thanks.