Forum: Bryce


Subject: More on Bryce5 render times - probable platform differences.

PJF opened this issue on Jul 18, 2001 ยท 42 posts


Man O' War posted Wed, 18 July 2001 at 9:08 PM

So you guys/gals think that there's a Corel conspiracy to screw over approximately 95% of its user base to favor the 3% Mac population. Make's a lot of sense doesn't it. There's "mucho" anger on this list and probably most of it's warranted, but come on. Corel may have done some things wrong, but so did Metacreations. Remember 2.0 on the PC? Were I to reply in the same vein I might bitch and moan about the multiple(!) programs allowing Poser animation imports into PC Bryce or the statement by the Mimic developers that PC users utilize Poser as an animation tool and Mac users utilize it solely for illustration purposes (bullshit), thus no Mac port. Hey, all the more reason to save up my coins for a 1.7G pentium:) Let's not turn the failings or benefits of Bryce5 into a platform war. Face it, both PC or Mac, Bryce rendering times were unworkable. Now with the process's new features, they've gone through the roof. Who in their right mind is going to wait hours for one NTSC frame, never mind 30 frames/sec or even worse 60 interlaced fields per second. Imagine further going to high AA to get rid of the everpresent sparkling! Multiple machine rendering isn't going to cut it either, as most users are limited to one or two machines. Additionally, it's a false argument that somehow all this is made better by having a "true ray tracing" engine. Everyone has their favorite engine and we can argue about the quality of each program's product, but Bryce's is hardly the end all in this respect. IMHO one major mistake with Bryce from the beginning was the absence of a Treelab. (As if landscapes were somehow divorced from trees. ) This has been fixed to a degree (no grass). The remaining major mistake is not having a rendering engine equal to the other components of the program. Maybe this will be addressed in the next upgrade, but I doubt it. manowar (This should keep us busy for the next day or so:)