Hi guys.
I'm using Houdini 19.0.657 in ubuntu 22.04.
When I click the "?" on any window to get the help browser, nothing happens. Anyone experiencing the same thing?
help window not working when "?" is clicked
4337 11 3- nelpiper73
- Member
- 75 posts
- Joined: May 2017
- Offline
- TangheStudent
- Member
- 88 posts
- Joined: Feb. 2021
- Offline
- nelpiper73
- Member
- 75 posts
- Joined: May 2017
- Offline
- jsmack
- Member
- 8043 posts
- Joined: Sept. 2011
- Offline
- protozoan
- Member
- 1717 posts
- Joined: March 2009
- Offline
- nelpiper73
- Member
- 75 posts
- Joined: May 2017
- Offline
- protozoan
- Member
- 1717 posts
- Joined: March 2009
- Offline
- nelpiper73
- Member
- 75 posts
- Joined: May 2017
- Offline
- protozoan
- Member
- 1717 posts
- Joined: March 2009
- Offline
- protozoan
- Member
- 1717 posts
- Joined: March 2009
- Offline
Without trying to force this onto you, I would consider an alternative to this type of startup though.
A lot of people and companies run houdini from a shell. You pop open a terminal, and (assuming it runs a bash shell or compatible), you'd set up the correct environment for it like so:
From then on this shell has the correct environment and paths set up (reminder: when executing a shellscript, it'll create a sub-shell and kill its environemnt upon completion, sourcing a shell script however retains the environment for as long as the shell lives)
Then you go (back) to your project directory, and start it from there, like
This of course can be reasonably automated.
Some of the advantages are:
- It's easy to have several sessions of different houdini versions open at the same time. Want to directly compare 19.0 and 19.5? Make two different shells, that source a different environment and start two houdini sessions
- The shell acts as a nice and quick console. All error outputs go there (and into its logs), also your own print() stuff
- When you have it you can use the shell to use all the command line tools that come with houdini from within your project structure, like iconvert and all the others
It's well worth looking into.
A lot of people and companies run houdini from a shell. You pop open a terminal, and (assuming it runs a bash shell or compatible), you'd set up the correct environment for it like so:
cd /opt/hfs19.5.303/
source houdini_setup_bash
From then on this shell has the correct environment and paths set up (reminder: when executing a shellscript, it'll create a sub-shell and kill its environemnt upon completion, sourcing a shell script however retains the environment for as long as the shell lives)
Then you go (back) to your project directory, and start it from there, like
cd /home/nelpiper73/myproject/hip
QTWEBENGINE_CHROMIUM_FLAGS="--no-sandbox" hindie
This of course can be reasonably automated.
Some of the advantages are:
- It's easy to have several sessions of different houdini versions open at the same time. Want to directly compare 19.0 and 19.5? Make two different shells, that source a different environment and start two houdini sessions
- The shell acts as a nice and quick console. All error outputs go there (and into its logs), also your own print() stuff
- When you have it you can use the shell to use all the command line tools that come with houdini from within your project structure, like iconvert and all the others
It's well worth looking into.
Edited by protozoan - July 30, 2022 14:43:04
Martin Winkler
money man at Alarmstart Germany
money man at Alarmstart Germany
- Steffen Dünner
- Member
- 15 posts
- Joined: Dec. 2015
- Offline
This was working for me on Linux Mint until yesterday. Now I have exactly the same problem as shown here [www.sidefx.com].
Edited by Steffen Dünner - Aug. 25, 2022 04:05:32
- alunablue
- Member
- 29 posts
- Joined: Nov. 2021
- Offline
-
- Quick Links