Version 2.05.0 - Updated on (14.08.14)

[LFedit]

Aoktar, awesome work on the 2.02 plug in, the advancements in the plug-in are amazing! Just wondering if there is any difference in using the Foreground and Background object in the live viewer. It was working in 1.5.2 and have been using it for compositing work very successfully. Can you check this, or anyone else confirm it's not working? Thanks again, awesome job!

Thanks i'm trying to make it better,
i have worked on back/fore. objects since 1.52. It should work on LV and picture viewer as usual with standart material. Standart material should have a image in diffuse channel.

can anyone confirm this is working in 2.02 i'm not seeing back/fore. objects with diffuse texture in LV or picture viewer, thanks

[LFedit]

can anyone confirm this is working in 2.02 i'm not seeing back/fore. objects with diffuse texture in LV or picture viewer, thanks

I went back to 1.52 and tested, it worked. Reinstalled 2.02 and it's working. Must have had a strange install. Thanks Aoktar, keep up the awesome work!

[aoktar]

can anyone confirm this is working in 2.02 i'm not seeing back/fore. objects with diffuse texture in LV or picture viewer, thanks

I went back to 1.52 and tested, it worked. Reinstalled 2.02 and it's working. Must have had a strange install. Thanks Aoktar, keep up the awesome work!

strange, it's working as seen in picture. Thanks

[momade]

thanks aoktar. 'display tag' works fine as you described. but still i only get one kind of motionblur, no matter what i set the 'octane object tag' or 'octane render settings' to.

[Ron]

can anyone confirm this is working in 2.02 i'm not seeing back/fore. objects with diffuse texture in LV or picture viewer, thanks

I went back to 1.52 and tested, it worked. Reinstalled 2.02 and it's working. Must have had a strange install. Thanks Aoktar, keep up the awesome work!

strange, it's working as seen in picture. Thanks

Tried that, but getting only distorted background image in LV. Adjusting texture tag settings has no effect.

Any advise?

Ron

[aoktar]

thanks aoktar. 'display tag' works fine as you described. but still i only get one kind of motionblur, no matter what i set the 'octane object tag' or 'octane render settings' to.

what kind of mot. blur is expected else? There is only transform animation!!! Why don't you check my motion blur samples?

[momade]

thanks aoktar. 'display tag' works fine as you described. but still i only get one kind of motionblur, no matter what i set the 'octane object tag' or 'octane render settings' to.

what kind of mot. blur is expected else? There is only transform animation!!! Why don't you check my motion blur samples?

well... i was just looking at the different m-blur obtions in 'octane object tag' and 'octane render settings' and i figured, that whatever i choose the result is always identical. but don't missunderstand me. the m-blur i see is amazing!!:)

[aoktar]

thanks aoktar. 'display tag' works fine as you described. but still i only get one kind of motionblur, no matter what i set the 'octane object tag' or 'octane render settings' to.

what kind of mot. blur is expected else? There is only transform animation!!! Why don't you check my motion blur samples?

well... i was just looking at the different m-blur obtions in 'octane object tag' and 'octane render settings' and i figured, that whatever i choose the result is always identical. but don't missunderstand me. the m-blur i see is amazing!!:)

are you meaning vertex or transform motion blur options? vertex mblur shows different if your objects is deforming. otherwise don't use it. it consumes lot of memory.

also don't forget, LV is not %100 correct for all situation or frames. Due of lacking some required frames. It's only produces quaranteed results when you sended a frame to LV or Picture Viewer.

[mate]

On Network rendering the overhead is much worse than expected.
With a 1Gb/s network, so ~100MB/s bandwith, octane only uses about 3MB/s in each direction.
Is this a setting somewhere we missed?

[aoktar]

On Network rendering the overhead is much worse than expected.
With a 1Gb/s network, so ~100MB/s bandwith, octane only uses about 3MB/s in each direction.
Is this a setting somewhere we missed?

it's out of my. But we used it very quick. Abstrax may helps