Jump to content

Search the Community

Showing results for tags 'Bug'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support Forums
    • News and Information
    • Affinity Support & Questions
    • Feature Requests & Feedback
    • Bugs in Affinity Designer & Affinity Photo
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Affinity Beta Software Forums
    • Affinity Designer Beta Forums
    • Affinity Photo Beta Forums
    • Affinity Publisher Beta Forums

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 721 results

  1. For several builds now clicking on the HSL layer adjustment has been causing Photo to crash
  2. Hi there, I have encountered a strange bug when working with PDF exports. To be more precise Overpass as a font. It gets exported as bunch of symbols instead of letters. Tested. Not a bug in my file, nor software (friend tested it as well) Link to download Overpass: https://overpassfont.org What it was supposed to look like: What I got in the PDF: My export settings:
  3. mje3748

    Huge Crashing Issue

    I'm trying to tidy up my portfolio for the summer, but everytime I open up a project in Affinity Designer and go to studio -> color -> and then try to make a color adjustment the software crashes. It does this mostly when I start to do things other than resizing and moving things around... so basically trying to perform anything further than that makes the software crash. I have tried uninstalling and reinstalling and updating (no updates are available) and still nothing works. Also, the layout of the screen seemed to have changed somehow during this process. When the application opens, my home screen no longer automatically brings up the layers or color wheel or anything. And then, trying to get them back and use them crashes the software. Super annoying. I am going to attach the error message that I get everytime the software crashes. I copied and pasted it into a pdf file. PLEASE PLEASE PLEASE HELP. I don't want to have to go back to Adobe Illustrator. Crash.pdf
  4. Hi! I've noticed quite an annoying bug when selecting and moving raster artwork within Affinity Designer's Pixel Persona. I've noticed this same issue in Affinity Photo, as well as the latest beta versions of Designer and Photo, and I have no clue why it happens. When drawing with something like the pixel brush or any brush that has a hard edge (with little to no anti-aliasing), the artwork blurs when being moved, but only when selected with a selection marquee tool, such as the lasso tool, first - see attached screen recording. This leaves a very visible difference between the selected and moved and unmoved artwork, and is even visible at 100%, which is obviously a big no-no for client work. Not totally unrelated, the selection path also seems excessively jagged on screen in comparison to something like Photoshop. I often use the selection tool when colouring my work, but the edge is noticeably jagged, even when zoomed out to 100% as well. I initially thought this may just be the pixel preview, but the jagged edge is very present - see attached screen shot, and it's also very present in the screen recording video too while making the selection path. As a final side note, a Wand Selection tool in Designer's Pixel Persona would be SOOOO helpful. Anyway, I'm not sure if these are bugs, but any advice or workaround for these things will be greatly appreciated! Screen Recording 2019-05-10 at 09.03.56.mov
  5. SunnySaul

    AD Smudge Brush Bug

    Hello, I am having a bug every time when using the Smudge Brush Tool. Some brushes crashes from the first try, some takes a little longer to crash after a few strokes, and some can last longer by changing the brush size, opacity, flow and/or hardness. But the bottom line is: it always happens and happens after a short while. 1. It is not dead pixels (It can be erased) 2. Happens every time with every brush only when using the Smudge Brush Tool 3. Happens both in Designer and Photo 4. My AD version is current (1.6.5.135) Any tips, answers or fixes, please reply. This tool is paramount for my workflow. Regards,
  6. I have been trying and trying to get Slice Export to work for me on Affinity Designer iPad. I watched the tutorial video on how to do it. It just doesn't work for me. I tried exporting to iPad folder and also to various iCloud folders as well, nothing, it just doesn't export anything.
  7. It is happening during zooming or moving an object, which is above the text. It's really annoying and shouldn't happen in non-beta version...
  8. Hi there, I'm working on AFD Beta 1.7.11 on MacBook Pro from 2018 with Mac OS X 10.14.4 and have to report a very serious problem with file saving: After working for some days on a larger project I saved the file (to iCloud), exported a PDF and quit working for this day. The other day upon opening the file I was prompted with a dialogue box asking if I would like to restore from a previously stored version (like after a crash). Not thinking about I clicked ok and AFD opened a version of my file which reflected the status from tow days or so before – all subsequent work was lost and couldn't be restored. I made a copy of the file leaving the original file as it was, double checked all relevant settings (i. e. restoring intervall set to 300 seconds) and started again this time working on the copy. During work I manually safed on a very regular basis every few minutes. After being ready I once again exported my work as PDF, saved and quit the app. Upon restarting the app and reopening the working copy file, once again the file didn't reflect the last saved status (the one I exported the PDF from) anymore. This time not as many parts as before where lost, but all parts done within the last two hours of work before quiting were gone. Different to the day before no prompt appeared. I haven't used the Beta again since then but went back to 1.6.1 so I can't tell if this is file specific or not. But I can definitely confirm that the file was saved over and over again manually including the last version before quit (the one I exported the PDF from). I can also confirm there wasn't a crash or forced quit before this.
  9. When scrolling up down, the grid scrolls too? See screenshots
  10. Ernest

    Incorrect SVG import

    I have SVG file that imported incorrectly in both Affinity Designer and Photo. 112.svg
  11. So I'm using pressure on a stroke. I was having issues with it distorting when using "Expand Stroke" (where smooth curves were changed to chunky edges). In another post on this forum, someone suggested enlarging the object and then expanding the stroke. In doing so, I discovered this super bizarre bug. See the attached images I show when I zoom in to one of the corners. I also show the expanded stroke and all the countless nodes. This is unusable if I ever want to expand this kind of stroke. Am I doing something wrong?
  12. Has anyone of you lovely people experienced issues with guides? They used to work ok - a bit buggy, but now they're completely broken. If anyone has a hack to unlock artboard guides on ipad pro I'd be so grateful! When I navigate to guides>show guides I can't move any of the existing guides, the only function I can perform is to add new guides - but even though I can add guides, these cannot be moved by hand/apple pencil (only by adjusting coordinates). Many thanks.
  13. Im getting into some sticky mud here. I'm the technincal administrator of an architectural office in Norway. I am advocating for the use of affinity products instead of Adobe after using your apps privately and finding it a positive experience. So we are trying to evaluate using Affinity Publisher at our office and everybody is trying it out, but today it did not want to open, saying a usual "the beta is too old, download the new one...". I downloaded the newest beta but upon running it says "Setup Failed"... I then repooted, ran as admin but nothing works. Now I wish to get rid of the program on our system but it cant uninstall saying "Another program is being installed"... I now have everybody else who use Affinity at our office staring down my neck asking me how to solve this. Any advice would be greatly appreciated as I feel as if im well into a deadend here... I have attached the failed setup log files. Setup.log SetupUI.log
  14. 1.7.0.105, .106 This was fixed, but now it's back (see thread 8799). I have a photo in portrait dimensions (= height > width), I click on 1:1 -> the crop happens within the photo, as it should. I have a photo in landscape dimensions (= width > height), I click on 1:1 -> the crop happens around the photo, adding empty space within the crop. Please fix again. Edit: Will be looked at
  15. I just purchased and downloaded Affinity Designer last night. I attempted to open a .ai file with it, and was met with an error regarding permissions. I also tried to save an Affinity project (.afdesigner), which was met with a permissions error as well. The error reads: I am only able to read/save files in my newly created Affinity Designer iCloud storage, which is not the workflow I will be adopting. Before anyone flags this as a duplicate or writes this off, know that I have: Tried saving to/reading from multiple directories within my home directory, not limited to my Documents folder. (eg: ` ~/`, `~/Pictures`, `~/Downloads`) Used CleanMyMac3 to repair my disk permissions (multiple times) Manually reset permissions on my home folder recursively to all subdirectories and files (Right click > get info > Permissions & Sharing) Manually reset permissions on my home folder via terminal Ran First Aid via Disk Utility Restarted my computer (between each step) Cleared Affinity Designer's data by holding down Ctrl while booting Uninstalled and re-installed Affinity Designer I've read that this is related to Apple's sandboxing. Regardless, it seems insane that the program can't interface with my hard drive. My email client, writing apps, and video games downloaded from the app store can, without any issues ever. Why can't Affinity? Also, if this is an App Store issue that is reoccuring, why not make a standalone version... I'd prefer that anyway.... Double bummer because I was so thrilled to be replacing Illustrator with an allegedly superior project at the cost of only $50. Hoping someone can help me.
  16. Publisher Beta, v1.7.0.293 for Mac: 15" MBP (2017), Mojave v10.14.4, 2.9GHz i7, 16Gb ram Since the latest Publisher update, whenever attempting to export pages from Publisher Beta, Atom (code editor) opens "tempimage_#.ext" files. I have not opened or modified Atom since prior to the last Publisher update. I have since disabled all Atom packages and restarted my entire system with no change in behavior. This happens for Publisher projects with one, several, and many pages... I am using master templates on all pages and have not confirmed if this occurs when not using templates. Additionally when in the export dialogue and I select a different file type to export to, Atom opens more windows. The export has been working despite this behavior.
  17. GolHello, I’m new to Designer on the iPad and have run into an issue when I drag and drop images from the web using slide over. I can place one image in the document ok, but when I try to drag a different one in it places the previous image again instead. Not sure if it’s a bug or if I’m doing something wrong. Any help would be much appreciated....
  18. Firstly I did a quick search here to see if this is a new issue but I didn't find anything with this exact issue. When I create a document and turn on the grid for snapping everything works as expected until I change the grid type to isometric or oblique, etc. After doing so the snapping locations are misaligned to the grid, even if I change back to the default grid layout. Please see the attached screenshot. Affinity Designer Beta 1.7.0.284 Windows 10 Pro Version: 1809 OS Build: 17763.379
  19. Number increase insanely when use mouse wheel change value on the input field, no matter scroll up or down, number going bigger...
  20. Hey everyone! When opening Document, Resource Manager, selecting all files and setting them to linked, my document will still be at 109,3MB file size. In fact, before linking the unlinked images, the file had 108MB. So linking even increases file size by a small amount. The Resource Manager will show them as linked and Publisher will report errors when renaming a file. It just doesn't decrease file size. And even when Publisher cannot fint a file, it is still being displayed, instead of an error frame, which I would expect. Is this a known issue? It seems it shouldn't be since there is a tutorial on the website for this. I am using High Sierra. Best wishes, Shu
  21. Hi when using any brush with pressure control, the stroke goes mental and glitches out - making it impossible to see what I’m drawing. I’m up to date on all software and have no issues with any other illustration apps on my iPad. D542FB05-5721-4194-AF5B-734D1E01D91D.MOV
  22. Hello, this bug is being discussed in another thread, but since it's being ignored by Developers for pretty long time, I decided to refresh it by creating a new topic with some new facts and a solution. "Merge Down Layers" (Ctrl+Shift+E) is very common and frequently used command, that we use to merge layers. Although it can corrupt your image in a lot of random cases by blurring you layers after merge. You can see what happens to layers if that occurs on attached image. After 1 merge you are losing sharpness, and after 2 or 3 merges you will start to notice that image got blurred, but it will be too late – your file is already corrupted. I attached *.afphoto file, so you can reproduce bug and see why this happens. I already found a workaround in the past, which is super annoying, but better then nothing – Create Empty Layer (Ctl+Shift+N) and merge down to this new layer. But today I found an ultimate solution for Affinity Developers, which is super easy to implement, and I hope they will do it ASAP: If you rastirize lowest layer before merge, nothing will be corrupted. So before Merge we should automatically rasterize lowest layer, and then we will never corrupt our image again. Some important facts for Affinity Developers: I attached *.afphoto file, you can reproduce the bug I reproduced bug in Beta too It's not because of "Force Pixel Allignment" or "Floating point coordinates" This is critical bug, that corrupts our work (I corrupted my images without noticing, other guys from previous thread also corrupted 4+ hours of work) This is not intended behaviour, please pay attention to this one and put yourself in our place This never happened in Photoshop with similar actions To get "bugged" layer you can resize existing normal layer and it becomes corrupted for future merges To fix this bug you just need to automatically Rasterize lower layer before "Merge Down" operation Thanks, hope you fix this asap and notify us! Corrupted Merge.afphoto
  23. Changing line size in the transform panel causes weird behaviours(disappears completely and can't undo). See attached video. Line Transform Input Bug.mov
  24. Designer is not rendering the content of the file correctly on the second monitor This is what designer looks like on the primary montor with 100% DPI setting. This is the same window that I have dragged over to the secondary monitor with 125% DPI setting. The drawn graphics has the wrong offset and scaling. The selection is still correct. any mouse actions, drawing and moving, works correctly, I can move the window to the primary monitor and see the correct result. It appears as the rendering is the problem. Affinity Designer 1.6.5.135 Windows 10
  25. This subject is being discussed in two other threads. But in each case, the discussion has shift towards peripheral considerations, leaving no chance for the initial question to be answered. I voluntarily put here no links to those threads in order to prevent readers to be parasitised by pheripherical and noisy considerations. What should be strictly discussed here : The "Merge Down Layers" (Ctrl+Shift+E) , a very common frequently used command, in some case (see details below) currently corrupts the image: contents of merged layers are blurred. Question: is there a good functional reason for this function to work so, knowing there's a simple way (doing a rasterization of the bottom layer before merging) to achieve the expected result : a merge that simply preserve the data of each layer ? Or is there currently an option to be activated to achieve in any case automatically the expected result ? Details : afphoto file attached to reproduce the bug reproduced in : 1.6.5.135 and Beta on Windows 10 and 1.6.11 on macOS Sierra reproduced with "Force Pixel Alignment" or "Floating point coordinates" options on and off: those options are no way a solution to this problem. a simple way to reproduced the bug with two pixel layers is to apply a transformation on the bottom layer before merging (note: by doing so, coordinates of the layer are no more integer ones) a simple way to prevent it : rasterize the bottom layer before merging For many users, the current behavior of the merge function is a fondamental problem (you can corrupt your work with one click if you're not aware). We would be glad to have an answer to the question above or the function to be fixed. Cos there is no technical limitation considering our use (it may not be elegant, but the merge function could simply process a rasterize operation before applying, which is the manual action required currently if you want to preserve the quality of your image). PS: actually, there's a video that illustrates this tricky behavior here Demo . See the seventh post
×