OTOY Forums

hi azen

i will later to day.

jorgensen

an other "issue"

all these nodes are completely useless, i can't navigate in this..

am i doing something wrong here? i just wanteded to copy a camera (for safty reasons, as i can't lock it), then i selected "show in graph editor" and......

jorgensen

Hi Jorgensen,
you need to select the Default View Render Target, then choose "Show in Graph Editor", and expose the Camera node.
Note that you can navigate in Viewport, and press the icon in screenshot, to go back to the first camera position exported: ciao beppe

I don't know what to say anymore guys. TiG's exporter still works wonders (v2017). The geometry is crisp and clean and organized.

Alternatively, had to wait 5 minutes for Octane plugin to build an empty scene on startup.

I gave up SU plugin almost three years ago, shortly after this "https://render.otoy.com/forum/viewtopic.php?f=31&t=45091"

BUT it has huge potential so I give it a try once more.....(now I can work 5-6 minutes whit out a crash, its a big improvement

1.
The geometry building has to bee faster. This to unleash big potential in direct feedback geometry editing and octane render kernel quality.

2.
Proxies and scatter are essential (I rely misses the old feature off low polygon generated stand-in in previous version. Its a downgrade in this respect).

3.
Window insertion has to update hole cutting

4.
Why are there difference in GUI plugin and Standalone? make it the same if there are not a god reason otherwise!!!

5.
Organizing of material nodes and naming of groups has to be better. Can the plugin generate a folder for each file when exporting (the asset folder is a mess).
Material nodes disappear all the time. Can it save material nodes if u group them and they are not connected?

6.
The UV size bug should bee easy to fix (working in meters and it multiply every values with 25,4/inches).

Proxies and scatter is a no no!!! (instant crash)

Proxies and only copy rotate etc. seems OK, but if I try to change material or lighting after use of proxies > instant crash.
It's also impossible to use octane on that file anymore. Has happened to five files in a row. Attached the last one.

hi azen

it's quite (to) easy to get sketchup / octane render to crash.

if i create a simple box by 1m x 1m x 1m, and export this as extensions > octane > export to > .ocs. and then use this box as a proxy - in a new scene, sketchup crashes instantly.

jorgensen

Jorgensen wrote:hi azen

it's quite (to) easy to get sketchup / octane render to crash.

if i create a simple box by 1m x 1m x 1m, and export this as extensions > octane > export to > .ocs. and then use this box as a proxy - in a new scene, sketchup crashes instantly.

jorgensen

I think the reason for this is when exporting link to the assets folder are generated and still present in SU file, thus getting a conflict linking this file.
At least this was what happened to me. I closed and reopened and proxie OK. But got a LOT of extra nodes (see image "ocs_groups2.png" in next post).

When using groups things get complex weary fast, and the consistency of how groups works inside SU and octane are not god. A strategy on this are important.
Should we only use components?
Maybe the developers of Scatter for SU has some input?
When exporting to Standalone and reopen, a file consisting only of 4-5 cubes, it gets insanely complex (see "ocs_groups2.png"). Azen, haze, beppe, CaptainCrowbar.....anybody?

Jorgensen wrote:hi azen

it's quite (to) easy to get sketchup / octane render to crash.

if i create a simple box by 1m x 1m x 1m, and export this as extensions > octane > export to > .ocs. and then use this box as a proxy - in a new scene, sketchup crashes instantly.

jorgensen

Hi Jorgensen,

We are aware of the proxy issues, and will address this once we have the Scatter issues resolved. There are pending updates internally that will contribute towards resolving this issue. Apologies for the inconvenience.

Cheers,
Azen