hehe just got my 7900gtx ,pics inside! FIXED PICTURES

[kingdomwinds]

which is faster in bf2?

 

[Jules]

Originally posted by: akugami

Originally posted by: MyStupidMouthTrue but got tired of the crappy shadows in bf2 and the crappy control panel. glad i came back to nvidia since i had the 7800gt. great drivers

I know multiple people have already asked but can you post screenshots of the problem? Is this going to be like another Farcry shadow rendering problem where nVidia incorrectly renders shadows? Aside from the shadows are there any other problems with the X1900? Who stares at shadows when they're playing a FPS?

Nope not gonna reinstall my x1900xt thanks though.

 

[Yreka]

Originally posted by: Elfear

Yreka- Have you tried ATI Tray Tools yet? I have never used CCC before because Tray Tolls works so well. Also what problems are you having with the drivers and ATI Tool?

I haven't tried Tray Tools yet. I was under the impression that there wasnt a working version for the 1900's yet. I will have to look into it again.

CCC-

CCC is more of an annoyance. I am not super anal about "bloat", I like to keep my systems up to date enough that I have a little overhead for stuff like that. The problem I have with it, is that its unessesary. I don't need all the cute little windows showing me what the different options do etc. Also, I just want a plain overclocking panel, overdrive sucks. Just leave it as 2d clocks are this, 3d clocks are this, current clocks are this. What is this "requested clockspeed" crap. Also, the "actual" clocks list the 2d clocks only regardless if a 3D app is running or not. My impression is that instead of fixing problems, ATI keeps trying to polish a turd. Give me Nvidia control panel + coolbits and I am a happy kid. I don't have to rely on shakey 3rd party apps to do things right.

Cat Drivers-

The problems I am having with the drivers mostly have to do with running D3D apps in windows. Crashing while minimizing, resizing. Mousing out of the 3d window will cause it to slideshow at less than 1fps until you mouse back in. Switching a D3D app to windowed mode, then back to full screen causes the gamma to go overdark. You have to open the apps options and move the gamma slider just a hair to reset. Little minor things like that. Not dealbreakers, but start to add up after awhile.


The second issue I have isnt with the drivers, but it is another "annoyance". When ever I restart *warm boot*, the display does not re-initialize until windows comes up. I either have to wait for that, cycle the inputs on my display, or do a cold boot. Not sure if this is an incompatability or what, but my Nvidia hardware never caused the problem.

ATI Tool-

I haven't delved much into ATI tool yet. I basically use it to monitor my temps because it has a plug in for LCD Studio display. I am not really motivated to use it to OC because of all the hoops you have to jump thorugh with it on the X1900 cards. For now, I just maxed out the card on the overdrive settings, and will wait for more mature software.

Could be a case of grass is always greener, but I dont remember having as many issues with Nivida, even SLI had less "quirks" for me. I dunno, things just seemed more... polished, while it seems like ATI has Creative's driver team working on their stuff.

And don't get me wrong, my experience with the X1900XT is overall positive. It rips, and looks gorgeous doing it, but when Nvidias hardware is this close you cant help but to start looking for differences... I still prefer my XT over 2 of any other card, but now with the 7900GTX, it finally has some single card competition

Couple that with my senseless urge to waste money on needless upgrades





The 7900GTX and X1900XT have the same HS mounting too dont they. I wouldnt even need a new water block.. hmmmmm

 

[nitromullet]

Can you explain what you mean with the warm boot issue? I'm not sure if I quite follow that completely... What actually happens..?

 

[Yreka]

When restarting windows, after it goes through its "saving settings" and restarts, the display does not come back up until windows has completely booted to the desktop. Any text, welcome, or log in screens will not show up.

Bascially
The display reads *Mode not supported* on my 2005fpw *DVI* or a yellow light+ no display on the 1 samsung LCD and 2 CRTs I have also tried. The "fix" is wait for it to boot completely, cycle inputs *on the 2005fpw*, or just shut down completely and turn it back on. Its almost like, if you have used SLI plugging the display cable into the wrong card.

I have 2 related MOBO CMOS settings, one is force video bios on restart and I cant remember the other one offhand. Any combination of those 2 don't seem to affect the problem. Also tried both DVI ports on the card, same thing.

ATI says its normal, but I have only heard of 1 other person who has the same issue. I suspect its either something terribly simple I am overlooking or some odd incompatability with hardware or firmware. To be honest, it dosnt bother me enough to do anything about it other than bi^ch. Its just another one of those "annoyances"

 

[Jules]

Originally posted by: Yreka
When restarting windows, after it goes through its "saving settings" and restarts, the display does not come back up until windows has completely booted to the desktop. Any text, welcome, or log in screens will not show up.

Bascially
The display reads *Mode not supported* on my 2005fpw *DVI* or a yellow light+ no display on the 1 samsung LCD and 2 CRTs I have also tried. The "fix" is wait for it to boot completely, cycle inputs *on the 2005fpw*, or just shut down completely and turn it back on. Its almost like, if you have used SLI plugging the display cable into the wrong card.

I have 2 related MOBO CMOS settings, one is force video bios on restart and I cant remember the other one offhand. Any combination of those 2 don't seem to affect the problem. Also tried both DVI ports on the card, same thing.

ATI says its normal, but I have only heard of 1 other person who has the same issue. I suspect its either something terribly simple I am overlooking or some odd incompatability with hardware or firmware. To be honest, it dosnt bother me enough to do anything about it other than bi^ch. Its just another one of those "annoyances"

I also had that didnt really bother me at all

 

[BW86]

lucky sob