Skip to content
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

Windows Py3.11 issue with OpenGL in USDView #2996

Closed
jonassorgenfrei opened this issue Mar 10, 2024 · 7 comments
Closed

Windows Py3.11 issue with OpenGL in USDView #2996

jonassorgenfrei opened this issue Mar 10, 2024 · 7 comments

Comments

@jonassorgenfrei
Copy link

jonassorgenfrei commented Mar 10, 2024

Hey

i tried building the latest USD [v24.03] with Python 3.11.2
It builds fine and i can use the library.
But the scene viewer in USDView stays black.
8c29f3be31a6aad3886a3ff4b1297b0173555074_2_1035x571

I build with Python3.10 and this works.

see: https://forum.aousd.org/t/usdview-black-screen/1307/5

@jonassorgenfrei jonassorgenfrei changed the title Windows Py3.11 issues with OpenGL in USDView Windows Py3.11 issue with OpenGL in USDView Mar 10, 2024
@jesschimein
Copy link
Contributor

Filed as internal issue #USD-9413

@BigRoy
Copy link

BigRoy commented Mar 12, 2024

Aside of the black screen do you get any errors or warnings reported in the console or command line that might hint to what is going on?

@jonassorgenfrei
Copy link
Author

Hey @BigRoy

unfortunatly there was no error shown in the terminal.
Is there any debug flag i can use with usdview to may be force more info to be shown?

@jonassorgenfrei
Copy link
Author

I think the most interesting thing is that it tries to open the programm twice.
I added a screen capture of running usd view:

2024-03-12.12-25-26.mp4

@BigRoy
Copy link

BigRoy commented Mar 12, 2024

I think the most interesting thing is that it tries to open the programm twice. I added a screen capture of running usd view:
2024-03-12.12-25-26.mp4

That's interesting indeed - could you run where python in the cmd prompt to double check whether it's picking up the python you expect it to.

Also, could you show the contents of the ..\install_default\bin folder?


You could try launching with the --traceToFile (and maybe --traceFormat) argument to see if that points you to anything. Maybe it reports anything useful.


Not sure how polluted your PATH and PYTHONPATH env is - but if there might be conflicts with something else on your system it might be worth trying to prepend the new values instead of appending to those variables so they are preferred over anything pre-existing. So end with e.g. ;%PATH% instead of starting with %PATH%;.

@jonassorgenfrei
Copy link
Author

jonassorgenfrei commented Mar 12, 2024

Just double checked that the correct python is executed this works well (i think otherwise my boost compile would complain).
grafik

Tried with Preprending the path unfortunatly the same result.

Here's the trace i got from running the application:
test.txt

Here with tracePython
test.txt

@BigRoy
Copy link

BigRoy commented Mar 12, 2024

Thanks for the details - I'll leave this to someone more knowledgeable this area.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants