[quote name='DodgeThis1986' post='1091225' date='Jul 21 2010, 08:47 AM']Bump - 7 Days and nothing and Orange Box had an update released yesterday with nothing regarding this :-([/quote]
Yup crosshair was broke in old CSS, when CSS updated to OBE crosshair is still borked.
It may be that the crosshair issue is something Valve must take care of however seeing as how CSS in on the OBE now and TF2 is also on the OBE and has a working 3D crosshair the fix can’t be too complicated.
But all that aside, if you run SLi and don’t want to disable SLi everytime you play CSS don’t get any drivers past the 197. All the drivers after 197.75 I have tried have serious issues in CSS. Flashbangs draw scrolling white bands across the screen. Shadows flicker and scroll much like the flashbangs. Oh, and the new killcam introduced in the update to OBE have what? You guessed it, scrolling translucent bars going up and down the screen but as an added bonus there is a flicker of the image that was taken the last time you saw the killcam.
All those problems, all with SLi, all very similar. And not it isn’t the CSS updates causing it. Before the beta and then the updates nVidia drivers started causing the same issues (minus the kill cam issue) in the old version of CSS which had not received a patch of any sort in ages.
So, while the crosshair may not be a nVidia issue I can’t see how the problems with SLi in CSS are not a nVidia issue. They introduced the glitches with driver updates and surely can take them out with driver updates.
[quote name='DodgeThis1986' post='1091225' date='Jul 21 2010, 08:47 AM']Bump - 7 Days and nothing and Orange Box had an update released yesterday with nothing regarding this :-(
Yup crosshair was broke in old CSS, when CSS updated to OBE crosshair is still borked.
It may be that the crosshair issue is something Valve must take care of however seeing as how CSS in on the OBE now and TF2 is also on the OBE and has a working 3D crosshair the fix can’t be too complicated.
But all that aside, if you run SLi and don’t want to disable SLi everytime you play CSS don’t get any drivers past the 197. All the drivers after 197.75 I have tried have serious issues in CSS. Flashbangs draw scrolling white bands across the screen. Shadows flicker and scroll much like the flashbangs. Oh, and the new killcam introduced in the update to OBE have what? You guessed it, scrolling translucent bars going up and down the screen but as an added bonus there is a flicker of the image that was taken the last time you saw the killcam.
All those problems, all with SLi, all very similar. And not it isn’t the CSS updates causing it. Before the beta and then the updates nVidia drivers started causing the same issues (minus the kill cam issue) in the old version of CSS which had not received a patch of any sort in ages.
So, while the crosshair may not be a nVidia issue I can’t see how the problems with SLi in CSS are not a nVidia issue. They introduced the glitches with driver updates and surely can take them out with driver updates.
[quote name='MistaP' post='1091236' date='Jul 21 2010, 08:14 AM']Yup crosshair was broke in old CSS, when CSS updated to OBE crosshair is still borked.
It may be that the crosshair issue is something Valve must take care of however seeing as how CSS in on the OBE now and TF2 is also on the OBE and has a working 3D crosshair the fix can’t be too complicated.
But all that aside, if you run SLi and don’t want to disable SLi everytime you play CSS don’t get any drivers past the 197. All the drivers after 197.75 I have tried have serious issues in CSS. Flashbangs draw scrolling white bands across the screen. Shadows flicker and scroll much like the flashbangs. Oh, and the new killcam introduced in the update to OBE have what? You guessed it, scrolling translucent bars going up and down the screen but as an added bonus there is a flicker of the image that was taken the last time you saw the killcam.
All those problems, all with SLi, all very similar. And not it isn’t the CSS updates causing it. Before the beta and then the updates nVidia drivers started causing the same issues (minus the kill cam issue) in the old version of CSS which had not received a patch of any sort in ages.
So, while the crosshair may not be a nVidia issue I can’t see how the problems with SLi in CSS are not a nVidia issue. They introduced the glitches with driver updates and surely can take them out with driver updates.[/quote]
[quote name='MistaP' post='1091236' date='Jul 21 2010, 08:14 AM']Yup crosshair was broke in old CSS, when CSS updated to OBE crosshair is still borked.
It may be that the crosshair issue is something Valve must take care of however seeing as how CSS in on the OBE now and TF2 is also on the OBE and has a working 3D crosshair the fix can’t be too complicated.
But all that aside, if you run SLi and don’t want to disable SLi everytime you play CSS don’t get any drivers past the 197. All the drivers after 197.75 I have tried have serious issues in CSS. Flashbangs draw scrolling white bands across the screen. Shadows flicker and scroll much like the flashbangs. Oh, and the new killcam introduced in the update to OBE have what? You guessed it, scrolling translucent bars going up and down the screen but as an added bonus there is a flicker of the image that was taken the last time you saw the killcam.
All those problems, all with SLi, all very similar. And not it isn’t the CSS updates causing it. Before the beta and then the updates nVidia drivers started causing the same issues (minus the kill cam issue) in the old version of CSS which had not received a patch of any sort in ages.
So, while the crosshair may not be a nVidia issue I can’t see how the problems with SLi in CSS are not a nVidia issue. They introduced the glitches with driver updates and surely can take them out with driver updates.
[quote name='MistaP' post='1091236' date='Jul 21 2010, 08:14 AM']Yup crosshair was broke in old CSS, when CSS updated to OBE crosshair is still borked.
It may be that the crosshair issue is something Valve must take care of however seeing as how CSS in on the OBE now and TF2 is also on the OBE and has a working 3D crosshair the fix can’t be too complicated.
But all that aside, if you run SLi and don’t want to disable SLi everytime you play CSS don’t get any drivers past the 197. All the drivers after 197.75 I have tried have serious issues in CSS. Flashbangs draw scrolling white bands across the screen. Shadows flicker and scroll much like the flashbangs. Oh, and the new killcam introduced in the update to OBE have what? You guessed it, scrolling translucent bars going up and down the screen but as an added bonus there is a flicker of the image that was taken the last time you saw the killcam.
All those problems, all with SLi, all very similar. And not it isn’t the CSS updates causing it. Before the beta and then the updates nVidia drivers started causing the same issues (minus the kill cam issue) in the old version of CSS which had not received a patch of any sort in ages.
So, while the crosshair may not be a nVidia issue I can’t see how the problems with SLi in CSS are not a nVidia issue. They introduced the glitches with driver updates and surely can take them out with driver updates.[/quote]
[quote name='MistaP' post='1091236' date='Jul 21 2010, 08:14 AM']Yup crosshair was broke in old CSS, when CSS updated to OBE crosshair is still borked.
It may be that the crosshair issue is something Valve must take care of however seeing as how CSS in on the OBE now and TF2 is also on the OBE and has a working 3D crosshair the fix can’t be too complicated.
But all that aside, if you run SLi and don’t want to disable SLi everytime you play CSS don’t get any drivers past the 197. All the drivers after 197.75 I have tried have serious issues in CSS. Flashbangs draw scrolling white bands across the screen. Shadows flicker and scroll much like the flashbangs. Oh, and the new killcam introduced in the update to OBE have what? You guessed it, scrolling translucent bars going up and down the screen but as an added bonus there is a flicker of the image that was taken the last time you saw the killcam.
All those problems, all with SLi, all very similar. And not it isn’t the CSS updates causing it. Before the beta and then the updates nVidia drivers started causing the same issues (minus the kill cam issue) in the old version of CSS which had not received a patch of any sort in ages.
So, while the crosshair may not be a nVidia issue I can’t see how the problems with SLi in CSS are not a nVidia issue. They introduced the glitches with driver updates and surely can take them out with driver updates.
[quote name='vaelo' date='30 October 2010 - 06:45 PM' timestamp='1288464329' post='1139582']
*BUMP* Is there a fix for this yet? :(
[/quote]
*BUMP*
Any news ?
@Nvidia we need a solution for this !!!!
@Hobby Developer, is there any developer there can create a small tool for this ?
a small programm that creates 2 (stereoscopic) crosshairs (we can use it for all games),
we need to set the distenz from the 2x crosshairs with two shortcuts. (X X)
[quote name='vaelo' date='30 October 2010 - 06:45 PM' timestamp='1288464329' post='1139582']
*BUMP* Is there a fix for this yet? :(
[/quote]
*BUMP*
Any news ?
@Nvidia we need a solution for this !!!!
@Hobby Developer, is there any developer there can create a small tool for this ?
a small programm that creates 2 (stereoscopic) crosshairs (we can use it for all games),
we need to set the distenz from the 2x crosshairs with two shortcuts. (X X)
It's a shame, but [b]realize there's nobody working on it[/b]! I mean it's been over a year since:
[quote name='andrewf@nvidia' date='26 June 2009 - 10:24 PM' timestamp='1246051471' post='558236']
We have been able to reproduce this issue in house.
[/quote]
But it's okay! I mean there's nobody out there playing Counter-Strike or using 64Bit Windows Systems nowadays /doh. So why should someone waste time in fixing senseless crosshair issues? (Yes, I know valve could also do so, but the lasersight issue is not only concerning CS:S and still persistent...)
Ermh, @nvidia for the sake of clarity: --> [b]WE REALLY REALLY NEED THAT FIXED!!![/b] <--
And yes, after all that time I'm really annoyed...
I have to admit that this 3D stuff is really impressive and I always say to myself: Wow, from now on you won't play anything without these glasses! And that's what I thought last year before realizing the driver issues in Vista x64... Meanwhile I use 7 x64 and I have to add: If nobody cares about playability, I really regret the purchase! Guess I'm not alone in thinking this.
Hopefully there will be a few hobby programmers to get that working. Hope dies last.
It's a shame, but realize there's nobody working on it! I mean it's been over a year since:
[quote name='andrewf@nvidia' date='26 June 2009 - 10:24 PM' timestamp='1246051471' post='558236']
We have been able to reproduce this issue in house.
But it's okay! I mean there's nobody out there playing Counter-Strike or using 64Bit Windows Systems nowadays /doh. So why should someone waste time in fixing senseless crosshair issues? (Yes, I know valve could also do so, but the lasersight issue is not only concerning CS:S and still persistent...)
Ermh, @nvidia for the sake of clarity: --> WE REALLY REALLY NEED THAT FIXED!!! <--
And yes, after all that time I'm really annoyed...
I have to admit that this 3D stuff is really impressive and I always say to myself: Wow, from now on you won't play anything without these glasses! And that's what I thought last year before realizing the driver issues in Vista x64... Meanwhile I use 7 x64 and I have to add: If nobody cares about playability, I really regret the purchase! Guess I'm not alone in thinking this.
Hopefully there will be a few hobby programmers to get that working. Hope dies last.
It's a shame, but [b]realize there's nobody working on it[/b]! I mean it's been over a year since:
[quote name='andrewf@nvidia' date='26 June 2009 - 10:24 PM' timestamp='1246051471' post='558236']
We have been able to reproduce this issue in house.
[/quote]
But it's okay! I mean there's nobody out there playing Counter-Strike or using 64Bit Windows Systems nowadays /doh. So why should someone waste time in fixing senseless crosshair issues? (Yes, I know valve could also do so, but the lasersight issue is not only concerning CS:S and still persistent...)
Ermh, @nvidia for the sake of clarity: --> [b]WE REALLY REALLY NEED THAT FIXED!!![/b] <--
And yes, after all that time I'm really annoyed...
I have to admit that this 3D stuff is really impressive and I always say to myself: Wow, from now on you won't play anything without these glasses! And that's what I thought last year before realizing the driver issues in Vista x64... Meanwhile I use 7 x64 and I have to add: If nobody cares about playability, I really regret the purchase! Guess I'm not alone in thinking this.
Hopefully there will be a few hobby programmers to get that working. Hope dies last.
It's a shame, but realize there's nobody working on it! I mean it's been over a year since:
[quote name='andrewf@nvidia' date='26 June 2009 - 10:24 PM' timestamp='1246051471' post='558236']
We have been able to reproduce this issue in house.
But it's okay! I mean there's nobody out there playing Counter-Strike or using 64Bit Windows Systems nowadays /doh. So why should someone waste time in fixing senseless crosshair issues? (Yes, I know valve could also do so, but the lasersight issue is not only concerning CS:S and still persistent...)
Ermh, @nvidia for the sake of clarity: --> WE REALLY REALLY NEED THAT FIXED!!! <--
And yes, after all that time I'm really annoyed...
I have to admit that this 3D stuff is really impressive and I always say to myself: Wow, from now on you won't play anything without these glasses! And that's what I thought last year before realizing the driver issues in Vista x64... Meanwhile I use 7 x64 and I have to add: If nobody cares about playability, I really regret the purchase! Guess I'm not alone in thinking this.
Hopefully there will be a few hobby programmers to get that working. Hope dies last.
Yes, very good point. Who in the heck plays Counter-Strike Source anymore? I mean it's still massively popular and massively supported by Valve. I mean, gosh, who would want that game fixed!
Yes, very good point. Who in the heck plays Counter-Strike Source anymore? I mean it's still massively popular and massively supported by Valve. I mean, gosh, who would want that game fixed!
Yes, very good point. Who in the heck plays Counter-Strike Source anymore? I mean it's still massively popular and massively supported by Valve. I mean, gosh, who would want that game fixed!
Yes, very good point. Who in the heck plays Counter-Strike Source anymore? I mean it's still massively popular and massively supported by Valve. I mean, gosh, who would want that game fixed!
same, crosshair is still 2d for me.
if i turn in-game crosshair off then i don't see any crosshair...
and btw: in "observer mode" crosshair works correctly! looks like counter strike has different type of crosshair which is not fixed wile default half-life crosshair is fixed...
if i turn in-game crosshair off then i don't see any crosshair...
and btw: in "observer mode" crosshair works correctly! looks like counter strike has different type of crosshair which is not fixed wile default half-life crosshair is fixed...
Same issue here. I've had this issue for about a year now and its been highly frustrating, especially when you have to Ctrl+T to turn off 3d vision in order to actually play the game during rounds. Like was said previously, the laser sight does nothing when activated, and with 3d vision, the game is practically unplayable because of the lack of a 3d crosshair.
I just discovered the forums a couple hours ago, I'm surprised this wasn't fixed a year ago, seeing as this is the most played game on Steam.
Same issue here. I've had this issue for about a year now and its been highly frustrating, especially when you have to Ctrl+T to turn off 3d vision in order to actually play the game during rounds. Like was said previously, the laser sight does nothing when activated, and with 3d vision, the game is practically unplayable because of the lack of a 3d crosshair.
I just discovered the forums a couple hours ago, I'm surprised this wasn't fixed a year ago, seeing as this is the most played game on Steam.
Main Rig- 3x 24" Asus GD245Q - 3D Surround ^_^, I7 965 OC 4.2GHZ, ASUS Rampage III, Corsair Dominator 2000MHZ 6GB DDR3, x3 Nvidia GTX 670 ASUS Direct CUII TOP, 2x Intel X25-M SSD RAID 0, X-Fi Titanium, W7 x64, Logtitech Z5500 speakers, 3D Vision
Laptop - 15.4" screen, 2.4GHZ CoreI7, 8GB RAM, 500GB Hybrid SSD, GTX555M, W7 x64
Tablet - Livefan, 64GB SSD, 1.8 Dual Core, 4GM RAM, Windows 8 Pro
PS3, Xbox360, Wii & PSP
Yup crosshair was broke in old CSS, when CSS updated to OBE crosshair is still borked.
It may be that the crosshair issue is something Valve must take care of however seeing as how CSS in on the OBE now and TF2 is also on the OBE and has a working 3D crosshair the fix can’t be too complicated.
But all that aside, if you run SLi and don’t want to disable SLi everytime you play CSS don’t get any drivers past the 197. All the drivers after 197.75 I have tried have serious issues in CSS. Flashbangs draw scrolling white bands across the screen. Shadows flicker and scroll much like the flashbangs. Oh, and the new killcam introduced in the update to OBE have what? You guessed it, scrolling translucent bars going up and down the screen but as an added bonus there is a flicker of the image that was taken the last time you saw the killcam.
All those problems, all with SLi, all very similar. And not it isn’t the CSS updates causing it. Before the beta and then the updates nVidia drivers started causing the same issues (minus the kill cam issue) in the old version of CSS which had not received a patch of any sort in ages.
So, while the crosshair may not be a nVidia issue I can’t see how the problems with SLi in CSS are not a nVidia issue. They introduced the glitches with driver updates and surely can take them out with driver updates.
Yup crosshair was broke in old CSS, when CSS updated to OBE crosshair is still borked.
It may be that the crosshair issue is something Valve must take care of however seeing as how CSS in on the OBE now and TF2 is also on the OBE and has a working 3D crosshair the fix can’t be too complicated.
But all that aside, if you run SLi and don’t want to disable SLi everytime you play CSS don’t get any drivers past the 197. All the drivers after 197.75 I have tried have serious issues in CSS. Flashbangs draw scrolling white bands across the screen. Shadows flicker and scroll much like the flashbangs. Oh, and the new killcam introduced in the update to OBE have what? You guessed it, scrolling translucent bars going up and down the screen but as an added bonus there is a flicker of the image that was taken the last time you saw the killcam.
All those problems, all with SLi, all very similar. And not it isn’t the CSS updates causing it. Before the beta and then the updates nVidia drivers started causing the same issues (minus the kill cam issue) in the old version of CSS which had not received a patch of any sort in ages.
So, while the crosshair may not be a nVidia issue I can’t see how the problems with SLi in CSS are not a nVidia issue. They introduced the glitches with driver updates and surely can take them out with driver updates.
It may be that the crosshair issue is something Valve must take care of however seeing as how CSS in on the OBE now and TF2 is also on the OBE and has a working 3D crosshair the fix can’t be too complicated.
But all that aside, if you run SLi and don’t want to disable SLi everytime you play CSS don’t get any drivers past the 197. All the drivers after 197.75 I have tried have serious issues in CSS. Flashbangs draw scrolling white bands across the screen. Shadows flicker and scroll much like the flashbangs. Oh, and the new killcam introduced in the update to OBE have what? You guessed it, scrolling translucent bars going up and down the screen but as an added bonus there is a flicker of the image that was taken the last time you saw the killcam.
All those problems, all with SLi, all very similar. And not it isn’t the CSS updates causing it. Before the beta and then the updates nVidia drivers started causing the same issues (minus the kill cam issue) in the old version of CSS which had not received a patch of any sort in ages.
So, while the crosshair may not be a nVidia issue I can’t see how the problems with SLi in CSS are not a nVidia issue. They introduced the glitches with driver updates and surely can take them out with driver updates.[/quote]
*BUMP* Is there a fix for this yet? :(
It may be that the crosshair issue is something Valve must take care of however seeing as how CSS in on the OBE now and TF2 is also on the OBE and has a working 3D crosshair the fix can’t be too complicated.
But all that aside, if you run SLi and don’t want to disable SLi everytime you play CSS don’t get any drivers past the 197. All the drivers after 197.75 I have tried have serious issues in CSS. Flashbangs draw scrolling white bands across the screen. Shadows flicker and scroll much like the flashbangs. Oh, and the new killcam introduced in the update to OBE have what? You guessed it, scrolling translucent bars going up and down the screen but as an added bonus there is a flicker of the image that was taken the last time you saw the killcam.
All those problems, all with SLi, all very similar. And not it isn’t the CSS updates causing it. Before the beta and then the updates nVidia drivers started causing the same issues (minus the kill cam issue) in the old version of CSS which had not received a patch of any sort in ages.
So, while the crosshair may not be a nVidia issue I can’t see how the problems with SLi in CSS are not a nVidia issue. They introduced the glitches with driver updates and surely can take them out with driver updates.
*BUMP* Is there a fix for this yet? :(
Core i7 920 @ 3.6Ghz, 6GB 3 Channel, SLi GTX670 2GB, SSD
It may be that the crosshair issue is something Valve must take care of however seeing as how CSS in on the OBE now and TF2 is also on the OBE and has a working 3D crosshair the fix can’t be too complicated.
But all that aside, if you run SLi and don’t want to disable SLi everytime you play CSS don’t get any drivers past the 197. All the drivers after 197.75 I have tried have serious issues in CSS. Flashbangs draw scrolling white bands across the screen. Shadows flicker and scroll much like the flashbangs. Oh, and the new killcam introduced in the update to OBE have what? You guessed it, scrolling translucent bars going up and down the screen but as an added bonus there is a flicker of the image that was taken the last time you saw the killcam.
All those problems, all with SLi, all very similar. And not it isn’t the CSS updates causing it. Before the beta and then the updates nVidia drivers started causing the same issues (minus the kill cam issue) in the old version of CSS which had not received a patch of any sort in ages.
So, while the crosshair may not be a nVidia issue I can’t see how the problems with SLi in CSS are not a nVidia issue. They introduced the glitches with driver updates and surely can take them out with driver updates.[/quote]
*BUMP* Is there a fix for this yet? :(
It may be that the crosshair issue is something Valve must take care of however seeing as how CSS in on the OBE now and TF2 is also on the OBE and has a working 3D crosshair the fix can’t be too complicated.
But all that aside, if you run SLi and don’t want to disable SLi everytime you play CSS don’t get any drivers past the 197. All the drivers after 197.75 I have tried have serious issues in CSS. Flashbangs draw scrolling white bands across the screen. Shadows flicker and scroll much like the flashbangs. Oh, and the new killcam introduced in the update to OBE have what? You guessed it, scrolling translucent bars going up and down the screen but as an added bonus there is a flicker of the image that was taken the last time you saw the killcam.
All those problems, all with SLi, all very similar. And not it isn’t the CSS updates causing it. Before the beta and then the updates nVidia drivers started causing the same issues (minus the kill cam issue) in the old version of CSS which had not received a patch of any sort in ages.
So, while the crosshair may not be a nVidia issue I can’t see how the problems with SLi in CSS are not a nVidia issue. They introduced the glitches with driver updates and surely can take them out with driver updates.
*BUMP* Is there a fix for this yet? :(
Core i7 920 @ 3.6Ghz, 6GB 3 Channel, SLi GTX670 2GB, SSD
*BUMP* Is there a fix for this yet? :(
[/quote]
*BUMP*
Any news ?
@Nvidia we need a solution for this !!!!
@Hobby Developer, is there any developer there can create a small tool for this ?
a small programm that creates 2 (stereoscopic) crosshairs (we can use it for all games),
we need to set the distenz from the 2x crosshairs with two shortcuts. (X X)
Please help.
*BUMP* Is there a fix for this yet? :(
*BUMP*
Any news ?
@Nvidia we need a solution for this !!!!
@Hobby Developer, is there any developer there can create a small tool for this ?
a small programm that creates 2 (stereoscopic) crosshairs (we can use it for all games),
we need to set the distenz from the 2x crosshairs with two shortcuts. (X X)
Please help.
*BUMP* Is there a fix for this yet? :(
[/quote]
*BUMP*
Any news ?
@Nvidia we need a solution for this !!!!
@Hobby Developer, is there any developer there can create a small tool for this ?
a small programm that creates 2 (stereoscopic) crosshairs (we can use it for all games),
we need to set the distenz from the 2x crosshairs with two shortcuts. (X X)
Please help.
*BUMP* Is there a fix for this yet? :(
*BUMP*
Any news ?
@Nvidia we need a solution for this !!!!
@Hobby Developer, is there any developer there can create a small tool for this ?
a small programm that creates 2 (stereoscopic) crosshairs (we can use it for all games),
we need to set the distenz from the 2x crosshairs with two shortcuts. (X X)
Please help.
It's a shame, but [b]realize there's nobody working on it[/b]! I mean it's been over a year since:
[quote name='andrewf@nvidia' date='26 June 2009 - 10:24 PM' timestamp='1246051471' post='558236']
We have been able to reproduce this issue in house.
[/quote]
But it's okay! I mean there's nobody out there playing Counter-Strike or using 64Bit Windows Systems nowadays /doh. So why should someone waste time in fixing senseless crosshair issues? (Yes, I know valve could also do so, but the lasersight issue is not only concerning CS:S and still persistent...)
Ermh, @nvidia for the sake of clarity: --> [b]WE REALLY REALLY NEED THAT FIXED!!![/b] <--
And yes, after all that time I'm really annoyed...
I have to admit that this 3D stuff is really impressive and I always say to myself: Wow, from now on you won't play anything without these glasses! And that's what I thought last year before realizing the driver issues in Vista x64... Meanwhile I use 7 x64 and I have to add: If nobody cares about playability, I really regret the purchase! Guess I'm not alone in thinking this.
Hopefully there will be a few hobby programmers to get that working. Hope dies last.
With this in mind: *BUMP*
It's a shame, but realize there's nobody working on it! I mean it's been over a year since:
[quote name='andrewf@nvidia' date='26 June 2009 - 10:24 PM' timestamp='1246051471' post='558236']
We have been able to reproduce this issue in house.
But it's okay! I mean there's nobody out there playing Counter-Strike or using 64Bit Windows Systems nowadays /doh. So why should someone waste time in fixing senseless crosshair issues? (Yes, I know valve could also do so, but the lasersight issue is not only concerning CS:S and still persistent...)
Ermh, @nvidia for the sake of clarity: --> WE REALLY REALLY NEED THAT FIXED!!! <--
And yes, after all that time I'm really annoyed...
I have to admit that this 3D stuff is really impressive and I always say to myself: Wow, from now on you won't play anything without these glasses! And that's what I thought last year before realizing the driver issues in Vista x64... Meanwhile I use 7 x64 and I have to add: If nobody cares about playability, I really regret the purchase! Guess I'm not alone in thinking this.
Hopefully there will be a few hobby programmers to get that working. Hope dies last.
With this in mind: *BUMP*
It's a shame, but [b]realize there's nobody working on it[/b]! I mean it's been over a year since:
[quote name='andrewf@nvidia' date='26 June 2009 - 10:24 PM' timestamp='1246051471' post='558236']
We have been able to reproduce this issue in house.
[/quote]
But it's okay! I mean there's nobody out there playing Counter-Strike or using 64Bit Windows Systems nowadays /doh. So why should someone waste time in fixing senseless crosshair issues? (Yes, I know valve could also do so, but the lasersight issue is not only concerning CS:S and still persistent...)
Ermh, @nvidia for the sake of clarity: --> [b]WE REALLY REALLY NEED THAT FIXED!!![/b] <--
And yes, after all that time I'm really annoyed...
I have to admit that this 3D stuff is really impressive and I always say to myself: Wow, from now on you won't play anything without these glasses! And that's what I thought last year before realizing the driver issues in Vista x64... Meanwhile I use 7 x64 and I have to add: If nobody cares about playability, I really regret the purchase! Guess I'm not alone in thinking this.
Hopefully there will be a few hobby programmers to get that working. Hope dies last.
With this in mind: *BUMP*
It's a shame, but realize there's nobody working on it! I mean it's been over a year since:
[quote name='andrewf@nvidia' date='26 June 2009 - 10:24 PM' timestamp='1246051471' post='558236']
We have been able to reproduce this issue in house.
But it's okay! I mean there's nobody out there playing Counter-Strike or using 64Bit Windows Systems nowadays /doh. So why should someone waste time in fixing senseless crosshair issues? (Yes, I know valve could also do so, but the lasersight issue is not only concerning CS:S and still persistent...)
Ermh, @nvidia for the sake of clarity: --> WE REALLY REALLY NEED THAT FIXED!!! <--
And yes, after all that time I'm really annoyed...
I have to admit that this 3D stuff is really impressive and I always say to myself: Wow, from now on you won't play anything without these glasses! And that's what I thought last year before realizing the driver issues in Vista x64... Meanwhile I use 7 x64 and I have to add: If nobody cares about playability, I really regret the purchase! Guess I'm not alone in thinking this.
Hopefully there will be a few hobby programmers to get that working. Hope dies last.
With this in mind: *BUMP*
if i turn in-game crosshair off then i don't see any crosshair...
and btw: in "observer mode" crosshair works correctly! looks like counter strike has different type of crosshair which is not fixed wile default half-life crosshair is fixed...
if i turn in-game crosshair off then i don't see any crosshair...
and btw: in "observer mode" crosshair works correctly! looks like counter strike has different type of crosshair which is not fixed wile default half-life crosshair is fixed...
Just posting we are aware of the issue and will investigate a fix for our next major driver release.
Just posting we are aware of the issue and will investigate a fix for our next major driver release.
CPU: i7 2600K @ 5GHz |MOBO: MSI Z68A-GD80 (G3) |RAM: Corsair 16 GB |GPU:2x MSI 980 GTX SLI |HDD: x2 WD Black 1TB Edition |SDD: Intel 60GB setup for Smart Response |PSU: Pro Gold Corsair 850W |SOUND: Creative SB xtreme gamer |CASE: xclio 380a |MONITOR: Acer GD245HQ |OS: Windows 8.1 Pro x64 |ROUTER: ASUS RT-AC68U
I just discovered the forums a couple hours ago, I'm surprised this wasn't fixed a year ago, seeing as this is the most played game on Steam.
I just discovered the forums a couple hours ago, I'm surprised this wasn't fixed a year ago, seeing as this is the most played game on Steam.