Hi @ilya
I know how frustrating initial setup can be! I have no knowledge of that specific error, but since the environment and Perceptilabs should work from those instructions, let’s see whether we can find out a bit more…
Firstly, just so you know, as just another user like you I don’t have access to the bug report that can be filed from with Perceptilabs, so I’ll let Perceptilabs people come back if they have any insight from that.
Some things you can try to produce more info to help diagnose this:
- What particular GPU are you using? (general system description might be helpful)
- Start Perceptilabs with the command -perceptilabs -v=3. The -v=3 enables verbose logging and there may be some useful information in the console window to share
- If you followed the recipe for setting up the environment exactly you have also installed jupyterlab. I also uploaded a jupyter notebook on this post. Does running that notebook indicate any specific issues?
- Can you clarify what you meant by this:
I think that something was wrong with python because I had visual UI but without visualization of a specific node. (Probably, it is because it’s using python for it).
Can you say a bit more to clarify the statement, “Probably, it is because it’s using python for it”? I’m not sure how to interpret that.
Cheers, Julian