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
    • News and Information
    • Affinity Support & Questions
    • Feature Requests & Feedback
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • Report a Bug in Affinity Designer
    • Report a Bug in Affinity Photo
    • (Pre 1.7) Affinity Range Bugs Forums
  • 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 745 results

  1. Hello guys, I'm on the latest 1.7 version in Affinity Designer. I noticed that when i select a color by dragging inside the color picker box i end up getting 3 different CMYK values as shown in the screenshot below. I think this is a bug, unless i'm missing something. Can someone explain what's happening? Thank you. Edit: When i minimize the Program window and then maximize it, it shows the correct color in the large picker box, but it doesn't refresh in the color tab on the right until i select another object.
  2. Bug: The pickers do not pick the correct point in the Curves dialogue The graphs in the Affinity Curves dialogues input at the bottom and output at the left Input (bottom) has zero left and 100 right Output (left) has zero bottom and 100 top This can be seen in the following: On a CMYK version of a colour chart I have set two Samplers on the Info panel - the left sampler in the white paper, showing 0,0,0,0; and the right sampler in the pure cyan square showing 100,98,1,3 The curve in diagram 1 shows: a huge spike on the left at zero, from the white of the paper zero transformed to 87 (from the flat of the line on the left 100 being unchanged by the point top right of the graph These are confirmed by the new sampler values, the blue tinge to the white paper, and the unchanged solid cyan square If I now use the picker and place it in the cyan square, the node created on the graph is bottom left, somewhere around (12,12) in coordinates (second screenshot). First it should clearly be at one end of the line (as the blue square is 100% cyan) and it should be at the right-hand end of the line. Similarly if I reset and use the picker to choose from the white area (with zero cyan) it gives me a node top-right, rather than bottom left. This error can go unnoticed when selecting a single node because the curve will be symmetrical, so, if, say, the point chosen was 80, then the node would be 20, and the resulting curve when dragged down would be down equally at 80 and 20. However when trying to create an S curve, it falls apart (and wastes a lot of time!)
  3. For several builds now clicking on the HSL layer adjustment has been causing Photo to crash
  4. Hi, In first place coment that I very happy with your product, but with the last version I have a little problems: 1.- when I have few minutes working with my wacom intuos pro m (pth-660) sometimes the program crushes, and im forced to close de program with de task admin. 2.- I can't see the brushes when I works with the wacom tablet, they are always the cursor arrow, and i can`t see the form or size. Someone can help me? thanks in addvance.
  5. 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
  6. Using Affinity Designer 1.7.0.367, on Windows 10 x64 version 1809. Save As option is broken for any document I try to open and save. I have attached GIF with the recording of the error. Milan Petrovic
  7. Hi, since last update, I can't move my brush size ! Slider does not work at all. Is there a way to fix that? I'm on the latest version of Affinity for iPad. And I'm working on an iPad pro 12.9 OSX 12.2. Thx for your answer.
  8. Hello everyone, I'm having an issue where both Affinity Designer and Photo stay at "Not Responding" for about 3 minutes when starting up the program and THEN it opens fully. Basically it is super slow to open. This is a clean install as I just bought the software and there's nothing else running on the PC and the PC is still new and running well so it's clearly a problem with the software. I already tried changing the performance options (Renderer to the dedicated GPU instead of the iGPU which is the default for some reason. Also tried WARP). As for how well the program runs once it opens it's, meh, it runs jerky, zoom animations are slow and panning is super slow (This is NOT 60fps as advertised, more like 5fps) BUT if I use the touchscreen it works quite well, much better than the touchpad. I tried the software on a Mac and it was amazing but on Windows it kinda sucks so far. My Specs are: Windows 10 Home (1903 / 18362.145) Intel i7-8550U RAM 16GB iGPU: Intel UHD Graphics 620 dGPU: Nvidia MX150 EDIT: It appears that panning and zoom have improved somewhat! But sadly it still takes super long to start and still says "Not responding".
  9. 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.
  10. When i use brush with presure sensitivity, the brush make a weird line and make chopy shape i dunno my device not compitable or what (my devices is ipad 6 2018) i need brush for making font, any one have the same issue's here? help me to solve this D18B7D97-D185-422C-8E05-374BC510AC19.MP4 A815AFBA-86AA-4735-A17B-FFC3527004A0.MP4
  11. The Gradient Fill palette(?) at the bottom of the screen is not always indicative of the fill of the shape selected. In the attached video, notice the indicated fill types of the shapes being selected. Also, notice how the linear gradient tool freaks out a bit as you select between shapes... A92393BC-9ABE-4995-9829-E0E356226E93.MP4
  12. matisso

    Brush zoom bug

    Hello, Today I needed such a simple drawn shape and thought I would do it in Designer, since I convinced my employee to buy a licence. However I ran into a strange and annoying bug – merely upon changing zoom level, the brushed stroke changes its appearance. I have included the link to an animated gif that shows the shape at 75, 100, 150 and 200% zoom and a source file as well. What’s even more frustrating, I actually discovered it after i had exported the PNG file at twice the resolution and found out it the stroke changed in it. Try opening the attached .afdesign file (Windows 10 at my end here at work) and clicking Ctrl + + and Ctrl + - and see the stroke going “alive”. Please see this: https://imgur.com/a/8F7DUB5 Regards, Matt brush-bug.afdesign
  13. Hi I am using Designer 1.7.0.367. The app does not respond to ANY keyboard input - be it shortcuts or even text. Accept importing the frankentoon nature brushes there have been no customizations. As seen by this text, the keyboard works properly on all other apps . How do I solve this?
  14. When scrolling up down, the grid scrolls too? See screenshots
  15. When you edit the gradient in a Gradient Overlay effect, and you turn the color of one side to 0% opacity and THEN try to change the color of that color, the color selector window immediately closes after a single click. It does make the change, however. You can also set the opacity to 1%, select your color and move it to 0% afterward. Why would you want to change the color when it's 0% opacity you ask? Because it still affects the transition and blending of the gradient from one side to the other.
  16. If you accidentally switch to separate mode, which I did, I cannot switch back to Merge All Windows. Does not work any longer after the new update.
  17. Hello! So, these new versions look great and I'd love to start using them, but I have some weird problems going on since the first beta release. I use my wacom tablet all the time, and I'm used to scaling brushes holding Alt + Lclick & Rclick, which I do after assigning such a modifier to one of my wacom pen's button. It works perfectly in the stable 1.6 versions of Designer and Photo, also on Photo 1.7.0.367, the latest release. But whenever I use the same command on Designer 1.7.0.367, it doesn't work. It just paints, as if Lclicking and dragging. This is one problem. Also, all of a sudden, the software stops getting instant feedback from my brushes/pen. I click and drag, but it only updates when I release the click. Did anyone else encounter these bugs? I can upload stuff to showcase, if needed. Thanks
  18. Pen tool suddenly switched to pixel default over the weekend and won't switch back to points. Every time I draw a line and try to change it to points it automatically reverts back to pixels. I now have to draw the line, click on the pencil tool to change to the desired point size. Very annoying. Noticing a lot of bugs with this update.
  19. Hi all, My name is Andrew and I'm graphic designer of Eurosud Cataldi srl (in Italy). Today I have notice that my pen not work proprely in Affinity Designer only (work very good with Affinity photo and Krita). My pen not cover all the screen in AD and when I go left for select vector brush it jump on right side of the screen. How is possible that few days ago it have worked relly good and now is broken? Can anyone help me please? PS: I have two monitor and all pc driver updated. Sorry for bad English
  20. Just been playing about with the new Guides Manager. Whenever I edit the margins, it instantly reverts back to what it was before (both typing the number and using the arrows). When editing the margins under Document Setup everything works fine, including updating the numbers shown in the Guides Manager.
  21. After the update, everything crashes and I have a deadline! How the hell can I roll back? I am dead in the water. Every file I try to open, the app crashes continually! I just updated and now I need to rollback. This is an emergency as I have a freaking deadline in a few hours. HELP!!!!!!! Update: Found someone with the same issue, it is a bug. Was about to find a temp workaround, I think. Went to preference and saw it defaulted to Metal and I switched to GPU, at least I can open a few of the files. Still testing. I had no issue whatsoever with the previous version and I have been a long time user. Mac Settings: AMD Radeon R9 M370X 2048 MB Intel Iris Pro 1536 MB Complete log attached crash.dmp
  22. Hi, I just purchase the Affinity Photo at Mac App Store. After installation, I tried to start the App and it crash after it show the start up banner. I am using iMac 2011 21.5" with Radeon Pro WX7100 eGPU on macOS 10.13.6. Any log / stacktrace I can provide for this issue? Thanks!
  23. 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:
  24. Hey there, I really like the performance optimizations, but I found a really ugly bug. The menu on the right side has fuzzy letters. When I'm moving it to my external display and back, everything is fine.
  25. 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
×