Is anyone else having a problem where houdini 16 (CentOS 6.8, houdini 16.0.504.7.7) seems to forget where its saving scene files?
If I do a ‘save as’ if defaults to my user directory and I have to navigate to where I'm working on the network, clicking $HIP takes me back to my user directory too.
Not a show stopper but pretty frustrating!
Houdini forgetting where $HIP is?
6796 12 2- Hezza
- Member
- 17 posts
- Joined: Jan. 2008
- Offline
- Enivob
- Member
- 2528 posts
- Joined: June 2008
- Offline
Yep, on Windows I get the same thing from time to time. Where I thought I saved in one folder yet the HIP ends up in another. I guess it is operator error but it sure would be nice if there were some smart code in Houdini that remembered recent paths like the Adobe products have.
Using Houdini Indie 20.0
Ubuntu 64GB Ryzen 16 core.
nVidia 3050RTX 8BG RAM.
Ubuntu 64GB Ryzen 16 core.
nVidia 3050RTX 8BG RAM.
- Hezza
- Member
- 17 posts
- Joined: Jan. 2008
- Offline
- matthew_h_k
- Member
- 24 posts
- Joined: July 2007
- Offline
- Enivob
- Member
- 2528 posts
- Joined: June 2008
- Offline
I thought when you Set Project you were setting the $JOB variable, not the $HIP varible. The $HIP is simply the folder where the .hip file is currently located. If you follow up the Set Project with a Save As to that same folder then the $HIP and $JOB would be matched.
Edited by Enivob - March 15, 2017 12:54:05
Using Houdini Indie 20.0
Ubuntu 64GB Ryzen 16 core.
nVidia 3050RTX 8BG RAM.
Ubuntu 64GB Ryzen 16 core.
nVidia 3050RTX 8BG RAM.
- Hezza
- Member
- 17 posts
- Joined: Jan. 2008
- Offline
- dreamagery2
- Member
- 24 posts
- Joined: Jan. 2015
- Offline
Yep. I have been using Houdini for 2 years. And L'o and behold. This is upsetting. I am getting the same thing. I used to be able to set the project by simply clicking on the project director, and voila. The project was set. Now, in Houdini 16, it does not do that. Is Side Effects working on this?
Edited by dreamagery2 - June 2, 2017 00:03:20
Greg
- Richard Costin
- Member
- 101 posts
- Joined: May 2006
- Offline
- jsmack
- Member
- 7733 posts
- Joined: Sept. 2011
- Offline
- Richard Costin
- Member
- 101 posts
- Joined: May 2006
- Offline
- sokay
- Member
- 4 posts
- Joined: Nov. 2017
- Offline
I know this is a super old topic, but I'm having this issue from time-to-time on Windows in Houdini 18 still.
When saving a new .hip, the save dialog starts in “Windows/System32” folder. After saving the .hip somewhere, $HIP becomes where the file is saved. I believe this is as expected. My problem is that when I render something in Mplay, the $HIP location remains “Windows/System32”. I have to navigate back to expected $HIP location each time. Is this expected behavior?
Does anybody have any workarounds or fixes for this? I'm thinking it might have something to do with my Houdini not being installed in the Program Files directory or something.
Thanks.
When saving a new .hip, the save dialog starts in “Windows/System32” folder. After saving the .hip somewhere, $HIP becomes where the file is saved. I believe this is as expected. My problem is that when I render something in Mplay, the $HIP location remains “Windows/System32”. I have to navigate back to expected $HIP location each time. Is this expected behavior?
Does anybody have any workarounds or fixes for this? I'm thinking it might have something to do with my Houdini not being installed in the Program Files directory or something.
Thanks.
- jsmack
- Member
- 7733 posts
- Joined: Sept. 2011
- Offline
sokay
I know this is a super old topic, but I'm having this issue from time-to-time on Windows in Houdini 18 still.
When saving a new .hip, the save dialog starts in “Windows/System32” folder. After saving the .hip somewhere, $HIP becomes where the file is saved. I believe this is as expected. My problem is that when I render something in Mplay, the $HIP location remains “Windows/System32”. I have to navigate back to expected $HIP location each time. Is this expected behavior?
Does anybody have any workarounds or fixes for this? I'm thinking it might have something to do with my Houdini not being installed in the Program Files directory or something.
Thanks.
How are you starting Houdini? The shortcut normally has the ‘start in’ folder set to the home directory. Alternatively, you can launch houdini from the houdini command line tools and the working directory will be the directory from which the command was executed. Starting in windows/system32 indicates that maybe you are starting houdini as administrator.
- sokay
- Member
- 4 posts
- Joined: Nov. 2017
- Offline
jsmack
How are you starting Houdini? The shortcut normally has the ‘start in’ folder set to the home directory. Alternatively, you can launch houdini from the houdini command line tools and the working directory will be the directory from which the command was executed. Starting in windows/system32 indicates that maybe you are starting houdini as administrator.
Thank you jsmack! I was using a “Pin to Start Menu” shortcut and the “start in” folder was empty. I changed it to my Houdini project folder and it works better for me now. The shortcut didn't seem to be running as administrator but this works for me.
Thanks again!
Edited by sokay - Sept. 16, 2020 17:14:02
-
- Quick Links