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

Search the Community

Showing results for tags 'afp-2990'.

  • 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 (Staff 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.5 Beta 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 5 results

  1. This is more of a question: I don't know if this is just a beta issue or intended functionality but it doesn't make a whole lot of sense. ...and if the assistant is routinely going to step in and rasterize layers (even when I don't ask it to), then why not here?
  2. Hello all, i want to merge pixel layers with the shortcut CTRL Shift E, the top layer is deleted. Steps to reproduce: menu---select--selecct all layers menu--Layer--merge selected (shortcut: CTRL+SHIFT+E) when the levels are selected manually from bottom to top, the result is as expected. This bug affects both the beta version1.8.4.665 and the customer version. Cheers
  3. Expecting same look after merger but layer order is changed and end result doesn't look correct
  4. Usually, I use the inpainting brush and clone brush on a separate pixel layer for which current layer and below is selected. I noticed when I exported an image on which I had made these corrections, that they could be seen in the export, but not the image when viewed in Affinity Photo. Flattening the image before exporting cures the problem, but this is quite inconvenient. The images are included. Two images of the errors are provided, one with the errors pointed to. Also, when I tried to merge the correction pixel layer with the original base layer, the corrections disappeared altogether, so flattening the document will solve the problem, but merging the two layers will not. Update 3, it appears to be a problem caused by an interaction between the layers and the lanczos 3 (Non Separatable) compression because if I use bicubic, it don't see the artifacts.
  5. I am affinity photo (mac) 1.8.1 user. I started using it since 1.8 appeared in the App Store. I would like to inform you of two problems found in 1.8. The first one is related to Layer Merge. Unlike in previous versions, there was a problem with Merge Selected in 1.8. If you select two or more layers and click this menu, the bottom layer is given priority, not the top one. This Merge Selected problem may or may not function properly. So when this happens I have to use the menu [Merge Visible]. * I have captured the relevant content as a video. Another problem occurs in the tab. [Sliders] is sometimes enabled by default. In this case, even if I change the option to [Wheel], which I usually use, I work for a while and then go back to the [Sliders] option. * I wanted to capture a video about this problem, but now it works again (it doesn't mean it's fixed in 1.8.1) Layer_Merge_&_Sliders.m4v
×
×
  • 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.