NVIDIA claims top DX9 GPU marketshare spot.

indio said:
The number's quoted are derived from a Mercury Research quarterly report , although they do a good job not referencing it till the middle of the story. That could just be their writing style though.

edit : The numbers quoted by Xbit Labs that is.
WE'RE DISCUSSING SOMETHING BASED ON FIGURES FROM MERCURY RESEARCH AND NO ONE HAS MENTIONED THAT MERCURY RESEARCH IS BASICALLY JUST AN EXTENSION OF NVIDIA'S PR DEPARTMENT?!?!

Sorry, I gotta go have some coffee and bang me head into the wall for a while for even taking this seriously. I was wondering how in the heck nVidia could have possibly maintained their marketshare in light of their recent fiascos and mediocre cards, now I know: PR BS! :mad:
 
DaveBaumann said:
Evildeus said:
Anyway, where can i find the link where it shows that the FX5200 doesn't do FP32 in hardware? (i was in vacation so surely i missed something)

http://www.digit-life.com/articles2/ps-precision/index.html
I asked in hardware you answer with drivers?
Moreover Tridam says
With 44.03, you can't use FP32 but with beta drivers or quadro drivers, this problem doesn't exist. FX5600 and 5200 hardware seem to do FP32 properly.
So, what is what?

Yes, and your statement bears no relation to the figures being talked about here.
Excuse me, but where did i say it was in relation? i just said from the begginnning that from NV perspective that chip sold and shipped is the same think, i never talked from board makers point of view. You are the one talking about board makers and real number of chips sold to consummers....
 
Evildeus said:
DaveBaumann said:
Evildeus said:
Anyway, where can i find the link where it shows that the FX5200 doesn't do FP32 in hardware? (i was in vacation so surely i missed something)

http://www.digit-life.com/articles2/ps-precision/index.html
I asked in hardware you answer with drivers?
Moreover Tridam says
With 44.03, you can't use FP32 but with beta drivers or quadro drivers, this problem doesn't exist. FX5600 and 5200 hardware seem to do FP32 properly.
So, what is what?

Yes, and your statement bears no relation to the figures being talked about here.
Excuse me, but where did i say it was in relation? i just said from the begginnning that from NV perspective that chip sold and shipped is the same think, i never talked from board makers point of view. You are the one talking about board makers and real number of chips sold to consummers....
I'm sorry Evildeus, but you do realize you're defending the point of view of a known bought research company?

Seriously, it's an un-winnable argument and a moot point since it has been pointed out that this article was based on Mercury Research numbers. That's like saying that nVidia dominates the marketplace based on nVidia's personal in-house numbers. :rolleyes:
 
Evildeus said:
I asked in hardware you answer with drivers?

With WHQL driver that do not offer full compliance with the API. There is obviously some reason why why they do not off compliance with the API with their official drivers! :rolleyes:

Excuse me, but where did i say it was in relation?

So what was the point of even mentioning if it bear no relation to the figures being discussed?
 
All analysts are "bought". They don't make any money unless they can sell their products, and they don't make a very good product unless they get cozy to the people they're analyzing.

That being said, however, historical sales data is umpteen times more reliable than technology assessment or sales forcast data.

If Mercury says that these are Q2 numbers, I really don't have too much trouble believing that they're mostly in line with reality. I might question if the numbers reflect world wide sales, but the percentages would probably continue to bear out even if they missed a market like China. (If anything, China would skew the numbers toward the cheap end)
 
Tridam said:
If an IHV says that its new chip is DX9, does Microsoft ensure for compliance? Isn't it a choice of the IHV to presents its products as a DX7, DX8 or DX9 parts with a single constraint: not shock press and people to much??? I've never seen a clear Microsoft's definition of a DXx product.

I think thats part of the point of the introduction of the DCT DX9 tests.

