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

ℓurié

Members
  • Posts

    27
  • Joined

  • Last visited

Posts posted by ℓurié

  1. 10 minutes ago, ℓurié said:

    Hello all,

    unfortunately I have bad news. In recent days I tested the latest release and the lag reappeared (even worse than before), but now it doesn't hit Curves, Shapes and Stroke (a very light latency is still there, but it doesn't impede the work). Now the massive lag affects the paragraph alignment (only Align Left, Centre and Right. With Justify is ok). I don't know if the previous release (1790) was affected, because I tested it less and after I deleted the files for reinstallation. Maybe yes, but it doesn't matter. What matters is realizing that the problem isn't fully resolved, because this delay makes the programs unusable. Now I don't know if it affects other elements, in the next days I will try again the whole Suite and I will update the topic if there will be news.

    Hello @Chris J

    As you can see, it's the same lag and it affects the whole Suite, but now it affects the paragraph alignment. When it starts, even creating and closing a simple document can take a long time. It would be nice if you could fix it, because it makes the Suite unusable (for me).

    I'm available for any help. Thanks for your attention.

  2. Hello all,

    unfortunately I have bad news. In recent days I tested the latest release and the lag reappeared (even worse than before), but now it doesn't hit Curves, Shapes and Stroke (a very light latency is still there, but it doesn't impede the work). Now the massive lag affects the paragraph alignment (only Align Left, Centre and Right. With Justify is ok). I don't know if the previous release (1790) was affected, because I tested it less and after I deleted the files for reinstallation. Maybe yes, but it doesn't matter. What matters is realizing that the problem isn't fully resolved, because this delay makes the programs unusable. Now I don't know if it affects other elements, in the next days I will try again the whole Suite and I will update the topic if there will be news.

  3. Thanks all for the contribution. Unfortunately I don't have much time, but I tested the latest beta (1790) for about five hours. Maybe I'm dreaming, but the issue seems solved. The whole suite is more responsive and the lag disappeared. This is great news. Now I look forward to working with the 2.1.

    Thank you so much, Serif. I really appreciate it.

  4. As you can see, I've experience with a massive lag with the whole Suite, especially with the selection/deselection of any shapes or curves. The lag starts after a short time with any file, and it extends to related tools (Shapes and Pen/Node), Stroke and File menu. The only way to stop it is to restart the apps every time. I used Photo for the videos (you can see them for more details) but the lag also affects Designer and Publisher. I have this lag with any update of V2, and now it also affects the Beta. None of that happens with the V1. It's been more than five months, and I can't work seriously with V2.

    I'm really embittered.

     

    LAG.afphoto

  5. On 3/13/2023 at 2:06 PM, stokerg said:

    What CPU and GPU do you have in your PC?

    I can see you have access to the beta, if you are getting lagging in the beta of V2, please make a separate post in the Beta section of the Forums about this and the QA team will be able to look into this with you.

    Hello @stokerg

    these are my specs: CPU: Ryzen 3 3100 / GPU: HD 7750

    Unfortunately I'm currently using an old gpu, but it's a temporary solution. I've another gpu (RX 6600) but for some reasons I can't use it now. Is the problem related to gpu performance? Because yes, I'm also trying the Beta and it's better (but not quite). I also noticed that if I decrease the brush size, the lag disappears.

    My biggest problem, however, remains the lag with the selection of objects (especially the curves) which doesn't affect the V1. But I will write about this in another topic.

  6. On 1/30/2023 at 2:56 PM, stokerg said:

    Hi @chessboard,

    Please do keep me posted if there's any change.

    @mara.cernoch I'll admit, I was hoping for better news but this is still good information to have as it helps narrow things down a bit for us.  Leave this with me, as I need to speak to the QA team and will update here once I've got something else for you to try :) 

    Hello @stokerg, I have this issue with the whole Suite. I'm using the latest MSI/EXE version. I also tried the 2.1 Beta, but the lags remained. It happens with any file after some time and the only way to stop it is to restart the apps every time. OpenCL is disabled. Unfortunately this lag makes the software unusable for me. It would be nice if you fix it.

  7. On 1/5/2023 at 6:37 PM, SrPx said:

    Edit: It also happens with Knife tool, but the 'copy as SVG' (preference) trick also works as a workaround.

    I got the shapebuilder and booleans problems just with basic Arial.

    I think it's all related, causing problems in both shape builder and booleans (EDIT: and Knife), some issue in the code converting text to curves, or something to fix by them in the text item itself.

    The other day I found a workaround consisting in, after converting to curves, and also maybe 'geometry->merge curves' depending on the case, setting then in Preferences/general-> clipboard  "copy as SVG" (no need to restart the app). Then copying these curves (ctrl + c   or right click "copy", I mean) that come from text, then click "paste special" in Edit menu (for the sake of speed, can assign a shortcut to Paste Special, I did so) , and then a dialog box that appears, choose "paste as Scalable Vector Graphics" (SVG). It generates a group, while you need to operate directly over curves, so, in the layers panel move the curves out of the group and delete the empty group.  Or select the group, right click, ungroup (or just ctrl shift G with the group selected) , if you prefer so.

    I would warn not to delete the original curves too fast after doing the paste, as if the paste doesn't do it in-place, you can use snapping (on) to make it match perfectly with the original in position (if snapping settings are correctly configured) in a fraction of a second.

    This fixes it for me. Takes a few seconds (it takes way more time to explain it :D ). To at least doing what I want in the project, until this gets fixed. Is not long to do, and can even deactivate the preference setting on the fly after the fact, as it takes the change without restarting.

     

    Just checked now again (tho I had discovered it the other day), and yep it happens with any Arial text (I don't think it's happening only with some fonts...) converted to curves, and the trick seems to work for shapebuilder and booleans.  

    One cool thing is that if you prefer to have all time "Clipboard: copy as SVG" preference off (ie, as the copy&paste "SVG style" thing might flatten some other features when copying, but not sure about it, it's just intuition), as needs no restart, can activate only for a moment (or a 4 hours session) when you need shapebuidler or booleans, then go to preferences again and change it back.

    Of course, it's a bug. It very much needs fixing.  But I think the above is a "fast" and ok workaround, meanwhile.

     

    Thank you too for your suggestion @SrPx. I tried this workaround and it works. But I noticed that this bug doesn't happen with any Arial text and it also happens with some non-Arial text. But now I'm testing the new Beta 2.1 and the bug seems to be fixed.

  8. On 1/19/2023 at 4:17 PM, Paulie68000 said:

    As another workaround, I found that if you have Affinity Photo/Designer 1.x still installed - if you convert your font to curves in 1.x you can then copy and paste those curves into Photo/Designer 2.x and the boolean operations will work on them (including knife and shape builder).

    Thank you for your suggestion @Paulie68000 but unfortunately I tried this workaround and it doesn't work in my case.

  9. Hello,

    I've noticed these bugs. When I try to use the Shape Builder with some fonts it doesn't work correctly. The same fonts (or font families) are also affected by another bug with the Boolean Operations. Both bugs don't affect all fonts and they only happen when I place the letters at a specific positions. Look the video:

    If it helps the developers, these are the same fonts that are affected by the bug with the Knife tool:

    https://forum.affinity.serif.com/index.php?/topic/172021-knife-tool-doesnt-work-with-fonts/

    Thanks for your attention.

    Shape Builder & Boolean Operations Bugs (Font - Arial).afdesign

  10. On 11/12/2022 at 7:42 PM, Phojoegraphy said:

    After years of begging, pleading and demanding, we finally have vector warping. I'm very happy to finally have it, but I honestly can't say I like it very much for every use. It's very useful for freehand warping, but anything structured, (like for typography when you need symmetry & verticals/horizontals to stay true,) it is a bit of a chore to use.

    We need more behaviors and tools:

    1. The nodes to be able to snap with modifier key like a regular node. Vertical, horizontal, 45 degrees.

    2. Have a toggle or modifier for symmetrical node behavior both in same direction and opposite directions.

    3. Better presets that are easier to edit. Employing a special node like the shape tools use would be extremely useful for preset use. This way we can make flag, raised edge, and warps that need symmetry with ease. (See Vector Styler).

    I totally agree. I really appreciate the new tools and the hard work of developers. But we need this features as soon as possible. Also there are still many bugs to fix.

  11. Hello, I have some news.

    Unfortunately I don't have much time, but I tried again and again. Unluckily the bug also affects the straight letters. But... I've noticed that it doesn't affect all font families. Look the next video:

    I also tried with others font families and it seems that only some of these are affected.

    I attach the file, but you can try with others font families.

    Knife tool bug - Font Families.afdesign

  12. 12 hours ago, nezumi said:

    I have posted about this bug too in other thread. In my experience its not about fonts - its about straight line. Try to use knife tool without shift, just freehand cut through font/objects. If you use knife tool on its own, without shift all should be fine. Kindly let me know if this is the case for you too.

    Hello @nezumi,

    thank you too for your reply.

    It looks like the same bug. As I specified above it only happens when I press SHIFT for straight cut (vertical, horizontal, 45° degree). But in my case it only happens with fonts, even after converting them to curves (only with the straight letters it's ok). With the other shapes I haven't noticed any issue for now.

    Look this video:

    Instead, with freehand mode it's ok with all shapes and all fonts.

  13. 11 hours ago, Komatös said:

    @ℓurié

    I also have no problems with the knife tool.

     

    Designer_698jNQonTU.gif.69c16f58750aa8286d5acf1e61bb34ae.gif 

    Hello @Komatös,

    thanks for your reply.

    But in your video I can see the same bug. Look carefully and let's analyze it.

    The first cut leaves behind some curves. It's the line outside the fonts. The left side of & isn't cut. You can check this with the Node tool (press CTRL+Y to see if you use Windows).

    1537114028_FirstCut.jpg.fcfadbd6bbbe2527a1331a731029aafa.jpg

    The second cut only works with the left side of B. The right side of B and & aren't cut, despite you have selected all three elements.

    1192650159_SecondCut.jpg.89f25bea7f8dc567954b0762a0fed86b.jpg

    A correct cut is this:

    But I've noticed that it works correctly only with a straight fonts (A in the last video is totally straight). Instead, with the other shapes I haven't see any bugs for now.

    Eventually sorry for my english and thanks for your attention.
     

  14. Hello,

    I've found a bug. The Knife tool doesn't work correctly with fonts, even after converting them to curves. As also reported by another user, the bug only happens when I use Shift for straight line. With freehand mode it's ok.

    With the other shapes I haven't noticed any problems for now.

    Thanks for your attention.

    Knife Bug 1.afdesign Knife Bug 2.afdesign Knife Bug 3.afdesign

×
×
  • 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.