- PERFORMANCE / CACHING**:**
When modeling or doing simulations, sometimes we might have a big amount of nodes or data in our node streams. This could be problematic when we are opening working on these scenes and trying to be more efficient. To alleviate that issue, we should use FileCache SOP, geometry ROP or Stash SOP. In my case, I am pretty much so far using only File Cache SOP and LOP.
- VIEWPORT:
Sometimes viewport tends to behave weird. These issues are mostly visual so best way to fix those is to navigate to Windows → Restart Viewport
- RENDERING CURVES:
When we are having Curves inside our scenes, they can be seen as geometry when rendering. In that case, we can manipulate the width of the rendered Curve with ‘‘width,, attribute. Use Attribute Create node and name attribute width.
- VIEWPORT
Every now and then, isosurface might display some black spots in the viewport. Having to high Anti Aliasing in Display Option settings can cause this, so potential solution is to lower your AA settings.
- RENDERING
USD Render ROP when rendering sometimes due to using MPlay as image viewer, will stop the render at some random frame. If that happens, solution would be to A) Make sure to Save already rendered frames B) Close down the MPlayer, setup new render range inside ROP, from where you ended previous rendering and start rendering again.
- SOLARIS [LOP]
More often than not, Import Scene nodes will create performance issues which will affect your work. So to prevent that, make sure to use SOP Import, or even SOP Create in case you would like to build your assets from the LOP context.
- KARMA RENDERING
- VIEWPORT
If for any reasons, Geo Container World Space is behaving weird in comparison to Object level World Space, then simply create new Geo Container with correct orientation and copy and paste SOPs from container which behaves like broken. This can happen if orientation of Object and Geometry levels are not matching (Z - always forward or front).