As it's said in the 3 first posts this Topic, Rikk's bug happen by default in 10.19 with
Maya 2016.
As I already explained in the second post this
render
bug is triggered by a
viewport
issue
Jolbertoquini wrote:1 - set preference/Display/legacy openGL, reboot Maya
2 - set vieport to 2.0 with texture display
3 - create object + one Octane Material + load 1 bitmap in diffuse
4 - IPR render white object
This is how to trigger the Rikk's bug in
Maya 2017, ( it doesn't happen by default in 2017 because viewport 2.0 default mode is broken for Octane texture display.)
BK wrote:We are currently investigating on this and hopefully, we can provide a fix ASAP. Also, it would be a great help if we have a sample scene to debug here.
@Bikram, what's the point of the bug reports, if you don't read carefully the posts in the Topic ?
No scene sample is needed, in Maya 2016 with 10.19, if you let viewport 2.0 to default opengGL mode, none of the image textures are loaded when you open a scene, neither for viewport or for IPR.
So Rikk's bug is just obvious by default, how could you missed it ?
As I already explained the Rikk's bug (texture not loading) is just one more bug triggered always by the same problem:
I already documented this problem a lot and provided sample scenes to you, for the other "material render white " bugs.
JimStar made a partial quick fix in 10.18 but also added some new relative bugs as "the texture not loading" issue.
Octane Material/texture viewport display implementation is such an awful hack that it triggers render bugs, (all the "material render white" bugs family).
To solve this problem permanently and stop to add new bugs by patching bad code,
there's no other way than to remove from the plugin the
Viewport Shader/texture Display "Feature" (which does more harm than anything else)
and implement it from scratch again but properly this time...