Originally posted by: Sonikku
It reminds me of the time Half Life 2 suspiciously ran poorly on Nvidia hardware at release when compared to ATI, only to see the gap narrow considerably when Nvidia fans found work arounds to Valve's engine. It seems this time around Nvidia has done something similar. It's things like this that really make me hate the PC industry. -_-
On Vista it does nothing unless you run the game under the DX9 path.What happens when you enable AA in the drivers?
I want screenshot and benchmark evidence of their claims. If FP16 really looked identical then Valve would've never bothered implementing a mixed mode path for FX cards, something that took them a very long time to do.http://shenmue.planets.gamespy...2703&highlight=#552703
Originally posted by: 40sTheme
You guys have put -dx9 in the shortcut command line for Bioshock, right?
Oh, and on nV cards, you have to rename it R6Vegas_Game.exe.
Originally posted by: 5t3v0
Originally posted by: 40sTheme
You guys have put -dx9 in the shortcut command line for Bioshock, right?
Oh, and on nV cards, you have to rename it R6Vegas_Game.exe.
Does this work? I've decided against buying the game, certainly at full price, because of the lack of FSAA on Vista.
Originally posted by: n7
Originally posted by: 5t3v0
Originally posted by: 40sTheme
You guys have put -dx9 in the shortcut command line for Bioshock, right?
Oh, and on nV cards, you have to rename it R6Vegas_Game.exe.
Does this work? I've decided against buying the game, certainly at full price, because of the lack of FSAA on Vista.
For me, that didn't work, & it caused a BSOD when exitting the game.
So no more renaming or DX9 forcing for me, as i'd much rather play a game with jaggies than crash.