CrazyBomber
Power Member
Catalyst 3.5 -> menos de 5 megas
o q eh q ha nos drivers da nvidia para precisarem de 20 megas??... ah pois eh...
o q eh q ha nos drivers da nvidia para precisarem de 20 megas??... ah pois eh...
Originally posted by Crusher
O Quake3 já foi mais vítima quando a Dell ainda não usava o score do 3D Mark para vender PCs.
A este passo ainda receio que o próximo ainda vai ser o Doom3 ou o HL2.
BTW... ninguém notou por exemplo, que os Detonators em cada lançamento estão a ficar cada vez maiores? Bolas 20Mb por uns drivers contra os 6Mb (se não me engano) dos Catalyst 3.4?
Originally posted by ptzs
Porque são drivers unificadas para uma duzia de chip's diferentes?
Vcs escolhem cada coisa pikuinha pa embirrar...
Actually it was posted on ixbt forum:
http://forum.ixbt.com/0010/044212-30.html
- Detonators have 73-element table of "recognized" applications
- ~50 "recognized" shaders
He simply wrote rivatuner-patch hich will "block" detection routines in the driver.
IMHO just a matter of time to see how 8500 fps in GT4 jumped ahead...
Sergey Dikarev As if you kill I do not see in the branch according to the reference of the references about the quality of antialiasinga given by you.
With the anisotropy you do confuse?Yes even where there about other applications/appendices? All I dig out now driver to the object/subject of detekta of applications/appendices on the name of ekzeshnika.In DED driver 44.03 table of the identified applications/appendices contains altogether only 73(!!!)element
I investigate now in more detail what precisely flags is stored each descriptor.It surrenders to me, that with the anisotrail we obtained precisely first, for which so had long ago been they not fought - is remembered when I it dug up the possibility of the stage-by-stage limitation of the level of anisotropy in DED driver were included the appropriate tuning in RT, many they complained about the fact that they are not too intuitive for the novices and for obtaining the acceptable result necessary to be adjusted slightly under yengine of each toy.
Did throw ideas in the forums apropos of the automatic recognition of application/appendix and limitation of anisotropy at the specific textural stages in the dependence on the specific character of cursor?Most likely precisely this NV it made, although this to still check necessary more precise (in favor of this speaks the fact that the corresponding limitations of anisotropy for the textural stages are blocked for NVekh).Although to make similar in * benchamrke * - the meanness, for similar bargains must be struck. One additional small commentary apropos of the fact that this found the programmers from ATI during disassembling of driver and studying the algorithms of filtration in Detonator'ye.
Lie this is hundred per-cent.First, physically it cannot be on the code of driver said for what precisely applications/appendices it is sharpened.During the creation of context the driver calculates the 128- bit check sum (64 bits for the check sum of the name of ekzeshnika + of 64 bits for the check sum on the names of all windows of the current process).
Yes even very code of the calculation of check sum occupies several soten(!!!)lines (it is clear in order to hinder disassembling).Roughly speaking from the check sum to obtain the name of ekzeshnika * impossibly *. they would see they this code - they would raise much more to noise apropos of other applications/appendices.So that most likely in ATI by the analysis of algorithms and study of grooves is implied the trivial renaming of all applications/appendices specialists
Originally posted by Strakata
Eu até estava a pensar em me partir todo a rir, mas pronto, fica para outra altura.
E daí.....