ivom wrote:I know that for using XSI plugin in full version you also need standalone license(I have both). Does this mean you need also Octane standalone installed on same machine you are using XSI plugin?
Hm, good question,
i think it is enough to have the license.
ivom wrote:Is it correct if we have Octane 2.X standalone and I'm rendering inside XSI(plug ver. 1.02RC11), plugins reports OctaneRender version 1.55 (1550000). Is it because it is compiled using 1.55 SDK? and therefore it won't have 2.X features yet?
Yes, thats correct. There are some missing features which aren´t implemented in the 1.x version. So i want to implement it first for the users which have payed for the 1.x version before i switch to 2.x.
ivom wrote:Also I'm experiencing some crashes with very simple scene (1 cube without texture), when I left render region open with XSI idling, XSI after while runs out of memory.Process monitor shows plenty of free ram. Maybe it needs more GPU RAM but I don't have any GPU RAM monitor(have you some favorite?) at the moment so it hard to say why need so many GPU RAM.
Thank you
Thanks for the info with the memory leak, will try to fix it.
A simple cube should ever fit in your memory.
GPU-Z is a good monitor. For windows 7 you can find some gadgets, when they are enabled on your system.
ivom wrote:Something is wrong with Texture_Mix node. Whenever I'm using it, material behaves like standard diffuse. When I debugging scene graph it doesnt translate texture_mix node at all. See attached picture.
You have a texture_mix and a material_mix. The first is only for textures, the other onyl for materials.
This is bad to handle in Softimage because they used the some output pins.
face