What do you mean. You are showing the Y values as zeroed out(and you said that is correct).
What Y values did you want 'preserved' from the DXF file?(the screen shot you posted shows both images are the same).
Found 2045 posts.
Search results Show results as topic list.
Technical Discussion » Problem when importing DXF File to Houdini
- BabaJ
- 2047 posts
- Offline
Houdini Indie and Apprentice » The difference between rendered particles and render views
- BabaJ
- 2047 posts
- Offline
jsmack> njm818.
Photoshop should have no problem reading exr, which does not divide by alpha, and which should match the render view more closely.
Indeed Photoshop works with exrs really well.
Personally when I work on a project and am going to do a render specifically to export out to Photoshop, I find I don't do much 'fine tuning' of the render beforehand.
With exrs in Photoshop I rarely have to do much to get a desired final image other than create an exposure adjustment layer and adjust gamma.
Edited by BabaJ - yesterday 07:23:55
Houdini Lounge » Houdini 20.5 Rumors
- BabaJ
- 2047 posts
- Offline
Houdini Indie and Apprentice » group-name from name attribute
- BabaJ
- 2047 posts
- Offline
Houdini Indie and Apprentice » group-name from name attribute
- BabaJ
- 2047 posts
- Offline
djdoogle123
But except when it comes to the rbd bullet solver it doesn’t like it as it also uses a name attribute what would be a good work around here?
Before you run your geo through the sim, you could make an attribute like 'original_name' and assign the values as if it was 'name'.
Then after the sim, you could delete all 'name' attributes with delete attribute sop, except 'original_name' attribute.
Then use the rename attribute sop to change your 'original_name' to 'name'.
Edited by BabaJ - May 24, 2024 16:31:32
Houdini Indie and Apprentice » How to randomise the colors on a Ramp node?
- BabaJ
- 2047 posts
- Offline
Generally you should be able to do what you want with a ramp parameter,
but since you haven't provided a hip file we can't see the context/setup you are applying the ramp parameter in.
but since you haven't provided a hip file we can't see the context/setup you are applying the ramp parameter in.
Houdini Indie and Apprentice » Iterative loop
- BabaJ
- 2047 posts
- Offline
gordig
Everything I'm reading about the Solver SOP suggests that it's meant to run every frame,
Yes it does run every frame, but it also has the capacity to 'know/get' values from the previous frame.
gordig
If I plug that same VEX code into the Solver SOP, I get the same results as before
Yes of course you will have to modify your code to reflect what you want to do.
At the moment you actually don't have any 'absolute' values to reference to carry forward for each next frame, because you are constantly changing your reference every frame (@f) and changing it twice on those instances in which it matches a frame number.
Edited by BabaJ - April 28, 2024 09:08:57
Houdini Indie and Apprentice » Iterative loop
- BabaJ
- 2047 posts
- Offline
gordig
If that gets stored by the conditional executing, then the new value of @f will drive the next blink.
But it doesn't get 'stored'. It only knows what the current values as they are per frame.
gordig
I could pre-generate a list of blink frames based
Yes...that's kind of a 'brute' force way of doing things.
You might want to look at how sop solvers work, as you can work as if values are stored.
If you look at this page, the initial explanation should help show how it is similar with what you are doing.
https://tokeru.com/cgwiki/The_solver_sop.html#prev-frame-vs-previous-frame [tokeru.com]
Houdini Indie and Apprentice » Iterative loop
- BabaJ
- 2047 posts
- Offline
gordig
At frame 59, I get new values of @f = 115 and @fr = 56. Sounds good, right? But after frame 59, it reverts to the initial values, so there's never a second blink.
That's because at frame 59 it ($F) matches your code you have set up for only that Frame.
gordig
Why isn't the last line, which should add the interval of the next blink onto the frame number of the previous blink, actually doing that?
Unless it's a specialized node, the wrangle does not 'see/know' what the values are for the previous frame, and so neither what values where calculated. It is only calculating what you have on any given frame.
If you want a blink at other specific frames you will have to make a conditional statement for those specific frames,
or you could make use of a solver sop which can remember previous frame values so that your code can accommodate that scenario.
Edited by BabaJ - April 26, 2024 08:49:42
Technical Discussion » read an attribute name
- BabaJ
- 2047 posts
- Offline
Gerardo Castellanos
I mean, I want to access to the values of that parameters,
As alex and I have already shown you can access the value of the parameter with:
chs("../attrMask")
What is entered into that paramater and how you decided to treat it is another matter.
In all cases a string paramter that you are accessing is just that - only a string.
mask_noiser
or it could be:
@mask_noiser
In either case, it's still only a string and you will have to decide how to deal what is entered or not. How it is entered, or not, etc.
Since it's a string and if a 'proper' name is entered, it can be used to pass into a function argument.
If you want to get a point value for example of an attribute specified by your parameter name entered:
int Result = pointattrib(0,chs("../attrMask"),5);// if attribute specified refers to an integer float Result = pointattrib(0,chs("../attrMask"),5);// if attribute specified refers to an float // etc. etc.
If you are wanting to do some general reading of all types of attributes, you are going to have to determine 'class/types' as part of the process.
https://www.sidefx.com/docs/houdini/vex/functions/attribtype.html [www.sidefx.com]
https://www.sidefx.com/docs/houdini/vex/attribtypeinfo_suite.html [www.sidefx.com]
Also, if you or the user entered '@' as part of the parameter text entered, you will have to parse out that symbol character from the string parameter before passing it as a string argument to one of those functions.
Edited by BabaJ - April 20, 2024 10:50:58
Technical Discussion » read an attribute name
- BabaJ
- 2047 posts
- Offline
Gerardo Castellanos
Thanks, but I would like to access to the values of that attribute with a @`chs("../attrMask")`, and I get the same error message when it is empty.
What do you mean?
You're accessing a parameter that has only one value and is not bound to anything unless it has been done so intentionally, which if that was the case you could just access the attribute itself.
If you want to create an attribute with that parameter value just do what alex said but instead of a local variable:
s@attrMask = chs("../attrMask");
Technical Discussion » Deleting first and last point over for each primitive
- BabaJ
- 2047 posts
- Offline
You can isolate/group/set attributes for the first and last points of the primitive by
using the primpoints() function.
It returns an array of point numbers that belong that prim, in the same order as they are on the primitive.
So you can select by index the first element and last element of the arrays.
using the primpoints() function.
It returns an array of point numbers that belong that prim, in the same order as they are on the primitive.
So you can select by index the first element and last element of the arrays.
Edited by BabaJ - April 18, 2024 12:03:48
Technical Discussion » Bulge on attribute ?
- BabaJ
- 2047 posts
- Offline
The Bulge SOP was made to work with metaballs.
If you just want to 'shape' by attribute alone you could do what I have in the hip.
If you just want to 'shape' by attribute alone you could do what I have in the hip.
Houdini Indie and Apprentice » Trace node producing jagged edges and weird normals
- BabaJ
- 2047 posts
- Offline
For your 'problem #1" the 'issue' is that you are using a png so it is a 'raster' image with anti-alising of the pixels to give the appearance of a smooth edge.(There's no parametric information defining the shape. The appearance of the 'edge' is created by 'dimming' pixels from view, for a 'blurring' effect, but the pixels themselves still form a step-wise/jagged pattern).
So there is no actual 'smooth edge'(parametric) to trace/duplicate - It's being done algorithmically by the trace node to get as close as possible; To what an actual smooth edge might be.
If your imput geometry was vector based - like an *.igs file format, then you could have a better source to work from.
However, if you adjust the trace nodes step parameter and follow the trace node after with a smooth node and set that node parameter 'Constrained Boundary' to none, the method parameter to 'Curvature Dominant' and then adjust the Strength and Filter parameters, you should be able to get a better working result.
So there is no actual 'smooth edge'(parametric) to trace/duplicate - It's being done algorithmically by the trace node to get as close as possible; To what an actual smooth edge might be.
If your imput geometry was vector based - like an *.igs file format, then you could have a better source to work from.
However, if you adjust the trace nodes step parameter and follow the trace node after with a smooth node and set that node parameter 'Constrained Boundary' to none, the method parameter to 'Curvature Dominant' and then adjust the Strength and Filter parameters, you should be able to get a better working result.
Edited by BabaJ - April 15, 2024 13:03:37
Technical Discussion » Why are there no surface generated from rail node?
- BabaJ
- 2047 posts
- Offline
Houdini Lounge » HOUDINI 20 INSTABILITY
- BabaJ
- 2047 posts
- Offline
alexeyvanzhula1984Never said they didn't.
Many people (including developers when sending RFE) have already confirmed this error
You asked, and I replied I don't.
Houdini Lounge » HOUDINI 20 INSTABILITY
- BabaJ
- 2047 posts
- Offline
alexeyvanzhula1984
1. select face
2. press T
3. Press Sapcebar
4. Press Escape
After this, do you really not see any errors?
No, I don't.
Technical Discussion » How to get rid of new vertices by subtraction Boolean ?
- BabaJ
- 2047 posts
- Offline
Subutai
Almost, the bottom vertices still seem to be present.
That's because of your input geometry.
Try cleaning it up first. You have double prims.
Edited by BabaJ - April 13, 2024 13:02:26
Technical Discussion » How to get rid of new vertices by subtraction Boolean ?
- BabaJ
- 2047 posts
- Offline
Houdini Lounge » HOUDINI 20 INSTABILITY
- BabaJ
- 2047 posts
- Offline
-
- Quick Links