For the record I must have turned on the ‘Generate Script file’ button.
The tutorial matches a default scene.
-my bad.
ral
Found 38 posts.
Search results Show results as topic list.
Technical Discussion » Render a sequence with mantra problems
- ral
- 49 posts
- Offline
Technical Discussion » Render a sequence with mantra problems
- ral
- 49 posts
- Offline
Beuty-I forgot about that MMB. Thats such a nice tool.
It all came down to the same thing-the script output flags indeed were on.
I'll have to check and see if thats me or if the tutorial scene provided comes with those checked on (if so maybe the scene should be resaved
with them off?!).
-many thanks craig!
ral
It all came down to the same thing-the script output flags indeed were on.
I'll have to check and see if thats me or if the tutorial scene provided comes with those checked on (if so maybe the scene should be resaved
with them off?!).
-many thanks craig!
ral
Technical Discussion » Render a sequence with mantra problems
- ral
- 49 posts
- Offline
I just finished the new rocket tutorial (from the web) and was gonna render it. But mantra is giving me heck. :?
Rendering from the Output level
-I get a red arrow on the Mantra1 node even though my output path is legit. So what else could be wrong?
-The tutorial has me set my Render Command (Variance, Bucket size and Verbose). But why now can I not edit the Render Command again?
Its grey and I cannot access the + anymore for edits.
-I at one point was able to edit the Render Command (not sure how) and I made it a 2 processor render and removed remote host (since its a local render). It seems like a render was attempted but it seem to crash with every frame started by each processor (I had to kill everything houdini from thre windows task manager). On disk there are files in name only
so mantra named the file and then crashed.
So maybe I'm being stupid-but whats up?
-ral (newbie)
Rendering from the Output level
-I get a red arrow on the Mantra1 node even though my output path is legit. So what else could be wrong?
-The tutorial has me set my Render Command (Variance, Bucket size and Verbose). But why now can I not edit the Render Command again?
Its grey and I cannot access the + anymore for edits.
-I at one point was able to edit the Render Command (not sure how) and I made it a 2 processor render and removed remote host (since its a local render). It seems like a render was attempted but it seem to crash with every frame started by each processor (I had to kill everything houdini from thre windows task manager). On disk there are files in name only
so mantra named the file and then crashed.
So maybe I'm being stupid-but whats up?
-ral (newbie)
Technical Discussion » Odd ballooning effect when Cloth and RBD solvers merged
- ral
- 49 posts
- Offline
I think I've got it sorted. It appears to be related to the connection order.
-still if there is any thoughts as to ‘why’ this is the case I am happy to hear 'em.
-ral
-still if there is any thoughts as to ‘why’ this is the case I am happy to hear 'em.
-ral
Technical Discussion » Odd ballooning effect when Cloth and RBD solvers merged
- ral
- 49 posts
- Offline
I was messing about with a finished version of Dynamics Quickstart
tutorial (table cloth, vase, ball). All works fine except for an odd ‘ballooning’ effect that looks like the table top is ‘swelling’ out through the cloth. Yet I don't think its really the table top-its almost like a foreign piece of geometry is present. :?
It seems to come from the Merging of the RBD system (the ball) and the Cloth Solver. If I bypass the merge and connect each solver by itself to the Gravity node then the results are as expected. There isn't a lot of options with Merge so I'm not sure if there is a way around it.
Any idea whats going on? and if there is a better way to link the two
(besides keeping them seperate?)
-thanks
ral
tutorial (table cloth, vase, ball). All works fine except for an odd ‘ballooning’ effect that looks like the table top is ‘swelling’ out through the cloth. Yet I don't think its really the table top-its almost like a foreign piece of geometry is present. :?
It seems to come from the Merging of the RBD system (the ball) and the Cloth Solver. If I bypass the merge and connect each solver by itself to the Gravity node then the results are as expected. There isn't a lot of options with Merge so I'm not sure if there is a way around it.
Any idea whats going on? and if there is a better way to link the two
(besides keeping them seperate?)
-thanks
ral
Technical Discussion » Keyboard disconnects during Houdini sessions?
- ral
- 49 posts
- Offline
Yup Windows. I'll try that memory test-good one.
I haven't scene XSI do this particular thing-the only thing in common is
that its ‘suddenly strange unexpected behavior that rights itself when the application is restarted’. I've used XSI the most but I'll occasionaly see something like this in Max or Maya as well.
-ral
I haven't scene XSI do this particular thing-the only thing in common is
that its ‘suddenly strange unexpected behavior that rights itself when the application is restarted’. I've used XSI the most but I'll occasionaly see something like this in Max or Maya as well.
-ral
Technical Discussion » Keyboard disconnects during Houdini sessions?
- ral
- 49 posts
- Offline
In XSI I would have called this a memory corruption. As it fixes itself if its restarted.
I've found in both Houdini 8 and 8.1 I will get a situation -after working on a scene for awhile- that suddenly my keyboard input is ‘blocked’-yet mouse input still works. But I can't do much more with the scene except save it. If I go outside Houdini the keyboard is indeed working.
If I restart Houdini and load that scene again everything is back to normal and I can continue to work.
Graphics is a Quadro FX 500/600. Is there anything I could have set on the graphics card or in Houdini itself that would account for this?
It can happen 5-10 times a day if I am working all day…
-ral
I've found in both Houdini 8 and 8.1 I will get a situation -after working on a scene for awhile- that suddenly my keyboard input is ‘blocked’-yet mouse input still works. But I can't do much more with the scene except save it. If I go outside Houdini the keyboard is indeed working.
If I restart Houdini and load that scene again everything is back to normal and I can continue to work.
Graphics is a Quadro FX 500/600. Is there anything I could have set on the graphics card or in Houdini itself that would account for this?
It can happen 5-10 times a day if I am working all day…
-ral
Technical Discussion » Read an Image Sequence for a VEX layered surface
- ral
- 49 posts
- Offline
Today we are cooking with gas-but I'm scratching my head too. Now both these work.
smoke_seq_01.`padzero(3,$F)`.pic
smoke_seq_01.$F3.pic
I am pretty sure I was at the correct frame when having trouble
and I am pretty sure extra spaces weren't a factor either. But
since computers are never wrong I'll assume I was a door knob anyway.
chalk it up to newbieness.
Thanks everyone!
ral
smoke_seq_01.`padzero(3,$F)`.pic
smoke_seq_01.$F3.pic
I am pretty sure I was at the correct frame when having trouble
and I am pretty sure extra spaces weren't a factor either. But
since computers are never wrong I'll assume I was a door knob anyway.
chalk it up to newbieness.
Thanks everyone!
ral
Technical Discussion » Read an Image Sequence for a VEX layered surface
- ral
- 49 posts
- Offline
For the record CHOPS load these ‘funky’ image sequences just fine.
In fact -in a more user friendly way- this browser anticipates these as sequences and uses the approriate expression for each automatically.
So it seems to point to a bug Texture Map in VEX Layered surface and its browser.
Frankly a single standard browser that handles both scenarios everywhere image files can load would seem to be my order of the day.
Why do we want slightly different browsers-one more limited for this exercise than another in different parts of the software?
-ral
In fact -in a more user friendly way- this browser anticipates these as sequences and uses the approriate expression for each automatically.
So it seems to point to a bug Texture Map in VEX Layered surface and its browser.
Frankly a single standard browser that handles both scenarios everywhere image files can load would seem to be my order of the day.
Why do we want slightly different browsers-one more limited for this exercise than another in different parts of the software?
-ral
Technical Discussion » Read an Image Sequence for a VEX layered surface
- ral
- 49 posts
- Offline
Each of these sequences is in its own folder-but all the folders are at the same location on our content server. So I browse up a folder and down into the next one and select the first image in the list. Then -depending on padding- i swap the frame number
for $F.
like so
smoke_seq_01.001.pic
becomes
smoke_seq_01.$F3.pic
When I do load a sequence that works I see the change straight away in SHOPS . Otherwise all I see is the Shader Surface (when it fails).
And its always the same sequences that fail too-not like a random refresh issue. And for the record-the bad texture link isn't rendering either.
BTW all the folders at this location have underscores in the names (not spaces) so thats not the issue either.
-thanks for the ideas-but its still a mystery.
-ral
for $F.
like so
smoke_seq_01.001.pic
becomes
smoke_seq_01.$F3.pic
When I do load a sequence that works I see the change straight away in SHOPS . Otherwise all I see is the Shader Surface (when it fails).
And its always the same sequences that fail too-not like a random refresh issue. And for the record-the bad texture link isn't rendering either.
BTW all the folders at this location have underscores in the names (not spaces) so thats not the issue either.
-thanks for the ideas-but its still a mystery.
-ral
Technical Discussion » Read an Image Sequence for a VEX layered surface
- ral
- 49 posts
- Offline
Thanks J.C.
Could it be a problem on Windows only?
I've just now tried my problematic sequences in build 625 (windows)
and I seem to have the same behavior still.
Should i mail a link to this issue on the 8.1 forum?
-ral
Could it be a problem on Windows only?
I've just now tried my problematic sequences in build 625 (windows)
and I seem to have the same behavior still.
Should i mail a link to this issue on the 8.1 forum?
-ral
Technical Discussion » Read an Image Sequence for a VEX layered surface
- ral
- 49 posts
- Offline
Yup mines older-and on windows (XP) as well-8.0.474.
I was thinking it was because i had an unmounted drive on the network.
But thats not the case.
More info-I guess i have a bug (in 474).
Different sequences seem to be ok-while others are broken-from here it seems to be related to if the sequence name itself -like Houdini perceives two types of padding in the same file name?
i.e. smoke_seq_01.001.pic
fails-as does
fire_anim_burst3B.0001.pic
but
Flames_Sprites_00001.pic
anim_smoke5.1.pic
Are just fine.
-so you think its fixed in a newer build then?
-ral
I was thinking it was because i had an unmounted drive on the network.
But thats not the case.
More info-I guess i have a bug (in 474).
Different sequences seem to be ok-while others are broken-from here it seems to be related to if the sequence name itself -like Houdini perceives two types of padding in the same file name?
i.e. smoke_seq_01.001.pic
fails-as does
fire_anim_burst3B.0001.pic
but
Flames_Sprites_00001.pic
anim_smoke5.1.pic
Are just fine.
-so you think its fixed in a newer build then?
-ral
Technical Discussion » Read an Image Sequence for a VEX layered surface
- ral
- 49 posts
- Offline
Hmm-Thanks Craig.
But that didn't seem to work either.
Any other ideas besides renameing the sequence?
-ral
But that didn't seem to work either.
Any other ideas besides renameing the sequence?
-ral
Technical Discussion » Read an Image Sequence for a VEX layered surface
- ral
- 49 posts
- Offline
Hmm-found some oddness with one sequence though.
Two sequences-both sequences load as single images too so its not corrupted.
anim_smoke5.1.pic works fine as anim_smoke5.$F.pic
-But
smoke_seq_01.001.pic fails with smoke_seq_01.$F3.pic
-am i still being a knob?
:?: -ral
Two sequences-both sequences load as single images too so its not corrupted.
anim_smoke5.1.pic works fine as anim_smoke5.$F.pic
-But
smoke_seq_01.001.pic fails with smoke_seq_01.$F3.pic
-am i still being a knob?
:?: -ral
Technical Discussion » Read an Image Sequence for a VEX layered surface
- ral
- 49 posts
- Offline
Technical Discussion » Read an Image Sequence for a VEX layered surface
- ral
- 49 posts
- Offline
Maybe I'm being a doorknob-but I couldn't quite find the right solution in my searches here. I'd simply like to use an Image Sequence instead of a single image in my shopnet which uses a VEX layered surface.
So just have Texture Map load entire sequence instead of a single file.
Most softwares make this trivial with a flag in the browser.
I thought maybe if I load the first frame Houdini would read them all-but I don't think it is.
-maybe there is a more Houdiniesc way to do this…
-ral
So just have Texture Map load entire sequence instead of a single file.
Most softwares make this trivial with a flag in the browser.
I thought maybe if I load the first frame Houdini would read them all-but I don't think it is.
-maybe there is a more Houdiniesc way to do this…
-ral
Technical Discussion » Wispy smoke tutorial
- ral
- 49 posts
- Offline
Indeed thanks Ondrej.
I was looking for a way to indentify the ports-I guess i just didn't baloon tip the correct hotspot.
-ral
I was looking for a way to indentify the ports-I guess i just didn't baloon tip the correct hotspot.
-ral
Technical Discussion » Wispy smoke tutorial
- ral
- 49 posts
- Offline
I'm taking a few days to look at houdini for the first time.
I'm making my way through the totorials-in particular ‘wispy smoke’.
In Part 3 after Step 6.
I do not see the result I expect which is a few metaballs being driven
by particles (created at step 1). All the other steps seem to work fine till this point.
“Copy metaball to points
In the Viewer pane press tab > Copy and RMB-click twice to accept. Wire the output of the delete1 sop into the Template input of the Copy sop. Playback the results.”
They mean connect the ‘delete1’ output into the left side input port of the ‘Copy’ node correct? I do this but the metaballs don't move.
Ive repeated Part 3 several times now and i don't think i have whats expected (upon playback).
Is there anything obvious i am missing?
Maybe its some obscure display I've missed (thats easy to do)?
-thanks
ral
I'm making my way through the totorials-in particular ‘wispy smoke’.
In Part 3 after Step 6.
I do not see the result I expect which is a few metaballs being driven
by particles (created at step 1). All the other steps seem to work fine till this point.
“Copy metaball to points
In the Viewer pane press tab > Copy and RMB-click twice to accept. Wire the output of the delete1 sop into the Template input of the Copy sop. Playback the results.”
They mean connect the ‘delete1’ output into the left side input port of the ‘Copy’ node correct? I do this but the metaballs don't move.
Ive repeated Part 3 several times now and i don't think i have whats expected (upon playback).
Is there anything obvious i am missing?
Maybe its some obscure display I've missed (thats easy to do)?
-thanks
ral
-
- Quick Links