Jump to content
You must now use your email address to sign in [click for more info] ×

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
    • 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. So I have a project I just finished that was a live document. I kid you not, as I’m clicking to go hit save or export or something to make a hard copy… the program glitches, crashes. I go back in to reopen the file, but it instead duplicated 3 project folders somehow… there is a thumbnail of the file inside but no live document to open (it says 0) so I can’t save it from the dashboard. I assumed there would be some temp folder for the cached files I could scrounge for and reopen the last instance, but I can’t find one and don’t see any mention of one. Is it hidden in system folders? I am so frustrated. In other programs, this would be the natural troubleshooting but not here… is there some way to restore a file from cache or did I just lose a lot of work because the file corrupted/disappeared? I have my files stored in the iPad, not syncing to a cloud. edit; I can rename the folder, which renames all 3. I tried updating, restarting the app and iPad.
  2. 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
  3. 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..
  4. I frequently use my iPad with the folio case which props it at a slight angle. Interestingly Affinity Photo AND Affinity Designer seem to be reacting to this angle when trying to place photos. The whole interface flickers strangely and taps aren't always registered. The video demonstrates it in Affinity Photo but the behavior is also the same in Designer. Previous to 2.0 I noticed other features in Affinity Designer such as keyboard visibility that were delicately affected by the slight angle. I haven't determined if these are still issues but I haven't seen any other iPad app that has had issues with this angle. You'll notice the flickering only occurs while the iPad is at the slight angle, but not when it is upright. This is an 11in iPad Pro M1 running iPadOS 16.2 (a). I have noticed this in previous versions of the OS IMG_5679.MOV
  5. Hi there. I have been using the pen tool on Affinity Photo for Mac for a long time and often use the ability to create tapered lines using the pen tool. I cannot see anywhere on the ipad version where I can change the line thicknesses over distance. Am I missing something? Also when I import a file that does have varying vector stroke thicknesses, every shape and line I create in the ipad app afterwards has the exact same line profile which I am powerless to change. Is this a glitch? Or is there a section were I can change this in app? Please help!
  6. Check it out! If the text box isn't big enough to handle a hard or soft return my whole canvas zooms out to some unknown area! I'm using an M1 11in iPad Pro. RPReplay_Final1680459285.mp4
  7. Greetings, Affinity Photo 2.0.3 Steps to reproduce: Take any raster layer, 8bit, sRGB Add Live Filter "Gaussian Blur" with eg. 10 px radius Change the opacity of Live Filter to 1% Change blending mode of Live Filter to "Overlay" Until now, everything seems to be fine. You are seeing an almost unmodified layer content. Now, change the Live Filter opacity from 1% to 0% First bug: Despite that blur itself is actually not visible, obviously the image is being applied to itself in Overlay blending mode, while You should be seeing unaltered image. For reference, You may want to convert the document to CMYK FOGRA39, and check there (it behaves correctly). You are still in sRGB. Grab the "Radius" slider and move it randomly. Image is being divided into semi-random areas, similar to screenshot below. Try to "merge" the Live Filter. The artefacts are likely to be embedded into layer pixels. This procedure takes "gaussian blur" as an example. Same glitchy beaviour occurs also when using different Live Filters. KR,
  8. 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.
  9. 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
  10. 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.
  11. 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
  12. 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?
  13. 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
  14. 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.
  15. 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.
  16. 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.
  17. 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
  18. 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
  19. 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.
  20. 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.
  21. 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.
  22. 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
  23. 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.
  24. 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.
  25. 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.
×
×
  • 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.