Ok, got it. I think there should be more elegant way of solving this problem tho..
I was thinking of linking standard SU materials with Octane ones for quite awhile now but haven't figured how to solved it yet.
temp directory
- Seekerfinder
- Posts: 1600
- Joined: Tue Jan 04, 2011 11:34 am
Thanks Fuzzy.fuzzybro wrote:Ok, got it. I think there should be more elegant way of solving this problem tho..
I was thinking of linking standard SU materials with Octane ones for quite awhile now but haven't figured how to solved it yet.
Win 8(64) | P9X79-E WS | i7-3930K | 32GB | GTX Titan & GTX 780Ti | SketchUP | Revit | Beta tester for Revit & Sketchup plugins for Octane
Hello there.
I like both ideas.
1-Love the possibility of packing entire project with the SU temp textures/files, etc. That would be great
2- possibility to link default SU mat. with some specific Octane mat.
Example:
SU glass - octane glass
SU concrete - octane concrete
..... Etc
It could be done in 2 or 3 ways....
1- some of us could transform/convert the corrent SU materials to Good Octane materials and send to Fuzzy and this material lib could be default SU. New user would love that...and could use them as reference to create new. Copy and paste and tweak.
2 - we could choose what mat would allways load linked to SU default mat lib ( a selection of them )
This option would have the problem of mapping as the texture aplied to the geometry in SU is diferente from the one loaded in Octane.
This could work to things like glass, concrete, colours, emissions,
Lets think about it.
Cheers
Resmas
I like both ideas.

1-Love the possibility of packing entire project with the SU temp textures/files, etc. That would be great

2- possibility to link default SU mat. with some specific Octane mat.
Example:
SU glass - octane glass
SU concrete - octane concrete
..... Etc
It could be done in 2 or 3 ways....
1- some of us could transform/convert the corrent SU materials to Good Octane materials and send to Fuzzy and this material lib could be default SU. New user would love that...and could use them as reference to create new. Copy and paste and tweak.
2 - we could choose what mat would allways load linked to SU default mat lib ( a selection of them )
This option would have the problem of mapping as the texture aplied to the geometry in SU is diferente from the one loaded in Octane.
This could work to things like glass, concrete, colours, emissions,
Lets think about it.
Cheers
Resmas
i7-2600k | SSD Vertex 3 | WD Velociraptor | WS Revolution | 16GB Ram HyperX | PSU LEPA G1600W | 3 X Asus GTX590 |
https://pt-pt.facebook.com/arq.resmas
https://pt-pt.facebook.com/arq.resmas
- Seekerfinder
- Posts: 1600
- Joined: Tue Jan 04, 2011 11:34 am
I'm with you Resmas.resmas wrote:Hello there.
I like both ideas.![]()
1-Love the possibility of packing entire project with the SU temp textures/files, etc. That would be great![]()
2- possibility to link default SU mat. with some specific Octane mat.
Example:
SU glass - octane glass
SU concrete - octane concrete
..... Etc
It could be done in 2 or 3 ways....
1- some of us could transform/convert the corrent SU materials to Good Octane materials and send to Fuzzy and this material lib could be default SU. New user would love that...and could use them as reference to create new. Copy and paste and tweak.
2 - we could choose what mat would allways load linked to SU default mat lib ( a selection of them )
This option would have the problem of mapping as the texture aplied to the geometry in SU is diferente from the one loaded in Octane.
This could work to things like glass, concrete, colours, emissions,
Lets think about it.
Cheers
Resmas
Seeker
Win 8(64) | P9X79-E WS | i7-3930K | 32GB | GTX Titan & GTX 780Ti | SketchUP | Revit | Beta tester for Revit & Sketchup plugins for Octane