OTOY Forums

smicha wrote:Important question Captain: will I be able to use ocs (e.g. as proxy) when the ocs was created under 3.00?

Probably not. Some 3.0 OCS that only use features common to v2 and v3 may work, but files that use any new features from 3.0 are unlikely to work with a 2.x plugin.

Octane 3.0 is still in its early test release phase; we don't have a definitive roadmap yet. You can expect to see a test release of a 3.0 version of the SketchUp plugin at some point, but I can't give you an ETA for that yet.

Thanks captain for the answer. It's good that we can use obj proxy - for me it's for preview purposes as the standalone is still my primary Octane engine.

BTW - do you plan to work on nodal approach that Fuzzy started?

Hello and regards,

I wanted to wish you all a Happy 2016, I now have a license for this plugin and am excited to use it and see it's development. I mainly use Daz Studio and am a heavy user of its Octane plugin.
Because I have been involved in the Daz forums, while the Daz plugin went from a really low state to a now much higher state, I am interested to share thoughts and workarounds I encounter while this plugin develops towards V3.

My first findings are that this is rather stable, as so long as I am aware of some things. (apologize if these are known in the manual, or mentioned in the forum somewhere).

(1) Tab Whitening (going blank)
One thing that I first ran into was that the 'Octane Material Editor' tab would suddenly blank to white, and then the 'Octane Viewport' and 'Octane Materials' tabs would quickly follow. I had to close out of SU and reload the whole scene in SU in order to get them functioning again, but ultimately it would happen again. Way to resolve is to close out all the Octane tabs, then FIRST open up the 'Octane Viewport', followed by the materials. In this order, the functionality will be restored without needing to close out and reopen SU itself.

(2) Materials not updating
Way to resolve is to click that round arrow for building geometry on the 'Octane Viewport', it seems to then 'unlock' the live updating of materials that you are attempting to edit. For example, I changed a car's body color, then when I tried the windows it was not working. But then when I rebuilt the geometry on the Viewport, all of the sudden now the windows could be tweaked just fine.

(3) Export to OCS causes 'Octane Viewport' to turn to mush
Again, way to resolve is by clicking that round arrow for building geometry on the 'Octane Viewport'. This button returns it back to normal, although it does have to render again.

Anyway, just wanted to say hello and give a heads up on my workarounds. Looking forward to everyone else's posts.

This was just a scene with other creator's 3DWarehouse components while I messed with the plugin. And here is the Haunted 'V3 Medium Scattering' version with the standalone

blank octane viewport.

the first time i open the octane viewport it works just fine, when i open again the viewport stays blank

jorgensen

I had the issue some time ago - what I noticed is that after closing vram does not drop on a rendering card.

hi smicha

how do you close vram?

thanks

For now it's fine (win 7 + SU 2016). What I did (if I remember well) I opened and closed material editor. Let me know if it works.

well it seems that the material editor is doing something, but the editor is also stays blank.
but now i can open the render view, but i need to open an close the editor every time.

i might need to update screen drivers, but there is no contact to nvidia right now.
sometimes the view looks like the attached screenshot.

as the skatter plugin did not work, i had to update internet explorer.
could that be the problem?

try to orbit your scene and see if it helps

Are you guys up to date with your nVidia drivers?