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'.

  • 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

  1. After the 1.6 update, the expand stroke function that wasn't accurate with rounded rectangles before, now is completely broken (see screenshot of a rounded rectangle, circle, and a cog). Upd. It seems to happen only in certain affinity files, not all of them. Regards, Anton
  2. Hi everyone, I was working on a project for a client in Affinity Designer 2.4.0, and suddenly, while I was testing different fonts for a logo, it crashed Windows 11 (blue screen of death). When I restarted the computer, Affinity Designer didn't open the file anymore, stating that it appeared to be corrupted. I'm a professional branding and packaging designer. I charge hourly, and I've already worked 15 hours on this project. In other words, this file is extremely important, and I need someone from the Affinity team to jump in and help me urgently. I've attached the file to this message. Please, anyone, help! Thank you in advance. Tres Five logo.afdesign
  3. Screen Recording 2024-03-10 at 14.49.02.mov Same for cog tool and probably others. V 2.4.
  4. Applying the states takes almost 5-7 minutes! I have to mention that I have 16067 layers.
  5. Hi, There is a problem with my HSL. It doesn't look like it is supposed to. I can't see all the colours as you can see in the image. HSL is usually showing in a form of circle but I have only one quarter of the circle. Thanks for helping, Lauriane
  6. - looks like Smudge tool still not working when applied on pattern-layer. Instead of smudging it add more and more original background color. Steps to reproduce: create pattern layer and fill it with random color. Then apply smudge tool, - instead of no-changes observe white (original document background color) stroke: early report for v1: Note that Blur-brush tool have similar issues when applied on/close to pattern border area.
  7. Problem: When exporting to TIFF, any of the Subject, Tags, Comments metadata fields are corrupted (changed to Chinese characters). Usually the Subject and Tags or the Subject and Comments fields are corrupted depending on scenario. Steps (Scenario 1): 1. Add metadata tags to a TIFF file in File Explorer. 2. Open in Affinity Photo. 3. Export to TIFF unaltered (with ZIP compression). Steps (Scenario 2): 1. Add metadata tags to an image in Affinity Photo. 2. Export to TIFF (with ZIP compression). Steps (Scenario 3): 1. Add tagged TIFF files to Batch process in Affinity Photo. 2. Use Batch process to export TIFF files unaltered to TIFF (with ZIP compression). The goal of resaving the file with ZIP compression is to workaround the bug in File Explorer that saves tagged TIFF (Zip) as TIFF (LZW) at about three times the size. However, I currently have no editors available that can save a TIFF file with metadata intact without corrupting it (this is also a bug in all Adobe products last time I used them, which was quite some time ago, and the reason I would attempt to use File Explorer to add metadata after editing). Side discussion: Compression is an interesting problem. On top of the metadata tagging in File Explorer roughly tripling the file size by converting to LZW, simply embedding a TIFF in an AFPHOTO file roughly doubles its size, and if the layer is rasterised with no modifications whatsoever, the AFPHOTO file doubles in size again (even when saved as a fresh copy to compact it). All of this adds up to massive (and expensive) storage waste. They say storage is cheap, but it isn't cheap enough to want to buy three times as many hard drives at several hundred dollars a pop to do the job of one. For the sake of not sharing family photos, examples are a frame exported from Blu-ray movie for desktop wallpaper. Tags made up to be "typical" (with Unicode characters). [Explorer bug has been reported to Microsoft.] export.tiff original.tiff
  8. Bug Using either the . or delete keys on the iPad Pro/iPad Air 4 attachable Magic Keyboard return (null) when entering a form field for an attribute (I.e. document dimensions, transform tools, stroke size, etc.) The expected result would be 10.4 instead 10(null)4 centimeters when entering a value into the transform or other tools. Delete doesn’t remove text either. For example, if I enter 10.5 and hit delete the then 4, the output should be 10.4 but the systems renders it as 10(null)5(null)4. Temporary Workaround Can be corrected only by using the touch interface to use the calculator’s . And <x| Virtual key. Devices Used: iPad Air 4 (2020) on iPadOs 14.2 Magic Keyboard
  9. EDITED to make clear file 1 and file 2 remained open the whole time, at the same time. Still think the problem is with the "embedding" logic. EDIT 2: now I understand the resource manager correctly, I can clear that description up... Designer 2 version available as of today, 2.3.1 methinks, MacOS 13.latest Ventura intel 2019 MacBook Pro 16inch 1. Open ai file download from domestika.org design course 2. Save to native file .afdesign we shall call this file 1. 3. drop in .psd files 4. make some art boards around all the assets (those already in the file, and those dropped in as PSD's) SIDE NOTE on STEP 4: (weirdly the objects within the ai file didn't appear to have an artboard at first opening in designer, a black bg in designer around all the files, but then dropping in new psds, they were only visible in the overlapping area with the including objects, invisible if dragged off the overlapping area of the original objects. So I had to make an artboard around them, then the document bg became gray (I later changed this since I didn't like that) but then I noticed in layers panel, there was only 1 artboard, the one I had created.... weird to me that there was an invisible "implicit" artboard from the original ai conversion/import? Let me know if this is supposed to happen? I have LOTS of ai files to deal with (as I'm sure we all do, sigh)... not just this project. 5. make a new design file, we shall call file 2, with several artboards 6. copy (command-c) one of the mb? embedded psd's in file 1 (resource manager lists the path of original file), but, "make linked file" is not available.! 7. paste into file 2. 8. click away until I am using pixel persona tools on the pasted in embedded file in file 2.... unfortunately, all changes I make there ALSO affect the embedded psd object in file 1. 9. confused I open resource manager in file 2 now. it shows the path of the same original psd object/file supposedly "embedded" in file 1.... Again, I cannot "make linked file", its grayed/ghosted/not available. But resource manager already considers it embedded in the file list, just as in file 1... on the other hand, since designer thinks it's correctly embedded, I cannot MAKE it actually embedded. So files can neither be properly embedded, nor linked in these two files. I played with another new afdesign file, dropped a jpeg in there, and it's fine, it says embedded, but the "make linked file" IS AVAILABLE. In the meantime, I will simply drop a new copy of the file from finder... but that sucks... b/c I Did some work already on a half dozen such objects in file 1.... which now is not copyable without "linked" editing behavior... I've done my best to be clear here. Hopefully this can be explained, or if not, squashed like a bug! Thanks for giving adobe a run! Things like this sorta suck though... sad face...
  10. Handy Pinning panel is listed in Studio/Text but it seems it does not exist in (exceptionally badly done) Shortcuts settings. Anyone knows where did that little Pinning rascal go?
  11. This is a bug since V1. When using the official folio case for the 11in iPad Pro in the low angle mode the keyboard will refuse to hide. It will hide and then immediately come back. I'm wondering if this an Apple issue or an Affinity issue but it doesn't appear to do this in any other app so I'm tempted to say there's something in designer that's the culprit.
  12. I'm having some trouble with cross-references in an Index. I have one cross-references (where in the index it says See and shows another index item) that doesn't show up in the index at all. I have many cross-references that show up in the index, but instead of saying See and showing the name of the other item, it repeats all the page numbers that the other item has. And then finally I have a few that properly say See and show the other index item. How do I get them all to display properly?
  13. I have uninstalled and reinstalled Affinity Designer v2 multiple times. I have tried to repair, reset, and even uninstall the old apps to figure out whats wrong. I do not have this issue with affinity photo v2. The moment I hit "export" on Affinty Designer v2, the entire program freezes and will no unfreeze so I have to kill it in task manager. I can open the same files and export them just fine in Photo, I don't know what the issue is. Please help! (I have been using affinity products for years and this is my first issue I have had with any of the programs)
  14. Hi I have tried to stack different light files with different kinds of settings. But they all keep stopping a third into the stacking and nothing furter happens.. Anyone else having this problem? Best regards Lars
  15. I observed strange behavior when it comes to align objects to other objects that are clipped or masked. I prepared three cases, please watch my little demo video. - Case 1: When I try to align the blue rectangle to the masked group, the object aligns to the most left edge of all the items in the group. I would have expected the object to align to the most left visible edge, but I guess the thought process here is that the objects in the group didn't really change their size. By selecting the mask, I can easily change the visible area. - Case 2: The blue box aligns to the visible edge of the clipping rectangle, makes kind of sense, since clipping to my understanding means that nothing can be "outside" of the "carrier object". However I now can't easily resize the visible part without stretching everything else. - Case 3: This is probably the most weird one....If I mask the objects, just like I did in case 1, but this time I mask the objects themselves, not the group, the alignment is just like in case 2 (blue box aligns to the most left visible point). In my mind this is inconsistent: In case 1, the mask of the group was ignored when it came to alignment, however here, the mask matters for the alignment. Can anybody clear me up on this? Is this all intended behavior and I just don't get it right? 2020_02.12-00_31.mp4
  16. Hi, I'm Rawi, I usually draw illustrations for cars. there is something in my designer affinity today I don't know why this happened, before I updated to 2.3 it was safe for the shape builder tool. I used to select all the lines then tidy them up with the shape builder but after I updated to 2.3 I can no longer do that. and not just the shape builder tool, when I use the feature to fill in color it just doesn't work even though it could before. I hope to find a solution here.
  17. I'm using Affinity Publisher 2 on windows but the issue is with the entire Affinity line. I got this free font Aquire Free Font - Download Free Font (befonts.com) Inside the software the font is rendered like this But after export to pdf for example it looks like this The font renders without letter spacing in other programs as well. It's only Affinity issue. What could be the problem? Is there any setting I can change to fix this? This makes the software basically unusable because the final exported image never looks like the edited image...
  18. I've tried to choose exporting with a transparent background (PNG) for this Designer 2 file. The matte is set to nothing but I still get a white background. I've made a quick video to detail all of this: https://d.pr/v/48SVS7 Hope it's a bug and that I don't have to switch the document background every time I want to export a transparent png or gif. Also, exporting to the size of the canvas/artboard is the only option. Being able to simply export selected and/or the entire piece (not the artboard) would be a great way to get exactly what you want and none of what you don't.
  19. A bug in Publisher v1 and v2 causes the table of contents (TOC) layout to go berserk when refreshed because it sponges up unrelated character/paragraph styles from the document. During a TOC refresh, the update function superimposes whatever character or paragraph style is used last in the document on top of the actual TOC styles. This should never happen since Publisher uses independent TOC styles to generate a TOC. For example, if I apply a red character style somewhere in the document and then proceed to refresh the TOC, the entire table of contents will turn red. The same goes for paragraph styles. If I apply a numbered list style somewhere in the document and then go to the TOC to reload it, every TOC entry will start with a number. The TOC only sponges up style settings which are undefined in a TOC style (or its ancestor's TOC style) but defined in the last used document style. With undefined settings I mean unchecked settings or [No Change] settings, anything that can inherit a value. So if I explicitly set the base TOC style to use black text, the unrelated red character style can no longer affect my TOC layout. This workaround works but is impractical for documents that use numerous styles. Since any of these could affect the TOC at some point, you'd need to overrule quite a few settings. Luckily, there's a more suitable workaround, albeit a bit silly. Workaround: Make sure nothing in the document is selected. Go to the Text Styles panel. Set the Paragraph and the Character style to [No Style]. Click somewhere in the TOC to make it active. Refresh the TOC from the Table of Contents panel. The TOC now exclusively uses TOC styles. This behaviour must be a bug. I can't think of any reason why this would be a feature. It appears that forum user Loquos experienced the same issue last November, so I'm pretty sure it's not my setup at fault. Steps to reproduce the problem: Create a new document. Place two regular text frames on the page. From the Table of Contents panel, insert a TOC in frame one. Add a few lines in frame two and apply the default Heading 1 style to each. Go to frame one and refresh the TOC. Edit the TOC style 'Base' and disable the tick mark next to the text colour setting (character fill). Type some text in frame two. Add a new character style and set its text colour to red (character fill). Apply the red style to the text you typed in step seven. Update the table of contents in frame one. The new character style colours the contents red, even though it is entirely unrelated to the TOC layout. When I tried to reproduce the bug in a new document, I noticed that even though the Base style for the TOC is based on [No Style], it is far from empty. Almost every setting in the Base style has a default value. This explains a lot. I tend to defenestrate the default styles when I create a new document. My styles only have values for the settings I need. They don't have default values for unused style elements. This likely caused these daft TOC layouts, but that's beside the point. My approach should've worked just as well. After all, a TOC should never sponge up settings from a random document style. It doesn't make sense, but it is what's going on. I'm using macOS 12.6.3 and the latest Affinity Publisher (2.0.4). I always use the Table of Contents panel to update the TOC. I did not try the Preflight panel's TOC update feature. Hardware acceleration does not affect the issue. Neither does it help to unplug all external hardware. The problem exists in both Publisher v1 and v2. It would be great if the Affinity team could look into this peculiar behaviour and hopefully fix it! Thank you!
  20. I'm on Windows 10, drawing with a Huion 22in drawing monitor. In Affinity Designer and Photo, every time my stylus approaches the screen, the eraser tool is activated. This'll happen several times while trying to select another tool. Clip Studio and Photoshop don't seem to have this issue. Thanks.
  21. I am having difficulty adding a rectangle as a background in Publisher. It appears to be impossible. I have checked the settings, but something seems to be amiss. The white background behind the text is preventing me from seeing what is behind it. There might be a bug causing this issue. This situation is quite frustrating. CleanShot 2023-12-19 at 08.40.28.mp4
  22. I have noticed that many times when I have multiple objects close to each other they seem to have a small gap when I zoom out. I just now zoomed all the way in and there appears to be a gap. This occurs both when I have the "Move by whole pixel" enabled and disabled in the snapping tool. Here you can see a small gap when I am zoomed out and when zooming really really close you can see the gap be there clearer . Does anyone know why this issue occurs and how to set up the settings to eliminate it. I know the issue goes away when I export the image since the gap is less than a pixel wide but it is annoying not being able to preview your picture without exporting it.
  23. Hi everyone, I'd like to bring back a bug report that has been totally ignored since 2021, which I think is urgent and deserves to be discussed. Below you can find two very old threads talking about it. to summarize: the white balance tool is not working properly for non-raw files both in the develop persona and in the photo persona (through the adjustment layers). -what the tool should do: colour pick a pixel and equalize the RGB values to convert the colour of the pixel to a neutral grey (RGB values equal to each other) then apply the same RGB shift to the whole image. -what the tool really does: in develop persona with a raw file it works properly, when used on tiff, png, jpg (etc.) it does not work. What we observed: -the sliders in the develop persona with a raw file open are called "temperature" and "tint" and both of them are properly moved automatically when using the white balance tool, in this case it works properly; -however in the photo persona (white balance adjustment layer) they are called "white balance" and "tint", and only the "white balance" slider move when colour picking the image, we don't see why they should be called and behave differently since it is the same tool that already works properly for raw files in the develop persona. A possible way to fix the bug: -just apply the same rule applied for raw files (in the develop persona) also to non-raw files (both in the develop persona and photo persona adjustment layers). kind regards: Riccardo
  24. Hello, I find it very irritating that files which were edited with Affinity Photo and saved in .afphoto format are suddenly displayed as Affinity Publisher files, i.e. with the .afpub extension and associated symbol. When I click on the file, it automatically opens in the publisher software. But I 100% never opened and saved the file in question in Affinity Publisher. The whole thing gets even stranger: When I view the properties of the file, it shows up as an Affinity photo file! (See photo evidence). This is all totally weird.
  25. If you drag an image (eg: *.png) from a .ZIP file onto a document in Publisher v2.2.1 the application will crash. NOTE: Worked in v1.0. ***Also crashes in beta Publisher 2.30 (2114) MacOS: Sonoma v14.1.1 (23B81)
×
×
  • 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.