jvd said:LunchBox said:wasn't the ruby demo made for the R430?
There are 3 ruby demos
ruby 1 ) r420 she steals the brief case with the diamond and then jumps out of the blowing up air platofrm factory thingy
ruby 2) r480 ? the refresh , she is on a motor bike that i believe flys and 2 guys are chasing her
ruby 3 ) recently shown at e3 . Has hdr and other things not in the previous ones this one is for the r520 that should be released soon
Shifty Geezer said:Otherwise it shows the transition to unified shaders won't be transparent which'll make their adoption for PCs kinda tricky.
You sure Dave? I heard they were making the unified shaders out of plexiglass. :|DaveBaumann said:"Unified shaders" or not is transparent for a given environment such as the PC with Windows/DX; what isn't transparent in this case is the entire environment surrounding the unified shaders.
That's what I thought, which is why I said it must probably be CPU limited. If it weren't the port to PPC that dropped the frame-rate from 60 to 30 fps, then it's the GPU. IF that were the case, use of unified shaders isn't transparent. With the case unified shaders SHOULD be transparent, the difference in frame rate between PC+R520 and G5+Xenos wouldn't be so vast, unless Xenos is very underpowered to R520 elsewhere, which I don't believe is the case.DaveBaumann said:Errr, sorry, but WTF?Shifty Geezer said:Otherwise it shows the transition to unified shaders won't be transparent which'll make their adoption for PCs kinda tricky.
"Unified shaders" or not is transparent for a given environment such as the PC with Windows/DX; what isn't transparent in this case is the entire environment surrounding the unified shaders.
Presumably the demo was CPU bound as the conversion was only made in a week from Intel to PPC.