Page 1 of 1
Does Moho still slow on mac O (SX)
Posted: Thu May 04, 2006 10:48 pm
by riledguy
Does 5.3 fix the OS X problem of Moho slowing down after time?
Posted: Tue May 09, 2006 3:18 pm
by riledguy
No one has used 5.3 in OSX and can tell me if it still slows down with use?
Posted: Tue May 09, 2006 4:41 pm
by CartoonM!ke
I'm still a noob with Moho, but I really haven't noticed a slow down. The longest I've used it was for about 3 hours, little animation, lots of renders. Using Mac OS X 10.3.9
Posted: Tue May 09, 2006 6:27 pm
by riledguy
CartoonM!ke wrote:I'm still a noob with Moho, but I really haven't noticed a slow down. The longest I've used it was for about 3 hours, little animation, lots of renders. Using Mac OS X 10.3.9
Well try doing a bunch of drawing, building and animating and let me know if you would.
I really hope they have fixed this. Though even with the problem it is a great program.
Posted: Wed May 10, 2006 12:33 am
by heyvern
Can you be more specific?
Is there something specifically you do that slows down?
There is a free demo that you could try out. Why not try it yourself and see if the problem is fixed?
I have only Used Moho on Mac.
There seem to be a lot of mac users here... so... if there is a problem I haven't heard about it or experienced it.
-Vern
Posted: Mon May 15, 2006 6:53 pm
by spoooze!
I've been using Moho for over a year now and it hasn't slowed down really.
James

Posted: Mon May 15, 2006 6:58 pm
by riledguy
spoooze! wrote:I've been using Moho for over a year now and it hasn't slowed down really.
James

Good to know.. I guess in 5.3 they fixed the problem.
Great news.... great app
rock on and animate on all
Posted: Mon May 15, 2006 8:44 pm
by Lost Marble
riledguy, which version were you using when you had the slowdown problem?
Posted: Mon May 15, 2006 8:50 pm
by riledguy
Lost Marble wrote:riledguy, which version were you using when you had the slowdown problem?
5.0.7 Slows down with use for me on OSX
Posted: Tue May 16, 2006 1:23 am
by Lost Marble
OK, yeah, that problem on OS X was fixed somewhere between 5.1 and 5.2. So that explains why you were still seeing it.