Jump to content

Search the Community

Showing results for tags 'glitch'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Affinity Support & Questions
    • Feature Requests & Suggestions
  • 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
    • Report a Bug in Affinity Publisher
  • 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


MSN


Website URL


Skype


Facebook


Twitter


Location


Interests


Member Title

  1. EDIT: * The format i was editing is TIFF16 with LZW compression. Is not a DNG or RAW. While editing a photo, everything is fine but they stop appearing when I zoom in and out, move or apply a brush to areas of the image. However, they remain recognisable by affinity for automatic tracing and adjustments, they are simply not displayed on the screen. When the document is exported, the destruction is still there. If I convert to .psd and open in Phtoshop it comes out fine. i5 12th with 16 GB RAM and Intel Xe 98 CE using graphics accelerator. Latest DHC drivers. Windows 11. When you export, the data gargabe still there. But if you export from PSD and later in photoshop you export to PNG the file it's fine This is a representantion of what happend during the edit, just zooming and panning creates the issue.
  2. Hey I had something crazy happen with infinity designer.. I was using the Fill Tool on my m1 Mac (Metal turned off) and it started getting suuuuuper lagggy, and 5 minutes later my mac told me I had 0 storage left. I checked and found that affinity dropped a 141 GB file into my Mac's private file storage! I resolved this and continued to use the fill tool which lagged a bunch, then poof! Half of my layers started glitching out, they either disappeared or leave weird glitch marks. As i move around the software they dip in and out, but remain gone 90% of the time, Im wondering if there is a way to fix this? I tried exporting and opening the file on an intel Mac. Same issues. Guess the file is "corrupted" even though the layers seem to technically still be there. If anyone has a fix for this or any ideas let me know! Thanks 1872750970_ITISYOURBIRTHDAY.afdesign
  3. I've been experiencing some strange display issues with Affinity Photo recently, where initially the files appear glitched after opening them. This preview goes back to normal (the way it should be) once I zoom in and out a bit, but that initial preview usually gives me major anxiety, as if the file became corrupt or glitched somehow. The pinkish red colour is not present anywhere in the illustration, so it's just been a very odd glitch. I haven't noticed this anywhere else, so I presume it's not a display issue and rather just a bug in the app, and it doesn't happen with every file every time (seems to happen at random with various files). I managed to capture a screenshot of this - below.
  4. I encountered a quite annoying UI bug in both Designer and Photo when using Live Perspective filter + artboards. It seems that render glitches appear on the canvas pretty randomly, in addition to a "border stretch" effect of what's displayed on the border of the artboard. The "border stretch" glitch can be somewhat workaround by reducing the size of the artboard content as to add some padding to the artboard. However the other glitches remain. Moreover, the glitches "update" on each canvas resize/zoom as you may see on the different screenshots attached. I am also attaching two files that show the issue. While these are .afdesign files, sending them over to Photos actually leads to the same glitches. These are using artboards, Live Perspective filter and symbols. Versions: - Designer 1.10.4 - Photo 1.10.4 - macOS 12.2.1 FYI, I tried disabling GPU acceleration, changing display rendering from metal to CPU, and any possible combination of both without success. Hope this can get fixed sometime! Mockup.afdesign Mockup.afdesign
  5. Hello! So i'm having this issue where on some images there is this weird edge. It still appears after being exported. Any fix maybe?
  6. After attempting to lay out some body text without reaching for my Mac I became furious with the process in Designer. This has been the case through my last 4 or 5 months with this tool. Here are a few thoughts on how it could be improved. When tapping into a text box, the interface attempts to keep the cursor in view at all times in the most jarring manner. When the on screen keyboard is up, this results in unintended jumps that make it confusing to pan and scroll the art board while editing. I would prefer that the interface either doesn’t move at all when editing the contents of a text box, or opens a content editor that takes you out of the layout completely while editing. The OS-default editing cursor doesn’t exist. This means if I want to go back, select a word, edit a word, or select a whole paragraph I need to use a confusing combination of hip-shooting exactly where I want the cursor to go with my giant fingers and selecting text without being able to control the beginning and end of the selection. Adapting to the OS-default would be great. Controls for resizing the text box and panning are still available when editing text. From a UX perspective, I would appreciate text editing being a completely isolated process especially on a device that invites fingery clumsiness. Tap the box to edit, all you can do is edit. Tap a done button, you’re back to the layout. (I’m experiencing way more ease writing this post in your little WSYWIG editor on my iPad than in Affinity D) Affinity is a great tool for comping up design ideas right on the iPad and I love it for that. But I DREAD when I have to put some text in there. Please consider these comments! Love Dan
  7. I know there is an archived theme. Confirming that this problem persists in the newest version 1.8.3. Moreover we can observe these damn lines in Xnview picture viewer also, when viewing images, that were edited in Affinity Photo. So this is a real bug or not? I don't get it.
  8. To Serif team. May we please know, in the end of 2021, why canvas rendering algorithms are still so terrible in all Affinity apps? 
