The issues are in 2015.

Yes - you must open the preview window (render) to export to ocs. Does it work for you?
Yes it works for me, but the standalone is very complex, I prefer to render within sketchup and because the material editor is screwy I cant at the moment.
I think large sketchup models are causing problems for ...

Everything works fine . Please send an example with skp file that causes your problems and I convert it into ocs scene.
OK, I think as a new user I am getting confused so my apologies. Can you read my first post where I asked how do I export to ocs from sketchup?
The export to ocs is greyed out in ...

smicha wrote:It's built in the plugin - save to ocs.

The one that doesn't work?

TIG's exporter works like a charm. Just export each component separately and join them with the 'geometry group' node in the standalone.
I'm confused, I just found TIGS exporter thread and in Dec 2014 he said

"I have stopped any further development of this Ruby script. :-( I'm afraid it stays as ...

I'm sorry but here is simply no good exporter from sketchup to standalone.
Don't even bother with the SU plugin for exporting as the way it is exported it is again unusable in standalone.
I guess you could use TIG's plugin for export IF you keep your poly count low.
Non of my models are low poly ...

Whats quickest way to export to standalone studio? Do I have to start the render once in Sketchup so it builds the octane geometry then export as .ocs?
Sorry for the noob question, I'm just back to trying octane now I have a decent machine and the SU plugin seems very unstable.

I've gone back to 2.13 - 0.13.87 and it works much better. Plus the renders start a lot quicker too. Latest version is screwed.

This version has a very unstable material editor. What version of the plugin is the most stable that I can go back to?

Any reason why 'export to OCS' is greyed out on my version?