Composition issue when specifying an invalid defaultPrim

[marktucker]

Unzip the attached empty.usda and prims.usda: defaultPrimIssue.zip

1. Open usdview empty.usda
2. In the interpreter window, run:

s = usdviewApi.stage
l = s.GetRootLayer()
with Sdf.ChangeBlock():
 l.subLayerPaths = ["prims.usda"]
 l.defaultPrim = "1234"

3. The stage will have no prims on it still. If the above process is followed again, but with the last line of the script changed to l.defaultPrim = "_1234" (i.e. a valid, but non-existent prim name), the stage gets populated as expected.

[jesschimein]

Filed as internal issue #USD-11579

(This is an automated message. See here for more information.)