Shake won't render

[Oxide]

I'm running Shake 2.51.1116 and I've built a tree that I want to render. I've rendered 10 different versions to view my WIP, but now when I have done the final tweaks to it, it won't render.
I can't imagine what went wrong..... please advice.

[Oxide]

Here's an update on my problem. I can get Shake to render a single frame of the composite, but when I want it to render a range of frames, it does nothing....

[Oxide]

Yet another update on this weird problem.
I have a 100 frame sequence that I made. Can't render frames 1-100, can't render frames 2-99 but I can render frames 3-98.

[Aruna]

What does your file out node look like? Your image file out should be in the format of:

//Babylon/D/Projects/VFXtalk.Challenges/output2/vfx001.aruna.@.jpg

or something similar. Let me know how that works out.

[Astroboy]

I had a simmilar problem once. And that whas caused by a plug-in that i´ve placed in the wrong directory.

So if you use other plug-ins than the default ones you might want to check that out.

[Oxide]

Well, the file out node is fine, however I'm using 2 plugins.
The funny thing is, the only thing I changed was I put a few more layers and changed the animation of one plugin. Everything had been rendering just fine when all of a sudden those few frames won't render (and the strange part is that they're all supposed to be black as nothing is happening yet). I know I can just add 2 black frames at the begining and the end, but the whole thing strikes me to be a bit strange...

[phiru]

hey..
i just installed shake on ubuntu 7.10 and im having similar probs. My system gets extremely slow when i just run shake and open a sequence. I managed to re render just one frame of my sequence with just a basic set alpha node applied on it and then my whole system crashed.
i have a macbookpro 2.4 ghz dual core processor 2 gb ram with linux loaded on a partitioned drive
is there anything i can do to speed up shake..coz right now it is quite useless
advice deeply appreciated!!!
thank u!

[phyx]

When rendering to Quicktime;

place a 'Crop' node before your 'FileOut'. Quicktime movies will not render properly if the framesize changes.

Also, sometimes we have to change the name of the 'FileOut' movie for Shake to render properly. The same settings in Shake will sometimes only render a 32kb file, or will render the correct 100 Gig file with a different name... very buggy.

This gets frustrating with long renders. We recommend that you check your renders (hide Shake, then 'get info' on the Quicktime File) while they are rendering, to make sure they are actually being rendered properly. If the files stays at 32kb even after several frames have rendered (watch the Shake Flipbook as it renders), it is not rendering properly.