WEEK 3
updated 1/26/2025
Render
Render Test
Reference
reference
TROUBLESHOOTING
Abnormal CPU Usage
CPU usage chart
When I was rendering locally in Karma CPU with the usdrender_rop node, it took much longer than usual. I found out that it was because I hit render to disk and minimized the main window, which prevented the CPU from being fully utilized at 100%. When I reopened the main window, the CPU usage returned to normal, as you can see on the CPU usage chart, with the CPU usage remaining at 100% in the latter part.
Nuke Read File Error
When I import rendered exr files into Nuke, it's reporting an error, while the exr files are good to go as they should.
Read error
Read's Attribute
As you can see, the file name on the error is different from the one on the attribute panel, and the mark "#" is the cause that made Nuke unable to read the files. Because # is used as a wildcard to represent frame padding in file sequences. When Nuke parses the file path, it interprets the # as a placeholder for frame numbers rather than as part of the actual filename. This leads to an error because Nuke is unable to resolve the path correctly.
Texture error
When my team member gave me the texture, it glitched. He used a group to assign different materials to different parts of the geometry, which works perfectly fine on his computer. However, even though we were using the same model file, the order of the primitives was not the same, which caused the mismatching.
Texture fix
Then, after a discussion with him, we decided to separate the geometry and assign the texture individually, and it works fine for everyone.