OTOY Forums

WOW New Release.... Thanks...

I did two updates today.
When I updated from 2.25r3 to 3.00a3.1, the live viewfinder crash I had been experiencing before went away, didn't crash all day.
When I updated from 3.00a3.1 to 3.00a6 the crashing came back instantly.
Same situation, with Live Viewer active and network render active caused crashing moving around the scene.
There are no errors on the network side.
ScreenGrab: https://www.dropbox.com/s/1gnb8ia4089mh ... h.mp4?dl=0

Let me know if there is any other info I can help provide.

natemac00 wrote:I did two updates today.
When I updated from 2.25r3 to 3.00a3.1, the live viewfinder crash I had been experiencing before went away, didn't crash all day.
When I updated from 3.00a3.1 to 3.00a6 the crashing came back instantly.
Same situation, with Live Viewer active and network render active caused crashing moving around the scene.
There are no errors on the network side.
ScreenGrab: https://www.dropbox.com/s/1gnb8ia4089mh ... h.mp4?dl=0

Let me know if there is any other info I can help provide.

do you have running alpha6 on client side?

aoktar wrote:

natemac00 wrote:I did two updates today.
When I updated from 2.25r3 to 3.00a3.1, the live viewfinder crash I had been experiencing before went away, didn't crash all day.
When I updated from 3.00a3.1 to 3.00a6 the crashing came back instantly.
Same situation, with Live Viewer active and network render active caused crashing moving around the scene.
There are no errors on the network side.
ScreenGrab: https://www.dropbox.com/s/1gnb8ia4089mh ... h.mp4?dl=0

Let me know if there is any other info I can help provide.

do you have running alpha6 on client side?

Of course.
I just swapped back to stand along a3 and plugin a3.1 and live viewer runs like a charm.
It only occurs in 2.25r3 and 3.00a6. I've only tried those 3 versions of the plugin with Stand Alone, so that's all I can validate.

natemac00 wrote: Of course.
I just swapped back to stand along a3 and plugin a3.1 and live viewer runs like a charm.
It only occurs in 2.25r3 and 3.00a6. I've only tried those 3 versions of the plugin with Stand Alone, so that's all I can validate.

What's your osx, nvidia/cuda driver versions?
Ok. Do this tests:
1a-Activate "async. updates on settings->other". Switch to on view layout. And do same actions with A6. Netrender=Enabled.
1b-Disable "async. updates on settings->other". Switch to on view layout. And do same actions with A6. Netrender=Enabled.

2a-Activate "async. updates on settings->other". Switch to on view layout. And do same actions with A6. Netrender=Disabled.
2b-Disable "async. updates on settings->other". Switch to on view layout. And do same actions with A6. Netrender=Disabled.

Give me the results.

aoktar wrote:

natemac00 wrote: Of course.
I just swapped back to stand along a3 and plugin a3.1 and live viewer runs like a charm.
It only occurs in 2.25r3 and 3.00a6. I've only tried those 3 versions of the plugin with Stand Alone, so that's all I can validate.

Ok. Do this tests:
1a-Activate "async. updates on settings->other". Switch to on view layout. And do same actions with A6. Netrender=Enabled.
1b-Disable "async. updates on settings->other". Switch to on view layout. And do same actions with A6. Netrender=Enabled.

2a-Activate "async. updates on settings->other". Switch to on view layout. And do same actions with A6. Netrender=Disabled.
2b-Disable "async. updates on settings->other". Switch to on view layout. And do same actions with A6. Netrender=Disabled.

Give me the results.

I'm missing which setting this is or am I in the wrong place?

i meant "syncronisation on geo. updates". Sorry

3.00 Alpha 6
Sync Geo - Enabled|Network - Enabled = No Crash
Sync Geo - Enabled|Network - Disabled = No Crash
Sync Geo - Disabled|Network - Enabled = Crash
Sync Geo - Disabled|Network - Disabled = No Crash
(Restarted Cinema for each test)
Ran each twice with same results.
Original Test File: https://www.dropbox.com/s/cubsxh7awvgi7 ... 1.c4d?dl=0
Screen Grab: https://www.dropbox.com/s/8p73aim17n07m ... s.mp4?dl=0

3.00 Alpha 6
Sync Geo - Enabled|Network - Enabled = Crash
Sync Geo - Enabled|Network - Disabled = No Crash
Sync Geo - Disabled|Network - Enabled = Crash
Sync Geo - Disabled|Network - Disabled = No Crash
(Restarted Cinema for each test)
Ran each twice with same results.
Test File: https://www.dropbox.com/s/bzkscivec3qx0 ... e.c4d?dl=0
Screen Grab: https://www.dropbox.com/s/y928zds990l0s ... t.mp4?dl=0
(This type of area light crash I think I noticed in Alpha 3 as well)

Might be a stupid question but does anyone know why the renders are coming out black? Just installed the Alpha6 version

krofl wrote:Might be a stupid question but does anyone know why the renders are coming out black? Just installed the Alpha6 version

Not a problem. It's a bit tricky and experimental to make proper pairs from TFD to Octane. If you add and object tag it would try to initialize the proper settings for you as TFD's settings.
It looks to available channels of tfd and also render smoke/fire shader settings.

In Medium tab, we should set which channel goes to Octane's output. I suppose we should have filled abs/scatter channel. If you want to see emission effects, need to have a texture emission in Medium Volume, also rgb/float/etc.. textures in Scatter/Absorption slots.