If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Originally posted by TDB don´t get me wrong, I will eat my words the second matrox, actually do something about this bug, I just think it is kinda suspicious that it hasn´t been fixed yet.
like they are not prioritizing the bugfix high enough!
There is no fix for this. It's a hardware fault. Only fix is to put a different graphics card in your machine.
Well finally an answer and I suppose we cant blame Matrox as they did say that the FAA 16x method would have problems in a lot of games. So we are stuck with the card
Originally posted by VigilAnt
There is no fix for this. It's a hardware fault. Only fix is to put a different graphics card in your machine.
VigilAnt
if that is the case then the right thing to do is to offer us a fixed parhelia or a refund, instead of saying that, "they havn´t heard anything new yet".
or at the very least pull the bugged parhelia back from the market and sell out of the revised ones. instead of pretending that they are bugfree.
This sig is a shameless atempt to make my post look bigger.
if that is the case then the right thing to do is to offer us a fixed parhelia or a refund, instead of saying that, "they havn´t heard anything new yet".
or at the very least pull the bugged parhelia back from the market and sell out of the revised ones. instead of pretending that they are bugfree.
I would have to agree with you there, I believe that if Matrox are to keep their fanbase and customers then they will either have to find a fix or RMA the cards
Originally posted by ganyaik This is what I wanted to ask. How come if they're f*cked up that they release drivers every now and then?
maybe they are just polishing the beta-revisions they already have in the pipeline.
the BBZ are several revisions ahead of us, so they could probably release a few more drivers, without starting on new driver revisions.
This sig is a shameless atempt to make my post look bigger.
I see. OK, thanx for the info.
3dfx: I wonder if they wanna keep their fan base at all. This "banding is normal" behaviour is now what I would call "we wanna keep our customer base" attitude. I hope I'm wrong with it.
If Matrox replaces every P out there (or at least from everyone who notices it and complains about it) this will hurt them a lot i believe, and only brake their neck faster.
However i'm a bit dissapointed that Matrox doesn't say us upfront(?) in the face how the things are, but instead we have to get the information through the backdoor.
I guess Haig isn't to blame, he probably was strictly forbidden to tell.
they could still sell the current parhelia, if they said: "only works with DVI-D monitors" on the box.
or as a kind of low-end MMS card for 2d-only workstations.
but the fact that they, continuingly and well-knowingly, still sells the bugged parhelia, with out stating the cards limitations, is just wrong!
is it even legal?
Comment