GeForce GTX 580
Posted 26 April 2011 - 10:38 AM
I've been using a Radeon 4800 series card for a while without any trouble, but I need put it in another workstation so it's time for an upgrade.
If I really really should not get this card. Please post now
Posted 26 April 2011 - 12:48 PM
Ended up getting the EVGA GeForce GTX 580 and it comes with some overclocking tools.
I'll install it later and let you know if it works with Houdini
Posted 28 April 2011 - 09:03 AM
So, my advice to you is that if you have a stable Nvidia GEForce driver, keep it! Don't update every time a new driver is released. Or if you do, be prepared to roll it back
Posted 21 June 2011 - 05:59 PM
I only ever notice issues with the Geforce cards when using Maya with high performance viewport rendering switched on.
That said, my work is confined to dynamic simulations and Ive never had a scene with more than 2 textured objects since switching to the 580s.
Posted 30 June 2012 - 07:38 AM
What driver are you using? I just got a Zotac 580GTX 3GB and run the 295.59 driver on Fedora 16.
Using open-cl I get a 30% performance increase for pyro compared to a quadcore I7 920, 2.67 CPU. I can view about 20 mil polygons reasonably well. I would say most of it works well.
Though viewing just a grid or even an empty scene it takes about 2 sec time after I press the spacebar before I can tumble around. As far as I'm concerned this is the moment where data is copied to vram. How ever I find this very slugy, I wonder if it might be the driver version. Any recommendations?
Houdini Master Version 12.0.634
Number of Cores: 8
Physical Memory: 11.73 GB
OpenGL Vendor: NVIDIA Corporation
OpenGL Renderer: GeForce GTX 580/PCIe/SSE2
OpenGL Version: 4.2.0 NVIDIA 295.59
OpenGL Shading Language: 4.20 NVIDIA via Cg compiler
Detected: NVidia Consumer
Edited by Nerox, 30 June 2012 - 07:40 AM.
Posted 03 July 2012 - 09:49 AM
This is an issue specific to Fedora Core 15 and 16 that appears related to the processing of the spacebar state by the X server. It's not graphics driver related. I don't have a suggestion or workaround for it, unfortunately.
Posted 03 July 2012 - 11:12 AM
Has any one tested this on Fedora 17?
Posted 10 July 2012 - 06:02 AM
Do you know to which specific bug it is related in Fedora core 15 and 16? I would like to check if its fixed in 17 before I go over the hassle of upgrading. Else I'll downgrade my system to 14.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users