I have found several clues, and eliminated some potential troubles. In Blender console, I have seen that some empties and curves present in the layers selected for the alembic export were signaled. I moved them on an unexported layer, as well as a very simple object with only two materials causing trouble for an unknown reason, and also an object with an unused material.
After this cleaning, I still get the server crash.
I also have :
Octane : WARNING : only nodes-textures are supported
Octane : WARNING : only nodes-materials are supported
But as Alembic doesn't manage with materials and textures (I will set them up in Standalone anyway), I don't think that these two warnings are essential.
I did more tests and noticed one line in the Blender console saying that the server failed searching a Compute 1.3 model (which is not supported) !My cards used for rendering are GTX 380 3GB (Compute model 2.0), selected in the plugin panel in check boxes 1 and 3, as it they are in Octane's preferences\Cuda panel.
My display card is a GTX 260 (Compute model 1.3) is not used for rendering, and is in position 2 in Octane's Preferences\Cuda panel and is unchecked.
Displaying my scene in Blender 3D Window in Rendered mode works fine and I have perfect interactivity like in Octane. I can enable at any time GPU 1 or GPU 3 and see the Fps count changing, tells me that everything works well at this point.
But whatever Display mode I use in Blender (Solid/rendered), attempt to render with Octane Inside Blender sometimes works, but more often fail when the line of top of the Render window says "Refreshing server", and the server closes.
The main problem remains the same: the Alembic export fails as said previously : Blender console saying that the server failed searching a Compute 1.3 model (which is not supported) !
Why is the plugin searching a Compute model 1.3, as it is not supported ?
Please could you fix that ?
Cheers,
Philippe.
.