-
Notifications
You must be signed in to change notification settings - Fork 202
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
[MAYA-121681] / [MAYA-126141] Cannot add new [Def1] #2052
Comments
Hi @suekieza. I am able to reproduce and have logged this issue as MAYA-121681. |
cool cool |
@suekieza , we (at the studio I am working for) are experiencing the exact same issue. |
Hi all, we just scheduled this on our side. |
@suekieza this should be now fixe don MayaUSD 0.19.0. are you able to test and confirm on your side? :) |
I built tag v0.19.0 and I am getting the same error.
Error:
Maya allows the creation of the new "def" only if the active target is the layer that the parent prim is defined. @santosg87 , could you give us a step-by-step to reproduce your fix? Just to be sure we are in the same page. |
ah! I think I see the issue better now. on our testing, we found that opinions on ancestors couldn't be added previously. That was the fix that we included. after re-reading this issue quite a few times, this is about sister layers, not a hierarchy issue. our workflow that now works is:
I logged a new issue for the adjacent layers internally for investigating. internal ticket ID [MAYA-126141] |
@suekieza @msercheli this issue should be fixed with #2720. I have tested internally and creating a prim is possible in any layer. are you able to build with that commit and test on your side? otherwise, this should be available on future releases of mayausd :) |
Hi @santosg87 , Thanks for the fix. I see the removal of the code that was preventing it. Once again, thanks. |
Describe the bug
Error: RuntimeError: file C:\appnet\applications\maya\2022-x64\Maya2022\Python27\Lib\site-packages\maya\app\ufe\outlinerSupport.py line 27: Cannot add new [Def1] under [prop]. It is defined on another layer. Please set [seq010_sh010_manifest.usda],[seq010_manifest.usda] as the target layer to proceed.
Why cant I create a new def under the "scope prop"(see image)? I would expect it to add overs to my chosen layer like:
over "shot"
{
over "prop"
{
def "def1"
{}
}
}
I don't want to add this def on the "seq010_manifest.usda" layer. I can add to any layer I want using overs in houdini and in USD externally, so why lock this in maya?
Specs (if applicable):
The text was updated successfully, but these errors were encountered: