Moho still lags on Mac unless started in low resolution mode

[synthsin75]

If that's the case, Dave, Moho has the option to disable custom cursors.

[Greenlaw]

I'm curious to hear if that works.

Also wondering if there any performance benefits to doing that on a Windows machine. Guessing it's minimal but maybe I'll be surprised.

[MrMiracle77]

Protected memory is one of those areas where Microsoft has been ahead of Apple over the years, so I wouldn't expect a difference changing Moho's settings in Windows.

[arglborps]

It's a bug a memory leak, has nothing to do with protected memory.
Modern macOS (Mac OS X) is based on BSD Unix and NeXTSTEP which had protected memory long before Windows even existed.

[arglborps]

I have no idea why people are early adopters of new OSs and software versions when they rely on them for work.

I have no idea why Apple bothers to put out developer previews of new OS releases like half a year or more ahead of the release when developers (and shamefully the large companies are the worst – cough, cough, Adobe, cough, ToonBoom, cough, cough) just don't bother making sure their software is ready for the new OS on release date.

Oddly enough in most cases, smaller developer houses are usually very good at getting their software ready in time and release updated versions of their software AHEAD or at least within days of the new OS release.

Shining examples are Affinity (Designer, Photo, Publisher), FlyingMeat (Acorn), Rogue Amoeba (Audio Hijack Pro, etc.), Pixelmator, and naturally Apple's own software divisions.

[synthsin75]

I have no idea why people are early adopters of new OSs and software versions when they rely on them for work.

I have no idea why Apple bothers to put out developer previews of new OS releases like half a year or more ahead of the release...

There simply aren't enough developers to hammer on it and find all the bugs. That's why fixes are made after a public release, software has beta testers, etc.. There's just no substitute for the number of testers a public release provides. Personally, I don't fully adopt anything until at least two years after a public release, and I keep the last proven stable release just in case.

[stephenthomas0]

Chiming in as I'm having the same issue. Very very slow playback is one thing, but I'm finding the whole interface very laggy. It feels like every single click in the interface is followed by a lag of about a second before you see the result of the click. This makes animating very painful and I'm not sure if I'm imagining it, but the latest update (13.5.2) feels even worse.

I'm using a MacBook Pro with an i9 processor, so it's not a slouch. Can confirm that lowering the screen resolution speeds things up, which isn't an ideal solution as there's less room to work in

Has anyone raised a ticket on this since Lost Marble has taken over?

[arglborps]

I've raised the issue in the support forum (https://lostmarble.com/support/) and the the developers are aware of the issue. I also sent them links to several threads in this forum where the problem is mentioned.

[stephenthomas0]

This makes animating very painful...

Correction. This makes doing anything very painful. Even selecting layers, tools, any kind of interaction has a delay. Even keyboard shortcuts to change tools are incredibly slow.

[stephenthomas0]

I've raised the issue in the support forum (https://lostmarble.com/support/) and the the developers are aware of the issue. I also sent them links to several threads in this forum where the problem is mentioned.

Ah great, thanks for raising it. Really hope they focus on performance over anything else on the next release.

[JoelMayer]

I'd already save 100 years of my life-time if the drop down menus wouldn't blink every time i select something.... mac OS classic style

[chucky]

Everyone should just check the timeline visibility of layers, that, brush and particles are the worst offenders when it comes to slowdowns.
If you have check boxes visible in that timeline visibility column you may be having some serious chugging going on.
I think a display checkbox to toggle that quickly could be a good idea.

[stephenthomas0]

Everyone should just check the timeline visibility of layers, that, brush and particles are the worst offenders when it comes to slowdowns.
If you have check boxes visible in that timeline visibility column you may be having some serious chugging going on.
I think a display checkbox to toggle that quickly could be a good idea.

It feels like the whole application is super slow, so I'm not sure if it's a timeline issue, that would just relate to playback yeah?

[arglborps]

It's the viewport rendering that's just really slow when you use higher resolutions. It's not related to particle emitters or other things (although those make the viewport in Moho just unbearably slow).