However, there does appear to be some precision issues when running FP32 on NV30/31/34 as witnessed by the PS2.0 procedural texturing test in 3DMark03 (without NVIDIA's replacement shaders). This issue isn't present on NV35.
 
Anyone have access to a LexisNexis database? I'd sure like to find out if Mercury Research has EVER said anything negative about Nvidia.
 
You'll likely find that no independant analyst will ever say anything negative about anybody.

Assuming they get their money from selling their reports, they don't want to alienate anybody.

Assuming they do their reports as part of a stock brokerage firm doing due diligence, they don't want to be sued for defamation of character.
 
RussSchultz said:
All analysts are "bought". They don't make any money unless they can sell their products, and they don't make a very good product unless they get cozy to the people they're analyzing.

That being said, however, historical sales data is umpteen times more reliable than technology assessment or sales forcast data.

If Mercury says that these are Q2 numbers, I really don't have too much trouble believing that they're mostly in line with reality. I might question if the numbers reflect world wide sales, but the percentages would probably continue to bear out even if they missed a market like China. (If anything, China would skew the numbers toward the cheap end)

The question remains. "How does Mercury Research generate the numbers?" I am fairly certain they don't have access to raw data and a lot of the the numbers are generated by speculation and/or interviews with the affected companies PR departments. Do you think they let these ppl. into there accounting departments?
I really don't believe any numbers coming out of Mercury. The process for the evaluations is not transparent. The basis of Mercury Research's value and accuracy is rested on the number of periodicals that quote them :rolleyes:
 
I don't wanna be argumentitive here. I just know that the current state of fair and impartial GFX evalution is pathetic (with the exception of Beyond3D :p ) My personal ax to grind open standards. That is the only way to push the industry forward constructively. I find that fudging up the abilities and limitations of cards (ala GFmx , FX5200+DX9) is hurting 3d graphics progress. When developers program to the lowest common denominator progress slows. When reviewers and analysts influence perception in a way that makes sub-standard products "appear" acceptable we all lose.
 
Evildeus said:
Well sorry, but it's not what you think, or what Nv think, or even god, it's what MS think, that is important. They are or aren't DX9 compliant (labelled by MS), there's no half path. Anything else is irrelevent.

So, OK, then you'd say that a product which supports several DX-version features in software is exactly equal to a product which supports the same features in hardware? Either one can get a "DX-x compliancy" badge from M$. To me, this simply means that comparing products on the basis of DX-version compliancy *as awarded to driver sets by M$* is not the best way to evaluate hardware.

Rather, the best way would be to see which hardware best supports the DX-spec in hardware. Some will be more equal than others in this regard--which has always been the case.

I remember with my 3dfx V5 5.5K that shortly before the company folded it released a "DX8" driver set. Yet, in it were software workarounds for API feature support that, it turned out, didn't work so well in actual DX8 games using some DX8 features....;) Did the fact that this was a WHQL driver set (to my recollection) mean that the V5 was suddenly mutated into a piece of DX8 hardware? No, of course. And that's my point. If I am not mistaken as well, ATi will be releasing (or already has released) drivers for it's 9000 value cards which are "DX9" compliant, when it's well known the card at best supports DX8.1 in hardware. The point I'm trying to make is that getting a DX9-compliant driver set through M$ does little to tell us about the functionality of the hardware.
 
Actually, they generate their numbers by:
-looking at financial statements from the producers
-contacting retail outlets and getting information from them
-talking to suppliers and oems and determing their sales

While it isn't an exact science, there should be enough information to come up with a somewhat reasonable picture, though I know from experience sometimes the analysts get it completely wrong (usually underestimating the market in general)
 
RussSchultz said:
All analysts are "bought". They don't make any money unless they can sell their products, and they don't make a very good product unless they get cozy to the people they're analyzing.

Heh-Heh...;) They also won't get repeat business if they make a habit of telling their clients what they'd rather not hear...;)

I remember 3dfx also employing Mercury to prove various points back in 1999 & 2000 about various things...from benchmarks to sales figures, man, according to Mercury 3dfx was unstoppable...;) (During the period 3dfx retained Mercury for such "studies", of course.) 3dfx got a lot of press-release mileage there.

