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

Search the Community

Showing results for tags 'bug report'.

  • 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 13 results

  1. Affinity SVG redender issue in Photo.zip Hi, I think there is an issue with SVG image rendering in Affinity Photo V2. I imported the same SVG image in both Affinity Photo and Affinity Designer. Set all the settings to similar state and then zoomed in. I saw the though the Designer rendered the SVG image perfectly the Photo rendered with some jagged edges. You can find the Designer and Photo files and the screenshots of my settings in both the apps. Please confirm if this is a bug or not? Thanks, Sanal
  2. I think it would be much easier if you could copy paste this info from within the Help > About... window, formatted the way Serif wants to see the info (and in a way that it displays correctly on the forum) and what you want to see. That's how its done in FreeCAD, where versioning is also important to take into account regarding bugs, see: Unlike a signature, this always ensures the relevant info is up to date with OS updates and such.
  3. Case-Sensitive Forms are an OpenType feature designed to replace some glyphs with alternates when All Caps is applied. (Official description here.) Activating Case-Sensitive Forms (a checkbox in the Capital section of the Typography window) should have no effect except when All Caps is applied, but currently Case-Sensitive Forms is replacing relevant glyphs whenever the feature is activated regardless of case. In the examples illustrated here, Case-Sensitive Forms include and upward shift of hyphens and parentheses for Abril, Lygia, and Albertan and a switch from oldstyle to lining numerals for Abril and Lygia. All of these behaviors are correct in the right column where All Caps has been applied but incorrect in the left column where case is unchanged. Additionally, activating Case-Sensitive Forms forces capital letters from Lygia. I suspect that there is something different and/or wrong with Lygia’s coding but note that it would likely not matter if Affinity’s handling of Case-Sensitive Forms were correct. Additional notes The same examples exported from Adobe InDesign 18.0 is included for comparison. As far as I know, it is not possible to turn off Case-Sensitives Forms in that program. This issue to be affecting Publisher v1 as well, but I think it might be a new issue. PDFs I have exported more than a few months ago do not show this unexpected behavior, but I’m having trouble finding definitive evidence that I had Case-Sensitive Forms turned on at that point. Minor nit: ‘Case-Sensitive’ should be hyphenated in the Typography window.
  4. Currently we have to work around this bug by limiting the page range because all value pairs are global. This could be fixed if the data sets would be referred to by their file name instead of loading all the files at once and telling the files where they can be loaded instead of referencing from where they're needed. Example: source.json:string_name This would also make the Data Merge more robust and enable it as a normal object that doesn't require everything to be baked into a new document.
  5. Affinity crashed when I used the photo stacking function After starting again a bug report window was displayed I clicked submit, which caused an instant crash Now affinity wont start anymore I tried uninstall and reinstall of the latest and previous versions, nothing helped.
  6. I'm exporting my vector graphic as an svg. When I open the svg in Firefox or Google Chrome most of the colour is missing. I think all the missing colour is the gradients My SVG is filled with stuff like fill:url(#_Radial2) but I can't find anywhere in the file where #_Radial2 specifies a colour Unchecking "flattern transforms", "use hex colours", or use "relative coordinates" had no effect --------------- I uploaded screenshots of my export settings, as well as what the SVG looks like in a browser, and also the SVG file itself trombone.svg
  7. Hi, recently I came across a bug or a strange behavior in the Publisher. When I try to open the Text Style palette, Publisher takes some 15–25 % of the CPU and freezes. Also it takes more and more memory till it's full. I've been working on a document for several days now and today I encountered this. The other documents are fine. Also opening a backup file I do every day doesn't help. Does anybody have a clue, what's going on? Is there a way how could I figure out, where's the problem? I am on the latest Publisher and the latest Windows. Thank you very much!
  8. I think I may found a bug concerning margins on making a new master page. Please repeat the steps. 1. Make a new master page. While the dialogue prompt comes up specify the following margins (as an example with page/document size of 1080 x 1920) Left: 120 px Right: 120 px Top: 250 px Bottom: 250 px Click OK. You will notice the bug, such that the margin specifications for "Left" and "Top" seems to be switched. To fix this, you'll have to go into Guides and fix the "switch" between "Left" and "Top." Once you press OK, you'll see the intended margins aforementioned. I was able to verify the bug by making another master page and purposely substituting "Top" margin as "Left" and vice versa. Once you OK, you'll see this new, master page looking as correct and intended and going into Guides Manager, you'll see the margins correctly correspond as intended.
  9. I stumbled upon this problem testing Publisher on both Windows 10 and MacOS (Sierra) and working on one document on two systems. First I created a document on a Mac - just a few pictures in presentation. All files were saved in cloud (I use SYNC.COM for synchronising files on a few computers). When I reopened the same document on a Windows PC - Publisher couldn't find missing resources and asked if I want to locate them (the SYNC folder on a Mac and a PC have different paths so Publisher can't locate resources automatically). After locating just two files (the pictures where in two different subfolders) - Publisher found all the other resources but the preview of pictures on the layout where not updated and look pixelated. So I had to replace all the pictures manually (update button was not active in the Resource Manager). Then worked more on the document - adding numerous images... saved and synced to cloud. Later I opened the document again on a Mac – same situation – Missing Resources – Publisher asks to locate them – I find all the folders, pics get found but the previews again are pixelated... Technically everything looks fine, the links are OK in the Resource Manager... but not only the previews are low quality (like the links were broken) but also when I export the document to PDF - the pictured don't appear at all in the PDF! Looks like the Resource Manager thinks that it updated the links but actually the links are still broken. So again I'll have to relink all the pictures manually. Any ideas how to update the links in bulk?
  10. When I try to batch process using the parallel processing capability, some of the files are not processed. The missing files are not always the same. This happens when processing to JPG or PNG. No issues when exporting to TIFF, EXR or when NOT using parallel processing To recreate the problem: 1-Create 1 aphoto file with something and save it in a folder 2-Copy and past that file several times (I created 272 copies) and rename them for easy reference (example A-1, A-2, ...) 3-Batch process all the files to JPG or PNG with Parallel processing ON and to a different folder for easy reference 4-Check the total files processed and compare to the original files For convenience, I'm attaching the test files test files.zip
  11. I've noticed a problem when using the liquify tool on images with transparent background (video attached) To recreate the problem: 1 - Create a new image with transparent canvas 2- Draw something on a new layer 3-Liquify it, making sure the visible grid during liquify is smaller that the canvas size 4-Clip canvas Bug liquify.mp4
  12. I have a situation on Affinity Photo / Designer v 1.6.4 where I need to do two fairly basic things that I can't see how to do: 1) I need to use, write and print text layers with a Right - to - Left layout; arabic text. I copy the text I want to use from other documents and paste it into Affinity and regardless of font or other setting the text is desrever . usable not obviously is This . I can not change this. This affects all characters on the text . The copied data works fine and displays correctly on other applications such as text editing software but the text displays the wrong way around on both Affinity Products. How can this be fixed? 2) I wish to look up the File Details , such as edit times, file storage location and filesize of opened documents in both Affinity Photo / Designer but I can't find a way of doing this. I needed to find the storage filepath of the document I was working on (see above) but couldn't find this information on the program. How can this be fixed? Please Note: I have explored search engines and similar Affinity topics on both these issues but have not found any success. I have also looked through all the menu options within the programs also to no success.
  13. Most of the time (not all of the time, difficult to tell when it will strike) the "Space After Paragraph" setting in the Paragraph panel sets itself to 12pt rather than a default value, regardless of the font size. This is based on a fresh installation of RC2 on Windows 10 Pro; it's effectively happening on the first document I've produced with this installation of AD and I haven't changed any of the default settings. If there's any other details you need, let me know and I'll try to provide them.
×
×
  • 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.