On 15 June 2016 at 09:48, Alistair Leslie-Hughes leslie_alistair@hotmail.com wrote:
Signed-off-by: Alistair Leslie-Hughes leslie_alistair@hotmail.com
dlls/wined3d/directx.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
This isn't necessarily wrong, but why is this needed/more correct?
Hi Henri,
On 15/06/16 20:51, Henri Verbeet wrote:
On 15 June 2016 at 09:48, Alistair Leslie-Hughes leslie_alistair@hotmail.com wrote:
Signed-off-by: Alistair Leslie-Hughes leslie_alistair@hotmail.com
dlls/wined3d/directx.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
This isn't necessarily wrong, but why is this needed/more correct?
I used this video card. When I was playing a game which requires 512MB of video memory it causes a crash due to out of video memory.
Since this card comes with 512MB by default, it seems like the correct thing to adjust.
Best Regards Alistair Leslie-Hughes
On 15 June 2016 at 13:25, Alistair Leslie-Hughes leslie_alistair@hotmail.com wrote:
On 15/06/16 20:51, Henri Verbeet wrote:
This isn't necessarily wrong, but why is this needed/more correct?
I used this video card. When I was playing a game which requires 512MB of video memory it causes a crash due to out of video memory.
Since this card comes with 512MB by default, it seems like the correct thing to adjust.
Ok, but there are supposedly variants with 1024 MiB of video memory as well, which then creates a similar situation when someone wants to run an application that requires 1024 MiB of video memory. More generally speaking, for any card that has variants with different amounts of video memory, there's a trade-off between potentially reporting more memory than the card actually has and potentially reporting less memory than the card actually has. I tend to think it's safer to err on the side of reporting too much memory, so in that regard this is fine, but the entire issue also just goes away when you use a driver that supports GLX_MESA_query_renderer. Is your card not well supported by Nouveau?
-
Alistair Leslie-Hughes -
Henri Verbeet