Version 3.00 - Alpha10.1 (30.04.2016)

[pxlntwrk]

Hi,
nice update, thanks again

render region back in game

[aoktar]

Hi,
nice update, thanks again

render region back in game

Thanks! Nice to hear somebody made it worked.

[eyeonestudio]

Hi Dev Team & Aoktar

My VDB source has several fields.
I want to put "Heat Field" to "Emission".
Could you make it?

[sdanaher]

thanks for getting the OSX Alpha 10.1 out Ahmet!

[joecurrie]

joecurrie,
i can't reproduce the problem on windows or osx. Can you save and send this scene? Also please try with latest A6.2

Hi Aoktar,

Please see attached scene and log this is now using Alpha 6.2.

Thanks

In 3.00 alpha 8 I added a new release log flag rdStart which adds some additional logging during the startup of render threads. When Ahmet releases a new plugin based on alpha 8, it would be great if you could try to reproduce the problem with this log flag enabled and send me the files. Hopefully I will then see a bit clearer.

Hi guys,

Just tried with the new alpha 10. Getting the same thing, attached log, I added rdStart to the octane_log_flags.txt.

I've tried looking into what "device 0: can't bind to render thread (0x0) in scope of other thread (0x7fd49e5f0d30)" means if its a CUDA error or something but can't find anything.

It's fine for rendering 1 job at a time because all I need to do is load the scene into live viewer first, but queuing fails to start a second job because the scene isn't loaded into LV. Anything else I can try?

Cheers,

Joe

[aoktar]

Hi Dev Team & Aoktar

My VDB source has several fields.
I want to put "Heat Field" to "Emission".
Could you make it?

a.png

Can you send me this vdb?

[CCIDgfx]

Am I missing something with the new update? The fog Object isn't showing up at all now

[aoktar]

Capture.PNG

Am I missing something with the new update? The fog Object isn't showing up at all now

Yes it's 10.0. Update to 10.1

[abstrax]

Hi guys,

Just tried with the new alpha 10. Getting the same thing, attached log, I added rdStart to the octane_log_flags.txt.

I've tried looking into what "device 0: can't bind to render thread (0x0) in scope of other thread (0x7fd49e5f0d30)" means if its a CUDA error or something but can't find anything.

It's fine for rendering 1 job at a time because all I need to do is load the scene into live viewer first, but queuing fails to start a second job because the scene isn't loaded into LV. Anything else I can try?

Cheers,

Joe

Thanks for trying. Unfortunately there is no additional logging (there should be). I assume that you have multiple octane_log_flags.txt files flying around and you modified the wrong one or you made the change after you started C4D. The log flags file should be searched on OSX next to the liboctane.so file and will be loaded once during startup.

[valters]

Good day. Thanks for the amazing daily work! Here is small report/request from me but if all that was said before just ignore my msg
On the left side of the image we see created material and on the right side we see same material imported from LiveDB (same thing on both v2 and v3)
1. [NE] Rgb Spectrum node lost some connections and recreate it self few times taking a "friend" ColorCorrection
2. [NE] Float Texture node missed totally
3. [NE] Transform node creates self always individually for each second node it was connected
4. [NE] [request] Position of nodes unchanged. Means they are located same place where they was/planned by author
5. [NE] [request] Shift + Click to select multiple nodes
6. [NE] Right Click/ Save Material As Orbx not working
7. [NE] If you copy main mix material from attached file to a new project you can expect unlinking of some node connections
8. [NE] Sometimes Preview Materials all just black even drag not helping (if to turn Upd. Preview on Drag)

I will pray that someday node positions will be saved as it was seen by author before material export and there will be no "self recreation" of them. Because that will be super powerful for creating "smart" materials

9. [Devices][LV] Wrong indification of GPU list:
GPU0 in PC == GPU1 in OR and temps in LV from GPU2
GPU1 in PC == GPU0 in OR and temps in LV from GPU0
GPU2 in PC == GPU2 in OR and temps in LV from GPU1

Thanks for attention