It's just not pleasant to see at all. Lots of glitches, fps drops, screen tearing, jumping objects and visible tiling/blocky artefacts during any changes being made. While searching here on forums, I found lots of topics covering all these issues.
 Some of them are five or six years old. But some of these topics are much more recent. Various configurations, pretty good CPUs and GPUs of all sorts.
 But same screen tearing, artefacts and visible tiles. For a such long period of time. And there are still no fixes for that. In some of those topics I've found official responses, that "this is done by design", "it's the way our apps render the canvas".
 Well, it's not a good design then. And certainly not a good way to render the canvas. How you, at Serif, find it acceptable? Are you ok with seeing canvas rendering like that in your apps? How it passes QA and being shipped to your customers? Why there are headlines on Affinity website: "fast and glorious", "pan and zoom at 60fps", "handle 1000s of objects with no lag", "optimized for documents of any complexity"? When it is simply not true, but rather false statements. At least it is not true as long, as such core performance problems still persist for so many people, including myself. Why not consider implementing something like v-sync in your canvas rendering pipeline? Or something else that will prevent visible artefacts appearing during canvas updates. So it will wait for all the tiles to finish calculating their image data and then the whole visible part of the canvas will be composited and painted in a single (at least on the visible to user level) draw event. It will significantly reduce overall performance? Well, maybe, but then you'll need to find a solution for this as well.
 Now it looks like the best idea for you was to throw all these tiles at your customer's screen as fast as possible. Because who notice that mess? They'll be fine with that. But I do notice that. And I want to avoid any screen tearing and tile artefacts in my experience with apps even on the most basic and simple tasks.
So, where is mine "smooth and glorious 60fps experience"? I'm not even starting doing any serious graphic design work because I don't like your canvas in its current state. Sorry. Second, why mouse polling rate plays such significant role in your apps canvas performance? Recently I discovered this myself, and it was confirmed with your team members, that reducing mouse polling rate to default 125Hz significantly improves screen canvas performance. Significantly, but still not perfect yet. So why not restrict any user input events and sync them with dispay refresh rate / gpu redraw cycle? Just an example. The latest Safari has new option in their Debug menu: "Prefer Page Rendering Updates near 60fps". It ignores the display's refresh rate and throttle all in-window paint events down to commonly safe and achievable 60fps. So why not consider something like this and limit overall fps and user input event processing for the sake of overall performance improvement? Maybe then we'll get a better canvas? My main question is: is it an absolutely impossible to seamlessly refresh the canvas without all these tiles flickering around constantly once anything is changed in the viewport? I'm just wondering why it is still being considered as normal in Affinity apps to have a canvas behaving this way? Sorry if my post seems to be a rant or offended you in some way. I had no intent of doing that. 
I'm really wondering if Affinity suite can be made better for all of us. Or we shouldn't expect anything better being done in this direction. Maybe it's really a one big "pain in the a.s" problem for any software developers to make CPU and GPU properly talk to each other? 
Maybe there are lots of problems with major OS developers ditching OpenGL and moving towards Metal/DirectX? Also, we've seen this recent Apple's movement from separate CPU and GPU with dedicated memory to SoC solutions with unified, shared memory.
 Yes, I can understand that your apps should greatly benefit from that. Obviously, lower latencies, less memory copy operations, overall faster access to data.
 All things being done in one place. But... But at the same time I feel that it's just wrong to keep telling anyone on Twitter how good and fast your apps perform on those recent Apple SoCs, while its canvas (which is the main working and the most important area) lags and glitches in general for anyone with more traditional system configuration, even on the most simple scenarios like moving an artboard or a single layer around. I couldn't be the one who notices that. And my system is pretty powerful and it's clear that it deserves better performance and smoother visual response. What I see now is simply unacceptable for me. To be completely honest, I must say that I love your apps. Overall, they are much, much better for me than anything I've seen in this field. There are so many great features and innovative decisions, little details, that make it truly great.
 Every time I discovered these in your apps I was so excited and happy, because I remembered how bad the same thing was in Adobe's products. I remember lots of annoying, terrible things that made me leave Adobe's universe once and forever.
 Vast majority of these things remain unchanged for many years. Because they don't care about their software and customers at all. I found your company and your products to be a complete opposite. Small and passionated company with people really interested in their products. 
