hard/soft issues?

[popster]

hi, just purchased A:M, but am experiencing problems on my mac. I've a MDD DP 1gHz Mac, with 1.5GB ram , OS X 10.4.6, and standard graphics card (Radeon 9000 Pro, 64MB). I am forced (!) to use a PC at work (trans to I rarely use it), and compared the performance of the two. I used Lambrina, with a Can-Can chor. On the PC (a very lowend P4, standard GPU) it will play without dropping frames, no problem. On my Mac, the same file is practically unuseable - it drops so many frames. Am I missing something? If it's the GPU, would something like a 9800 Pro (either 128 or 256 MB) make a difference? At the moment, it makes using A:M for animation nigh impossible. Hope you guys can steer me in the right direction. Cheers, Paschall

[MMZ_TimeLord]

When you say it drops frames... are you in shaded mode? or wireframe? or possibly shaded wireframe?

 

MACs historically have been slower running A:M. (Unless I am mistaken)

 

The main problem I can see is the video card you have doesn't have enough RAM. I had a PC with a low RAM card and it too experienced problems with shaded mode. Although I don't think it was as severe.

 

Can you post a screenshot?

 

MAC users will surely try to help as well.

[popster]

thanks - it's shaded mode. I've just tested it on a dual G5 2gig, with a 64MB 9600 Pro - works fine. If it's the graphics card, I'll upgrade. cheers

 

When you say it drops frames... are you in shaded mode? or wireframe? or possibly shaded wireframe?

 

MACs historically have been slower running A:M. (Unless I am mistaken)

 

The main problem I can see is the video card you have doesn't have enough RAM. I had a PC with a low RAM card and it too experienced problems with shaded mode. Although I don't think it was as severe.

 

Can you post a screenshot?

 

MAC users will surely try to help as well.

[luckbat]

It's the graphics card. Processor and RAM affect rendering speed; GPU/VRAM affect realtime playback speed. Get a 128MB card if you can.

[C-grid]

I've a MDD DP 1gHz Mac, with 1.5GB ram, with a Radeon 9000 Pro, 64MB.

I've just tested it on a dual G5 2gig, with a 64MB 9600 Pro - works fine.

 

 

Hello popster,

 

I'm sure you'll see the answer.

 

Niels.

[popster]

thanks everyone - I'm looking at buying a 128 or 256 9800 Pro; thanks again

[C-grid]

thanks everyone - I'm looking at buying a 128 or 256 9800 Pro; thanks again

 

Hello popster,

 

Work with the stuff you have right now and buy a faster computer in time.

 

Niels.

[Guest jandals]

I upgraded to a 256 MB Radeon 9800 a while ago but I don't get smooth playback in A:M. But I don't preview animation in A:M anyway. I always render a shaded preview and watch it at its final framerate.

[luckbat]

The more patches you have visible, the slower the playback. One trick I use is to change the character models' default Chor display settings to "shaded" or "shaded wireframe," while the environment is set to "wireframe." Then, I hit the numpad '7' key to switch to Default View. The resulting playback is much faster than when you're in Shaded View.

 

Us Mac users also get a playback speed boost when we hit "play," then Alt-Tab to the Finder while the animation is still playing.

 

Remember: if your model is complex enough to make your GPU chug, you should probably be animating using proxies.

[robcat2075]

On the PC (a very lowend P4, standard GPU) it will play without dropping frames, no problem. On my Mac, the same file is practically unuseable - it drops so many frames.

I think this indicates that a stronger GPU will not help much.

 

A:M really doesn't make extensive use of all the real-time powers of graphics cards since graphics cards are polygon oriented.

 

CPU speed is the biggest factor in your real-time playback, more powerful GPUs offer diminshing returns.

 

At least that's what I have heard the Hash people say numerous times. If that's changed, let me know, I'll go out and buy a faster card.

[popster]

thanks everyone; things are a little clearer now. I appreciate your feedback. It's presumably down to mesh approach in A:M that is causing this unusual blimp - I've used Cinema 4D in the past, which automatically utilises both my processors and all the features of my (limited) GPU. thanks again, cheers, Paschall