NCP-OUSD 試験問題を無料オンラインアクセス

Consider a USD that has a root Xform, that has a child Sphere, that in turn has a child Cube.
Xform
- Sphere
-- Cube
When you open the USD, you see the sphere and the cube. But when you author the Sphere to be invisible, the sphere disappears, but the Cube is still visible.
What could be causing this behavior?

• A.Nested gprims are illegal in OpenUSD, and their imaging behavior is undefined.
• B.Visibility is hierarchical in OpenUSD, so the root Xform must be made invisible in order for all of its descendants to be invisible.
• C.Visibility is explicit in OpenUSD, so the Cube must be explicitly authored as invisible.

Why would you not see a sphere when opening this scene?
#usda 1.0
(
defaultPrim = "wall_a_inst"
upAxis = "Z"
)
def Xform "wall_a_inst" (
instanceable = true
variants = {
string Emissive = "Default"
}
prepend variantSets = "Emissive"
)
{
def Sphere "Sphere"
{
}
variantSet "Emissive" = {
"Daytime" {
}
"Default" {
}
}
}

• A.The "Emissive" variant set is missing the material bindings for both "Daytime" and "Default".
• B.Because "wall_a_inst" has instanceable=true and a composition arc, variants, the sphere that is inside of
  "wall_a_inst" but outside of its variantset is not part of the instanced scenegraph.
• C.Sphere are guide geometry that are invisible by default.

Which of the following are valid reasons for choosing to use or develop a standalone converter instead of an importer/exporter for a digital content creation (DCC) application? Choose two.

• A.You don't have access to an SDK to develop a native exporter for the DCC.
• B.Standalone converters are the only way to convert proprietary formats.
• C.Your workflow requires batch conversion that is not suitable within the DCC.
• D.A converter always produces higher-fidelity results compared to an importer/exporter.

Which of the following statements about debugging complex LIVRPS scenarios are correct?

• A.Specialize arcs cannot be overridden, so they can be ignored during debugging.
• B.Payload arcs should be checked before Reference arcs for more efficient debugging.
• C.Local opinions should be checked first when debugging composition issues.

Which of these are valid types for custom attributes in OpenUSD? (Choose two.)

• A.assset paths
• B.string arrays
• C.structs
• D.dictionaries