Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Materials Assignment Bug Produces Transparent Renders #81

Closed
AlexeyAdamitsky opened this issue Mar 1, 2021 · 5 comments
Closed

Materials Assignment Bug Produces Transparent Renders #81

AlexeyAdamitsky opened this issue Mar 1, 2021 · 5 comments
Assignees
Labels
bug Something isn't working needs qa Ready for testing

Comments

@AlexeyAdamitsky
Copy link
Contributor

Blender 2.92
BtoA Dev Branch e5dd725
Arnold SDK 6.1.0
Windows 10 2004

I've been experiencing a bug with materials assignment that produces transparent renders. It has been happening for a while now but I couldn't spot why it's happening. Seems a bit random to me but I'm sure it's not.

Here is a scene created from scratch. Once the scene is ready I assign and setup some basic materials.
image

With the first render we see the bug. The background (2) and the pedestal (1) are rendered as transparent objects or aren't rendered at all I'm not sure what is happening here.
image

Only changing the names of objects that generates issues to anything else helps to solve the issue.
image

Now scene renders as expected.
image

I attached the scene with the issue described above. To see how issue I'm experiencing with transparent objects you need to remove .BUG (including dot) in the names of two objects I mentioned above:
Arnold_Test_Scene.zip

@osiriswrecks
Copy link
Contributor

@AlexeyAdamitsky This sounds similar to an issue I was having yesterday. Essentially, materials that existed in the Arnold Universe already weren't being applied properly. Can you download the latest alpha-rc3 and test again?

@AlexeyAdamitsky
Copy link
Contributor Author

Ok, I think I figured out what is causing the issue here. I'm testing it on the latest RC3 2a1b41d branch.

If I reproduce the bug the render won't even start with the latest build. Using the same name for an object and material causing the issue. Changing one or the other will stop causing issues and render will run fine.

image

@osiriswrecks
Copy link
Contributor

AHA! I know what the problem is. Because the node names are the same for both it's basically skipping the second object because it thinks it's the same thing. We'll have to add another level of specificity to the unique name we generate to separate them.

osiriswrecks added a commit that referenced this issue Mar 4, 2021
…etween mesh objects and materials if they have the same name #81
@osiriswrecks
Copy link
Contributor

@AlexeyAdamitsky This issue should be fixed. When you get a chance can you confirm?

@osiriswrecks osiriswrecks added bug Something isn't working needs qa Ready for testing labels Mar 4, 2021
@AlexeyAdamitsky
Copy link
Contributor Author

Yes, I checked and I can't reproduce the bug anymore. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs qa Ready for testing
Projects
None yet
Development

No branches or pull requests

2 participants