PDA

View Full Version : PNY Quadro FX 2000


postreal
11-25-2003, 12:19 PM
Hi.
Im thinking to buy "PNY Quadro FX 2000" display card. Anybody
have experience with these ? Are they good with 3d max ? Is these better cards ?

Emmortal1
11-25-2003, 01:59 PM
I can't really comment on the FX 2000, but I have an FX3000 and use Maya 5. The Quadro line of cards are definitely the best cards all around. I formerly had purchased an ATI Fire GL X2, the top of the line offering from ATI, and had severe problems with the card. Random crashes, horrid performance, and overall lack of support from ATI's Fire GL representives made me dump the card faster than a pie eating champion with an explosive case of diarrhea.

The FX line has excellent driver support, knowledgeable support staff, and second to none performance. I highly recomend them over 3dlabs and ATI.

Emmortal

markdc
11-25-2003, 08:51 PM
I have the fx1000 and it's blazing fast until you use meshsmooth. You can put a meshselect or editmesh on top of the mesh smooth, but you lose the speed again when you start editing the model at the edit poly level. Make sure you get the maxtreme drivers.

stephen2002
11-25-2003, 09:24 PM
Originally posted by brian_dlm
I have the fx1000 and it's blazing fast until you use meshsmooth.

Wouldn't this be dependent on the CPU and not the GPU?

markdc
11-25-2003, 09:52 PM
Originally posted by stephen2002
Wouldn't this be dependent on the CPU and not the GPU?

Both.

Emmortal1
11-25-2003, 11:08 PM
The "display" of the mesh in the viewport is handled by the GPU of your gaphics card, how many verts are on screen and how fluid you can move the mesh around is all handled by the GPU. The operation itself of smoothing the mesh would be handled by the CPU so in reality it's not really both, just the initial operation handled by the CPU and the display of the result handled by the GPU.

Emmortal

markdc
11-26-2003, 12:57 AM
Originally posted by Emmortal1
The "display" of the mesh in the viewport is handled by the GPU of your gaphics card, how many verts are on screen and how fluid you can move the mesh around is all handled by the GPU.


That's what I'm talking about. If he gets fx2000 he will see an increase in viewport speed, but not as dramatic when the mesh is smoothed. It doesn't take alot of CPU time to subdivide the mesh. The bottle-neck is in displaying it.

Emmortal1
11-26-2003, 01:04 AM
Right, just making sure that was clear, thanks!

Emmortal

CgFX
11-26-2003, 06:29 AM
Originally posted by Emmortal1
The "display" of the mesh in the viewport is handled by the GPU of your gaphics card, how many verts are on screen and how fluid you can move the mesh around is all handled by the GPU. The operation itself of smoothing the mesh would be handled by the CPU so in reality it's not really both, just the initial operation handled by the CPU and the display of the result handled by the GPU.

Emmortal

To be a little more picky, since this is a mesh you are actively modifying I would be a little surprised if it was display-list'ed or cached on the graphics card. This means that it is drawn in immediate mode which means the CPU has to copy all the polys to the GPU for every frame. That means that CPU performance (particularly the CPU memory bandwidth) is very much involved still.

postreal
11-26-2003, 09:15 AM
Hi
Here is my new computers setup :

SC742i 450 watt chassis
Supermicro X5DAL-TG2
Dual Xeon 3,066 Ghz
1 Gb - 2 Gb ECC Registered DDR RAM
ATLAS 10K IV 36GB U320W 10000RPM (SCSI hd for system)
2* DIAMONDMAX+9 120GB DMA133 7200RPM 8MB (For stuff)
PNY Quadro FX 2000
Canopus Dv Storm 2
Creative Sound Blaster Extigy (USB)
+ other stuff

How this looks, should I change something ? Thanks for your answers :)

Emmortal1
11-26-2003, 03:10 PM
I would change out that atlas drive. Go with a Hitachi 15k rpm drive, you won't regert it.

Emmortal

postreal
11-26-2003, 03:17 PM
what about these

Maxtor Atlas 15K 80-pin (36 Gt, 15000 RPM) or
Maxtor Atlas 15K 68-pin (36 Gt, 15000 RPM)

?

CGTalk Moderation
01-16-2006, 07:00 PM
This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.