My X-Fi got along just fine with my X1800, 4870, and 5850.
Want a cookie?
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
My X-Fi got along just fine with my X1800, 4870, and 5850.
Want a cookie?
I love when people post like this, (not saying anything against you) but this sounds a LOT like my reply some post up about a GTX280. in fact it was very similar as it was forcing my screen to 16:9 instead of 16:10. i here it is
only when the retail version of windows 7 came the work around didn't work and I have downgraded my card for the time being.
There simply is no shortage of horror stories from both sides. that doesn't negate your personal experiences, but for every one like you there is another on the other side.
and for the record FSX did run faster on some of the older hardware but that is true on both sides (I understand it has something to do with the engine Microsoft uses.)
I flat have to agree with you about the prices though.
Your not alone. Over the last 5 years I have experienced a minor niggle or two from both companies, but no real game breakers, and those niggles were usually fixed within a driver release or two.
I love when people post like this, (not saying anything against you) but this sounds a LOT like my reply some post up about a GTX280. in fact it was very similar as it was forcing my screen to 16:9 instead of 16:10. i here it is
only when the retail version of windows 7 came the work around didn't work and I have downgraded my card for the time being.
There simply is no shortage of horror stories from both sides. that doesn't negate your personal experiences, but for every one like you there is another on the other side.
and for the record FSX did run faster on some of the older hardware but that is true on both sides (I understand it has something to do with the engine Microsoft uses.)
I flat have to agree with you about the prices though.
You're only offering me one because you know I'm right.
Destroyed.
What bugs? I don't see a 28 page thread about Nvidia drivers and/or hardware causing odd crashes unlike the GSOD thread. I am also effected by that "59hz bug" but it hasn't caused me a single problem.
I honestly can't say that Nvidia drivers have been headache free but unlike with my experiences with ATI these Nvidia bugs are rarely game breaking. The only two that I have dealt with in a long while now is not being able to force AA in FO3 due to a stutter and Gothic 1 and 2 not working.
As for FSX around the time that I used that 4870 which was outperformed quite a lot I also tried out a GTX260 and it performed about on par with that 9800 maybe a little worse.
These questions are also the same ones the enthusiast community (us) has been asking anyway, so I'm not really sure what all the "omg flamebait fanboy war" BS is about... BSN is always pretty lack-luster IMO, too.
Actually I have first hand knowledge on this. It was a simple bug in the NVIDIA DX10 driver that caused GT200 products to initially be slower than the G80 and it was promptly fixed in the next release. It's not some universal truth.. but nice try.
go search for it. I have three threads myself on the subject. then go look in the nvidia forum for some of the others. either you haven't looked or suffering from fanboi vision impairment. I am sorry but as bad as ATI may be Nvidia just doesn't have room to talk. Don't get me wrong, I don't doubt your personal experiences here but if I was going off of just mine I would be praising ATI drivers and condemning Nvidias. clearly as your experiences have gone that probably is not right. There just is no shortages on either side of horror stories. If you put it perspective it becomes hard to take a side on this. Just because I have not personally had an issue with ATI drivers doesn't justify a pro ATI driver stance, so I don't see how you can justify your.
Over 200 systems I've worked on that had Nvidia and CL products, all had BSODs, all I removed the CL products, all stopped having BSODs. I call that a problem with CL drivers, not Nvidia.
This.
I find with either brand the major issues that draw headlines usually impact a small but vocal group. My personal issues with both companies have been minor and generally dealt with quickly.
Gah, I know you've got to be trolling but I can't help myself. Here's a logic analogy:
Say you have two trains, A and B, on a single track heading towards each other on a collision course. You, standing off to the side observe the resulting collision and wreckage. The only information you see is two trains running into each other, causing a wreck.
-Now, if you were to lift up and remove train A from the track, do they still collide? No. Train B passes on just fine
-If you lift up and remove train B from the track, do they still collide? No. Train A would pass through just fine.
Now who is at fault? Based on simply observing the wreck, you can not physically determine which train is at fault. Removing one OR the other from the track will prevent the wreck, but again this does not conclusively prove one way or another which train was ultimately responsible for going the wrong way. You simply don't have enough information.
You could remove train A from the track in identical situations 200 times; it still wouldn't prove it to be train A's fault because likewise, you could remove train B from the track 200 times and prevent the wreck as well. Quantity means nothing.
If you somehow hadn't figured it out, train A and train B are creative/nvidia products. It doesn't even matter which trains you assign them to. Can you tell me, based on this information, which train is at fault? We are of course, for the sake of the argument, ignoring entirely the reports of the nVidia train derailing itself for no reason, as well as the reports that ATI developed a flying train that flies way above the track.
All you've proven is that having both trains together on the same track is a bad idea.
Stop making nVidia users look bad. It hurtses usssss
You see the glass half full, I see it half empty. Either way, I truely do not believe all 28% of vista BSODs were directly caused by Nvidia drivers but a decent portion, 5-8% were caused in part by CL drivers.
I can't believe CL is getting a pass by so many people here on this. They have sabataged their own drivers to force upgrades to cheaper products. Pulled a major PR snafu by putting the clamps on DanielK and his fix for CL Live, Live 5.1, Audigy and Audigy2 line driver fixes, something CL COULD NEVER SEEM TO FUCKING DO! Hell he even had fixed drivers for the X-Fi and X-Fi2 line of sound cards that CL put a stop to. but yet all Nvidia based BSODs without a doubt or question has to be the result of Nvidia, nothing else could possibly have plyed a role in their drivers creating the BSODs.
I can't believe CL is getting a pass by so many people ...
While I also think CL's drivers are not so good, you don't seem to have any idea why those features were left out of the Audigy 2 and older cards for Vista. Licensing.
CL, for whatever reason, only licenced all those features that they cut from the Vista drivers, for Win 9x/2K/Xp. They did not have the rights to put them in the Vista driver. That later changed, and the current drivers do have the features back in it. Daniel_K did a great service for the community but, put CL at risk of a lawsuit since he was on their boards giving away hacked drivers that included ip Creative did not have license for in Vista. At the point that Daniel_K asked for "donations", the situation kind of required CL to act as they did.
I do not condone CL's actions totaly in that situation either, charging Audigy2 owners for full featured drivers, not coming clean from the get go on why, not fixing the situation earlier, being a general ass about every thing, etc., but they could not let Daniel_K keep doing what he was doing without risking themselves. CL does not get a pass, but as has been stated a dozen times by a dozen people already, Ati did not have the problem with CL, Nv did. A rational person, even a fanatic, would assume the Nv drivers are to blame, and not CL in that case.
Your only evidence is that you have decided to believe it is CL's fault. Nv has not come out and said that it was CL's fault, and they would have were it true or even plausible.
Oh, and Daniel_K's hacked drivers were just that. Hacked, all he did was unlock/add the features/software CL cut out or did not include for licensing reasons. He did absolutely nothin to improve stability of fix bugs that he did not introduce with his hacking around. with the drivers.
Shhhh, you're making nvidia look bad.^ lol Daniel K did not write creative drives lol he just mixed and matched them and played around with the ini files to get the features to work on the older cards. His drivers cannot be any more stable....
Isn't that the point?
Shhhh, you're making nvidia look bad.
Haven't they always been the killers of innovation? They ruined Aureal because they had a better product than Creative, and even when Aureal were bankrupted and Creative bought all the IP they still killed the better tech.Man I wish I could run Creative Labs for 2 years. I would turn them back into the innovator that they were back in the old days with cards like the SB 16, AWE 32, SB Live, etc
I would like to see ATI and Nvidia create a base driver that can stream in incremental updates, you know, sorta like tons of other pieces of software that exist...