Jump to content

Recommended Posts

Not sure what the issue is but ever since the 1.7 update, Designer is SLOWWW, hangs on moving a simple shape on the artboard. Verging on unusable!
iMac (Retina 5K, 27-inch, Late 2014)
4 GHz Intel Core i7
32 GB 1600 MHz DDR3
AMD Radeon R9 M295X 4 GB

Share this post


Link to post
Share on other sites

I probably shouldn't post as it's not useful as a bug report, just an observation. I'm having performance issues with it too. I'm a small fraction of the way through something and it's already bogging down but not all the time. The pen tool isn't as smooth or quite as responsive as 1.6 either, sometimes noticeably so. It's not something you know unless you try and then it's too late because of the file format change. I did try and copy/paste it all back in to 1.6 by re-installing the RC so I could have both versions open but that didn't work so I'll muddle on and then go back to 1.6 and try again later.

Share this post


Link to post
Share on other sites

I think since 1.7.1 the program is working like before. Perhaps it was with this issue?: Fix for Metal issues on some Intel GPUs and older operating systems

So all is fine again.

Share this post


Link to post
Share on other sites
On 6/19/2019 at 3:06 PM, Washound said:

I think since 1.7.1 the program is working like before. Perhaps it was with this issue?: Fix for Metal issues on some Intel GPUs and older operating systems

So all is fine again.

Ahh wonderful! Thanks for letting us know. :) 

Share this post


Link to post
Share on other sites

OK, now here is a file that is causing issues with working on a masked image... The cursor creates a pattern behind the object with mask. Very difficult to work with this happening.

Screen Shot 2019-08-12 at 12.11.05 PM.png

Share this post


Link to post
Share on other sites
49 minutes ago, Washound said:

Here you go Sean

composite_27.zip

Thanks for that file. It looks like it is being caused by the Lighting Filter at the top of the document. Disabling that stops it from happening, when I re-enable it the issue comes back. I'll get it passed on to development.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×