04-20-2011, 05:31 PM
04-20-2011, 05:37 PM
I hope you right and the driver know it. Anyway it was not a statement of truth, only a guess, a possibility.
04-20-2011, 05:47 PM
the driver doesn't need to know anything about the vram size.
04-20-2011, 08:35 PM
Before trying these new drivers I test the old drivers and the problem were still there.
My Card Graphic => http://www.gainward.com/main/vgapro.php?id=454
My Card Graphic => http://www.gainward.com/main/vgapro.php?id=454
04-20-2011, 10:43 PM
So it's a problem with the hardware then *that ONLY shows up in PCSX2 in DX11 mode*.
The video shows this pretty well: This is not a normal rendering bug that is common to GSdx / PCSX2.
It rather looks like a tiny bit of GPU logic circuitry is bad, and GSdx just happens to use it.
The video shows this pretty well: This is not a normal rendering bug that is common to GSdx / PCSX2.
It rather looks like a tiny bit of GPU logic circuitry is bad, and GSdx just happens to use it.
04-20-2011, 10:52 PM
If I understand all my games work pc or emulator (dolphin and other) Gta 4 maximum, crysis 2 or less and the other games up no problem, but my graphics card to a problem and it is not pcsx2 that bug? Allow me to have doubts about your proposal.
04-20-2011, 11:08 PM
comparing PC games to pcsx2 is just a complete nonsense.
I get your point, though. Bu t Iguess what Rama means is that gsdx sends standard instructions to your GPU. Just imagine now that pcsx2 uses a standard instruction that isn't used in Crysis nor GTA IV but is used in some games under pcsx2.
that would explain why pcsx2 encounters that "bug" meanwhile standard pc games don't
I get your point, though. Bu t Iguess what Rama means is that gsdx sends standard instructions to your GPU. Just imagine now that pcsx2 uses a standard instruction that isn't used in Crysis nor GTA IV but is used in some games under pcsx2.
that would explain why pcsx2 encounters that "bug" meanwhile standard pc games don't
04-20-2011, 11:25 PM
Ok i understand the good, I must wait for new drivers ^ ^ !
04-21-2011, 12:22 AM
Once upon a time there was Win98. It was a good boy but not the smartest one, strangely it was prone to give the "Out of memory" if the system had "too much RAM", something above 256MB although it was able to recon and deal with much larger amount. And still it's own memory manager was unable to make use of more than 128MB by itself...
This kind of issue arises mainly where cache or paging is involved, the driver need to know and be able to deal correctly with the available resources, or might abuse it and actually worsen things.
I can't tell for sure the amount of memory was the cause of the issue in that specific case, but I would not grant as certainty it can't be, not for something which are still in almost experimental phase. Of course the driver can be optimized to use whatever amount of memory it can manage, but is it already?
This kind of issue arises mainly where cache or paging is involved, the driver need to know and be able to deal correctly with the available resources, or might abuse it and actually worsen things.
I can't tell for sure the amount of memory was the cause of the issue in that specific case, but I would not grant as certainty it can't be, not for something which are still in almost experimental phase. Of course the driver can be optimized to use whatever amount of memory it can manage, but is it already?
04-21-2011, 04:24 AM
lets all chip in to buy Rama some Fermi test hardware.