Mismatched Tags Warnings #2
Assignees
Comments
|
Filed as internal issue #135153. |
|
This should be addressed with b0f30ef. Closing! |
pixar-oss
pushed a commit
that referenced
this issue
Oct 18, 2016
Node-culling is a crucial optimization in Pcp composition that is a win against the natural tendency for scene structure to accumulate down namespace. The basic idea is that, as we walk down namespace, we can prune off branches of the composition structure as soon as we know they contribute no further opinions. However, the rules for which nodes we can cull are subtle due to certain features that require preserving empty structure. But it turns out we can be more aggressive with variant culling than we had been. (Internal change: 1664515)
pixar-oss
added a commit
that referenced
this issue
Jun 17, 2017
If a prototype prim is not a referenced model prim, make sure we build it "high" enough in the hierarchy to preserve material bindings.
Leverage PxrUsdKatanaReadXformable to gather primvars from the UsdGeomPointInstancer. Set them on both the "usd point instancer" location and its "instance array" child. Make sure to use the proper scopes ("point", "primitive").
Compute more data (e.g. the stage) upfront and pass them to the helpers as args.
(Internal change: 1758066)
kaischroeder
referenced
this issue
in autodesk-forks/USD
Feb 2, 2022
initial js render delegate improvements
This was referenced Feb 9, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Platform: Mac OSX
Compiler: Apple LLVM version 7.3.0 (clang-703.0.31)
There are currently several occurrences of
-Wmismatched-tagsbeing triggered when building on newer compilers, such as relatively current clang. This comes from forward declarations of types not matching the way in which they were defined, i.e. one uses the keywordstructand another usesclass. These should be cleaned up.The text was updated successfully, but these errors were encountered: