Valve is a liar. Cheating on Halflife2
- Thread starter engall
- Start date
engall, read this if my post didn't make things clear: ATI & Valve - Defining the Relationship.
engall you need to stop taking things as a word-for-word literal meaning. What was meant was that the game had not been optimized to give any company an advantage over the other(s). the nv3x codepath does not give nvidia cards an advantage over other cards. You could actually look at including a standard DX9 codepath as an ATi specific optimization because it's very well known that nVidia hardware is crippled by using DX9 and ATi benefits from it. Optimization is a relative thing- you could say that they optimized for both ATi and nVidia by including the DX9 and mixed nv3x paths but not including an advanced path tailored to the Matrox Parhelia (which would be VS2.0 and PS1.4(?)).
engall you are not asking a question or trying to understand anything here; you are making a statement. If you wanted to ask a question then you should be open to accepting an answer which everyone except you proposes as correct. You appear to me to be nothing but a troll attempting to incite anger towards Valve, but it's not going to work because people are far from dumb enough to fall for such FUD.
engall you are not asking a question or trying to understand anything here; you are making a statement. If you wanted to ask a question then you should be open to accepting an answer which everyone except you proposes as correct. You appear to me to be nothing but a troll attempting to incite anger towards Valve, but it's not going to work because people are far from dumb enough to fall for such FUD.
Frankly I detected a lot of tongue-in-cheek and ironic sarcasm from the first post, and then some leg-pullings later on when people started jumping on him. Now it just seems like engall's goading people on because it amuses him.
Have we learned NOTHING from W.O.P.R.? The only way to win is not to play.
Have we learned NOTHING from W.O.P.R.? The only way to win is not to play.
Joe DeFuria
Legend
cthellis42 said:Have we learned NOTHING from W.O.P.R.? The only way to win is not to play.
How about a nice game of Chess?
Engall is simply right, there is little point but the hilarity of Valves juxtaposition in statement is quite good.
edit:
BTW a further example of what could be considered misleading/lying is this
it took 5x the time to optimize it for the nv3x series as the r3xx series. Which implies they optimized it for the r3xx series as well. Otherwise they are saying that the engine was written in 1/5 the time as the optimizations for the nv3x took which I doubt since that means they have been optimizing for nv3x for the last 3 years or so.
edit:
BTW a further example of what could be considered misleading/lying is this
it took 5x the time to optimize it for the nv3x series as the r3xx series. Which implies they optimized it for the r3xx series as well. Otherwise they are saying that the engine was written in 1/5 the time as the optimizations for the nv3x took which I doubt since that means they have been optimizing for nv3x for the last 3 years or so.
I did read the quote however since the r3xx is the generic dx9 then optimizing it = optimizing the r3xx path since it is the r3xx path, names are irrelevant. I just found it funny. One could call the nv35 mixed mode and optimization on the dx9 path too, but since the r3x doesn't use it it is called the nv3x optimized path. Similarly since the nv3x doesn't use the dx9 path and only the r3x does.. anyway I assume you are smart enough to grasp what I am saying w/o further elaborations.
Of course the refutation is that the NV3x can run the dx9 path but the r3x cannot run the nv3x path and therefore the r3x path is truly generic and so forth, whereas the nv3x path is specific.
I will only say to this that is a vendor uses dx9 functionality which favors one card (which all of it will since nv3x sucks), and writes the regular path and optimizes it for the r3x then it might as well be called the r3x path and not the dx9 path but names are reletively meaningless.
Of course the refutation is that the NV3x can run the dx9 path but the r3x cannot run the nv3x path and therefore the r3x path is truly generic and so forth, whereas the nv3x path is specific.
I will only say to this that is a vendor uses dx9 functionality which favors one card (which all of it will since nv3x sucks), and writes the regular path and optimizes it for the r3x then it might as well be called the r3x path and not the dx9 path but names are reletively meaningless.
Which part of "generic dx9 path" is so hard to understand? I don't know if there are any other DX9 cards coming out in the near future, but if there are you can safely bet that they'll be using the generic path just like ATI... Valve are unlikely to be doing optimizations for other manufacturers.
The generic path also, of course, runs perfectly happily on a Geforce FX... it's just dog slow because it's not a 'generic' board.
It still is possible that the generic DX9 path was written using both the NV3x and the R3xx as development platforms, or (at the very least) test systems. In that case, it is optimized to perform as best as possible at full precisions on both. Since this wasn't enough for the NV3x, though. . .
The juxtaposition is only there because they didn't go over every statement with a fine-toothed comb to search for literal discrepencies. Their tone was there and all their information was plain to see, so what-the-fuckever.
Chris123234
Regular
Maybe he's trying to point out that Valve said they did not optimize. And that if the NV3X had raised the performance to that of the R3XX levels then valve may have kept quiet about it and not announced it.
But probably not.
But probably not.
Similar threads
- Locked