Forum: Bryce


Subject: After QuickTime5 upgrade, Bryce5 won't render animation!

Alleycat169 opened this issue on Jan 24, 2002 ยท 11 posts


Alleycat169 posted Thu, 24 January 2002 at 1:28 PM

Like I said. I had to upgrade to QT5 to view some stupid movie trailer, now Bryce5 won't "render animation". Do I have to pay for a full pro version of QT5 just to be able to render? I tried deleting QT5 and reinstalling QT4 from B5 CD, but with no luck. It just keeps making me upgrade to QT5. When I open the Render Animation window I can configure it and save the .mov file, but when I close it nothing happens, no render begins at all. What can I do to remedy this? Or do I just have to shell out more money to Apple?


tradivoro posted Thu, 24 January 2002 at 2:10 PM

If you have norton utilities, run windoctor.. I'm pretty sure that it's a problem with Direct X... Quicktime and a couple of other things do it... I also have Vue d'Esprit and after I installed the demo of 3ds Max, I couldn't render to file in Vue.. Later on I ran Norton, it fixed whatever Direct X problems adn was able to render to file again in Vue...


Alleycat169 posted Thu, 24 January 2002 at 2:22 PM

windoctor? I'm on a Mac, not a PC. Sorry, I should have made that clear. I will try running Norton Disk Doctor and see if that helps.


Alleycat169 posted Thu, 24 January 2002 at 2:38 PM

I just ran Disk Doctor and it didn't help.


wolf359 posted Thu, 24 January 2002 at 3:51 PM

Do you have any other programs that suddenly wont save a quicktime movie jus curious



My website

YouTube Channel



Alleycat169 posted Thu, 24 January 2002 at 4:02 PM

Wolf359 (hangs head), that was a dark day for The Federation huh? To answer your question I hadn't tried any other apps to see, but I may try some of them now that you mention it. I just installed the B5.1 patch and got the same message when selecting a folder to save the .mov file. It basically says "QuickTime is missing some elements that make it unable to complete this function. Checking the QuickTime Server to see if they are available.". This message came up ONCE, the first time I tried to render animation and it came up ONCE after the update. Unfortunately I was not online when it "searched the Quicktime server" so it said it was unavailable. When I did go online and tried again NOTHING HAPPENED and the dialog never reappears to search the QuickTime server for the missing elements. I'm about ready to do a complete reinstall and update rather than pay Corel (which I own stock in) for one stupid tech support question.


clay posted Thu, 24 January 2002 at 5:03 PM

Try selecting everything in your scene, group it then copy and paste it into a new bryce scene, I've had this happen to me 3 or 4 times in the past, somehow the file gets corrupted, but when I copy and pasted to a fresh file it worked fine.

Do atleast one thing a day that scares the hell outta ya!!


Alleycat169 posted Thu, 24 January 2002 at 5:52 PM

That's not it, but thanks for the reply. Still working with Corel tech support.


Alleycat169 posted Thu, 24 January 2002 at 6:10 PM

Okay, working fine now. Apparently because I did not delete my QuickTime Extension before upgrading from QT 4 to 5, my system kept thinking that there was an older version of the QT application, even though I deleted them all. Turning off all my QuickTime extensions and throwing out the main Quicktime extension, then doing a complete reinstall seemed to help. Even after that Bryce5 said it was still missing a file "QuickTime Authoring" when I tried to render animation. This time I was online when I launched and it quickly downloaded the Authoring file and I was back in business...albeit three hours later. I went ahead and updated to Bryce5.01, now all I have to do is replace all my user palettes that I wisely backed up and everything will be back to normal. Thanks everyone who replied, it's the thought that counts.


wolf359 posted Thu, 24 January 2002 at 7:42 PM

Glad to hear it.



My website

YouTube Channel



tradivoro posted Fri, 25 January 2002 at 12:34 AM

Great to hear you're back up and running...