OTOY Forums

When I do a File->Archive to collect all the maps associated with a Max file/project, Octane materials aren't fully compatible. I haven't done extensive testing, but it seems like the 'standard texture' slot in Octane materials doesn't get collected properly.

Archive is an indispensable tool for professional, production environments.

Hi paulforgy,
In my opinion, standard slot texture has no use. I do not know why it is there.
I suppose it comes from first plugin version and/or maybe previous developer wanted to integrate 3dsMax standard texture with Octane, but it was not.
Under what circumstances do you use it instead of Octane slots?
Regards
Paride

@paulforgy, try Project Manager, it can collect maps and all assets to make archive. It collect bitmaps too
And a lot more !!!
@Paride : bitmap can be usefull for example to work with UVs or Viewport Canvas.

"In my opinion, standard slot texture has no use. I do not know why it is there." if I remember well, I do asked for this option

paride4331 wrote:Hi paulforgy,
In my opinion, standard slot texture has no use. I do not know why it is there.
I suppose it comes from first plugin version and/or maybe previous developer wanted to integrate 3dsMax standard texture with Octane, but it was not.
Under what circumstances do you use it instead of Octane slots?
Regards
Paride

Why would I use it? Because it's compatible with Max's native materials and renderers which function properly in the viewport. Octane materials suffer from many bugs and lighting issues when it comes to viewport display. I've reported several of these bugs. I can't do my work in an Octane render window.

HHbomb wrote:@paulforgy, try Project Manager, it can collect maps and all assets to make archive. It collect bitmaps too
And a lot more !!!
@Paride : bitmap can be usefull for example to work with UVs or Viewport Canvas.

"In my opinion, standard slot texture has no use. I do not know why it is there." if I remember well, I do asked for this option

Archive collects maps as well, it's built in and it's free.

I mean it collect the bitmap in 'standard texture' slot in Octane materials properly.

Hi paulforgy,
What does it mean to use "Max's material" in standard slots? Do you mean Max's texture?
And what are "bugs and lighiting issue" that using standard slot textures instead of Octane texture slots are solved?
Said that, you're right, archive does not work properly with Octane standard slot.
Regards
Paride

paride4331 wrote:Hi paulforgy,
What does it mean to use "Max's material" in standard slots? Do you mean Max's texture?
And what are "bugs and lighiting issue" that using standard slot textures instead of Octane texture slots are solved?
Said that, you're right, archive does not work properly with Octane standard slot.
Regards
Paride

I have to use Max native materials in order to get proper representation in the viewport. If I assign a bitmap texture in a Max standard material, I can instance or copy that straight into the standard map slot in Octane, and switch back and forth. One material for working(modeling, UV's, etc.), and one for rendering with Octane. Octane decided to use their own conventions for bitmaps(tiling vs scale, transforms, output adjustments, etc.), which means it's not trivial to switch back and forth.

The viewport bugs I'm referring to have been reported in this forum. I believe you've replied to them. Octane materials don't light correctly. Octane maps don't respect Max viewport texture resolution settings and are too low resolution to be useful in many cases.

Here are the bugs I was referring to:

viewtopic.php?f=81&t=64942
viewtopic.php?f=81&t=65006

Hi paulforgy,
thanks, I will check them again the to-do list:
high-res textures, AO and Lights preview in 3dsMax viewport.
Regards
Paride