claudio_101
Oct. 13, 2008 06:43:42
Hey,
I'm doeing the tutorial about wedging, but the render doesn't seem to get further then frame 1. Whereas the frame range is configured correctly.
All suggestions are welcome!
Thx,
c.
JColdrick
Oct. 13, 2008 08:15:11
It's your mantra ROP - you have a post script entry that puts a watermark onto your image, and it's apparently failing(under Scripts/Post Frame Scripts). Disable that and it should work. I'm unfamiliar with that myself, but then I'm not a frequent apprentice user, and I've not done the tutorial(which I assume is supposed to work with Apprentice?). You might want to make sure you're running the latest Houdini.
Cheers,
J.C.
P.S. Actually, in retrospect I would imagine that's there to help identify your passes and is part of the tutorial. Either you've made a syntax error or it's non-windows friendly…not sure. Since you'd never in a million years hard-burn text over your precious renders, for the short term you could just do without.
claudio_101
Oct. 13, 2008 08:45:38
Hey JColdrick,
Thx, the addition of the script is asked in the tutorial. Maybe it's because I'm working on a Mac. It would be very nice if the script would work, but it doesn't matter here because it's just an exercise.
JC, one more question. for one resean or the other I can't use the $F variable anymore. If I use it in ex. translate x of any node it gets red and when I MMB click on it, it says: SyntaxError
thx m8
System: MAC OS X 10.5.5, dual quad-core, 10gig RAM, Geforce 8800 GT
Houdini: 9.5.255
edward
Oct. 13, 2008 11:31:16
claudio_101
for one resean or the other I can't use the $F variable anymore. If I use it in ex. translate x of any node it gets red and when I MMB click on it, it says: SyntaxError
It sounds like you have the expression language for your node parameter(s) set to Python. For $F you should be using the hscript expression language. Alternatively, to do $F in python, I think it is
frame().
claudio_101
Oct. 13, 2008 11:50:17
thx Edward, you were right on the spot! :wink:
Allegro
Oct. 14, 2008 11:03:14
It looks like it's because you're using Apprentice.
With Apprentice, even if you name an image $WEDGE.$F3.pic, the actual image that gets saved will be $WEDGE.$F3.picnc
In the Post Frame Script, we are looking at `chs(“vm_picture”)` as the file path for where we will read, and write our image with the script. It looks like it's hiccuping because of the issue of `chs(“vm_picture”)` looking for .pic, while such an image doesn't actually get created.
If you change your Output Picture to $WEDGE.$F3.picnc the post frame script should run without a problem.
claudio_101
Oct. 16, 2008 03:50:22
Hey Allegro, I've tryed what you asked but whit no result.
I attached the necessary file, maybe you can have a look.
System I'm working on is: mac 10.5.5, houdini 9.5.259
Cheers,
C.
Allegro
Oct. 16, 2008 12:05:27
There were a couple of hiccups in your file.
First, in your post frame script, an “s” somehow got snuck into your script just before the -m
Second, Houdini doesn't cooperate particularly well when you have spaces in your paths. In this case you have …/Houdini II/The Wedge Rop/…
If you rename your various folders to use underscores instead of spaces (or simply no spaces) you should no longer have any problems.
claudio_101
Oct. 18, 2008 11:52:58
Hey Allegro, thx m8.
It was like you said, problem is solved now.
Cheers