Okay, Still no luck today. What I've tried: install houdini locally. Create local user. No environmental variables set except for default PATH. Source houdini_setup_bash just before launching houdini. Both 64bit and 32bit houdini initiate correctly. But:
- with the 64bit version: I can navigate nfs shares, but the path object crashes houdini when starting to draw in viewport.
- with the 32bit version: the path object works as expected, but I can't navigate to remote nfs shares. I can navigate to shares over nfs, shared from the local host however. Needs further investigation.
No difference with xfwm4 window manager.
The shares I can't read in the 32bit version are from an apple file server, and I see two entries in the automount directory: /net/god/Volumes/G-Raid/production (that file exists twice). Although the 64 bit version and other gnome-aps don't have a problem with that, it is odd at least.
Also, the 64bit houdini doesn't crash with the path object if I load a hip file that was originated in 32bit houdini and create a new path.
Mystery prevails. However, I'm probably getting 2 unrelated problems: the 64bit could be distro dependant, the 32bit problem could be due to inappropriate share.
Found 75 posts.
Search results Show results as topic list.
Technical Discussion » Houdini on Ubuntu 64 bit
- DriesD
- 109 posts
- Offline
Technical Discussion » Houdini on Ubuntu 64 bit
- DriesD
- 109 posts
- Offline
Hm. The 7174 drivers are no different. I think I can rule out it being a driver problem now? Also, I'm using gnome, in which the LD_LIBRARY_PATH gets overriden. When am I supposed to source the houdini_setup_bash script? What does your LD_LIBRARY_PATH variable say under ubuntu gnome?
Technical Discussion » Houdini on Ubuntu 64 bit
- DriesD
- 109 posts
- Offline
Mark, are you running the 64bit version of houdini? Are u using the 64-bit nvidia drivers?
Edward, I double checked digital assets, but no embedded ones. The path object is defined by $HFS/houdini/houdini/otls/OPlibObjects.otl
I uninstalled all my self made digital assets.
I'll try the 71.74 drivers now. I'll report back.
Edward, I double checked digital assets, but no embedded ones. The path object is defined by $HFS/houdini/houdini/otls/OPlibObjects.otl
I uninstalled all my self made digital assets.
I'll try the 71.74 drivers now. I'll report back.
Technical Discussion » Houdini on Ubuntu 64 bit
- DriesD
- 109 posts
- Offline
Hey John,
The bug occurs when I start a paht object in the viewport at object level. When I click for the first point and then move the mouse to set a second point, Houdini segfaults. At Sop level, the same thing happens with a curve SOP. (sorry, that was very badly posted).
I'm also convinced that it is related to the 64 bit version. (although, the path object works fine on an existing .hip file which was first made up with a 32 bit version Houdini)
Okay, so when moving back to 32 bit, houdini doesn't recognize my nfs mounted filesystem anymore, meaning: in any dialog window, I can't navigate to a share. I can navigate through all the local files, but not a share. My home directory is on a share, so all my personal settings are not loaded. It's actually a share from an apple server, but it works just fine in the rest of linux. (I'm trying now to see whether a share that is in fact an export from the local filesystem will work. And for the record, the shares are automounted.
The other path of my thoughts goes down to the LD_LIBRARY_PATH variable. In ubuntu, by default, there is no LD_LIBRARY_PATH set but the file /etc/ld.so.conf looks like this:
$cat /etc/ld.so.conf
/lib32
/usr/lib32
/usr/X11R6/lib32
When sourcing houdini_setup_bash, the LD_LIBRARY_PATH gets set to /production/software/linux/houdini/dsolibusr/liblib and those last 2 entries are 64 bit libraries. Would it get confused?
Will the system setting get overruled by the environmental variable?
Hmm, continuing the search…
Thinking about it: the LD_LIBRARY_PATH is set only just before the houdini binary gets called. I'll try to set it systemwide. Maybe subprocessed are not aware…
The bug occurs when I start a paht object in the viewport at object level. When I click for the first point and then move the mouse to set a second point, Houdini segfaults. At Sop level, the same thing happens with a curve SOP. (sorry, that was very badly posted).
I'm also convinced that it is related to the 64 bit version. (although, the path object works fine on an existing .hip file which was first made up with a 32 bit version Houdini)
Okay, so when moving back to 32 bit, houdini doesn't recognize my nfs mounted filesystem anymore, meaning: in any dialog window, I can't navigate to a share. I can navigate through all the local files, but not a share. My home directory is on a share, so all my personal settings are not loaded. It's actually a share from an apple server, but it works just fine in the rest of linux. (I'm trying now to see whether a share that is in fact an export from the local filesystem will work. And for the record, the shares are automounted.
The other path of my thoughts goes down to the LD_LIBRARY_PATH variable. In ubuntu, by default, there is no LD_LIBRARY_PATH set but the file /etc/ld.so.conf looks like this:
$cat /etc/ld.so.conf
/lib32
/usr/lib32
/usr/X11R6/lib32
When sourcing houdini_setup_bash, the LD_LIBRARY_PATH gets set to /production/software/linux/houdini/dsolibusr/liblib and those last 2 entries are 64 bit libraries. Would it get confused?
Will the system setting get overruled by the environmental variable?
Hmm, continuing the search…
Thinking about it: the LD_LIBRARY_PATH is set only just before the houdini binary gets called. I'll try to set it systemwide. Maybe subprocessed are not aware…
Technical Discussion » Houdini on Ubuntu 64 bit
- DriesD
- 109 posts
- Offline
Sorry if some of you are offended by doulbe posting (this question is on the mailing list too), but I thought of trying my luck here as well.
Does anybody out here has 64bit Houdini running on Debian or Ubuntu? I get a segfault when trying to make a path at object level (sop level idem). Apart from this path object bug, there doesn't seem to be any other issue. I noticed that the crash occurs only when moving the mouse. You can set a start point but moving the mouse after that segmentation faults. Grrr. I'm so close. The REALLY weird thing is that when using a .hip file that was started on a 32 bit version, the path object works just fine. A new hip file doesn't.
Among the things I've tried to resolve this: delete all the non-default otl's, rename my $HOME/houdini8.0 directory, create new desktop,… I tried all this with the latest 64 bit build: 8.0.517, but also with the earliest 64bit build: 8.0.410 and all builds in between.
I also tried to revert back to a 32 bit version (8.0.523), but then houdini doesn't seem to recognize my nfs mounts anymore. Could ASSUME_KERNEL have something to do with that?
System information:
AMD 64x2 (dual core)
kernel 2.6.12-10-amd64-k8-smp
Nvidia Geforce 6600 GT PCI Express
Nvidia drivers 1.0-8178
At first I thought the path object bug was related to openGL graphics, but I'm ruling that out now since I have the same problem on a machine with AGP 8x Geforce 5200.
Can somebody help me pin down this little bugger?
Thanks.
Dries.
Does anybody out here has 64bit Houdini running on Debian or Ubuntu? I get a segfault when trying to make a path at object level (sop level idem). Apart from this path object bug, there doesn't seem to be any other issue. I noticed that the crash occurs only when moving the mouse. You can set a start point but moving the mouse after that segmentation faults. Grrr. I'm so close. The REALLY weird thing is that when using a .hip file that was started on a 32 bit version, the path object works just fine. A new hip file doesn't.
Among the things I've tried to resolve this: delete all the non-default otl's, rename my $HOME/houdini8.0 directory, create new desktop,… I tried all this with the latest 64 bit build: 8.0.517, but also with the earliest 64bit build: 8.0.410 and all builds in between.
I also tried to revert back to a 32 bit version (8.0.523), but then houdini doesn't seem to recognize my nfs mounts anymore. Could ASSUME_KERNEL have something to do with that?
System information:
AMD 64x2 (dual core)
kernel 2.6.12-10-amd64-k8-smp
Nvidia Geforce 6600 GT PCI Express
Nvidia drivers 1.0-8178
At first I thought the path object bug was related to openGL graphics, but I'm ruling that out now since I have the same problem on a machine with AGP 8x Geforce 5200.
Can somebody help me pin down this little bugger?
Thanks.
Dries.
Technical Discussion » BUG: switch COP doesn't accept channels
- DriesD
- 109 posts
- Offline
Thanks twod, this is actually very helpfull for my mind :-). Optimization such as using an integer in the blend COP and all the other issues you adressed is indeed really the sort of thing my thinking has become accustomed to using Houdini and it's great to know it is there in COPS too.
Technical Discussion » BUG: switch COP doesn't accept channels
- DriesD
- 109 posts
- Offline
Okay, so this is by design. I still feel a tad uncomfortable with this. Especially with the fact that the inputs have to have the same lenght. I would think overlapping frame ranges shouldn't cause a problem. Maybe it is me and I have to maybe stick to for a longer while, but I feel I have to alter far too many things or add a lot of nodes before I achieve what I want in cops. I admit I'm used to using onother node base compositor :roll:
For instance, there is so many ways to use mask: there is using an M plane from the input, there is attaching another one to the bottom of the node, there is a slider for the effect amount, you have to scope the plane used as a mask, you have comp operations for them in every node, I found this very confusing.
Generally how I work is: prepare/generate your source and mask images and use a simple comp operation on them at the end of the tree. Like this I can always see what state my sources are in. I realise this way is also possible in cops right now, but I always get terribly affraid that I'm not using the least computational way to achieve my effect (less nodes, means less pixel operations, means faster, right?)
Because I use more nodes to give me more visual feedback at any stage, I like the idea of stripping off the parts of the image that I don't need (planes and ranges). This means that not every node in the network has the same frame lenght or planes. Some branches have only b&w. But I run in to troubles like the one described above when trying to connect one branch to another…
Okay, I'll move on now. Cheers.
For instance, there is so many ways to use mask: there is using an M plane from the input, there is attaching another one to the bottom of the node, there is a slider for the effect amount, you have to scope the plane used as a mask, you have comp operations for them in every node, I found this very confusing.
Generally how I work is: prepare/generate your source and mask images and use a simple comp operation on them at the end of the tree. Like this I can always see what state my sources are in. I realise this way is also possible in cops right now, but I always get terribly affraid that I'm not using the least computational way to achieve my effect (less nodes, means less pixel operations, means faster, right?)
Because I use more nodes to give me more visual feedback at any stage, I like the idea of stripping off the parts of the image that I don't need (planes and ranges). This means that not every node in the network has the same frame lenght or planes. Some branches have only b&w. But I run in to troubles like the one described above when trying to connect one branch to another…
Okay, I'll move on now. Cheers.
Technical Discussion » BUG: switch COP doesn't accept channels
- DriesD
- 109 posts
- Offline
In Cops:
FileIn: foo.tga–
>—-switch:if($F>100,1,0)
FiloIn: bar.tga–
That just gives me a red arrow. “An input could not be evaluated”. Keyframing the channel gives the same thing, but when I change the value of the switch manually when no channel is there, it works as expected.
This does NOT happen when the inputs are sequences.
Hey I just found a workaroung: if you override the range for BOTH FiliIn nodes and unclick “Still Image”, it works.
Maybe there is a feature hidden there, but I don't think this is very intuitive.
FileIn: foo.tga–
>—-switch:if($F>100,1,0)
FiloIn: bar.tga–
That just gives me a red arrow. “An input could not be evaluated”. Keyframing the channel gives the same thing, but when I change the value of the switch manually when no channel is there, it works as expected.
This does NOT happen when the inputs are sequences.
Hey I just found a workaroung: if you override the range for BOTH FiliIn nodes and unclick “Still Image”, it works.
Maybe there is a feature hidden there, but I don't think this is very intuitive.
Houdini Lounge » Houdini and dual Opteron
- DriesD
- 109 posts
- Offline
Hmm… Isn't it stand for “Intel Architecture 64” or something? It's definitely Intel-based CPU, I am sure. Not sure if the IA-32, IA-64 is applicable to AMD-based CPU, tho…
I thought that Intel Architecture 64 was just a rename of the amd's 64 technology because intel didn't want to loose to much face. So, does anyone know whether the houdini ia64 distro works on an opteron?
DRie.s
Houdini Lounge » Houdini and dual Opteron
- DriesD
- 109 posts
- Offline
Indeed, buying hardware that isn't going to be used is a waste, but it's good to hear that Peter is apparently using the opterons with great succes. Even though Houdini wouldn't be compiled for 64 bit, other software for the workstation could be, hence my choice for either suse or gentoo. I'm gonna put some questions out on the gentoo list and get their point of view, but generally, gentoo has been really quick in catching the very latest, even without using their experimental tree. My hope is it wouldn't be that painfull to run a linux workstation which uses 64bit software for the greatest part.
And if sidefx is gonna make a 64 bit version compiled for the new upcoming intels, does that mean that the Opterons will also run under 64 bit or will they be bound to 32 bit houdini versions?
And if sidefx is gonna make a 64 bit version compiled for the new upcoming intels, does that mean that the Opterons will also run under 64 bit or will they be bound to 32 bit houdini versions?
Houdini Lounge » Houdini and dual Opteron
- DriesD
- 109 posts
- Offline
Hi John,
I'm afraid I know Paul all too well being a rebel and such, and I found out working with him that I can relate to his thinking. Our decisions have literally made our paths cross. Is it coincidence that he's going for an opteron system? Is Paul more bleeding edge than me? Of course I'm gonna go for an opteron! No doubt about it now! ;-)
I knew Paul had gone for dual opteron, but he's on a short break. He mentioned Rangi had such a system too, do you Rangi? I was just wondering if anyone else did, because you know John, these guys don't necessarily know why exactly they are going bleeding edge. I mean the theory and all, that's where people like you come in, right? Thanks for you point of view. Anyone else with technical details about Opteron?
I'm afraid I know Paul all too well being a rebel and such, and I found out working with him that I can relate to his thinking. Our decisions have literally made our paths cross. Is it coincidence that he's going for an opteron system? Is Paul more bleeding edge than me? Of course I'm gonna go for an opteron! No doubt about it now! ;-)
I knew Paul had gone for dual opteron, but he's on a short break. He mentioned Rangi had such a system too, do you Rangi? I was just wondering if anyone else did, because you know John, these guys don't necessarily know why exactly they are going bleeding edge. I mean the theory and all, that's where people like you come in, right? Thanks for you point of view. Anyone else with technical details about Opteron?
Houdini Lounge » Houdini and dual Opteron
- DriesD
- 109 posts
- Offline
I'm planning on installing a houdini workstation. Up until now, I've worked on linux with classic 32 bit machines.
Anybody has any experience with dual Opteron - houdini setup? I realise i'm trying to do something that is at the very edge of the available technology here. What I'm looking for is caveats, tips and tricks as I haven't bought any hardware yet. What motherboard, processor? Does the memory need to be of a certain kind? Do I need to fill the memory banks with equal sized memory sticks? Do I need more memory per se because of the 64-bit structure? I don't need to worry at all about the lower clockrates of opteron vs PIV? Any consequences for What has your preference or what would you buy if you had to buy a new system for houdini?
I have Gentoo installed on my current machine and I'm quite happy with it. If I was to consider another distro, it would probably be SUSE.
I can afford at this point in time to spent some time tweaking, setting up, compiling, … It's a jump in darkness a little bit, I'm guessing I'm looking for confirmation whether it can be done. A dual opteron SOUNDS very cost effective…
Thank you,
DRie.s
Anybody has any experience with dual Opteron - houdini setup? I realise i'm trying to do something that is at the very edge of the available technology here. What I'm looking for is caveats, tips and tricks as I haven't bought any hardware yet. What motherboard, processor? Does the memory need to be of a certain kind? Do I need to fill the memory banks with equal sized memory sticks? Do I need more memory per se because of the 64-bit structure? I don't need to worry at all about the lower clockrates of opteron vs PIV? Any consequences for What has your preference or what would you buy if you had to buy a new system for houdini?
I have Gentoo installed on my current machine and I'm quite happy with it. If I was to consider another distro, it would probably be SUSE.
I can afford at this point in time to spent some time tweaking, setting up, compiling, … It's a jump in darkness a little bit, I'm guessing I'm looking for confirmation whether it can be done. A dual opteron SOUNDS very cost effective…
Thank you,
DRie.s
Houdini Lounge » delete edge with out destroying model????
- DriesD
- 109 posts
- Offline
I was strugling with this issue as well. You can't do it in one step. You have to dissolve and then blast or delete the points left behind. With EdgeCollapse you can do it at once but your geometry gets deformed… Unless a better solution pops up all of a sudden??
Houdini Lounge » Whoohoo
- DriesD
- 109 posts
- Offline
The girl is someone I met during my travelling in India, Puna. Next to the Houdini GUI the most beautiful thing I have ever seen :-P
Houdini Lounge » Whoohoo
- DriesD
- 109 posts
- Offline
Yeah man, GREAT initiative.
Hope to see those Modeling and animation tutorials updated soon (with the support materias maybe? Are those available at the moment? I'm looking at the brush_lesson.pdf in Learning>General)
I was also wondering if there are any plans of making an Apprentice version downloadable. With a broadband connection I find this doable.
Cheers.
DRies.
Hope to see those Modeling and animation tutorials updated soon (with the support materias maybe? Are those available at the moment? I'm looking at the brush_lesson.pdf in Learning>General)
I was also wondering if there are any plans of making an Apprentice version downloadable. With a broadband connection I find this doable.
Cheers.
DRies.
-
- Quick Links