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 705 results

  1. Number increase insanely when use mouse wheel change value on the input field, no matter scroll up or down, number going bigger...
  2. 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
  3. Changing line size in the transform panel causes weird behaviours(disappears completely and can't undo). See attached video. Line Transform Input Bug.mov
  4. 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
  5. 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
  6. This is something I have noticed in plenty of software over the years, but I'm posting here because I'm currently having this issue with Affinity Designer (desktop). See attached image at full resolution for an example. I am making a lot of tiled patterns that need to connect seamlessly. I create them with a grid and am careful to snap my points to the grid perfectly. The coordinates in the info panel confirm this. Yet my shapes do not always join and I can see the background between the hairline gaps that should not exist. Why does this happen and is there anything I can do to fix it? (I have been moving my points to ensure they overlap in the final product, but I consider this a hack; if I want to continue working on a pattern I then have to snap all of the points back into place manually.) Notes: As you can see in my attachment, sometimes the shapes DO connect seamlessly. There doesn't seem to be any reason why some places have the gap and others don't. This isn't a factor of zooming. I can zoom right out and still see the hairline gaps. This isn't just a AD display issue. I am exporting these as raster files and the gaps are still there in the finished product. Another side effect of this is when I Boolean join my shapes, they often don't add together nicely. This is actually really annoying.
  7. 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
  8. Hi, I have just installed a new version of affinity publisher but I cannot open png or jpeg files anu more, the program simply does not see them... I hope it was not the plan, was it? Sincerely, TK
  9. Hi, I’m having a glitch while using the Affinity Photo app. The version is 1.6.12.86. The iOS version on the iPad Pro 12.9 inch 3rd gen (2018) is 12.2. Basically the problem consists in that when I make a new document (in this case a print a4 doc), and make a pixel layer and start drawing with the paint brush tool, I get slight artefacts on the screen (like blocks or squares or so, and they disappear and reappear randomly). I have seen in other forums that some are also having this issue, but just with the latest iPad Pro versions (11 inch and 12.9 inch, 3rd gen models). It’s a really annoying thing, since I want to use the program for sketching and drawing a lot and this makes the experience really bad, considering it’s an otherwise excellent application! Here’s a video attached so you can understand it better. You can see the first glitches at 0:56s, and major glitches at 2:13 (which is what I normally experience a lot). Thank you. 5856E5F3-D0C3-4B14-BA1E-C19DB1BA32A8.MP4
  10. 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.
  11. Hi guys :) loving all your applications, Ive been playing with publisher for several hours and love it, But, I experienced 2 crashes so far with the program while a duplicating text and moving that text, while I was holding down the left mouse button and moving the text, thats when the program crashed. Im new to your applications, so I dont know where the crash files are located. :) anywys, just wanted to report the crash. thanks :)
  12. In the first place I wanted to post in Suggestions, that the change of values with the triangles e.g. in Table Insets are ridiculous small. But then I remembered Preferences User Interface where you can define the Decimal Places for Unit Types. Changing values there left questionmarks on my face for the rest of the UI. We are just talking here about millimetres, table insets and the tiny triangles to change the values. If other parts of Publisher have the same "bug" I am too lazy to search for right now. Observation 1: Changing values for Decimal Places requires a restart. This information is missing here. Observation 2: If the Decimal Place is set to 0, then there are 10 mm-steps when you click the triangle. Means if the inset is 2 mm next step is 10 mm, then 20 mm etc. pp. The width of the cell has no Decimal Place. Observation 3: If the Decimal Place is set to 1, then there are 1 mm-steps when you click the triangle. The width of the cell has 1 Decimal Place. Observation 4: If the Decimal Place is set to 2, then there are 0,1 mm-steps when you click the triangle. The width of the cell has 2 Decimal Places. accordingly for 3 to 6 Decimal Places. Seems to be that the Decimal places are miscalculated. No Decimal Place from Observation 2 must lead to 1 mm-steps and not 10 mm-steps. EDIT: Hmm, a few minutes more thinking makes me happy with the bug. One Decimal Place for millimetres is enough and 1 mm-steps for changing values would be perfect. OR: Correct the bug, BUT please NO decimal steps where you can change values with the triangles.
  13. ** UPDATE: it appears to be a bug with snapshots ** text i see on screen dose not match what is printed. so this is just a odd bug when printing it prints out a Chinese or Japanese symbol for some reason even when printing to PDF or a xerox or IBM printers they all have the same symbol at the end of the text but it is selective on which one it prints the symbol on as you can see on the print as seen in the png files below (yes i know the design is ugly at the moment there is a bit of malicious compliance here)
  14. When I replaced images in a publisher file. the ones in "portrait format" were inserted as landscape, minimized to fit the image box. I opened these in affinity photo turned them once anti-clockwise, then back and saved them. After this they were inserted correctly in Publisher. PS: I think there isn't a function which is very useful in InDesign when you want to replace/ relink your images. There you can use it to replace every image in the file at once by linking it to a another folder ( that has image file with the same names in it).
  15. AF Pub v1.7.0.283 Mac OS X 10.13.6 I'm trying to create a new table: Turn on Text>Show Special Characters Click the Table tool to insert a new table. Draw the Table on the page. The special characters for the cells of the table are not where they should be. See the screen capture below. As you can see there are no special characters in the first two rows and a row of special characters shows up under the table. The Text Style box shows that there are two text styles applied to the table text: Text Box+REB-RuleEndOfBlock. The RuleEndOfBlock style is used to put a ruled line at the end of the section as a visual queue that the reader is at the end of that part. Table Body + REB-RuleEndBlock + Align paragraph: Left; Align to baseline grid: On; Left indent: 1 in; Right indent: 0.1 in; First line indent: 1 in; Paragraph decorations: off I detached the table paragraphs from the text styles, then reapplied the Table Body text style. When I applied the Body text style to the text paragraph above the table, the table text style changes to become Table Body + Body. The text style now shows: Table Body + Font size: 11.3 pt; Default tab stops: 0.944 in; TabStop: 0.944 in; TabStop: 1.889 in; TabStop: 2.833 in; TabStop: 3.777 in; TabStop: 4.722 in; TabStop: Right 5.666 in The second image is what I see when I try to enter text in Row 1. Also note that the column letter cells are not lining up with the body columns. Even if I detach the text styles, the text is misaligned with the table. I attached the sample file that I'm working on. IM Document Template.afpub
  16. Hello there, As much as I'm loving the new Brush Editor features, there's a bug that's been around since the current stable Designer and Photo versions. I've reported it a couple of times already and I hope this issue gets addressed, because it really ruins the experience when using advanced features from the brush panel. When you add the Wet Edges option to a brush (from the editor), this option gets deactivated or non-recognized back when switching tools using the brush command key (B) and many times, when selecting the brush manually from the brushes panel. Let's say I need to erase something; I switch to the Eraser using (E), then I want to go back to my brush using (B) and when I do that, Wet Edges are switched off automatically, unless I double-select that brush... then, Wet Edges are back on. It totally ignores the stored brush settings. This affects dramatically the way brushes were originally designed. Thank you!
  17. Blend options are Broken in CMYK Modus: Bug: I try to remove a one color layer with "Blend option" but instead of removing one color its remove Multiple colors! (BGKru33tJI.gif) If i set "Source Layer Range" only to 0% (blendOptions.jpg) it don't remove the full channel color, still have black in my image. Future Request: What i would expect that in the background of "Blend options" should be a histogram for better fine-tuning. (blendOptionsRequest.jpg) Here some examples
  18. Hello Team i've been working on a project to check the new AFPub .270 but noticed: The software crash every time I tried to reorder the pages using the drag and drop method. i Tried to re-order one page at a time made the software crash. i Tried to re-order couple of pages (4 in this case) made the software crash Note: This Manual Re-ordering of pages was 100% working in previous version ! Suggestion: Not only it would be great for this to be fixed but, Dev's should implement a complementary method of Page re-reorder instead of havong only one way to do that, thus putting us in safe land; if one fails, we can use the other method. Blessings !
  19. Vernite dengi

    Project was missed

    When I rename my project names in folder, the folder was imported in itself. Few seconds later I was kicked from this folder and it was missed with projects inside it. Affinity Photo, iPad 6th generation.
  20. aenimanu

    Vector brushes go crash

    Hey there! So, I just bought the Grave Etcher vector brush pack and installed it. Everything seemed to work fine until it crashes the first time. Normally, I use to ignore the very first crash in awhile, but after the second and third crash, I tried installing the pack in Affinity Designer Beta to check if the error is still happening. The same error prompts (program suddenly quits). My current laptop is a macBook Pro from 2017, still much memory available and no other software is running at the same time aside from Spotify, so I guess it's not a memory issue. ¿Has anyone had the same problem with vector brushes as well? I didn't have issues with other vector brushes so far, so I hope it's not a failure of this very pack. Cheers and thanks!
  21. Mac version app 1.6.7 The preferences panel shows the English language when the system is set to Italian:
  22. Hello, I've been using Designer on My iPad Pro since it became available and I dig it. However, I've run into a problem whereby the app is using massive amounts of storage which makes no sense. I have very few documents stored, fewer than a hundred, the vast majority of them are purely vector and no more than 5 or 6 include bitmap images, yet Designer is using 352 GB of disk space! looking at the info available it says that the app is using 922 MB and that documents & data are 351 GB. This is crazy! There is no conceivable way that the files I have in the app could be anywhere close to 351 GB. At first I thought it might be related to the fact that I maxed out the available undos in settings, however, today I changed that to 500 and went through each file individually and erased all available history, this however did nothing to decrease the storage. I have also added a number of items to my assets, but they are also purely vector and I can't see them taking up this much storage either. Surely this must be an issue with Designer itself? If Someone at Serif could reach out to me and help me sort this out or explain what is goin on here, it would be very much appreciated as I have been unable to backup my iPad now for over a month due to the massive amount of date required to do so — since I need the iPad daily I haven't been able to allow the 2 or 3 days required to make an iCloud backup. If any forum members have had this issue or know what causes this I would also be happy to hear any advice or suggestions. thanks for reading
  23. I'm not sure if this has been posted. I did a quick look but didn't notice. And maybe it isn't actually a bug and I'm just silly. However I have a document that I was creating images of all the characters supported by custom LCD displays that we use at work. We have one that is a green background with black text, and then one that's blue background with white text. So after I finished with all the green, I started to create the blue ones. I made it so that they actually have all the pixels that you see on the LCD so each character is actually 41 different layers(the backdrop and then the 40 pixels). When I was recoloring from the green to the blue, I'd select all the pixels to change them from black to white. If I chose white with the color picker, and then clicked on it to change the colors, then the opacity of the layers stayed the same(I had 100% opacity for the pixels that are "on" and 10% opacity for those that are "off"). However, if I used a swatch, then the opacity that I had set was blown away and everything was made 100% black or white depending. I did try this on both the Mac and the Windows version and both act the same way. So maybe I'm just thinking that they should operate differently than they actually do? On a side note, if anybody wants some LCD fonts... I got 'em. There's a screenshot of the green background. I know that's from my iPad and not Windows, it was just more handy at the time that I made the screenshot.
  24. I made the mistake of clicking on the minimization arrow in the Assets Panel because I didn't want to see a sub-Category. Now I cannot open any of the Asset sub-categories, and I need to access something there! I've tried going to Window > Studio, and removing the Window from view & re-adding. I've tried resetting the studio view. I can select nothing in the Assets panel aside from the options and the dropdown to select another category. I've also tried restarting my computer. I'm out of ideas on how to get these to open again. Help! Running Affinity Designer Beta 1.7.0.257 on MacOS 10.14.3.
  25. euvoia

    Group Selection Bug

    Group selection doesn't work. You have to ungroup to be able to make selection. See attached video. Group Selection Bug.mov
×