I don't want to be disappointed with you guys. I believe in you. I believe in Serif. Just can't stand this canvas tiles flickering and tearing. Sorry.
  9. So I recently purchased Photo. I've noticed that when I use the hot keys on my drawing tablet (Huion Kamvas 13), I begin getting white lines around my brush strokes and around previous strokes (there was a post about this issue about a year ago with the same issue, but that's the only one I found). You can see what I'm talking about in the attached image. As best I can tell, this issue only triggers when hitting the hit key for "Brush" on the tablet. If I press "B" on a keyboard, the issue doesn't replicate. Yes, I can use a keyboard, but I'm not sure if this can be "fixed" or if an update can handle this glitch. I'm also interested in if there is another work around aside from using a keyboard that anyone has found.
  10. When selecting text using the space bar trackpad, the cursor moves around but starting a selection using a second finger on the keyboard only works when selecting forward. Additionally the ability to long press on the cursor to pick it up and drop it doesn’t work at all. iPad Pro 11in 3rd generation IMG_0053.MP4
  11. Pressing enter in a text field doesn’t update the cursor position visually, though it seems to be adding a return. The video demonstrates a single return vs pressing return twice and how the cursor doesn’t follow. FullSizeRender.mov
  12. See image attached, in the bottom left corner when I open a RAW image (Nikon D800 .nef), there's a square/block that's just a re-rendered copy from another part of the image. It goes away when I close the image and open it again and only happens for the first image I open during an editing session.
  13. When working with images in the Develop Persona, I am getting glitches where the image display reverts to its unedited state. If I perform any action it then returns to show me the image with all current edits. It’s definitely not affecting the image because it does export the correct version when applied, regardless of how it appears in the workspace. I’m not ruling out my ageing Mac as the potential culprit, particularly as its GPU isn’t up to scratch but I thought it would be helpful to post this in case it affects anyone else.
  14. An oddly specific bug I just discovered in Photo - unsure of whether this shows up in Designer too. While sketching out an ornate frame design, I used the symmetry tool with a brush, and everything proceeded as usual. I then used Shift to create a straight line and noticed that the stroke automatically coloured certain parts red - screenshot attached. I tried a few different brushes and ended up with the same result (as you can see), but only when using my tablet pen/stylus - this didn't happen when clicking with the mouse and holding Shift. The layers I worked on didn't have any FX applied, and red was not a colour I had selected (my foreground and background colours were black and white). I've done a quick screen recording for reference: https://youtu.be/blPZMQsAhNQ It's not embedded as a glitch into the document/file though, as I can easily use a "Colour Overlay" effect to change it back to black.
  15. Hello Affinity team.. i created a poster and all set to export ..but the problem comes when iam exporting as JPEG from AP...some strange glitches are coming in the final export. The only solution i found is to open that file in Affinity Designer and export it ..then everything is fine..i don't know why it is occuring ..may be its a bug ..That's why iam reporting here. Please solve this issue asap..
  16. Has anyone else noticed the layers panel in AFPhoto refusing to collapse layers or otherwise behaving erratically? I have experienced this on two different computers on multiple different files (though I do work on the same files between computers). I'll update this post with a screenshot next time I see it. Edit: Updated
  17. In Stock panel the filler text not scrollable in non-full-screen mode and cut off at the bottom. The second picture is when I swipe down to scroll up.
  18. Ever since the latest update I've been experiencing a notable increase in strange, brief, intermittent glitches on my iMac monitor when quitting Affinity apps. I don't experience it much when working in the apps (sometimes when merging layers), but it's definitely most notable a few seconds after I quit the apps. It seems somehow worsened when I have a browser window open (Google Chrome, Safari, or Brave). I've also experienced some screen flickers in-app when developing RAW images in Photo, especially any format other than DNG (such as the Nikon NEF format), or when working with larger files. I'm running a dual monitor setup (iMac and a graphics drawing tablet as my second monitor), and the latest version of MacOS (Mojave Version 10.14.6). It's difficult to explain, but it looks similar to glitches experiencing with failing graphics cards, but they only flash/flicker once and then disappear until I quit the apps again, where a failed graphics card would show a permanent glitched display. I initially thought this was a graphics card issue on my side (I've dealt with that before), but after some research I found that this is a known issue between certain apps and the newer MacOS. Here's an article stating that this is is well an issue that is fairly widespread, and can be caused when running certain apps: https://pdf.wondershare.com/macos-10-14/fix-screen-flickers-on-macos-10-14.html I've tried all the steps mentioned to help eliminate the flickering (SMC reset, NVRam reset, booted in Safe Mode, and even ran First Aid on my hard drive to try and iron out any possible system bugs). I have no idea what's causing this, but it's a bit worrying. I'm scared that I'm maxing out my graphics card, or somehow putting too much strain on it when quitting the apps or something. I've even set my Display to "GPU (Basic)", the Retina Rendering to "Low Quality", and disabled "Metal Compute Acceleration" in the Affinity preferences, but it doesn't seem to be helping. I've posted in Affinity groups on Facebook and have received confirmation from a few other users/people that they are also experiencing this when using Affinity. I just want to raise awareness of this issue by posting on here, and hopefully push for a possible fix.
  19. I've noticed a bug when merging layers down while they are part of a clipping mask. When you have more than one clipping layer on an object and you merge it down to the layer below it, it flattens the entire mask stack (including the parent layer) instead of just merging the two clipped layers. A bit tricky to articulate, but I've added an attachment here to try and visually explain what I mean.
  20. OS: Windows 10 ver. 2004, build 19041.338 Affected product: Affinity Designer 1.8.4.693 (non Microsoft store version) Hardware: Microsoft Surface Book 1st Gen (i5 6300u, 8gb ram, 256gb ssd) Microsoft Surface Pen (battery level 61%) Issue: When dragging nodes/lines or when resizing objects in Designer while using pen input the line/object/indicator will glitch and flash rapidly. More info: This issue first appeared for me after upgrading to version 1.8.4.693, it was not present in the earlier version i was using but that version was out of date and i do not know the version number. I believe the build i was using was installed around March this year. This issue does not seem to be present in Affinity Photo, i did not test in Publisher. The issue is only with pen input, both mouse and touch inputs seem unaffected at this time. General drawing and other activities are unaffected by the glitching. This happens on both new and current projects. The issue is present in all performance modes for the laptop, from power save to full performance mode while plugged in. This issue still occurs when a different Surface pen is used. As a troubleshooting step, all user settings were reset to default by holding CTRL on startup, issue still present. Here is a video of the issue, i apologize for the quality and terrible audio. Please mute or turn down before viewing.
  21. Hi, So i tried exporting a illustration into figma, but the layers just don't align, i will share my original view and the export view, can anybody help me out i am running on a time frame here PS. the PNG comes out A-OK Regards -Noobie37-letter.svg the PNG view SVG view
  22. Hello, There seems to be a glitch with the inner glow effect (edit: and with the outline effect). This glitch seems to at least specifically affect shapes with lower opacity. By viewing the 8 snapshots below, you will see that setting even only 0.1 radius to the effect results in changes to the whole shape instead of affecting only its borders. This happens no matter the blend mode, and no matter the intensity (although the effect is more pronounced with higher intensity. (Pictures 1,2,3,4 are in Multiply blend mode ; Pictures 5,6,7,8 are ine Normal blend mode). I am working on a macbook pro. This happened while following the fisherman tutorial in the AD workbook. r
  23. I found an interesting glitch by accident, it makes it possible to put folders into folders putting a folder inside a folder is really easy but geting it out is a bit tricky 1. have a full folder 2. hold a folder so you can move it around and open with another finger the full folder you want to put it in, move the folder from your other finger around and if the other projects in your folder move away from it you can just drop it in. 3. to get the folder out of the folder you need to hold the folder inside the folder again to move it around, you will se there is no "back button in the upper left corner to bypass this you have to open any project while you still hold the folder with one finger now you can go back out of the project and now there is a "back" button on the up left corner so you can go out of the folder while holding the other folder, just move the folder out of the current folder sometimes it works first try but sometimes it takes some more tryes (sorry for my bad English) Please make it to a real feature 4CDB4BF3-9F7F-4AF1-BF95-B1F8689B16C9.MOV
  24. Hi loves! The new update has been giving me some problems... I use fonts a lot & they are all listed out of order & just randomly.. takes forever to find the ones I need. lol Also I cannot upload a new font as well. Just a very glitchy update. I hope this gets fixed soon... I have a project I need to finish. 💜 thank you! - Leslie
  25. So I've been having some serious issues with Grid management on the windows version of Photo. It doesn't ever line up properly with the size of the canvas which is quite an irritation. This is how it looks with Auto Grid turned on. See how the right side is cut off? What is causing this?
×
×
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.