yes! RFE?
Nb. it wraps when you read the msg :-) (MMB on the node)
Found 130 posts.
Search results Show results as topic list.
Technical Discussion » Comment text box
- ben simons
- 387 posts
- Offline
Technical Discussion » WireGlueGroupConstraint DOP
- ben simons
- 387 posts
- Offline
Thanks Derrick!
I was actually changing this DOP to one which uses two Anchor Point Number
Position DOP's when I noticed the inconsistency. So - the data names are
just what then appears in the Details view, and that's all? I'm just trying to
better understand how it works at this level.
I'd wondered if this different name was something to do with needing a
unique dataname, or a mod on goal ordering (for rotation order?),
or … unimportant!
From what you've said, I gather that the Constraint DOP uses the internal
dataTypes, like “SIM_ConAnchorWorlsSpaceRot” to work out what is a valid
anchor?
I'm not sure what determines which is the “first” anchor. Is it the way a
constraint DOP is wired (counting inputs, from left to right)? The details
view lists the anchors and con-relat's in what appears to be unsorted order.
eg. I see:
ConstraintRot_3
- Anchor
- ConRelHard
- WireAnchor
Constraint_3
- ConRelHard
- GoalAnchor
- WireAnchor
I was actually changing this DOP to one which uses two Anchor Point Number
Position DOP's when I noticed the inconsistency. So - the data names are
just what then appears in the Details view, and that's all? I'm just trying to
better understand how it works at this level.
I'd wondered if this different name was something to do with needing a
unique dataname, or a mod on goal ordering (for rotation order?),
or … unimportant!
From what you've said, I gather that the Constraint DOP uses the internal
dataTypes, like “SIM_ConAnchorWorlsSpaceRot” to work out what is a valid
anchor?
I'm not sure what determines which is the “first” anchor. Is it the way a
constraint DOP is wired (counting inputs, from left to right)? The details
view lists the anchors and con-relat's in what appears to be unsorted order.
eg. I see:
ConstraintRot_3
- Anchor
- ConRelHard
- WireAnchor
Constraint_3
- ConRelHard
- GoalAnchor
- WireAnchor
Technical Discussion » WireGlueGroupConstraint DOP
- ben simons
- 387 posts
- Offline
Hi,
Linux H8.1.655
I think I might have found a typo inside the WireGlueGroupConstraint DOP.
This is actually an OTL, which contains an “Anchor: World Space Rotation” DOP called: anchorworldspacerot2
That inner DOP is using the Data Name: “Anchor” when i think it should be using: “GoalAnchor”. (?)
cheers,
ben.
Linux H8.1.655
I think I might have found a typo inside the WireGlueGroupConstraint DOP.
This is actually an OTL, which contains an “Anchor: World Space Rotation” DOP called: anchorworldspacerot2
That inner DOP is using the Data Name: “Anchor” when i think it should be using: “GoalAnchor”. (?)
cheers,
ben.
Technical Discussion » Primative Sop trick?
- ben simons
- 387 posts
- Offline
SimonHeya,
Being as its a primitive it moves it based on the position of the centroid…
If you still have the example, try RMB “delete channel” on the primative SOP's
pivot values, so that it's 0,0,0 instead of $CEX, $CEY, $CEZ. … Cool? It makes
sense, like you say, until a few more lines are added. I've attached an example
with 4 lines. The situation where the switch is set to “2” is curious. The right two
lines are off to the right.
To be clear, this is not a problem - i'm just messing around with the Prim Sop.
I know a transform sop with -$CEX, -$CEY, -$CEZ would be better generally.
cheers,
b.
Technical Discussion » Primative Sop trick?
- ben simons
- 387 posts
- Offline
Hey,
I found a funny solution to a simple problem today, except i'm not sure how to
interpret what's happening. I'm stamping a lot of line segments, variously
oriented, using the line sop with 2 points. The default Line Sop has the first
point at the origin. I wanted the origin to be half-way along the line.
Try this trick:
Place a Line SOP. Keep defaults, except change “dirx” to something like: sin($F).
Hit play - the line moves like a VU Meter.
Append a Primative SOP, and wire the Line SOP into both inputs.
Enable the Primative Sop's “Do Transform” toggle.
The origin is now at the line's centre. Hey? Cool. Ummm.. Why?
eg. Is it using the $CE{X,Y,Z} from the template input? Discuss.
I found a funny solution to a simple problem today, except i'm not sure how to
interpret what's happening. I'm stamping a lot of line segments, variously
oriented, using the line sop with 2 points. The default Line Sop has the first
point at the origin. I wanted the origin to be half-way along the line.
Try this trick:
Place a Line SOP. Keep defaults, except change “dirx” to something like: sin($F).
Hit play - the line moves like a VU Meter.
Append a Primative SOP, and wire the Line SOP into both inputs.
Enable the Primative Sop's “Do Transform” toggle.
The origin is now at the line's centre. Hey? Cool. Ummm.. Why?
eg. Is it using the $CE{X,Y,Z} from the template input? Discuss.
Technical Discussion » RFE polywire SOP
- ben simons
- 387 posts
- Offline
Simonomg. haha! yes. nice. thx simon. I just RTFM:
What's wrong with just putting $NX,$NY,$NZ in the upvector parameter?
The four numerical parameters support all the local variables of the Point operation, plus the LSYSTEM specific variables of $WIDTH, $SEGS, $DIV, $LAGE, $GEN, and $ARC.the docs need an update; there's more than four “numerical” parms.
Change “the Point operation” to “the Point SOP”?
oferIndeed! It's tempting to set it as a “permanent default” but they're ticking timebombs. Just when you get used to them, they're gone with the next version of Houdini (or you give another user a script with an opadd - boom!).
… you can just add it as a preset for the PolyWire SOP.
btw i noticed an “LSYSTEM” option in the presets menu.. Interesting.
b.
Technical Discussion » RFE polywire SOP
- ben simons
- 387 posts
- Offline
RFE for Polywire SOP
Perhaps there should be an option to use the input curve's normals?
AFAIK, presently, to do this, you need to enable the “Joint Upvector” option
and then enter the following 3 expressions for NX, NY, NZ:
point(“../pwInput”, $PT, “N”, 0)
point(“../pwInput”, $PT, “N”, 1)
point(“../pwInput”, $PT, “N”, 2)
Where “pwInput” is a Null SOP going into the Polywire SOP (to avoid clazy feedback/self-referencing).
It seems like this is what you'd normally want, so a toggle: “Use Wire Normals” might help.
cheers,
ben.
Perhaps there should be an option to use the input curve's normals?
AFAIK, presently, to do this, you need to enable the “Joint Upvector” option
and then enter the following 3 expressions for NX, NY, NZ:
point(“../pwInput”, $PT, “N”, 0)
point(“../pwInput”, $PT, “N”, 1)
point(“../pwInput”, $PT, “N”, 2)
Where “pwInput” is a Null SOP going into the Polywire SOP (to avoid clazy feedback/self-referencing).
It seems like this is what you'd normally want, so a toggle: “Use Wire Normals” might help.
cheers,
ben.
Technical Discussion » Using Renderman in Houdini
- ben simons
- 387 posts
- Offline
Houdini Lounge » How to render houdini particle as Ripoint for renderman ??
- ben simons
- 387 posts
- Offline
Hey,
Just been down this path for RiPoints. fyi: if you also want to set the renderman varying float “width” parameter, you can do this in a Point SOP by setting Particle->Scale, and use an expression which uses $PT
b.
Just been down this path for RiPoints. fyi: if you also want to set the renderman varying float “width” parameter, you can do this in a Point SOP by setting Particle->Scale, and use an expression which uses $PT
b.
Technical Discussion » RFE File SOP info
- ben simons
- 387 posts
- Offline
Yeah yeah. It might be faster to just insert a ‘z’ at the end of the line (so it goes red)
and then MMB on it. blah blah blah.. I'm not saying I can't work it out. :-)
I'm just saying it would be convenient if the filename simply appeared with the MMB info. RFE-like.
and then MMB on it. blah blah blah.. I'm not saying I can't work it out. :-)
I'm just saying it would be convenient if the filename simply appeared with the MMB info. RFE-like.
Technical Discussion » RFE File SOP info
- ben simons
- 387 posts
- Offline
REF File Sop - MMB shows current filename
It'd be great if the File SOP reported the filename it's using.
This information would appear, say, when you MMB on the node, and
in the Extended Information.
Nb. When the file sop cannot load a filename, it goes red and MMB reports
the filename it is trying to load (which is great). The problem is when
there's not an error, this info isn't there.
eg. I have a crazy expression in a File SOP, and it would be useful to see
the actual filename it generates:
`substr( chsraw(“../../file4_filename”), 0, rindex( chsraw(“../../file4_filename”), “$”))``padzero(4, $F+1)``substr( chsraw(“../../file4_filename”), rindex( chsraw(“../../file4_filename”), “.”), 1000)`
cheers,
ben.
It'd be great if the File SOP reported the filename it's using.
This information would appear, say, when you MMB on the node, and
in the Extended Information.
Nb. When the file sop cannot load a filename, it goes red and MMB reports
the filename it is trying to load (which is great). The problem is when
there's not an error, this info isn't there.
eg. I have a crazy expression in a File SOP, and it would be useful to see
the actual filename it generates:
`substr( chsraw(“../../file4_filename”), 0, rindex( chsraw(“../../file4_filename”), “$”))``padzero(4, $F+1)``substr( chsraw(“../../file4_filename”), rindex( chsraw(“../../file4_filename”), “.”), 1000)`
cheers,
ben.
Technical Discussion » Create trianglar mesh from points (x,y,z) data
- ben simons
- 387 posts
- Offline
http://oldsite.vislab.usyd.edu.au/staff/ben/aust/index.html [oldsite.vislab.usyd.edu.au]
Technical Discussion » BUG: WireObject DOP doesn't update path to renamed Geo
- ben simons
- 387 posts
- Offline
Hi,
Houdini 8.1.655, Linux
The sop pathname in a wireobject dop doesn't update when the geo it references is renamed.
I have a subnet with a geo and a dopnet in it. The dopnet contains a WireObject Dop, which has its SOP Path parameter set to “../../geo1/INTO_DOPS”. When I rename “geo1” to “inputCurves” the SOP Path param doesn't update (because, it appears, the blue display flag on the dopnet is off). If the display flag on the dopnet is on, then the pathname updates ok.
The pathname should update regardless.
cheers,
ben.
Houdini 8.1.655, Linux
The sop pathname in a wireobject dop doesn't update when the geo it references is renamed.
I have a subnet with a geo and a dopnet in it. The dopnet contains a WireObject Dop, which has its SOP Path parameter set to “../../geo1/INTO_DOPS”. When I rename “geo1” to “inputCurves” the SOP Path param doesn't update (because, it appears, the blue display flag on the dopnet is off). If the display flag on the dopnet is on, then the pathname updates ok.
The pathname should update regardless.
cheers,
ben.
Technical Discussion » RFE Sort columns in Details View Pane
- ben simons
- 387 posts
- Offline
Technical Discussion » RFE Sort columns in Details View Pane
- ben simons
- 387 posts
- Offline
Oh.. Yes. ops: But I was using Houdini 8.1 ;-) Coool.
btw: what's the use in selecting a column?
Can anything be done with the selection?
btw: what's the use in selecting a column?
Can anything be done with the selection?
Technical Discussion » RFE Sort columns in Details View Pane
- ben simons
- 387 posts
- Offline
Hey SESI,
RFE: It'd be useful to be able to sort by various columns in the Details View Pane.
ie. The usual GUI behaviour: you click on a column header and all the rows are sorted by that column. Clicking on the Point Number column would reset the sorted order to the usual numeric sequence.
cheers,
ben.
RFE: It'd be useful to be able to sort by various columns in the Details View Pane.
ie. The usual GUI behaviour: you click on a column header and all the rows are sorted by that column. Clicking on the Point Number column would reset the sorted order to the usual numeric sequence.
cheers,
ben.
Technical Discussion » Automatic popup window
- ben simons
- 387 posts
- Offline
Hey Pete,
Okay. How about a message in the “On Loaded” event for a dummy OTL? I just tried this and it worked.
Create a subnet, and “Create Digital Asset” from it. In the Type Properties->Events tab for the event type: “on loaded” enter something like: message “hello Peter R.”
Save and quit and load the hip file. You should see the message.
cheers,
b.
PS. Linux Houdini 8.1.704 Crash: I thought I'd be sneaky, and add an “oprm /obj/popup1” after the message line (to delete the OTL after the message pops up) and Houdini crashed. Changing it to “oprm $arg1” means the message comes up before the crash..
Okay. How about a message in the “On Loaded” event for a dummy OTL? I just tried this and it worked.
Create a subnet, and “Create Digital Asset” from it. In the Type Properties->Events tab for the event type: “on loaded” enter something like: message “hello Peter R.”
Save and quit and load the hip file. You should see the message.
cheers,
b.
PS. Linux Houdini 8.1.704 Crash: I thought I'd be sneaky, and add an “oprm /obj/popup1” after the message line (to delete the OTL after the message pops up) and Houdini crashed. Changing it to “oprm $arg1” means the message comes up before the crash..
Technical Discussion » Stuck Merge Sop (Yellow for Wire/DOPs)
- ben simons
- 387 posts
- Offline
Hey simon,
that's what i was trying to say about the “switch sop”. That approach doesn't work. At frame 1, the object merge goes yellow anyway (it does cook) and it stays yellow. So, by frame 12, when the switch switches to it, it hits the “invalid sop”.
It appears that once the object merge goes yellow the only way back is to manually wake it up.
that's what i was trying to say about the “switch sop”. That approach doesn't work. At frame 1, the object merge goes yellow anyway (it does cook) and it stays yellow. So, by frame 12, when the switch switches to it, it hits the “invalid sop”.
It appears that once the object merge goes yellow the only way back is to manually wake it up.
Technical Discussion » Stuck Merge Sop (Yellow for Wire/DOPs)
- ben simons
- 387 posts
- Offline
Houdini 8.0.655 Linux
I've got a Wire Object Dop with a “Creation Frame” set to 12. (btw, this is the cause of the problem it seems!) Then there's a Wire Constraint and a Wire Solver appended to that. A simple wire dop setup..
At Frame-1, the Object Merge Sop which extracts the DOPs geom is yellow. The warning says:
Putting a Switch Sop below the Object Merge, and switching to it after frame-12 doesn't help as the Object Merge Sop stays yellow (no geometry is extracted from Dops). Perhaps the Wire Object Creation Frame must be “1”, and the geometry going into DOP's has to be dummied for frames 1-12..
Is there some trick to make the Object Merge Sop re-check for valid DOP's Geometry?
cheers,
ben.
I've got a Wire Object Dop with a “Creation Frame” set to 12. (btw, this is the cause of the problem it seems!) Then there's a Wire Constraint and a Wire Solver appended to that. A simple wire dop setup..
At Frame-1, the Object Merge Sop which extracts the DOPs geom is yellow. The warning says:
“Invalid Sop Specified: /obj/dopnet1:wireobject1/Geometry”.Okay. Sure. The trouble is it stays yellow, past frame 12 when there is DOP geometry! For example, at frame-14, if some toggles are clicked on the Object Merge Sop, it recooks and all is good.
Putting a Switch Sop below the Object Merge, and switching to it after frame-12 doesn't help as the Object Merge Sop stays yellow (no geometry is extracted from Dops). Perhaps the Wire Object Creation Frame must be “1”, and the geometry going into DOP's has to be dummied for frames 1-12..
Is there some trick to make the Object Merge Sop re-check for valid DOP's Geometry?
cheers,
ben.
Technical Discussion » Merge sop problems
- ben simons
- 387 posts
- Offline
-
- Quick Links