Created on 16.04.2006 - 23:04

PeteBernert schrieb and if you set the Y resolution to some low value, can you then use the ultra high X without glitches?

It does that for me, Glitching/flashing bar on Very High X no matter what Y resolution I choose.

other thread schrieb Okay Im confused as someone with an x1600 managed to get it to work while his settings don't work for me, and hes reported it fixed to the author w/ cataylst 6.4 The mind boggles.

I think Pete knows it isn't fixed by now

Besides, it's the driver, not the plugin.

As for my configuration, who knows. Do you have the .NET 2.0 framework installed? I know I have that installed on my machine, could be one of the reasons. I also use Driver Cleaner Pro between each driver change, so that no driver remainants are left behind that could be a problem, not to mention the driver settings themselves.

Also, do you have a PCI-E card? Mine is AGP, and while I have no clue at all if that would make a difference in regards to the issue at hand, it's yet another difference that could/might/maybe be the difference between working and non-working.

[Dieser Beitrag wurde am 16.04.2006 - 23:07 von Kvasir aktualisiert]

Created on 17.04.2006 - 01:07

Hi

Yes I have a PCI-E version, and I have .NET 2.0 installed. I have tried installing fresh /w drivercleaner, with the same result.

I just hope ATI get round to fixing this soon, as much as I like ATI as a company if they say a feature is supported on its products specs it should be added onto the drivers at launch, with full functionality. Its like buying a car with a stereo but the radio on it doesn't work.

Created on 31.05.2006 - 07:02

I have had similar issues, which I was successful in correcting with the help of another forum member of NGEmu.

Check this thread out...it may help.

http://forums.ngemu.com/generic-epsxe-q … 00-xl.html

r2rX :D

Created on 31.05.2006 - 13:20

ready2rumbelX schrieb I have had similar issues, which I was successful in correcting with the help of another forum member of NGEmu.

As I've understand from that thread - you still have some issues with the black stripe in the left, so imo "successful" isn't the proper word

Created on 31.05.2006 - 17:55

FrancoisC schrieb I have a X1800 too, and I know of one game, Silent Hill 3, that can use 4096*4096 texture, and it work fine; but with the plugin it crash and says "No buffer available" But, I noticed one thing: if I select "Framebuffer object", it don't crash, I can hear everything in the game/bios, but I just have a grey screen..

and

Coyro schrieb I have the same situation with X1600. Hopefully, some solution will be found soon.

...that's what I was refering to. But, I should have been specific to what I was refering to (Grey Screen).

r2rX :D

[Dieser Beitrag wurde am 31.05.2006 - 17:57 von ready2rumbelX aktualisiert]

Created on 17.06.2006 - 12:05

I've got a similar problem to Kvasir's, although mine does not flicker, its a steady black bar through the left of the screen. Best I've seen it look so far though. Most games are perfectly playable, just with a small portion of the screen cut off. (btw this is with an x1900xtx w/ 6.5 cat drivers) I've been fiddling with it and driver settings and I've found that nothing helps it. And it is indeed caused by the X resolution set on 2. I hope we find the cause soon.

Created on 19.07.2006 - 15:37

I have the same problem as Kvasir on my X1600 card
until now I've not a solution

Looks like everybody considered it as the buggy of ATI drivers.
but from Catalyst6.3 to Catalyst6.6 the problem always existed.

ATI driver Team looks like have no interest in this.
Did I still have to play with 640*480 internal resolution?

Created on 24.07.2006 - 14:54

>Did I still have to play with 640*480 internal resolution?

ehehe, well, you can set the internal Y resolution higher than the X resolution, that will help a bit.

Created on 29.07.2006 - 05:02

The black border flicker is fixed in catalyst 6.8 and upward. Wait for it next month (6.7 just released today)

Created on 29.07.2006 - 07:57

Catalyst 6.7 realeased, with no help

what should I say to the ATI driver team?
Mistake, I should say the AMD-ATI team

wait for the next month