I call these companies "statistics for hire" and it's an age-old advertising trick. It's like the old ad on TV "3 out of 4 dentists recommend Trident sugarless gum for their patients who chew gum" and you investigate the small print (not included in the TV ad) and find out the "independent study" done as the basis of the ad was done by a company recruited and hired by Trident. In this case I especially like the "for their patients who chew gum" phrase which was added because most dentists recommend people not chew gum at all--especially if they've got braces...;)
 
RussSchultz said:
Ok, demalion. One final try.

I feel a qualified reviewer should know either that it does, or does not have whatever quality he is claiming it has (or has not).


Again, you are proposing "properly" cannot include an evaluation of performance, when it still seems rather abundantly clear to me that that assertion does not make sense.

Alternatively, you seem to be proposing that a reviewer should speak with certainty about performance when he hasn't run tests yet, and that they are incompetent if they do not.

Given your conversation, I picked the first, and I've covered it in detail. Do I have to quote it, or are you capable of understanding where I've explained this before?

Probably shouldn't enter the question, in my opinion.

Yes, I get that it is your opinion, Russ, we've gone over that. Are we finally going to discuss the problems with the way you proposed it?

Even if the quality in question is "the ability to run dx9 games at playable framerates" (which, I'll have to disagree that the construct of the sentence necessarily means that, though yes its possible that it that is what he meant)

This is progress...you're admitting that you were wrong when you said that this was not possible in your first reply. I still think your interpretation is the least reasonable, and I think I've provided ample reasoning as to why. However, by recognizing this you've removed the issue that made your stance completely incompatible with rationality, the english language, etc.. As long as you are consistent in this recognition, I can finally stop discussing the semantics of this point. I'd recommend that you work towards entertatining such possibilities earlier, however.

he should have enough familiarity with the product after reviewing it to know with more certainty than "probably".

Now we are on to logic again. Did you misspeak? "Even if the quality in question is 'the ability to run dx9 games at playable framerates'..he should have enough familiarity with the product after reviewing it to know with more certainty than 'probably'."

But, assuming we take properly to include "at high enough framerate to be acceptable":

Truly, it is a bit murky to know what a DX9 game will require in terms of performance, however In my opinion, any reviewer worth his salt wouldn't come to this conclusion especially after just having run the card through a shootout and demonstrating and concluding that the card does just fine on current games at a lower resolution.

Did you forget that we were discussing things like PS 2.0, Russ? Current games don't use PS 2.0, ergo there is a large logical gap in your proposal that current games show performance of DX 9 games. What conclusion should a reviewer come to after observing performance in games that don't use DX 9 shaders...that it "probably can run DX 9 properly", with properly including consideration of performance? What about observations about performance in PS 2.0 shaders?

Or is the problem not the viewpoint, but uncertainty? Would it have been fine if he'd said "it definitely can't run DX 9 properly", with performance being considered?

Assuming it has the same feature set as its larger brother (which it does), it should accomplish the identical thing on future games.

What!? It doesn't look like you misspoke, but simply believe the PS 2.0 hardware performance characteristics are not unique from other performance characteristics, or that they simply don't matter when...running PS 2.0 shaders. :oops:

Or, are we now to assume that properly means "at a given frame rate at a high enough resolution" so that once again I am "wrong"?

No, we are to assume we are talking about PS 2.0 and that PS 2.0 performance characteristics are a unique aspect of a card.
Consistent application of your "logical support", as far as you've presented, propose one or more possible interpretations that I see:

  • A GF 4 MX runs some current games faster than a 5200. Your logic would have it that the performance in current games indicates that the GF 4 MX would run future games faster, nevermind the differing shader capabilities and performance when implementing effects of the cards. This is the "performance in current games is universal" interpretation.
  • NV3x cards offer 16x AA. Your logic would have it that offering a feature makes it useful to use without regard to performance limitations. This is the "offering the feature is all that matters" interpretation.
  • Doom 3 (as an example) can offer its shadow effects via multipassing. Since many cards can do this, and Doom 3 can offer it, everyone with cards that have to implement shadows in this way will turn it on. This is the "no competent reviewer can express doubt about what a minimum framerate is" interpretation.

Russ, the rest of your post seems to depend entirely on what appear to me to be logical fallacies. Now, if I am wrong in my characterizations, just point out where I went wrong, and propose what you did mean instead, and we can discuss it. If I am not, pick one or more, of your proposals to discuss, and I'll explain further since it seems necessary. :-?

Please try to be somewhat consistent when doing this.

Also, if you think I shouldn't have snipped something, simply point it out.
 
RussSchultz said:
Actually, they generate their numbers by:
-looking at financial statements from the producers
-contacting retail outlets and getting information from them
-talking to suppliers and oems and determing their sales

While it isn't an exact science, there should be enough information to come up with a somewhat reasonable picture, though I know from experience sometimes the analysts get it completely wrong (usually underestimating the market in general)
If there is any room for a fudge-factor in figuring it, I know which way Mercury would fudge it. :devilish:

Again, if the article is based on numbers from Mercury Research it is useless. :)
 
RussSchultz said:
Actually, they generate their numbers by:
-looking at financial statements from the producers
-contacting retail outlets and getting information from them
-talking to suppliers and oems and determing their sales

Russ, do you have anything to base that on? I can't find anything on the Mercury site, and I've had one analyst tell me that this isn't the case with Mercury - he thinks the only one to go to these lengths is JPA.
 
DaveBaumann said:
However, there does appear to be some precision issues when running FP32 on NV30/31/34 as witnessed by the PS2.0 procedural texturing test in 3DMark03 (without NVIDIA's replacement shaders). This issue isn't present on NV35.

I've made some tests with a 'mathematical' shader to highlight the precision and it seems OK. Of course, some instructions could be done with a lower precision.

IE : NV3x are able to do a SINCOS instruction in a cycle only! Microsoft talks about SINCOS as a macro of 8 instructions slots and ATI seems to do it in 6 cycles (co-issue could help to do this in 6 cycles instead of 8 ). Maybe NVIDIA uses a lower precision (-> FX units) to reach a SINCOS per cycle. IIRC, the PS2.0 procedural texturing in 3DMark03 uses SINCOS. But I don't know if the precision issues in this test are related to SINCOS.
 
DaveBaumann said:
Evildeus said:
I asked in hardware you answer with drivers?

With WHQL driver that do not offer full compliance with the API. There is obviously some reason why why they do not off compliance with the API with their official drivers! :rolleyes:
Performance heh? :rolleyes: Or whatever reason... And furthermore they are able to do FP32 with beta drivers aren't they? So, the not being FP32 doesn's count don't you think?

Excuse me, but where did i say it was in relation?

So what was the point of even mentioning if it bear no relation to the figures being discussed?
Perhaps you should reread the 1st post where i say that, you will be able to find an answer ;)

PS: The forum is really slow today, or is it just me having some issues?
 
First off, I NEVER said that performance is not possible to be included in "properly" in his sentence. Unless "safe to assume" means "not possible"? (I guess I should be prepared for the essay on how it means exactly that!?)

Next, yes extrapolating performance IN PS2.0 is possible. The 5900 has a set of performance, the 5600 has a set of performance, the 5200 has a set of performance. They all have the same feature set. The 5200 is some fraction of the 5600 which is some fraction of the 5900. These fractions are pretty consistant across the feature set (in terms of fillrate, pixel shading rate, etc) It would therefor follow that if comparing card A and card b in fillrate leads to the conclusion that B is capable of providing acceptable framerates at lower resolutions, then when considering pixel shading. The only thing that would differ is the resolution at which it reaches parity to your criteria of "properly", unless we now include sufficient resolution in "properly".

And please, stop with the intellectual slights.
 
Back
Top