View Full Version : Help With New System, Slow Viewport Performance
01-08-2013, 07:24 PM
I need a bit of help with a newly built PC. A friend is building it and, by all appearances, it's a really good machine. 4.5 GHz Core i7 (Sandy Bridge) 6 Core, 12 GB RAM and a FirePro W7000 4GB GPU, 250 GB SSD and a 2TB HD. We installed 3DS Max 2013 with all available service packs and it seems to run smoothly until we hit the animation playback. We tested two separate scenes with minimal material and polygon loads, however playback according to FRAPS was only 1 FPS. CPU load was less than 20% and GPU load was less than 10%... zero most of the time. Default lighting. Simple transform animation for position and rotation. Approx 10k polygons total. Standard, single diffuse map textures only. We also noticed, and I don't know if there is a correlation, but 3DS Max dumped 50GB of .DDS texture caching to a temp folder.
I'm not sure what it is, but something is definitely wrong. The same two scene play smoothly on my 4 year old ASUS notebook. Does anyone possibly know what might be happening or where to look? Any help that can be offered is greatly appreciated.
01-08-2013, 08:02 PM
i would guess and say, make sure you've got the latest performance drivers and plugins:
and/or, you may need to switch to a different graphics driver via customize > preferences > viewport tab.
perhaps openGL performs better for AMD?
01-08-2013, 10:30 PM
FRAPS? As in screen video capture?
01-08-2013, 11:53 PM
FRAPS is a small app that provides real time frame rates on film, games, 3D apps, etc.
01-09-2013, 01:02 AM
I've used it to record videos but it in it's self effects your pc performance so I doubt it is reliable. Recording games such as BF3 had to drop it down to 720p and dual channel to not lag out.
Try disabling hyper threading on your CPU if your not doing long renders. I'm sure that's not the root of your problem, but It could help. Most things run single threaded, and having 12T is less then ideal.
01-09-2013, 03:04 AM
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.