ps3 is powerstrip 3.
De radeon is ongeveer net zo snel als de GF2 (16bits langzemer, 32bits gelijk), 2d beeldkwaliteit is beter (vooral hoge res.) DVD playback is top. en de kaart is al voorbereid op DX8 (dus veel hardware ondersteuning voor functies die in directx 8 komen, heeft de geforce familie niet)
De voodoo 5 is beter met FSAA maar dat is dan ook het enigste.<BLOCKQUOTE><font size=1 face=Verdana, Arial, Helvetica>quote:</font><HR>
http://www.rage3d.com/forum/ubbhtml/Forum13/HTML/001083.html
I'm the lead developer for the Radeon's Ark demo. I'm posting this to give some feedback and hints how to make the demo, Radeon's Ark, run better on some systems. First, it's important to note why the demo needs as much memory as it does. Initially, this demo was never intended to be shipped to end users. It was developed as a technology demo for marketing purposes. Given that, we developed this demo to run on a Radeon 64MB board with plenty of ram and swap file space. In addition, the demo was developed in under 3 months, so give us a little slack here. After the warm reception of the demo at the launch, we decided to ship the demo to end users. With the short amount of time I had to make tweaks, we got it running on a 128MB of system ram, but the obvious down side is the amount of memory/swapfile space needed at startup.
So why does it take 1-4 minutes to load the demo? I never spent the engineering time to optimize the load times because this was initially never meant to ship to end users. The two main things that take time at startup are texture compression and memory warming. We shipped all of the textures uncompressed in the scene file for compatibility reasons. A side effect of that is the amount of startup time needed to compress them on the fly. Since windows pages out memory, right before we draw the first frame of the demo, we need to touch all memory used by the demo to force Windows to page things off the disk into memory. The combination of these two steps takes about a minute. We plan to improve this in future demos.
The demo was also never fully tested on other video cards, mainly due to the lack of feature support on other cards. The only cards that even came close to the demo's requirements were the GeForce cards. However, the demo _requires_ the use of 5 user clip planes (specifically for the reflective glass), and since the GeForce doesn't support any user clip planes in D3D, the Radeon was the only card it could run on. Not to mention the lack of EMBM support on all other cards besides the Matrox G400 (which has problems with projective textures used in conjunction with EMBM as is used on all bumpy reflective surfaces in the demo).
Alright, enough babbling...so here are a few command line options that will hopefully improve performance on some systems. You can change the screen res at startup (it defaults to 1024x768), disable sound, and disable the letterbox (this was a last minute change to help performance on slower systems and 32MB cards):
-nosound (May help load times and framerate on some systems)
-640x480
-800x600
-1024x768 (default)
-1152x864
-1280x1024
-1600x1200
-letter (default letterbox mode)
-noletter (will run slower but will get rid of black padding for letterbox)
-loop (Will Loop the demo infinitely from opening to closing credits)
Example: Radeon'sArk.exe -640x480 -nosound
As far as screenshots go, just press the Print Screen button on your keyboard and then paste the contents into PhotoShop or some other image editing program. In the future we'll put in some automated key to spit out an image file of the current frame.
Alex Vlachos
3D Application Research Group, ATI Research
(PLEASE continue this discussion on this message board instead of emailing me directly. It's good to see so much enthusiasm about the Radeon, and it's nice to know forums like this exist.)[/quote]
:strip_icc():strip_exif()/u/7205/duke3.jpg?f=community)
:strip_icc():strip_exif()/u/182/crop66d4984812e9a_cropped.jpg?f=community)
:strip_exif()/u/3749/DukeNukemSmall.gif?f=community)
plus UT crashte vaak als ik van window naar fullscreen switchte (da zuigt tijdens of voor een war!) en m'n Radeon loopt nu stabiel op AGP4x (bij de KX133 liep ie naar een aantal minuten vast). Ok da maakt geen reet uit qua speed maar toch ... T zijn van die kleine dingen maar ik heb ze toch liever niet 
... Enig nadeel is dat m'n keyrate bij RC5 nu gedaald is van 2.82MKeys naar 2.22MKeys maargoed niet alles draait om RC5 (ok voor mij iig hehe). Genoeg off-topic geklets voor vandaag ... strax ff die (halve) Radeon tweaker downen om te kijken of ie bij mij goed werkt ...
.
:strip_icc():strip_exif()/u/5696/crop5ed3a08a378c9_cropped.jpeg?f=community)
:strip_icc():strip_exif()/u/7313/WolfLogo60.jpg?f=community)
...
...
Dit topic is gesloten.