Hello,
Is there a material limit in the Maya plug in? Currently I am working on a very intense poly, texture, and material scene. As of right now I have 56 Materials placed on to objects in the scene, and 5 lights.
Just wondering if I hit the cap of the materials that can be used, because when I "Render as gray material" it works just fine.
Cheers!
-Juan
Material Limit? Maya 2.04
Moderator: JimStar
That's awesome to hear! I don't really know whats going on under the hood but do you know why it's not rendering? I took some materials off some assets and put a basic diffuse material on them. It rendered just fine, but when I add those other materials back on it refuses to render. 
Thanks
-Juan
Thanks
-Juan
JimStar wrote:Enable "Verbose" in Octane settings and read the Octane log in script editor, it may help you to find where is the problem...
Yeah I've had it on this whole time. I've been doing a lot of trouble shooting today. I was not able to get out a single image other then a blue screen. I looked at the script editor and it was running just fine with no errors (I guess it thought it was rendering like normal). The only way I was able to render was to "render in gray material" first then turn it off, then I was able to get a render with my materials.
But here is the odd bit, when it would render some of the materials just came out black not accepting any light. When I looked at my hypershade a lot of the materials were messed up. Looking at the material preview some would only have normal maps showing, or the wrong textures. Every time I scroll down or up in the hypershape layout the materials will buffer and completely change. Looking at the attribute editor of the material I would see that the correct texture was applied but it would be different in the material preview. When I hit reload for the texture it changes the material and others along with it.
It's very odd I've never seen this happen but I was able to revert back to an older file that has 0 issues. I'm remaking all the material right now hopefully it doesn't happen again.
Anything helps thanks again!
Something like this may happen if you used some old scene, made in 1.X or beta 2.0 plugins. As one critical bug was fixed recently. Due to this bug Maya's scene files stored in Windows and Linux were incompatible, and I was forced to change the binary layout of some data inside scene file.
So, if you need to finish some previous WIP scenes - never switch to new beta or major versions "on the go"..
So, if you need to finish some previous WIP scenes - never switch to new beta or major versions "on the go"..
JimStar wrote:Something like this may happen if you used some old scene, made in 1.X or beta 2.0 plugins. As one critical bug was fixed recently. Due to this bug Maya's scene files stored in Windows and Linux were incompatible, and I was forced to change the binary layout of some data inside scene file.
So, if you need to finish some previous WIP scenes - never switch to new beta or major versions "on the go"..
This makes a lot of sense. What would you recommend doing that way not too much work is lost?
Do I have to go to an older version of the maya plug in or do i need to save the scene as and it will work fine as long as I'm in the 2.04 ver of it? Or do I need to completely remake all of my materials in a new version?
I just don't want the same thing to happen if I work on a reverted file.
What do you mean "saving as a new scene"? Did you open the old scene, and just saved it into other file?..jnuno_ wrote:I just tried saving as a new scene and that didn't work I started getting the same weird material issue again.
Haha yeah just to trick it and see if it would work. What would you suggest doing in this situation. Revert back to an older plug in and if so, how would I get the file im working now into a newer plug in version? Do I need to export everything and then remake all the materials or is there an easier way of doing this without losing to much work.
* the whole environment is imported as separate assets this is why we wouldn't want to start over.*
* the whole environment is imported as separate assets this is why we wouldn't want to start over.*