USD View Red-Tinting

Community Build and Deployment
1

Hey

i’m having an issue with USDView on Windows10 tinting the Scene in Red.

363530649-1e024b94-5e05-44fb-b35a-8bb2d60f402d
363530649-1e024b94-5e05-44fb-b35a-8bb2d60f402d3828×2102 329 KB

I was compiling Usd with Python 3.11.2 and the packages:

numpy==2.1.2
PyOpenGL==3.1.7
PySide6==6.8.0.2
PySide6_Addons==6.8.0.2
PySide6_Essentials==6.8.0.2
shiboken6==6.8.0.2

I tried it on a different system with the same python Version (but windows 11) where i didn’t see that issue, so somehow seems system related.
NOTE: on my Houdini Install which ships usdview build too i don’t have that issue.

I flagged it here aswell:

I’ve set the GPU to be used to the only GPU available:

grafik
grafik576×454 17.3 KB

Does anyone has seen that issue and an idea/hint how to sovle it?

I tried multiple times to recompile USD with cleaned-up Environments.

Thanks for any help inadvance.

Cheers
Jonas

Attaching the Render Doc Capture of the scene
usdviewCapture.zip (7.5 MB)

2

It almost looks like it’s showing an AOV of some kind, but not one I recognize.

The reason I think that is because it’s not just red tinted but there’s no shading in general across the surface.

If you go to Renderer>Hydra AOV does it show the selected option as Color?

3

Hey @dhruvgovil

yep it does show the color as used AOV in the settings:

grafik
grafik2046×1051 150 KB

I was aswell tryign to set the Aov to other: primvars:displayColor but that didn’t change anything either.

4

That is really odd. Are the two machines similar? Similar driver/OS/GPU?

5

No unfortunatly not complete.
They both (Laptop and Workstation) have the same Nvidia Driver version installed (565.90), i used the same Python and PySide6 version on both.
The main difference between the systems is Windows10 vs Windows11.

But i don’t believe it’s the actually hardware as i have Houdini installed on the System (which shows the red tint in the custom compile) and the USD-View shipped with Houdini looks fine. But Houdini Ships with PySide2 (probably custom build), while Python 3.11.2 doesn’t ship with PySide2 and only PySide6.

The left side is showing the custom compile, the right side the Houdini UsdView on the same system:

grafik
grafik2291×1028 461 KB

NOTE: i just recompiled with Python3.10 and PySide2 and it shows the same issue…

6

Could you try PySide 6.5 just to align with the vfx platform? I don’t think it would fix it but it would at least bring you closer to what other people have been trying it on.

Another thought is that usdview stores some user prefs somewhere. It’ll be in your user directory based on OpenUSD/pxr/usdImaging/usdviewq/appController.py at release · PixarAnimationStudios/OpenUSD · GitHub and might be worth clearing out just to see if it’s causing some behaviour that isn’t exposed to the app?

1 Like
7

I just tried downloading the USD 24.08, Python 3.10 build from:

and running it with the provided python environment and i still have that issue.
That’s really odd.
It seems pretty system related what wonders me the most, is that the Houdini USDView is working while the others don’t.

8

Hi @jonassorgenfrei It is working fine on windows 10 for me. Here are my settings that might help you get it working.

Python 3.10.10
PyOpenGL 3.1.7
PySide2 5.15.2.1
PySide6 6.6.3.1
PySide6_Addons 6.6.3.1
PySide6_Essentials 6.6.3.1
Jinja2 3.1.4
MarkupSafe 2.1.5
numpy 1.26.4
opencolorio 2.3.2

To make sure it is picking a dedicated graphicscard and not the built in one if you have two, you can set this envar to make sure to get the NVIDIA card.

set SHIM_MCCOMPAT=0x800000001

Hope it works out for you.
Cheers,
Dan

1 Like
9

Possibly worth trying usdview with --defaultsettings to make sure that there aren’t any settings via shortcuts you’ve accidently toggled which are remaining on.

1 Like
10

Hey @James

that actually does the trick! Thank you for the suggestion.
When i run it with –defaultsettings the viewport shows up as it should.

I tried deleting the .usdview folder in my home directory before which was not doing the trick, not sure why it’s working now, but yeah that worked! I now removed the .usdview again and everything is working as expected.

Cheers
Jonas

1 Like
11

Glad you got it sorted! That’s really weird that deleting the prefs folder didn’t do anything. If you ever encounter it again, it would be interesting to see what was in the prefs.
M

1 Like