Troubleshoot Viewport 2.0

If you are not able to obtain the expected results in Viewport 2.0, refer to the following for possible solutions and workarounds:

• When using the MHWRender::MRenderer::setGeometryDrawDirty() interface to mark a DAG object associated with an MPxDrawOverride object dirty, the optional topologyChanged parameter must be set to true.
• When using HLSL shaders, you may see different color gradients compared to using GLSL shaders. This is due to their different implementation of color interpolation. This may be corrected by increasing the number of subdivisions of the object to which the shader is applied.
• If you are using Screen-space Ambient Occlusion and the results differ from expectations; for example, faces appear dark, you may need to reverse your surface normals.
• If NURBS do not tessellate correctly or performance is slow, check that the ArubaTessellator.mll plug-in is loaded.
• If you hardware render a free image plane with an alpha channel in Viewport 2.0, it blends with the black background. The default gradient background values are not identical for the Viewport 2.0 workspace and for batch rendering, which defaults to black. Therefore, if you need to obtain the identical results from both renders, you must ensure that their background colors match by setting the scene view background to black. Cycle to black in the scene view by using +B.
• Ghosting of joints may cause slowdowns in Viewport 2.0.
• The Depth Peeling and Weighted Average Transparency Algorithms (Renderer > Viewport 2.0 > ) provide better transparency drawing that is independent of the sorting of objects. Models that can benefit from these transparency methods generally have internal faces.

  In addition, the following tips may be helpful:

  • If the grid draws on top of transparent objects (such as objects shaded with the AutodeskUberShader) , you can workaround the issue by using the Depth Peeling or Weighted Average transparency algorithms.
  • Transparent objects that overlap may not draw correctly if the Object Sorting transparency algorithm is used. Use the Depth Peeling algorithm instead.
  • If your image plane Display Mode is set to RGBA, your image plane is set to transparent. If you notice that it is blending with other textures, set the Display Mode to RGB instead.
• If you find that the shadows of your displaced surfaces are disappearing when you manipulate the light, you may workaround this issue by increasing the Displacement Clipping Bias under the dx11shader Attribute Editor.
• When TessellationON is selected in the dx11Shader Attribute Editor, the geometry is not used during screen-space ambient occlusion calculations.
• If you paint using the Paint Vertex Color Tool, the brush shape fall off may pick up some alpha and part of your geometry may appear transparent. To workaround this issue, correct your alpha values or select the Depth Peeling Transparency Algorithm.
• If you encounter z-fighting issues where UI elements and objects that are at the back show through the objects that are in front, increase the depth resolution. One easy method is to enlarge the near clip plane on the camera.
• If your motion blur has no effect when an image plane is immediately behind a moving object, you can workaround this issue by setting the MAYA_VP2_OFF_NON_PE_FRAGMENT environment variable to 1. Setting this environment variable allows the image plane to be included in the calculations of all scene post effects, such as SSAO, depth of field and motion blur.

 Except where otherwise noted, this work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License