Jump to content

WeekendProducer

Members
  • Content count

    17
  • Joined

  • Last visited

About WeekendProducer

  • Rank
    Newbie
  • Birthday September 19

Profile Information

  • Gender
    Male

Recent Profile Visitors

264 profile views
  1. WeekendProducer

    Save failed because the file could not be written to.

    I have the same problem, but I cannot solve it in any way I tried. I have many AD & AF files and all of them are stored on Google drive. But I have no problem with many, I have problem with few "special" ones as those get stuck and no matter what I do the file cannot be saved once opened. I have AP file on the remote disc and after failing to save under another name before making any changes to the file I download it on my local HD. So the file is on myy PC, but I can only open it and I'm unable to save it even the file has not connected to the remote file anymore. I got the same message and all I got as saved is a new 0 kb AF or Ad (empty) file with alternative file name. I managed to copy few elements from the original file (saved on my local HD) and create a new file from the clipboard and finally managed to save it under another filename. But I need to recreate it piece by piece instead of just be able to save it.... so frustrating and without any obvious reason.
  2. Hi I just discovered strange artifact within 2 of 3 my file exports (within same project file). Artifact stays there no matter the format of export (png / jpeg). Can someone please help me or try to explain what is happening. I have hundred of files and exports already and this is the first time I'm getting something like this. All files attached. UPDATE: I was started working on AD Windows, then continued on Mac, and finally get back on Windows machine to do final touches and export. Mac files are exported without artifacts!!! Only on PC I got this, but it is still a problem that should be checked. Thank you. 20180425_Yoga_tečaj_PCZ.afdesign
  3. WeekendProducer

    Fonts prerendering freezes the AD / AF

    Sorry guys here I am again with the same story. I'm just looking at my Affinity Designer (not responding) window for about 5 minutes already and it is still freezed by (pre)rendering fonts while I'm writing this. I have no time for this BS. It's a BAD solution and it should never been implemented this way. Now after it prerendered all fonts user will expect everything with the font search window to be fast and snappy but it IS NOT. It works so sloooow, it hangs while typing the font name and it shows those typed letters after 3 - 5 or even 10 seconds. Extremely frustrating. Give me opt in for prerendering. If I don't want that "feature" I can skip it and use the fonts the old way or in some hybrid solution like written below: Render on the fly by rendering and showing only the visible fonts as even those are prerendered the fonts windos is slow like it renders it again... Please FIX THIS ASAP. I cannot believe there is no proper reaction for this problem and that is not been solved already. AllAdobe products I used never had this problem on much slower machines and I have fonts rendered and shown within the font window without delay no matter how many fonts I have installed (or simulated as installed). thank you.
  4. WeekendProducer

    Memory leak in Affinity Designer

    Sorry guys here I am again with the same story. I'm just looking at my Affinity Designer (not responding) window for about 5 minutes already and it is still freezed by (pre)rendering fonts while I'm writing this. I have no time for this BS. It's a BAD solution and it should never been implemented this way. Now after it prerendered all fonts user will expect everything with the font search window to be fast and snappy but it IS NOT. It works so sloooow, it hangs while typing the font name and it shows those typed letters after 3 - 5 or even 10 seconds. Extremely frustrating. Give me opt in for prerendering. If I don't want that "feature" I can skip it and use the fonts the old way or in some hybrid solution like written below: Render on the fly by rendering and showing only the visible fonts as even those are prerendered the fonts windos is slow like it renders it again... Please FIX THIS ASAP. I cannot believe there is no proper reaction for this problem and that is not been solved already. AllAdobe products I used never had this problem on much slower machines and I have fonts rendered and shown within the font window without delay no matter how many fonts I have installed (or simulated as installed). thank you.
  5. WeekendProducer

    Memory leak in Affinity Designer

    Uh OK, I have thousands of fonts (simulated like installed with app for that), but I did not experienced such starting delay until lately... as Both AD and AP have the same problem, and yes I disabled the fonts and loading time is back to normal. It would be great, having that slow loading in mind, to move and somehow hide the process of "rendering" those previews in the background. I'm sure that was the case earlier as the AD/AP would freeze for some (but much shorter) time after the app is already loaded, and usually after starting to work with some file. Thank you and BR.
  6. WeekendProducer

    Memory leak in Affinity Designer

    I didn't experience this before 2018. But now starting AD takes ages, like 30+ seconds. I have SSD, 16GB RAM, i7 PC. On two different machines (similar hardware) I got the same problem lately. So after no file loaded, just AD, it occupies about 20% of processor resources and it just starts eating my memory slowly but continuously. Attached images are taken few minutes apart. Any known similar problems or fixes? Thank you. I have a Mac version so I'll try that also...
  7. WeekendProducer

    Changing position after grouping - AD

    ...also... I noticed all kind of weirdo things happens when doing copy paste symbols, doing paste within some layer, ending up completely "out of space" and distorted... The history (undo) gets broken, so if some unwanted changes were made to a Symbol while sync is on there is point of no return with undo and u get stuck with the unwanted changes... Check the video below (sorry for messing around I have only one hand and I recorded the video using my mobile...), just be patient and u'll see all the problems I'm facing: VIDEO 2 - Weird Symbols copy/paste behaviour
  8. WeekendProducer

    Changing position after grouping - AD

    Hi, many times I group few objects I got my grouped elements jumped to a some random(?) generated position, out of artboard I'm working on, and out of sight in general. Why is this happening? If there is any sense in what's happening is there a meaningful way to put it under control? Please check the video attached within the link below to see what I'm talking about: VIDEO
  9. I hate the triple extra workflow (and additional artboards and even additional document) I just did to accomplish something so simple as keeping the rasterized part of the image visible beyound the artboard just to have the bleed visible as it should be. Affinity Designer desktop really needs some love. You (Affinity team) put so much focus into that finger friendly iOS iPad version that it seems it hurts real production versions...
  10. After rasterizing an image all the part of the image out of the Artboard has been cut off and the bleed area which has been setup for the document has been ignored - I have no image parts visible out of the Artboard anymore. This of course is not acceptable as I need that part of the image outside of the Arboard to fill the bleed area - that's for the bleed is for. How to solve this? I have special situation where I need image to be rasterized together with some overlay text elements to get the desired output (for some reason what I see is not what I get after print export, so I only get the desired result after rasterizing the visible elements. Less important but a bit strange to see - The command for Rasterize in Affinity Design is written as Rasterise (with S instead of Z).
  11. I have a problem which happens repeatedly all the time now, having an Affinity Designer file, rasterize an group of objects, going to Edit in Affinity Photo, choosing a Mesh Warp tool to transform the rasterized group and few seconds after Photo Crashes together with file closed (I end up with empty Affinity Designer screen) and no backup save is done so it's not possible to recover the file if it is not saved manually in between the start and the crash. UPDATE: It crashes with the file I shared after x seconds no matter what tools I use and what I try to do in A. Photo... THE FILE: https://drive.google.com/file/d/0B1lVpM35qSdCX25kWjM3TW0xMmM/view?usp=sharing VIDEO: https://goo.gl/photos/xYsVNyGbcaGadhUv8
  12. I produce digital content for web, so a per pixel precision is a must. I won't go into all the nonsense of moving and creating objects ending with subzero values (size and position) no matter the "force pixel alignment" and other tools checked, in addition to all above, after exporting (creating slice from some object within artboard placed on some colored background) I got those subpixel thin hairlines visible!!! On the end product?!?! Visible on 1:1 So I just end up with sending to my client this BS (attached) as a solution - unfortunately I noticed the exporting error too late. Check the thin blue right and bottom border that should not be there. Slice size exactly matching the object size. Why should we not consider this as a bug that needs ASAP fix please?
  13. I produce digital content for web, so a per pixel precision is a must. I won't go into all the nonsense of moving and creating objects ending with subzero values (size and position) no matter the "force pixel alignment" and other tools checked, in addition to all above, after exporting (creating slice from some object within artboard placed on some colored background) I got those subpixel thin hairlines visible!!! On the end product?!?! Visible on 1:1 So I just end up with sending to my client this BS (attached) as a solution - unfortunately I noticed the exporting error too late. Check the thin blue right and bottom border that should not be there. Slice size exactly matching the object size. Why should we not consider this as a bug that needs ASAP fix please?
  14. I found new annoyances, within Pixel Persona and with raster image. If you select one part of the raster image, perform a cut & paste (without moving anything from it's original position) you will end up with a same subpixel hair thin line showing the cut which stays visible on the final export file. Duplicating the object(s) doesn't help here.
  15. I was creating and working with vectors in Adobe Fireworks (!!) and some Inkscape (free) and I found no trace of this problem before I switched to Affinity Designer. However I found more issues I never faced before in any vector software. 1) the stroke inside setting within a filled path leaves visible background fill color visible as a thin line on the outer edge of the stroke (or path, or object). https://www.dropbox.com/s/lm4roklhr6nezee/Affinity%20Designer%20stroke%20inside%20fill%20outline%20visible.PNG?dl=0 2) Another problem is Affinity D only because of nested/masking paths feature is possible within AD only. The thin white line (this one is always white no matter of the BG fill color or if the stroke even exists) is visible when child (nested) path is placed over the edge of the parent path so the child path is partially masked behind the edge of the parent path. The white edge is visible where child and parent paths are "touching" or crossing over each other. So this is a serious rendering problem - obviously not edge near edge related as this is path crossing / overlapping edge - that affects the work and on large projects there are no easy or quick fixes for this as it becomes a designers nightmare. https://www.dropbox.com/s/tzm0958i0epq2gi/20170215%20Affinity%20Designer%20object%20borders%20visible.PNG?dl=0
×