i am working on making a tornado digital asset
i am trying to reproduce the old technic from voppop from the old pop system,into the new popvop in dop.
But it seems that i am unable to import the point cloud open in the latest
you can check the file
Found 170 posts.
Search results Show results as topic list.
Technical Discussion » issue with popvop in popdop
- sami.tawil
- 172 posts
- Offline
Technical Discussion » issue with deforming static rbd and smoke interaction
- sami.tawil
- 172 posts
- Offline
Technical Discussion » issue with deforming static rbd and smoke interaction
- sami.tawil
- 172 posts
- Offline
for some reason when i use the “use deforming” with an animation at SOP level the smoke doesn't interact anymore with my object.
in the file there are too different method, one using the SOP level animated object(which doesn't work) and another one using OBJ level animation (which works fine)
just go in the smoke DOP and use switch to see the different result
thanks for answering
in the file there are too different method, one using the SOP level animated object(which doesn't work) and another one using OBJ level animation (which works fine)
just go in the smoke DOP and use switch to see the different result
thanks for answering
Houdini Lounge » question about buying houdini and upgrade prices
- sami.tawil
- 172 posts
- Offline
Houdini Lounge » question about buying houdini and upgrade prices
- sami.tawil
- 172 posts
- Offline
hello
i was thinking to get the full houdini 13 package “houdini fx” for my freelance.
i wanted to know if there are plans for upgrades or do we have to buy the new version of the software at full price every years?
thank you for answering
i was thinking to get the full houdini 13 package “houdini fx” for my freelance.
i wanted to know if there are plans for upgrades or do we have to buy the new version of the software at full price every years?
thank you for answering
Houdini Lounge » Help !!! mantra crash exit code -1073741795
- sami.tawil
- 172 posts
- Offline
are you on a laptop?
it seems so from your internal gfx card
i am not sure if houdini plays well with laptop
it seems so from your internal gfx card
i am not sure if houdini plays well with laptop
Technical Discussion » Smoke simulation unstable how to fix?
- sami.tawil
- 172 posts
- Offline
hello,
i started doing my own tornado, i put the high sim yesterday night.
i had a bad surprise checking the sim this morning that seams to work fine for around 400 frames till suddenly it blows up.
i looked around the forums and couldn't find any answer, i tried to add a drag node, and tried on a low res sim but it didn't help.
Does anyone knows how to fix this, is there a way to put a speed limit, or is there another trick
thanks for answering
i started doing my own tornado, i put the high sim yesterday night.
i had a bad surprise checking the sim this morning that seams to work fine for around 400 frames till suddenly it blows up.
i looked around the forums and couldn't find any answer, i tried to add a drag node, and tried on a low res sim but it didn't help.
Does anyone knows how to fix this, is there a way to put a speed limit, or is there another trick
thanks for answering
Houdini Lounge » utah teapot super heavy?
- sami.tawil
- 172 posts
- Offline
Houdini Lounge » utah teapot super heavy?
- sami.tawil
- 172 posts
- Offline
thanks for answering.
But i have a gtx titan and the issue doesn't happen in h12.5
it is actually twice as fast in 12,5
also noticed that moving the node itself is very slow, while moving the context of the node is very fast.
anyway it is just something i noticed , not a big deal,
i was just surprised at the performance
But i have a gtx titan and the issue doesn't happen in h12.5
it is actually twice as fast in 12,5
also noticed that moving the node itself is very slow, while moving the context of the node is very fast.
anyway it is just something i noticed , not a big deal,
i was just surprised at the performance
Houdini Lounge » utah teapot super heavy?
- sami.tawil
- 172 posts
- Offline
I might have expressed myself uncorrectly, i mean that the viewport speed is fine, but moving the pot around the viewport is very slow
Level of detail is set to 1…at any LOD i get the same response
even at 0.1 it is still very slow
anyway i did an FPS check
open scene drop a utah pot and a sphere
when i move the sphere i get 130 FPS
when i move the pot i get 7 FPS
i do nothing except dropping the node.
weird
Level of detail is set to 1…at any LOD i get the same response
even at 0.1 it is still very slow
anyway i did an FPS check
open scene drop a utah pot and a sphere
when i move the sphere i get 130 FPS
when i move the pot i get 7 FPS
i do nothing except dropping the node.
weird
Houdini Lounge » Shader and DA problem shifting to h13
- sami.tawil
- 172 posts
- Offline
Thanks for the corrected file!, i wasn't expecting so much.
goodluck with fixing the bug
cheers
PS: you guys at sidefx are truly amazing, definitely my favorite company.
goodluck with fixing the bug
cheers
PS: you guys at sidefx are truly amazing, definitely my favorite company.
Houdini Lounge » Shader and DA problem shifting to h13
- sami.tawil
- 172 posts
- Offline
it seems the problem comes from the surfacemodel node in the shader
it seems also that new connection are created, and pluged in the wrong input in the surface model
mantra: Unknown parameter: ‘falloff’
mantra: Unknown parameter: ‘diffuseRamp_the_basis_strings’
mantra: Unknown parameter: ‘(’
mantra: Unknown parameter: ‘catmull-rom’
mantra: Unknown parameter: ‘)’
mantra: Unknown parameter: ‘diffuseRamp_the_key_positions’
mantra: Unknown parameter: ‘1’
mantra: Unknown parameter: ‘diffuseRamp_the_key_values’
mantra: Unknown parameter: ‘BaseColorRamp_the_basis_strings’
mantra: Unknown parameter: ‘linear’
mantra: Unknown parameter: ‘BaseColorRamp_the_key_positions’
mantra: Unknown parameter: ‘0.970588207245’
mantra: Unknown parameter: ‘BaseColorRamp_the_key_values’
mantra: Unknown parameter: ‘0.699999988079’
mantra: Unknown parameter: ‘colorMapIntensity_the_basis_strings’
mantra: Unknown parameter: ‘colorMapIntensity_the_key_positions’
mantra: Unknown parameter: ‘colorMapIntensity_the_key_values’
mantra: Unknown parameter: ‘specularIntensity1_the_basis_strings’
mantra: Unknown parameter: ‘specularIntensity1_the_key_positions’
mantra: Unknown parameter: ‘specularIntensity1_the_key_values’
mantra: Unknown parameter: ‘specularColorRamp1_the_basis_strings’
mantra: Unknown parameter: ‘specularColorRamp1_the_key_positions’
mantra: Unknown parameter: ‘0’
mantra: Unknown parameter: ‘specularColorRamp1_the_key_values’
mantra: Unknown parameter: ‘specMapIntensity1_the_basis_strings’
mantra: Unknown parameter: ‘specMapIntensity1_the_key_positions’
mantra: Unknown parameter: ‘specMapIntensity1_the_key_values’
mantra: Unknown parameter: ‘specularIntensity2_the_basis_strings’
mantra: Unknown parameter: ‘specularIntensity2_the_key_positions’
mantra: Unknown parameter: ‘specularIntensity2_the_key_values’
mantra: Unknown parameter: ‘specularColorRamp2_the_basis_strings’
mantra: Unknown parameter: ‘specularColorRamp2_the_key_positions’
mantra: Unknown parameter: ‘specularColorRamp2_the_key_values’
mantra: Unknown parameter: ‘specMapIntensity2_the_basis_strings’
mantra: Unknown parameter: ‘specMapIntensity2_the_key_positions’
mantra: Unknown parameter: ‘specMapIntensity2_the_key_values’
mantra: Unknown parameter: ‘refractionIntensity_the_basis_strings’
mantra: Unknown parameter: ‘refractionIntensity_the_key_positions’
mantra: Unknown parameter: ‘refractionIntensity_the_key_values’
mantra: Unknown parameter: ‘refractioncolor_the_basis_strings’
mantra: Unknown parameter: ‘refractioncolor_the_key_positions’
mantra: Unknown parameter: ‘refractioncolor_the_key_values’
mantra: Unknown parameter: ‘refractionMapIntensity_the_basis_strings’
mantra: Unknown parameter: ‘refractionMapIntensity_the_key_positions’
mantra: Unknown parameter: ‘refractionMapIntensity_the_key_values’
mantra: Unknown parameter: ‘emissionIntensity_the_basis_strings’
mantra: Unknown parameter: ‘emissionIntensity_the_key_positions’
mantra: Unknown parameter: ‘emissionIntensity_the_key_values’
mantra: Unknown parameter: ‘0.5’
mantra: Unknown parameter: ‘emissionColor_the_basis_strings’
mantra: Unknown parameter: ‘emissionColor_the_key_positions’
mantra: Unknown parameter: ‘emissionColor_the_key_values’
mantra: Unknown parameter: ‘0.442000031471’
mantra: Unknown parameter: ‘0.702400028706’
mantra: Unknown parameter: ‘emiddionMapIntensity_the_basis_strings’
mantra: Unknown parameter: ‘emiddionMapIntensity_the_key_positions’
mantra: Unknown parameter: ‘emiddionMapIntensity_the_key_values’
it seems also that new connection are created, and pluged in the wrong input in the surface model
mantra: Unknown parameter: ‘falloff’
mantra: Unknown parameter: ‘diffuseRamp_the_basis_strings’
mantra: Unknown parameter: ‘(’
mantra: Unknown parameter: ‘catmull-rom’
mantra: Unknown parameter: ‘)’
mantra: Unknown parameter: ‘diffuseRamp_the_key_positions’
mantra: Unknown parameter: ‘1’
mantra: Unknown parameter: ‘diffuseRamp_the_key_values’
mantra: Unknown parameter: ‘BaseColorRamp_the_basis_strings’
mantra: Unknown parameter: ‘linear’
mantra: Unknown parameter: ‘BaseColorRamp_the_key_positions’
mantra: Unknown parameter: ‘0.970588207245’
mantra: Unknown parameter: ‘BaseColorRamp_the_key_values’
mantra: Unknown parameter: ‘0.699999988079’
mantra: Unknown parameter: ‘colorMapIntensity_the_basis_strings’
mantra: Unknown parameter: ‘colorMapIntensity_the_key_positions’
mantra: Unknown parameter: ‘colorMapIntensity_the_key_values’
mantra: Unknown parameter: ‘specularIntensity1_the_basis_strings’
mantra: Unknown parameter: ‘specularIntensity1_the_key_positions’
mantra: Unknown parameter: ‘specularIntensity1_the_key_values’
mantra: Unknown parameter: ‘specularColorRamp1_the_basis_strings’
mantra: Unknown parameter: ‘specularColorRamp1_the_key_positions’
mantra: Unknown parameter: ‘0’
mantra: Unknown parameter: ‘specularColorRamp1_the_key_values’
mantra: Unknown parameter: ‘specMapIntensity1_the_basis_strings’
mantra: Unknown parameter: ‘specMapIntensity1_the_key_positions’
mantra: Unknown parameter: ‘specMapIntensity1_the_key_values’
mantra: Unknown parameter: ‘specularIntensity2_the_basis_strings’
mantra: Unknown parameter: ‘specularIntensity2_the_key_positions’
mantra: Unknown parameter: ‘specularIntensity2_the_key_values’
mantra: Unknown parameter: ‘specularColorRamp2_the_basis_strings’
mantra: Unknown parameter: ‘specularColorRamp2_the_key_positions’
mantra: Unknown parameter: ‘specularColorRamp2_the_key_values’
mantra: Unknown parameter: ‘specMapIntensity2_the_basis_strings’
mantra: Unknown parameter: ‘specMapIntensity2_the_key_positions’
mantra: Unknown parameter: ‘specMapIntensity2_the_key_values’
mantra: Unknown parameter: ‘refractionIntensity_the_basis_strings’
mantra: Unknown parameter: ‘refractionIntensity_the_key_positions’
mantra: Unknown parameter: ‘refractionIntensity_the_key_values’
mantra: Unknown parameter: ‘refractioncolor_the_basis_strings’
mantra: Unknown parameter: ‘refractioncolor_the_key_positions’
mantra: Unknown parameter: ‘refractioncolor_the_key_values’
mantra: Unknown parameter: ‘refractionMapIntensity_the_basis_strings’
mantra: Unknown parameter: ‘refractionMapIntensity_the_key_positions’
mantra: Unknown parameter: ‘refractionMapIntensity_the_key_values’
mantra: Unknown parameter: ‘emissionIntensity_the_basis_strings’
mantra: Unknown parameter: ‘emissionIntensity_the_key_positions’
mantra: Unknown parameter: ‘emissionIntensity_the_key_values’
mantra: Unknown parameter: ‘0.5’
mantra: Unknown parameter: ‘emissionColor_the_basis_strings’
mantra: Unknown parameter: ‘emissionColor_the_key_positions’
mantra: Unknown parameter: ‘emissionColor_the_key_values’
mantra: Unknown parameter: ‘0.442000031471’
mantra: Unknown parameter: ‘0.702400028706’
mantra: Unknown parameter: ‘emiddionMapIntensity_the_basis_strings’
mantra: Unknown parameter: ‘emiddionMapIntensity_the_key_positions’
mantra: Unknown parameter: ‘emiddionMapIntensity_the_key_values’
Houdini Lounge » Shader and DA problem shifting to h13
- sami.tawil
- 172 posts
- Offline
hello
i have a D.A uber shader i did which took me a lot of time, and unfortunately it is broken in H13. is there any fix to that?
or i can just restart from scratch?
i have a D.A uber shader i did which took me a lot of time, and unfortunately it is broken in H13. is there any fix to that?
or i can just restart from scratch?
Houdini Lounge » utah teapot super heavy?
- sami.tawil
- 172 posts
- Offline
hey i tried the utah teapot in H13 and for some reason it is very slow to move around the viewport as if it was millions of polygons.
Houdini Lounge » Channel editor bugs out?
- sami.tawil
- 172 posts
- Offline
do you have 2 screens?
sometime having 2 screens bugs houdini
When i use my two screen i am unable to drag and drop.
i have to switch to single screen and restart houdini to fix that issue
sometime having 2 screens bugs houdini
When i use my two screen i am unable to drag and drop.
i have to switch to single screen and restart houdini to fix that issue
Houdini Lounge » GTX titan and horrendous drivers (314 and 320 beta)
- sami.tawil
- 172 posts
- Offline
i will do some test later,
i was working on 320.49, and notice some lag when using the shelf to bring a cube, as well as a lag when shifting shading mode.I do not know if it is related to the GPU tho.
i just reinstalled the 331.65 i will work with it for a while and i will come back to give some results, i am working on some smoke simulation, so i will try opencl to see if i still have crash in H13 as i had in H12.5
As for the 80 m polysphere i still have 12 fps.
I noticed that the openGL frame rate isn't limited to 120 FPS anymore thu.
i was working on 320.49, and notice some lag when using the shelf to bring a cube, as well as a lag when shifting shading mode.I do not know if it is related to the GPU tho.
i just reinstalled the 331.65 i will work with it for a while and i will come back to give some results, i am working on some smoke simulation, so i will try opencl to see if i still have crash in H13 as i had in H12.5
As for the 80 m polysphere i still have 12 fps.
I noticed that the openGL frame rate isn't limited to 120 FPS anymore thu.
Houdini Lounge » GTX titan and horrendous drivers (314 and 320 beta)
- sami.tawil
- 172 posts
- Offline
houdiniWannabesami.tawil
you are welcome twod
aslo i do not have crash using browser(until now)
my 80 m poly sphere was in the background and my pc was running without a glitch while on the houdini forums and a couple of youtube page open.
with drivers 331.58 win 8.1 pro
The browser crash ‘feature’ has been in builds for many months now, including the WHQL (not just beta). Thjs is one reason I've kept my rather old 314.22 drivers installed as I've had zero BSOD's with Win7-64.
You might scan the threads on 331.58 or earlier versions. You may be able to disable this feature by webgl.disabled & noscript.forbidWebGL in Firefox. I forget if this stops the crashes, but … I remember reading about how to disable a feature, so … I'm hoping this is the one.
I'm unsure how to disable in Chrome.
After all this time the Titan has been out, a bit depressing how buggy the drivers are.
i never had BSOD except when i installed the drivers 327, probably luck
Thanks for the tips anyway i ll check it
Houdini Lounge » GTX titan and horrendous drivers (314 and 320 beta)
- sami.tawil
- 172 posts
- Offline
when i use the basic explosion shelf preset on a sphere i get crash
using openCL at 320 max axis, i had the same problem with drivers 320.49 on win7…
what is weird is that it computes very fast and suddenly crash around the frame 20 most of the time
using openCL at 320 max axis, i had the same problem with drivers 320.49 on win7…
what is weird is that it computes very fast and suddenly crash around the frame 20 most of the time
Houdini Lounge » GTX titan and horrendous drivers (314 and 320 beta)
- sami.tawil
- 172 posts
- Offline
you are welcome twod
aslo i do not have crash using browser(until now)
my 80 m poly sphere was in the background and my pc was running without a glitch while on the houdini forums and a couple of youtube page open.
with drivers 331.58 win 8.1 pro
aslo i do not have crash using browser(until now)
my 80 m poly sphere was in the background and my pc was running without a glitch while on the houdini forums and a couple of youtube page open.
with drivers 331.58 win 8.1 pro
Houdini Lounge » GTX titan and horrendous drivers (314 and 320 beta)
- sami.tawil
- 172 posts
- Offline
i dont know why or how but now both drivers 331.58 and 320.49 are at 12 fps
It seems they are both good.
probably a background program was slowing down houdini
so yes 331.58 is as good as 320.49
i tried again with the 331.40 and houdini still doesnt start
here is the 80m poly sphere so you can test your performance on your gpu
It seems they are both good.
probably a background program was slowing down houdini
so yes 331.58 is as good as 320.49
i tried again with the 331.40 and houdini still doesnt start
here is the 80m poly sphere so you can test your performance on your gpu
-
- Quick Links