Jump to content
You must now use your email address to sign in [click for more info] ×

Search the Community

Showing results for tags 'afd-3028'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Frequently Asked Questions
    • Affinity Support & Questions
    • Feedback & Suggestions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • V2 Bugs found on macOS
    • V2 Bugs found on Windows
    • V2 Bugs found on iPad
    • Reports of Bugs in Affinity Version 1 applications
  • Beta Software Forums
    • 2.4 New Features and Improvements
    • Other New Bugs and Issues in the Betas
    • Beta Software Program Members Area
    • [ARCHIVE] Reports from earlier Affinity betas

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests


Member Title

Found 2 results

  1. Almost every time I run a boolean operation to divide or unite vector curves in AD, it freezes on me as shown in attached image. I have to force quit and restart the app and try again in smaller doses or move it to Illustrator and try again there. I have an iMac with 12GB of RAM - I don't know if the issue is I need more RAM, or if it's still a bug Affinity is fixing? I ordered more RAM recently, so I'll be able to try it again after installing it to see - but I wanted to see if anyone had any info pertaining to this issue - thanks!
  2. Designer. I encountered this problem by clicking a toolbar button on error, but I think you should know about it anyway - I don't know if it will bother other users in some scenario. Create 5 overlapping circles Click DIVIDE Click COMBINE Designer starts combining and it will never end. In this example it never stopped and memory consumption stopped around 1.2GB, in the original scenario that was very similar memory consumption continued in big steps until I terminated it around 4GB+ Beta .119
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.