Found 405 posts.
Search results Show results as topic list.
Technical Discussion » RFE: real time toggle hotkey
- deecue
- 412 posts
- Offline
Technical Discussion » textport not showing prompt
- deecue
- 412 posts
- Offline
If you made it a button in your KDE Panel, then there's an option there for it to run in a terminal
yup, that's good enough for me.. thanks ben. 8)
Oh you sad, sad, little GUI people, you…
hey now, i just like my hotkeys. i never said anything about a gui.
do you get the same thing if you start Houdini in a shell, then close the shell while it's up?
Nope. as long as the shell only exits after houdini loads, it's fine..
but of course you won't like the clutter.actually, telling the link to run in the terminal closes the terminal after the app loads.. so no worries about clutter..
So basically if the shell closes before Houdini returns an exit status the textport prompt breaks.
Yup. :roll:
Technical Discussion » textport not showing prompt
- deecue
- 412 posts
- Offline
ahh.. that's it.. thank you wolfwood. That's exactly what i'm doing. I have houdini bound to ctrl-alt-h in kde so i can just launch it right away.. but if i go to the terminal and run it from there, everything's fine..
very odd.. anyone wanna take a stab at why this is happening and even better, how to fix it (if possible)?
very odd.. anyone wanna take a stab at why this is happening and even better, how to fix it (if possible)?
Technical Discussion » textport not showing prompt
- deecue
- 412 posts
- Offline
This is on Suse 10, H8.0.422, 32bit, gcc3.4
If i switch any pane in to a textport, i get no prompt.
If i pop open a textport (ala alt-T), i get a prompt, but as soon as i enter the first command, it's gone.
Maybe this is a linux thing but i was used to seeing it there in windows.. Is it a bug? Feature? Prefs anywhere?
If i switch any pane in to a textport, i get no prompt.
If i pop open a textport (ala alt-T), i get a prompt, but as soon as i enter the first command, it's gone.
Maybe this is a linux thing but i was used to seeing it there in windows.. Is it a bug? Feature? Prefs anywhere?
Technical Discussion » RFE: real time toggle hotkey
- deecue
- 412 posts
- Offline
I would like to see a hotkey entry in the houdini/playbar context for the real time toggle. I realize i can bind fplayback -r on/off to a function key but i still think it's important enough to exist in the hotkey manager as well.. Plus, that option creates two hotkeys. One to turn it off and one to turn it on (unless i'm missing a toggle option somewhere). It seems especially important with dops now because you'll want to cache the sim in non realtime so it gets every frame.. But once it's cached, you wanna switch on real time so it doesn't fly by during playback..
thanks
thanks
Houdini Lounge » Suse 10 and dual head cards (OT)
- deecue
- 412 posts
- Offline
Actually… I just figured out what i was doing wrong. I kept attempting to configure multiple x screens based on one chip (card).. While this can be done supposidly, it's not recommended according to the nvidia readme. For some reason I could never get it to work and trying to get it to work caused big time problems for whatever reason.
So basically in the end, i just edited it by hand to use twin view instead of two x sessions and everything works lovely now. Man, that seriously was like 4 hours of screwing around late last night, until i took 5 min to read the readme closer and another 5 to add a couple lines involving twin view.. Teach me for paying attention to the net before paying attention to official documentation. :wink:
Anyways, now off to get this tv-out to work which is the whole reason i bought that crappy vanta 2 years ago. See in windows, i could only get it to either use the dual head or one head and the tv out. So i bought the vanta to have my dual monitors and tv output for cheap color correction at home. But now that i'm running suse, supposidly the nvidia linux drivers can handle all three outputs from the one card (twinview + vivo).. That would be sweet if i could get that to work.
Thanks guys for the replies.
So basically in the end, i just edited it by hand to use twin view instead of two x sessions and everything works lovely now. Man, that seriously was like 4 hours of screwing around late last night, until i took 5 min to read the readme closer and another 5 to add a couple lines involving twin view.. Teach me for paying attention to the net before paying attention to official documentation. :wink:
Anyways, now off to get this tv-out to work which is the whole reason i bought that crappy vanta 2 years ago. See in windows, i could only get it to either use the dual head or one head and the tv out. So i bought the vanta to have my dual monitors and tv output for cheap color correction at home. But now that i'm running suse, supposidly the nvidia linux drivers can handle all three outputs from the one card (twinview + vivo).. That would be sweet if i could get that to work.
Thanks guys for the replies.
Houdini Lounge » Suse 10 and dual head cards (OT)
- deecue
- 412 posts
- Offline
Alright you Suse guys, I could use some help..
I'm running Suse 10 and I have two nvidia cards : a dual head gf4 ti4200 and an old cheapo single head with a vanta gpu. Originally, I configured the system to be able to do dual monitors using one connected to the ti4200 and the other one to the vanta. This took some work but through getting old drivers that support legacy gpus and editing some files (according to suse and nvidia docs), I was able to get it to work.
But now, i'm wanting to forget about that old card and just use the dual head on the ti4200. This is what I'm having trouble with. No matter what i do, I can't get that thing to recognize the second head. According to the suse docs, sax2 is supposed to recognize it automatically and provide a box labelled “Activate Dual Head Mode” with a configure button beside it. I don't have this anywhere. I've tried to get it to work with the opensource nv drivers. I've ran YOU to get the latest Nvidia Drivers and tried them. I've downloaded the package from nvidia themselves and ran it in run level 3 manually. I've manually editing my xorg.conf file to try and get another device on there. But alas, nothing.
I've read a few posts on linux forums/newsgroups about people who had this working perfectly in suse 9.3, but as soon as they got 10 up and running, they hit problems left and right using sax2 (but were able to fix it by just copying the device selection in xorg.conf and setting it to the second screen.. unfortunately, this isn't working for me) I've also read things about Suse/Novell knowing of this issue and are trying to fix it. Whether this has any merit to it or not, I have no idea.
Sorry for the non-houdini-related post, but I figured you Suse people might be able to spread some love and help me out with this. Maybe even just post your xorg.conf file so I can see what you've got going on. Can anyone on 10 see the ‘Activate Dual Head Mode’ box?
thanks everyone,
dave
I'm running Suse 10 and I have two nvidia cards : a dual head gf4 ti4200 and an old cheapo single head with a vanta gpu. Originally, I configured the system to be able to do dual monitors using one connected to the ti4200 and the other one to the vanta. This took some work but through getting old drivers that support legacy gpus and editing some files (according to suse and nvidia docs), I was able to get it to work.
But now, i'm wanting to forget about that old card and just use the dual head on the ti4200. This is what I'm having trouble with. No matter what i do, I can't get that thing to recognize the second head. According to the suse docs, sax2 is supposed to recognize it automatically and provide a box labelled “Activate Dual Head Mode” with a configure button beside it. I don't have this anywhere. I've tried to get it to work with the opensource nv drivers. I've ran YOU to get the latest Nvidia Drivers and tried them. I've downloaded the package from nvidia themselves and ran it in run level 3 manually. I've manually editing my xorg.conf file to try and get another device on there. But alas, nothing.
I've read a few posts on linux forums/newsgroups about people who had this working perfectly in suse 9.3, but as soon as they got 10 up and running, they hit problems left and right using sax2 (but were able to fix it by just copying the device selection in xorg.conf and setting it to the second screen.. unfortunately, this isn't working for me) I've also read things about Suse/Novell knowing of this issue and are trying to fix it. Whether this has any merit to it or not, I have no idea.
Sorry for the non-houdini-related post, but I figured you Suse people might be able to spread some love and help me out with this. Maybe even just post your xorg.conf file so I can see what you've got going on. Can anyone on 10 see the ‘Activate Dual Head Mode’ box?
thanks everyone,
dave
Houdini Lounge » Arrow Keys and COPs
- deecue
- 412 posts
- Offline
oh yea… that tapping thing..it seriously drives me up a wall.. really need to fix that.. :evil:
Technical Discussion » RBD without volumes
- deecue
- 412 posts
- Offline
i was kinda wondering about this volume/open surface type stuff as well.. i was finally able to get a chance to try out H8 *just* last night for the very first time.. and of course, i probably did what everyone else did within the first couple seconds of launching it.. throw a box on a plane.. but for the life of me i couldn't get that dang thing to collide.. the ground plane dop worked fine, extruding the grid to make it a solid worked, but what's going on with that dang simple grid? and the odd thing on top of it all, while throwing a box on a grid did nothing, throwing a grid on a box worked perfectly (if anyone can atleast explain that one to me, it'd be nice)..
now i realize i spent a total of 3 hours playing with all this so far and know it's probably all in my error.. but it definitely was a wierd first experience.. gotta spend a lot of time in the docs and example hips now to get my head around it all..
now i realize i spent a total of 3 hours playing with all this so far and know it's probably all in my error.. but it definitely was a wierd first experience.. gotta spend a lot of time in the docs and example hips now to get my head around it all..
Technical Discussion » Rating topics on the Forum
- deecue
- 412 posts
- Offline
as much as i like the idea.. i have to be honest and say i don't really know if i'd actually take the time to rate a post or reply (and i get the feeling that a lot of other people wouldn't as well).. but hey, go for it if you really want to
Houdini Lounge » doc typo
- deecue
- 412 posts
- Offline
not big deal and def not urgent, but in hdox/houdini/content/base/whatsnew_80_hscript.xml , the last line should have ‘opparm’ instead or ‘oparm’. (and of course it should reflect the correct link)..
Technical Discussion » Render artifacts!!!!1
- deecue
- 412 posts
- Offline
Houdini Lounge » Favourite Operation
- deecue
- 412 posts
- Offline
hey jason,
you have to turn on the operator toolbar in the view pane first.. (pane menu->toolbars and controls->operator toolbar) once that's up, you'll see the favourite option icon on the left.. right click and choose..
you have to turn on the operator toolbar in the view pane first.. (pane menu->toolbars and controls->operator toolbar) once that's up, you'll see the favourite option icon on the left.. right click and choose..
Technical Discussion » Dyanmic Parenting not working correctly?
- deecue
- 412 posts
- Offline
i've used the dynamic parenting tool a bunch in h7.. worked like a charm.. haven't tried out h8 though.. what sort of problems are you having?
actually, now that i think about it… i had *one* issue that only seemed to crop up in *one* particular file.. and that was that it would throw the inital offset null and blend objs completely off from my network.. out in the middle of 2d node space somewhere.. was pretty annoying, but just meant i had to zoom out really really far, locate it, and drag it back to my main network area.. didn't seem to affect any functionability of it though..
actually, now that i think about it… i had *one* issue that only seemed to crop up in *one* particular file.. and that was that it would throw the inital offset null and blend objs completely off from my network.. out in the middle of 2d node space somewhere.. was pretty annoying, but just meant i had to zoom out really really far, locate it, and drag it back to my main network area.. didn't seem to affect any functionability of it though..
Technical Discussion » C-plane cannot toggled off in ortho views?
- deecue
- 412 posts
- Offline
the c-plane is only for persp viewports.. the ortho ones are set in the display prefs->grid tab..
Houdini Lounge » expressions vs hscript
- deecue
- 412 posts
- Offline
i suppose you could always use hscript to throw down and wire in an inline vop.. then edit the vex code parm
Houdini Lounge » expressions vs hscript
- deecue
- 412 posts
- Offline
thanks guys.. this does make it a lot clearer for me now in respects to each's purpose and reasoning. 8)
Technical Discussion » Channel group creation equiv not working
- deecue
- 412 posts
- Offline
ctrl+g - create a group from the displayed channels
ahhh thank god.. that will be so much nicer now..
Houdini Lounge » expressions vs hscript
- deecue
- 412 posts
- Offline
yea, what you're saying does make a good point as to the references of each one.. i can digg it..
i was actually about to come back and say “well what about opselect and opflag being expressions then”.. but after i thought about, that too does make sense since they're returning a list rather than setting a property like you would use opset for.. also, i suppose this would go towards your “overlap for convenience” comment which is a good to have..
but i have to be honest and say, my first reaction to:
was “well what about vex then? vex is essentially doing that”.. but i suppose expressions would be much quicker to throw down in a parm rather then setting up something in vex.. i dunno.. it's can get crazy when it comes to all these formats/languages at times..
thanks wolfwood..
i was actually about to come back and say “well what about opselect and opflag being expressions then”.. but after i thought about, that too does make sense since they're returning a list rather than setting a property like you would use opset for.. also, i suppose this would go towards your “overlap for convenience” comment which is a good to have..
but i have to be honest and say, my first reaction to:
Now the expression language is for evaluating data. Math functions, fetching channel data, query geometry details, etc.
was “well what about vex then? vex is essentially doing that”.. but i suppose expressions would be much quicker to throw down in a parm rather then setting up something in vex.. i dunno.. it's can get crazy when it comes to all these formats/languages at times..
thanks wolfwood..
Houdini Lounge » expressions vs hscript
- deecue
- 412 posts
- Offline
a couple questions for my own curiosity if you don't mind:
-what decides whether a function will become an expression or hscript command?
-in the begining, which was first, and why was the latter implemented after the other? did they pop up at the same time? and if so, why not just keep it to one format?
i guess this comes in response to me getting frustrated because i can't pull up help on functions because i forget that they actually might be an expression rather than hscript.. i go searching for keywords and thinking “i know there's an opthis and an opthat, where the heck is it!?” just to calm down and remember 5 min later that i should of been doing an exhelp -k instead of a help -k.. i would also think it would help with the whole “backtick this, double quote that, make sure you eval() that one first” ordeal..
thoughts anybody? would love to know some background info on this.. also some reasoning as to why ‘one format would be a bad thing’ from you people smarter than i would be nice… :wink:
-what decides whether a function will become an expression or hscript command?
-in the begining, which was first, and why was the latter implemented after the other? did they pop up at the same time? and if so, why not just keep it to one format?
i guess this comes in response to me getting frustrated because i can't pull up help on functions because i forget that they actually might be an expression rather than hscript.. i go searching for keywords and thinking “i know there's an opthis and an opthat, where the heck is it!?” just to calm down and remember 5 min later that i should of been doing an exhelp -k instead of a help -k.. i would also think it would help with the whole “backtick this, double quote that, make sure you eval() that one first” ordeal..
thoughts anybody? would love to know some background info on this.. also some reasoning as to why ‘one format would be a bad thing’ from you people smarter than i would be nice… :wink:
-
- Quick Links