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

Search the Community

Showing results for tags ' designer 2'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • 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.2 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


Last Updated

  • Start


Filter by number of...


  • Start



Website URL



Member Title

Found 3 results

  1. Hi, this bug report applies to the latest published version of AD2 on iPad running the latest iPadOS. The Bug Nested Symbols seem to get broken when they are propagated from one document to another using the Assets panel. Details I opened a new document, drew a rectangle and a circular shape, turned each one into a simple (not nested) Symbol. I moved the circle Symbol inside the square Symbol, creating a nested Symbol. Then I copied the circle Symbol twice to get 3 inside the rectangle, and added a stroke to the circles for better visibility. I created an Asset from the rectangle Symbol with its cargo of circles. Then opened a new document with no content, inserted the rectangle Symbol from Assets, and changed the fill on one of the circles. The circles no longer function as linked Symbols, so this change did not propagate to all 3 circular Symbols. And that’s a tragedy. Note to Repair Crew I also tried this with a simple Symbol (no contained Symbols) and that seemed to work, so the nesting seems to be a factor in this behaviour. Note to interested users The only reliable mechanism I’m aware of for transporting Symbols from one document to another is to collect them in a “Library” document, using Copy and Paste for the transfers. Painful, of course. Please let me know if there’s another reliable mechanism I’m missing. Cargo I’ve attached a screen recording and two documents to illustrate the problem. Symbols in Assets 01 is creation of the nested Symbol. Symbols in Assets 02 is insertion of nested Symbol from Assets. Both files were saved with their History. RPReplay_Final1692120786.mp4 Symbols in Assets 01.afdesign Symbols in Assets 02.afdesign
  2. I don't remember this happening before the recent update, but it could be some setting I changed and forgot about, but antialiasing in pixel view has a green or blue tint when it is caused by a mask but the outline of a shape has correct antialiasing. it's in RGB color space, and I tried to see if 16 bit would change it but nope. the screenshot with a glow was previously created and this bug did not show then.
  3. I'm trying to do some HDR mockups in Designer 2 but haven't gotten it to show extended brightness inside the app (on MacBook Pro internal XDR display). I created an RGB/32 document and applied an exposure adjustment greater than 1 to the layer I'm trying to brighten beyond "normal" display levels. I've tried applying the exposure adjustment to both vector and pixel layers. The 32-bit Preview panel doesn't allow me to click `Enable EDR` and instead of seeing extended brightness it's just desaturating the colors. I've repeated these steps in Photo 2 and the 32-bit Preview panel allowed `Enable EDR` and triggered the display's extended brightness as expected. Is there a different workflow I need to follow to see EDR/HDR in Designer?
  • 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.