Ah! Thank you both. I forgot about Mantra materials not compatible with XPU.
Any tip or good tutorial about rendering volumes with Karma XPU?
Thanks
Found 375 posts.
Search results Show results as topic list.
Solaris and Karma » Particles + Volumes : Karma CPU and XPU too different
- Grendizer
- 375 posts
- Offline
Solaris and Karma » Particles + Volumes : Karma CPU and XPU too different
- Grendizer
- 375 posts
- Offline
I get a beautiful render using Karma CPU but with Karma XPu that's a different story. Why are these renders so different? Karma XPU isn't compatible with such elements yet?
SideFX Labs Tech Art Challenge 2021 » WIP - TurnTable Object Node [Houdini Utility]
- Grendizer
- 375 posts
- Offline
Copy the file into the HDA folder of your project. Then go to menu Assets > install asset library > pick the hda file
Technical Discussion » Coordinates rounding?
- Grendizer
- 375 posts
- Offline
Well 2.5 was just an example. Perhaps this happen only on numbers that Aizatulin was telling about : 2.1 2.6 0.1 ...
But I still don't understand why these numbers don't stay the same as I entered. Even if I don't manipulate the handles, 2.1 turns to 2.1000000000000001, which is not the same VALUE.
Same thing with transforms at 0 that turn to microscopic values.
But I still don't understand why these numbers don't stay the same as I entered. Even if I don't manipulate the handles, 2.1 turns to 2.1000000000000001, which is not the same VALUE.
Same thing with transforms at 0 that turn to microscopic values.
Edited by Grendizer - 2022年12月3日 13:08:25
Technical Discussion » Coordinates rounding?
- Grendizer
- 375 posts
- Offline
Hey Aizatulin
Well no, in my case 2.5 is NOT the result of a calculation, it's just values that I type in, on some objects, in the transform tab at the /obj level, or in the base node in the geometry level. At the beginning all is fine and when I type "2.5" I can see "2.5".
Then when I go back to the same node, the value is converted to "2.499999999".
So the problem is not even a rounding problem, 2.499999999 is lower than 2.5, so the real problem is that the value is CHANGED.
The same happens with rotations. Even if I don't rotate an object , when its transform is 0, after a while Houdini keeps putting things like "-1.73472e-18". These values are so small they're equivalent to 0, but why does Houdini replaces "0" by "-1.73472e-18"?
THIS is what I don't understand, and no technical math page will put my mind at ease about this. I still think it's a bug.
Well no, in my case 2.5 is NOT the result of a calculation, it's just values that I type in, on some objects, in the transform tab at the /obj level, or in the base node in the geometry level. At the beginning all is fine and when I type "2.5" I can see "2.5".
Then when I go back to the same node, the value is converted to "2.499999999".
So the problem is not even a rounding problem, 2.499999999 is lower than 2.5, so the real problem is that the value is CHANGED.
The same happens with rotations. Even if I don't rotate an object , when its transform is 0, after a while Houdini keeps putting things like "-1.73472e-18". These values are so small they're equivalent to 0, but why does Houdini replaces "0" by "-1.73472e-18"?
THIS is what I don't understand, and no technical math page will put my mind at ease about this. I still think it's a bug.
Technical Discussion » Mountain to Attribute Noise: time slider?
- Grendizer
- 375 posts
- Offline
Well Ok I understand. But I still think Sidefx should have added a "mountain to attribute noise" guide in the Attribute Noise documentation. They could have explained, for example: in mountain if you put a height of 10, the equivalent is an amplitude of 1.
Mountain is very often used by Houdini users so I think this would have been useful.
Mountain is very often used by Houdini users so I think this would have been useful.
Technical Discussion » Coordinates rounding?
- Grendizer
- 375 posts
- Offline
Thanks Jsmack. I thought this button was to switch between expressions and expressions results , or between data type and value. But this works.
I still don't understand why you say "2.5 doesn't exist" but I'll stop bugging you
I still don't understand why you say "2.5 doesn't exist" but I'll stop bugging you
Technical Discussion » Coordinates rounding?
- Grendizer
- 375 posts
- Offline
Oh come on don't give me this typical Houdini Geek answer. When I type in 2.5 in Photoshop, Word, Candy Crush, ANY APP, I get 2.5, NOT 2.444444449. Why is Houdini not able to correctly round values like any other app???
Technical Discussion » Coordinates rounding?
- Grendizer
- 375 posts
- Offline
Technical Discussion » How can I manipulate a point/edge/primitave in world space?
- Grendizer
- 375 posts
- Offline
Well coming from Softimage too I'm also surprised it's so complicated to set global point positions in Houdini.
Adding some nodes is not at all straight forward, it would be such a slow workflow.
What would be great : being able to edit the geometry spreadsheet values.
Adding some nodes is not at all straight forward, it would be such a slow workflow.
What would be great : being able to edit the geometry spreadsheet values.
Technical Discussion » Coordinates rounding?
- Grendizer
- 375 posts
- Offline
This bug is still here since 2018 and probably before!! Nobody else finds this annoying?
Edited by Grendizer - 2022年12月2日 02:53:43
Technical Discussion » Mountain to Attribute Noise: time slider?
- Grendizer
- 375 posts
- Offline
Ok I was not sure it was the equivalent slider as a "pulse length" slider was already featured in the old Mountain node.
I'm not very satisfied with this node replacement. When I open an old Houdini scene and try to reproduce the mountain node in a new Attribute Noise node, it's not the same settings. In Mountain, my Height slider is set at 2.5. If I put the same value in Attribute noise's "amplitude", the input sphere is not deformed in the same way. So is there a "Mountain to Attribute noise" guide?
I'm not very satisfied with this node replacement. When I open an old Houdini scene and try to reproduce the mountain node in a new Attribute Noise node, it's not the same settings. In Mountain, my Height slider is set at 2.5. If I put the same value in Attribute noise's "amplitude", the input sphere is not deformed in the same way. So is there a "Mountain to Attribute noise" guide?
Technical Discussion » Mountain to Attribute Noise: time slider?
- Grendizer
- 375 posts
- Offline
Hello,
So in Hou 19 the Mountain node was replaced by the Attribute Noise node. OK no problem, but where is the "time" slider in the attribute noise? How can I get something similar?
Thanks in advance
GS
So in Hou 19 the Mountain node was replaced by the Attribute Noise node. OK no problem, but where is the "time" slider in the attribute noise? How can I get something similar?
Thanks in advance
GS
Technical Discussion » Bricker 2.0 VOP node: how to use?
- Grendizer
- 375 posts
- Offline
Well as for me I'd like to get some modelled brick pattern on a wall. Perhaps this VOP node is not useful for that?
Technical Discussion » Bricker 2.0 VOP node: how to use?
- Grendizer
- 375 posts
- Offline
SideFX Labs Tech Art Challenge 2021 » WIP - TurnTable Object Node [Houdini Utility]
- Grendizer
- 375 posts
- Offline
Ok the problem was on my side! This seems to be the cause of the problem: I had renamed the Turntable node to something else. Now that I reverted the name to "TurnTable1", all is fine!
See you soon!!
See you soon!!
SideFX Labs Tech Art Challenge 2021 » WIP - TurnTable Object Node [Houdini Utility]
- Grendizer
- 375 posts
- Offline
Thanks John for this update.
I just had the time to start to test it. Some functions seem broken like : when I connect a camera to the Output of the TurnTable_v_0_13 node, the camera doesn't turn around the scene.
See ya,
Gz
I just had the time to start to test it. Some functions seem broken like : when I connect a camera to the Output of the TurnTable_v_0_13 node, the camera doesn't turn around the scene.
See ya,
Gz
Solaris and Karma » Normal and Height-Bump map
- Grendizer
- 375 posts
- Offline
Technical Discussion » G
- Grendizer
- 375 posts
- Offline
Heyall, in Houdini can I press a key to recall the last action used? Just like "G" in Maya?
Solaris and Karma » Ambiant Occlusion in mtlx standard_surface?
- Grendizer
- 375 posts
- Offline
OK, got it! I'm now using a mtlxrange node instead of the MTLX ramp node. Thanks again Jsmack.
-
- Quick Links