OTOY Forums

Seems that most Octane for SketchUp users has left for V-Ray, or to the Standalone. It's a pity, .....it deserves a lot more attention. From my point of view as an architect, this plug-in has the most potential to release the MAGIC which CEO Jules Urbach talked about in this presentation: https://www.youtube.com/watch?v=TZCfg4doWYg

Arcitects using SketchUp are a HUGE user base for OTOY to tap into. And Octane has the edge in fast viz, if only it was more accessible. Architects generally don't want to learn Cinema 4D, Maya or MAX etc...
Jules are you listening?

I am reading the bugs and roadmap thread and can't help thinking that this plug-in needs more momentum and love from OTOY.

Some suggestions:
-Ask users (when there are some still using it) to test specific features that are in focus for next release.
-Make a list of feature not to use, news and technical details. Ref. http://poserphysics.blogspot.no/2016/03 ... pport.html
-Make a road map
-Give users a reason to invest their time (free v4 upgrade?)

Best Regards,
Johnny

Found a fairly stable working method....

1. Don't use materials

2. Load/unload terrain proxies from standalone (with materials).
It's a must to unload it before saving, or doing anything besides simple push/pull and move operations.

A request for next release:
Make the plug-in remember the positions of nodes in the nodegraph editor. My head is about to explode

Hi all,

Many thanks for the helpful suggestions. Just to keep the thread updated on progress - some of the more complex low-level integration challenges is now also being addressed with help from an additional developer. This has been very helpful thus far, and we are currently in the middle of testing and validating a fresh build with improvements to the inner-workings of the Octane Viewport and Nodegraph.

azen wrote:Hi all,

Many thanks for the helpful suggestions. Just to keep the thread updated on progress - some of the more complex low-level integration challenges is now also being addressed with help from an additional developer. This has been very helpful thus far, and we are currently in the middle of testing and validating a fresh build with improvements to the inner-workings of the Octane Viewport and Nodegraph.

Hi Azen,
Thanks for the update. Good to hear about the additional resources allocated to SU plug-in

The low-level integration are it related to major changes in Octane SDK, and preparing for Brigade in next release. Can you tell us anything about that?

FYI - I just tried Sketchup 2018 with Octane Render for SketchUp 3.07.0.14.

I have SU 2017 installed, and reinstalled the latest octane plugin.

I then copied the plugin stuff from the 2017 plugin folder over to the same folder in 2018.

The file:
C:\Users\<...>\AppData\Roaming\SketchUp\SketchUp 2018\SketchUp\Plugins\octane_render.rb
The folder and all contents:
C:\Users\<...>\AppData\Roaming\SketchUp\SketchUp 2018\SketchUp\Plugins\octane\

Started up SU 2018 and everything seems to be working OK. Note the sun/shadow on SU does not control octane's environment. However octane's Sun/Sky environment DOES control the SketchUp settings.

Honestly we got tired of trying beta versions.
We also paid the PLugIn (and I personally bought two) in addition to the standalone engine.
if Otoy wants us to continue using Octane, after two years, I think it's time to get a professional version, There are many other render engines on the market, really stable.
If we have to keep doing the beta testers, tell us clearly and roundly, we should eventually be compensated for this.
I do not know about you, but we have to work, do not play bugs... Two years of tips and strategies to get around the bugs! but come on, it's a shame.

ArchMP wrote:Honestly we got tired of trying beta versions.
We also paid the PLugIn (and I personally bought two) in addition to the standalone engine.
if Otoy wants us to continue using Octane, after two years, I think it's time to get a professional version, There are many other render engines on the market, really stable.
If we have to keep doing the beta testers, tell us clearly and roundly, we should eventually be compensated for this.
I do not know about you, but we have to work, do not play bugs... Two years of tips and strategies to get around the bugs! but come on, it's a shame.

Exactly!!

And A Good Year to everyone

cheers

ArchMP wrote:Honestly we got tired of trying beta versions.
We also paid the PLugIn (and I personally bought two) in addition to the standalone engine.
if Otoy wants us to continue using Octane, after two years, I think it's time to get a professional version, There are many other render engines on the market, really stable.
If we have to keep doing the beta testers, tell us clearly and roundly, we should eventually be compensated for this.
I do not know about you, but we have to work, do not play bugs... Two years of tips and strategies to get around the bugs! but come on, it's a shame.

+1
I am very tired too

ArchMP wrote:Honestly we got tired of trying beta versions.
We also paid the PLugIn (and I personally bought two) in addition to the standalone engine.
if Otoy wants us to continue using Octane, after two years, I think it's time to get a professional version, There are many other render engines on the market, really stable.
If we have to keep doing the beta testers, tell us clearly and roundly, we should eventually be compensated for this.
I do not know about you, but we have to work, do not play bugs... Two years of tips and strategies to get around the bugs! but come on, it's a shame.

+1
approaching 4 years waiting....

Not sure if this has been mentioned before but the materials that get created when launching the plugin are glossy by default, is there a plan to make that diffuse instead? Is there a way to prevent this?