CompuServe Messages

Our Raptor at work has never choked on a lengthy "Amiga-style" filename. It'll choke on other things, though, like poorly modeled objects. I've noticed LW 3.2 rendering differently than 3.1, in that certain objects with flaws will render OK in 3.1, but not in 3.2. The best thing to do is model cleanly. Also, when the Raptor is just sitting, blinking "ready" in the middle of a render, it is actually working and has not choked. Your turning-off, turning-on idea sounds dangerous and harmful to the computer and its hardrives. Do you do this all the time? Have you ever thought the Raptor was hung up, pressed ESC, popped back into Lightwave, only to see that the machine decided right then to "say" that it was working on the next frame? And, of course, it won't save that frame, and it won't escape out until it has finished its work on that frame. Frustrating, isn't it? However, I have found that letting the Raptor do its thing is the best solution. It's like a pot of water, no use waiting and watching…it'll boil eventually.