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

Halex

Members
  • Posts

    43
  • Joined

  • Last visited

Posts posted by Halex

  1. On 4/25/2024 at 2:27 AM, SrPx said:

    I would try disabling "Enable Open CL acceleration", as I can see it is checked, in the video... It (any brush) goes perfect for me (in Photo), there must be something different (and I definitely have that disabled; when I activate it, the brushes start lagging. Don't worry, it still will use your GPU).  The other thing different is that you have BOTH flow and accumulation varying by pressure (is there a reason for that?) I usually have only one value varied by pressure: flow, as is what gives the painterly build-up. For my brushes more dedicated to digital painting, I indeed set only flow as varying by pressure (as I change size constantly with wacom's ring). But for others, I set flow and size (a little bit only, in the case of size). Maybe that could be affecting too. But IMO the major red flag is the open CL thing activated. I would even restart Photo (exit and start it again, I mean) after you change that, to be sure.

    Here brushes go blazing fast. Maybe is the PC, the hardware, memory, GPU or CPU. Mine is a Ryzen 9 3900X, 32GB RAM, and a nvidia 3060 12 GB VRAM. I even save the files in an old HDD, and photo is on it, too (my Windows runs on a fast m.2 SDD, though).

    What size is that canvas ? (in a very huge canvas that could happen, and many other operations).
    Have you checked the Windows Task Manager (ctrl + shift + ESC ) to see that no other app or tsr, process, is somehow consuming many resources? (sometimes happens).
    But my strongest suspicion is the Open CL not being disabled. As I had that problem with even different configs and different PCs.

    Hello SrPx

    Your tips are always welcomed. The Open GL works good here, but it seems you found out the problem: turn off the accumulation pressure works better. I still need to do more experiments but it seems better for now. Thank you.

  2. For some reason "Tablet Input Method: High Precision" works better in older Affinity versions for me. I recorded a video showing how Flow works worse in new version. All my brushes are set in old "Tablet Input Method" and it will take a lot of work changing it again, also I really prefer the old "High Precision".

    So I'd like to suggest you the old High Precision as another option for next update.

  3. I have double click problems with "Tablet Input Method: Low Precision". I already disabled everything in my Wacom and Windows settings, but this problem still happens.

    One of the solution is changing it to "Windows Ink" Method, but another problem happens, the "Move Tool Aspect Constrain: Automatic (based on selection)", doesn't work (zoom is blurred when dragging).

    Another solution is changing it to "High Precision", but this method has slower strokes.

    I'd like a solution for "Low Precision" or "Windows Ink", because "High Precision" has slower performance. Here is a video recording what is happening.

  4. On 3/12/2024 at 7:04 AM, NotMyFault said:
    1. You need to activate snapping with option „force pixel alignment“. 
    2. the layer will stay sharp as long you keep it on while integer position, and use 90 degree angles or multiples, and do not change layer DPI / size
    3. otherwise you need to rasterize the layer once after every change which newly causes blurriness. this will „bake in“ the blurriness from layer misalignment.

     

    Wow, thank you very much! I changed the decimal to 3, activated the "Force Pixel Alignment", deactivated the "Move by Whole Pixel" and it works perfectly now. You are amazing.

  5. 9 hours ago, R C-R said:

    If you mean about 'activating' decimals, I think what @thomaso meant was to set Decimal Places for Unit Types for Pixels values to more than 1 decimal place, like to at least 3 or higher.

    Wow, thank you very much! I changed the decimal to 3, deactivated the "Move by Whole Pixel" and it works perfectly now. You are amazing, guys! 
    Thanks Thomaso and RC-R. I wish much success for you.

  6. 23 hours ago, thomaso said:

    If you move an object from a decimal position by whole pixels  movepixels.jpg.73f86f47725129bc9e11581d4385de96.jpg  then these decimals are maintained when moving.

    To avoid decimal pixel positions:

    1. Open the Transform panel to have an eye on decimal pixels. (make sure 'decimals' are activated in the app Preferences > User Interface)
    2. Set Pixels as ruler unit.
    3. Deactivate the option "Move By Whole Pixels". (but keep Force Pixel Alignment activated)

     

    Thanks Thomaso, it works when I try just to move the layer, but still has some problems when I change the angle. I think it is not possible to keep the image perfectly rotating it, but I just want to check it with you. Please, look if my "User Interface" prefences is correct to use the tool you suggested me:

    Print Interface.png

  7. 23 hours ago, thomaso said:

    The reduced quality appears to be caused by your various actions without having "Force Pixel Alignment" activated. This option avoids decimal pixel positions (e.g. in the Transform window) and reduces antialiasing applied to individual pixels. With every rasterization process after a position or size change, these pixels are then 'burned'.

    https://affinity.help/photo2/English.lproj/pages/DesignAids/pixelAlign.html

    In your video you seem to have the Toolbar currently deactivated. If it gets displayed you can access the "Force Pixel Alignment" with one click. It appears to be not available as menu command.

    pixelalignment.thumb.jpg.0ec179b8e0a883ae0434c2ce8ca4df8c.jpg

    Thanks, but it doesn't work here. I recorded another video showing the same problem, please, look if I did something wrong in the settings.

  8. On 3/10/2024 at 3:22 PM, walt.farrell said:

    I think you should Rasterize your layer 002 before you do the merge. If you don't, it has a different DPI than the existing layers in the document, and I think that will cause problems.

    Thanks, but the same happens when I rasterize it before merge them.

  9. 2 hours ago, SrPx said:

    Hello, I replied to your PM, I sent you some tips over there :)
    Please, let me know if some of that works...  :) 

    It does not happen to me although I have an even older Wacom (mine is Intuos 4 XL while yours is 5).

    Anyway, please try those things I mentioned, as at least will help discarding factors, and in the best scenario, might solve your problem.

    Edit: Also, if something works and solves the problem, to report it here for people checking this thing in the future. I had that issue years ago, but since a while never had this problem again, in several  installations and different hardware. So, I believe it might be one of the things I told you in that PM reply.

     

    Thank you for your help, SrPx

    I found out a solution!! Just go to Affinity Preferences / Tools / Tablet Input Method / High Precision.
    Now the double click is turn off.

    Untitled.png

  10. 4 hours ago, Callum said:

    Hi Halex,

    I can't see anything in your video that shows other lines becoming blurry as a result of the transform operations you are applying to your selected line. If possible could you provide screenshots that show the effected lines before and after transforming another line?

    Thanks
    C

    Hello Callum.

    Yes, take a look at that image, you can see how it become blurry when I try to scale a separate layer. You can see that bug trying that: copy a line art draw, cut some part of its, paste in other layer, scale that layer, merge with line art draw layer. Repeat that and you can see how the image loses resolution.

    Teste Resolução.png

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