#R3 Rendering
5 messages in this thread
I just received Release 3! Thank you very much for speedy delivery and
again thanks for an amazing program.
I haven't had a chance to really explore the new ground, but already
I'm excited by what I see. The Materials editor looks spectacular!
One question, though. I tried rendering a mesh in R3 and thought it
was slow, especially after the promised 30-40% rendering
inprovements. So I tested the mesh in both R2 and R3. I found that
this mesh, rendered in Phong with no anti-aliasing, took 0:45 seconds
in R2, and 0:52 seconds in R3 with the same rendering settings. Plus,
R3 has an extra 10 second screen redraw that I didn't experience in
R2. Obviously, as you add anti-aliasing and shadows, things slow down
further.
I've tried optimizing my system, rendering at 800×600 with 256
colors, but that only gave me a couple seconds. Any ideas? If you
need more info, let me know.
Not a fair test! Compare Phong/High in R2 with Metal/AntiAliasing On
in R3 for a straight comparison, and you'll see where R3 is faster
_and_ higher quality output!
Hello Greg,
Well, you are right. My test was unfair. I rendered the oldcity mesh on R2,
phong and high, and got it in at 2:34. In R3, phong and AA on, it was 1:49.
You're right, I'm sorry. I don't know why I panicked yesterday – I think I
mismatched my settings during the tests. Oops…
One weird thing, though. The screen redraw in R2 is less than 5 seconds, where
as in R3 it's 30-35 seconds. I'm using a Diamond Viper VLB graphics card,
800×600 with 256 colors. In r2 it was set up with RCPADI whereas in R3 it's
setup as a Vibrant compantible board, using the Diamond Viper P9000, or
something. I think that's where my troubles started, because factoring in the
screen redraw, the rendering times are about the same.
Any ideas?…
James
>> The screen redraw in R2 is less than 5 seconds, where as in R3 it's
>> 30-35 seconds. I'm using a Diamond Viper VLB graphics card, 800×600 with
>> 256 colors. In r2 it was set up with RCPADI whereas in R3 it's setup as
>> a Vibrant compantible board…
Something is seriously wrong here! First, check to see that you are
using the same driver on your Vibrant configuration as you did when
using it as an ADI in R2. If there is that much of a difference,
remember, you can still use the R2 driver as an RCPADI for the
display screen if you want, but something else is going on here.
Could R2 have been set up for a 16 color mode and R3 for a 256 color
mode? Again, an unfair test! We have found the VIbrant drivers to
be extremely fast in R3, so I'd look to see that they are set up
correctly.
And once you get them working, just wait until what Vibrant's Liquid
Speed does to them! Talk about fast redraws! Easily double the
speed in the 3D Editor!
As Greg says, something's VERY wrong with your display card setup.
The redraws in R3 are FASTER than those in R2 (once it's configured
correctly). His suggestions are good ones. Time for some system
sleuthing.