Help me understand Kyle

sxotty said:
I do not think it is in the best interest of a dev to purposely make a game run bad on any system. This is clearly a shortsighted thing to do, and while a small dev, or a subsidary that can be canned might do it, no respectable real dev would do it b/c in the long run it would piss people off and alienate some portion of their customers.

But who says the Dev is doing it? How many times have we heard now where the IHV has written the shaders for the dev? As hard as this may be to believe, maybe the Dev doesn't even realize the shader that IHV A wrote for them is specifically written so it hinders IHV B's performance. Maybe the Dev wouldn't know because when it's written that way it just evens them out rather than A being way behind.
 
Kyle's latest ill-informed rant left me wondering if he's fallen back in with nV again. Lovely how he's only bothered to ask nV for a comment, and he doesn't seem skeptical of their response at all.

But he's lookin' out for you, the common guy that doesn't like to do [h]ard things like try to anticipate future performance with current benchmarks. No, he's content to give it to ya like it is. Because we all buy new video cards every time a new game is released.

Note how he continually reminds people that FM is in it for the money. And nV isn't?

Hey, I respect the fact that nV doesn't want to waste time with synthetic benchmarks, but only wants to focus on games. I don't respect their then wasting time on cheating in 3DM03. I respect Kyle's decision to ignore 3DM03 in favor of more game benches. I don't respect his continual blaming the victim shtick.

I await his reaction to when nV throws in some optimizations for Max Payne 2. Will he whine that MP2 is an unreliable benchmark? Or will he commend nV for raising performance to levels it should have been at when the game was released?
 
Nar, mainly his rant just shows that when he's annoyed at something he'll STAY annoyed at something, and isn't likely to back down off any stance he took before. Kinda went out of his way to knock at FM, and sniped at nVidia as well. (Of course in going after FM he pretty much had to yield ground to some of the nVidia points, but I don't think it was "going back" to squat--just arming himself with whatever ammo he sees to shoot his target of choice.
 
Whats ironic is that NVIDIA states that this doesn't abuse their optimisations policy because its a they will optimise for games and 3DMark03 is a "benchmark-game" (yes, that came from Derek Perez).

At the start of the year this was a sysnthetic benchmark that wasn't reflective of games, but now they have their optimisation policy evidently its now not a synthetic benchmark but a benchmark game....
 
DaveBaumann said:
Whats ironic is that NVIDIA states that this doesn't abuse their optimisations policy because its a they will optimise for games and 3DMark03 is a "benchmark-game" (yes, that came from Derek Perez).

At the start of the year this was a sysnthetic benchmark that wasn't reflective of games, but now they have their optimisation policy evidently its now not a synthetic benchmark but a benchmark game....

I'm not quite sure it's "ironic" so much as a "slap your head, tear out chunks of hair, reach for the bottle of asprin" situation. :?
 
DaveBaumann said:
Whats ironic is that NVIDIA states that this doesn't abuse their optimisations policy because its a they will optimise for games and 3DMark03 is a "benchmark-game" (yes, that came from Derek Perez).

At the start of the year this was a sysnthetic benchmark that wasn't reflective of games, but now they have their optimisation policy evidently its now not a synthetic benchmark but a benchmark game....
I think I'm with cthellis42 on this one with the "I'm not quite sure it's "ironic" so much as a "slap your head, tear out chunks of hair, reach for the bottle of asprin" situation." attitude, but I'm still pre-coffee so it could just be a wake-up thang. ;)
 
Back
Top