Hi Marcus,
here are the results of some tests I made:
- Octane 24.3 cuda 3.0 and cuda 3.2 builds have same behaviour (I was wrong in my guess)
- Octane 24.3 has different behaviour than 23.5
May be I'm doing something wrong, but same command line option didn't give the same results.
Test protocol:
- simple scene with blue cube
- export to octane with -n and -l flags
- octane renders blue cube
- all files saved in 'relink-pass1' folder
- change cube material to red - same name
- export to octane with -r flag
- 24.3 renders blue cube
- 23.5 renders red cube
- all files saved in 'relink-pass2' folder
I've attached all files so you can verify. Please let me know if you need more information.
BTW, many thanks for the good job so far.
Cheers,
Lionel
OctaneRender® beta 2.43 (lin/mac/win) [OBSOLETE]
You do not have the required permissions to view the files attached to this post.
Desktop: Ubuntu 13.04 x64 - i7-3770K @ 3.5GHz - 32GB DDR3 - GTX670 2048MB
Laptop: Linux Mint 11 x64 - i7-2860QM @ 2.5GHz - 16GB DDR3 - Quadro 3000M 2GB
Software: NVidia 319.12 - Cuda 4.2.9 - Blender 2.66a
Laptop: Linux Mint 11 x64 - i7-2860QM @ 2.5GHz - 16GB DDR3 - Quadro 3000M 2GB
Software: NVidia 319.12 - Cuda 4.2.9 - Blender 2.66a
Did you change the cube material to red in Blender? Well, then the 2.43 behaviour is correct - it keeps the materials as you set them up in Octane. That's how it should be and the behaviour of 2.3 v5 is incorrect.yoyoz wrote:Hi Marcus,
here are the results of some tests I made:
- Octane 24.3 cuda 3.0 and cuda 3.2 builds have same behaviour (I was wrong in my guess)
- Octane 24.3 has different behaviour than 23.5
May be I'm doing something wrong, but same command line option didn't give the same results.
Test protocol:
- simple scene with blue cube
- export to octane with -n and -l flags
- octane renders blue cube
- all files saved in 'relink-pass1' folder
- change cube material to red - same name
- export to octane with -r flag
- 24.3 renders blue cube
- 23.5 renders red cube
- all files saved in 'relink-pass2' folder
I've attached all files so you can verify. Please let me know if you need more information.
BTW, many thanks for the good job so far.
Cheers,
Lionel
Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
That's pretty annoying behaviour. I was expecting that materials that are not attached to a node would be updated by the relink option while others stays untouched (or created if new materials).abstrax wrote:Did you change the cube material to red in Blender? Well, then the 2.43 behaviour is correct - it keeps the materials as you set them up in Octane. That's how it should be and the behaviour of 2.3 v5 is incorrect.
Cheers,
Marcus
Cheers,
Lionel
Desktop: Ubuntu 13.04 x64 - i7-3770K @ 3.5GHz - 32GB DDR3 - GTX670 2048MB
Laptop: Linux Mint 11 x64 - i7-2860QM @ 2.5GHz - 16GB DDR3 - Quadro 3000M 2GB
Software: NVidia 319.12 - Cuda 4.2.9 - Blender 2.66a
Laptop: Linux Mint 11 x64 - i7-2860QM @ 2.5GHz - 16GB DDR3 - Quadro 3000M 2GB
Software: NVidia 319.12 - Cuda 4.2.9 - Blender 2.66a
No, that's wanted, because a lot of people don't work with nodes at all and do everything in internal node graphs. They were forced to work with nodes in pre-beta 2.3 v5 and there has been a lot of complaining about it.yoyoz wrote: That's pretty annoying behaviour. I was expecting that materials that are not attached to a node would be updated by the relink option while others stays untouched (or created if new materials).
Cheers,
Lionel
The general workflow is to do geometry in your 3D app and materials in Octane and the initial export gives you just head start, so you don't have to start from scratch with every new project.
Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
Thanks that fixed it for me.Aenima wrote:@gvnwst: I have the same issue but on linux. You have internet connection and you can ping live1.refractivesoftware.com? If yes, try to login customer area and deactivate octane. Wait 30 mins and run again. Imho some problem about the licence checking and we get wrong error message.
GTX560Ti 2GB | i5 2.66 Quad | Win7 x64 | 12GB DDR3
Would it be possible you then add a new command-line option that would allow to force an update of internal node graph materials only?abstrax wrote:No, that's wanted, because a lot of people don't work with nodes at all and do everything in internal node graphs. They were forced to work with nodes in pre-beta 2.3 v5 and there has been a lot of complaining about it.
The general workflow is to do geometry in your 3D app and materials in Octane and the initial export gives you just head start, so you don't have to start from scratch with every new project.
Cheers,
Marcus
Cheers,
Lionel
Desktop: Ubuntu 13.04 x64 - i7-3770K @ 3.5GHz - 32GB DDR3 - GTX670 2048MB
Laptop: Linux Mint 11 x64 - i7-2860QM @ 2.5GHz - 16GB DDR3 - Quadro 3000M 2GB
Software: NVidia 319.12 - Cuda 4.2.9 - Blender 2.66a
Laptop: Linux Mint 11 x64 - i7-2860QM @ 2.5GHz - 16GB DDR3 - Quadro 3000M 2GB
Software: NVidia 319.12 - Cuda 4.2.9 - Blender 2.66a
Yes, that's possible, but that won't happen immediately. The request is notedyoyoz wrote: Would it be possible you then add a new command-line option that would allow to force an update of internal node graph materials only?
Cheers,
Lionel

Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
Thanks Marcus!abstrax wrote:Yes, that's possible, but that won't happen immediately. The request is noted
(when you'll be playing with command line options, please add a PT/DL switch while you're at it

Desktop: Ubuntu 13.04 x64 - i7-3770K @ 3.5GHz - 32GB DDR3 - GTX670 2048MB
Laptop: Linux Mint 11 x64 - i7-2860QM @ 2.5GHz - 16GB DDR3 - Quadro 3000M 2GB
Software: NVidia 319.12 - Cuda 4.2.9 - Blender 2.66a
Laptop: Linux Mint 11 x64 - i7-2860QM @ 2.5GHz - 16GB DDR3 - Quadro 3000M 2GB
Software: NVidia 319.12 - Cuda 4.2.9 - Blender 2.66a
Cool, thanks for the help.matej wrote:Well, it's happening with my competition scene, which is huge and I can't post it. When I'm finished with it, I'll create a test scene and a reproducible procedure, if I'll still experience any problems.
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
good morning!
a very good one!! since i use 2.43 with cuda3.0 octane seems to run stable now:)
still rendering...
cuda 3.2 seems to cause problems previously.
..dont know why the materials were not linked correctly previously. maybe i was just to sleepy to do it right and messed things up. sorry!
now it works:)
with cuda3.0 i can even use higher res while pt.
once again i got emphasize that its so much fun to see how fast this renderenginge works
thx dave
a very good one!! since i use 2.43 with cuda3.0 octane seems to run stable now:)
still rendering...
cuda 3.2 seems to cause problems previously.
..dont know why the materials were not linked correctly previously. maybe i was just to sleepy to do it right and messed things up. sorry!
now it works:)
with cuda3.0 i can even use higher res while pt.
once again i got emphasize that its so much fun to see how fast this renderenginge works

thx dave

- Mint 10 64bit nvidia drv 260.19.29/cudatoolkit3.0 intel q6600, 4gbRAM, GTX470 1,2GB
- Mint 10 64bit/ Win7 64bit nvidia drv 260.19.29/cudatoolkit3.2 amd X6, 16gbRAM, 2x GTX580 3GB
->Octane 2.44/ Blender2.5x
- Mint 10 64bit/ Win7 64bit nvidia drv 260.19.29/cudatoolkit3.2 amd X6, 16gbRAM, 2x GTX580 3GB
->Octane 2.44/ Blender2.5x