Jump to content

davidlower8

Members
  • Content count

    80
  • Joined

  • Last visited


Reputation Activity

  1. Thanks
    davidlower8 got a reaction from Jon P in App crashes when jumping from one table to another   
    It seems to be fixed. I can't replicate the bug at current. If I see it again I'll report here. Thanks.
  2. Thanks
    davidlower8 reacted to Jon P in App crashes when jumping from one table to another   
    This should be fixed in the latest beta looking at the video.
    Can you download it from here and let me know if you can still reproduce the crash?
    Thanks
  3. Thanks
    davidlower8 reacted to Wasp11b in Various table features   
    As regards (3), I find that if a click the row header arrow and select 'Insert Row', it does indeed add the new row above. However, if I ignore the header arrow and just right click on the row header the same menu pops up but this time if you select 'Insert Row' it inserts below the currently selected row! Of course, the operation should be clearly labelled as to whether inserting above or below.
  4. Like
    davidlower8 reacted to MEB in STILL BROKEN - Forced pixel alignment   
    Hi davidlower8,
    Yes, I did check them. Please allow me some time to test/check a few things and to talk with the dev team.
  5. Like
    davidlower8 got a reaction from Chris B in REALLY SLOW - affinity designer for mac   
    Ok it has been a week since this post and I believe this solution has indeed fixed the problem. Thank you all for your input.
  6. Like
    davidlower8 reacted to ashf in STILL BROKEN - Forced pixel alignment   
    As OP emphasized "export persona constantly exporting images with a 1px gap", I believe antialiased 1px line problem is the actual point on this topic.
     
  7. Like
    davidlower8 got a reaction from SrPx in STILL BROKEN - Forced pixel alignment   
    @SrPx thanks for the response buddy. Setting the decimal place to zero unfortunately achieves nothing. In essence all it is doing is hiding the decimal places so you can’t see them. But under the hood it is still introducing fractured pixels. So ultimately the pixel persona will still export slices with a 1px gap. This is the biggest grip for me because it is so freaking obvious when uploading these slices to client websites.
    Your other solution is a nice idea (thanks for that) but again it far more work than it should be. I don’t want to have to consciously be aware that my various layers are being contained in boxes. It completely defeats the simplisticty that affinity is suppose to be boasting. Until affinity decide to fix this I can’t see a walk around. As this has been a problem since launch (2014) and they have done nothing about it, does sadden me. I was / am a huge fan of affinity. But the work flow to export all my slices, symbols, images etc from my designs is simply making this a product I can’t use anymore. For messing around and chilling it’s fantastic. But for real client work uploading all your artwork with a white 1px gap is tragic. It even did it for a professional brochure I made (26 pages) with hundreds of layers. You can imagine my frustration when I had to refactor every single layer making sure both the physical size of the layer was solid pixels only, but also the position on the art board being solid pixels. If any one of those 4 measurements has a fractured pixel then it will upload the entire slice with a 1px gap. It is actually a really shocking  error/bug and I can’t believe this hasn’t been given more light.
    thanks for the input
  8. Thanks
    davidlower8 got a reaction from CLC in STILL BROKEN - Forced pixel alignment   
    Hey I want to flag this bug/issue again since it is still not being address or fixed and is creating a workflow in affinity that I can no longer continue to use. Please see video below of the example of how force pixel alignment does not work.
    It is becoming a serious headache, namly the export persona constantly exporting images with a 1px gap. I have since, through shear perservance learned the work flow to get around this problem. Forced pixel alignment should do what it says and the whole document works precisely on whole pixels regardless of scale, snapping or repositioning. Perhaps affinity should even add this as a clear option when creating a document in the first place. Add a tick box option next to the 'document units' dropdown menu and call it 'work with whole pixels'. Then have the additonal forced pixel button in the toolbar.
    My problem I face now is when a scale an object, let's say a simple piece of text. It does not scale to whole pixels. It introduces the fractured pixels, even though the whole documnent is working in forced pixel alignment. Due to this I have to constantly monitor and be aware of resizing everything to make sure it is working in full pixels. Is there a way when I scale an object, ie grabbing the blue handle points and increasing or decreasing its size, while maintaining full pixels? This would help massively on my end in solving how affinity works.
    Like others though this is really beginning to dent my ability to use Designer going forward. It is literally adding hours to my work flow.
    https://www.loom.com/share/d4d68bbd50ac4a68892ca40852a5cf72
  9. Like
    davidlower8 reacted to ashf in STILL BROKEN - Forced pixel alignment   
    Hmm, this is kinda annoying.
    Serif should offer some kind of fix at least if it's a pixel based artwork.
  10. Thanks
    davidlower8 got a reaction from CLC in STILL BROKEN - Forced pixel alignment   
    Hey I want to flag this bug/issue again since it is still not being address or fixed and is creating a workflow in affinity that I can no longer continue to use. Please see video below of the example of how force pixel alignment does not work.
    It is becoming a serious headache, namly the export persona constantly exporting images with a 1px gap. I have since, through shear perservance learned the work flow to get around this problem. Forced pixel alignment should do what it says and the whole document works precisely on whole pixels regardless of scale, snapping or repositioning. Perhaps affinity should even add this as a clear option when creating a document in the first place. Add a tick box option next to the 'document units' dropdown menu and call it 'work with whole pixels'. Then have the additonal forced pixel button in the toolbar.
    My problem I face now is when a scale an object, let's say a simple piece of text. It does not scale to whole pixels. It introduces the fractured pixels, even though the whole documnent is working in forced pixel alignment. Due to this I have to constantly monitor and be aware of resizing everything to make sure it is working in full pixels. Is there a way when I scale an object, ie grabbing the blue handle points and increasing or decreasing its size, while maintaining full pixels? This would help massively on my end in solving how affinity works.
    Like others though this is really beginning to dent my ability to use Designer going forward. It is literally adding hours to my work flow.
    https://www.loom.com/share/d4d68bbd50ac4a68892ca40852a5cf72
  11. Like
    davidlower8 got a reaction from SrPx in STILL BROKEN - Forced pixel alignment   
    @SrPx thanks for the response buddy. Setting the decimal place to zero unfortunately achieves nothing. In essence all it is doing is hiding the decimal places so you can’t see them. But under the hood it is still introducing fractured pixels. So ultimately the pixel persona will still export slices with a 1px gap. This is the biggest grip for me because it is so freaking obvious when uploading these slices to client websites.
    Your other solution is a nice idea (thanks for that) but again it far more work than it should be. I don’t want to have to consciously be aware that my various layers are being contained in boxes. It completely defeats the simplisticty that affinity is suppose to be boasting. Until affinity decide to fix this I can’t see a walk around. As this has been a problem since launch (2014) and they have done nothing about it, does sadden me. I was / am a huge fan of affinity. But the work flow to export all my slices, symbols, images etc from my designs is simply making this a product I can’t use anymore. For messing around and chilling it’s fantastic. But for real client work uploading all your artwork with a white 1px gap is tragic. It even did it for a professional brochure I made (26 pages) with hundreds of layers. You can imagine my frustration when I had to refactor every single layer making sure both the physical size of the layer was solid pixels only, but also the position on the art board being solid pixels. If any one of those 4 measurements has a fractured pixel then it will upload the entire slice with a 1px gap. It is actually a really shocking  error/bug and I can’t believe this hasn’t been given more light.
    thanks for the input
  12. Thanks
    davidlower8 got a reaction from CLC in STILL BROKEN - Forced pixel alignment   
    Hey I want to flag this bug/issue again since it is still not being address or fixed and is creating a workflow in affinity that I can no longer continue to use. Please see video below of the example of how force pixel alignment does not work.
    It is becoming a serious headache, namly the export persona constantly exporting images with a 1px gap. I have since, through shear perservance learned the work flow to get around this problem. Forced pixel alignment should do what it says and the whole document works precisely on whole pixels regardless of scale, snapping or repositioning. Perhaps affinity should even add this as a clear option when creating a document in the first place. Add a tick box option next to the 'document units' dropdown menu and call it 'work with whole pixels'. Then have the additonal forced pixel button in the toolbar.
    My problem I face now is when a scale an object, let's say a simple piece of text. It does not scale to whole pixels. It introduces the fractured pixels, even though the whole documnent is working in forced pixel alignment. Due to this I have to constantly monitor and be aware of resizing everything to make sure it is working in full pixels. Is there a way when I scale an object, ie grabbing the blue handle points and increasing or decreasing its size, while maintaining full pixels? This would help massively on my end in solving how affinity works.
    Like others though this is really beginning to dent my ability to use Designer going forward. It is literally adding hours to my work flow.
    https://www.loom.com/share/d4d68bbd50ac4a68892ca40852a5cf72
  13. Like
    davidlower8 reacted to Chris B in REALLY SLOW - affinity designer for mac   
    Oh I thought you meant issues with Metal compute on. It sounds like you need to keep Metal compute off but try experimenting with OpenGL and Metal (Display) to see which works for your setup. 
  14. Like
    davidlower8 reacted to Chris B in REALLY SLOW - affinity designer for mac   
    They are just different renderers. Software uses your CPU and is slower whereas OpenGL and Metal will use a discrete card. The Display setting is used to render what is drawn on the screen. Metal compute (in Designer) is used for brush performance.
    Try and use Metal instead of OpenGL unless you are experiencing performance issues but keep Metal compute off. 
  15. Like
    davidlower8 reacted to Chris B in REALLY SLOW - affinity designer for mac   
    Disabling 'Metal compute' from Preferences > Performance may be the solution. Alternatively, if it isn't enabled—try enabling it.
    Metal compute will heavily depend on your type of GPU so try experimenting with the setting to see what works best. 
  16. Like
    davidlower8 reacted to Morten_Hjort in REALLY SLOW - affinity designer for mac   
    Disable the "Enable Metal compute acceleration". That including using OpenGL fixed it for me. There are HUGE changes in performance depending on the settings, but Serif haven't been very vocal about it.
  17. Like
    davidlower8 reacted to Tezza2 in REALLY SLOW - affinity designer for mac   
    My machine is exactly as you describrd yours now. Ever since the upgrade I have had a lot of problems with it. Slow and very slow, high memory use and a couple of times my mac has hung up and I had to reboot. Deffinately the upgrade.
  18. Like
    davidlower8 reacted to Angelize in Create foil texture   
    Hi everyone!  Here is the video tutorial.  I hope this is helpful
     
     
    In the video I used a gradient swatch downloaded from a set posted by Design Art Studios  if you want to use the same gradient I used here is a link to the facebook post  https://www.facebook.com/groups/AffinityDesignerPhotoPublisher/permalink/1108543209314275/
  19. Like
    davidlower8 got a reaction from Alfred in How to install fonts from Mac to iPad   
    Thanks @PMudditt and @Alfred for this.
    @PMudditt I did not notice that feature before. I am almost certain it did not exist. Admittedly it was a good 6 months or more before I last checked. I just remember I couldn't get anything to work for ages. Anyway that feature worked very well. I imported all my fonts relatively painlessly. I have not noticed a lag in performance which is great.
    @Alfred I tried setting up individual profiles and although it worked it was too painful to do for 400-500 fonts. At the moment I only need the fonts for affinity designer. But it is a nice idea and useful to know.
    Thanks for the help everyone.
  20. Like
    davidlower8 got a reaction from Alfred in How to install fonts from Mac to iPad   
    Thanks @PMudditt and @Alfred for this.
    @PMudditt I did not notice that feature before. I am almost certain it did not exist. Admittedly it was a good 6 months or more before I last checked. I just remember I couldn't get anything to work for ages. Anyway that feature worked very well. I imported all my fonts relatively painlessly. I have not noticed a lag in performance which is great.
    @Alfred I tried setting up individual profiles and although it worked it was too painful to do for 400-500 fonts. At the moment I only need the fonts for affinity designer. But it is a nice idea and useful to know.
    Thanks for the help everyone.
  21. Like
    davidlower8 reacted to R C-R in Slice size, in Export Persona, too big when using adjustment layer   
    A screenshot of the Transform panel with the vector object selected with the Move Tool might help us see what the issue is. Also, in Preferences > User Interface, check to make sure the value for Pixels in the "Decimals Places for Unit Types" section is set to 1 or more -- if it is set to zero you won't see factional pixel values in the Transform panel because they are rounded off to whole pixel values for the display (but internally all the values retain the decimal part).
  22. Like
    davidlower8 reacted to R C-R in Slice size, in Export Persona, too big when using adjustment layer   
    I just wanted a screenshot of the Transform panel in the Draw Persona with the object selected with the Move Tool. There is no Move Tool in the Export Persona, so I neglected to mention it was the Draw Persona's Transform panel I was hoping to see.
    In retrospect, I should have made that clearer -- sorry about that.
  23. Like
    davidlower8 reacted to v_kyr in Slice size, in Export Persona, too big when using adjustment layer   
    Check the associated export preset by selecting/clicking on a slice.
    Further you can double click into the shown [1x ] text field and edit the 1x value there to the desired exact "700w, 367h" (width, height) size you want!

     
  24. Like
    davidlower8 reacted to walt.farrell in Exporting multiple files at smaller sizes   
    No, I never found anything more. The pulldowns in the dialog are fairly clear about the options you have in them.
    But you raise an interesting question about your experiences. In a quick test that does not happen for me. So, it would help to have a sample file that demonstrates this phenomenon. It would also help to know which Affinity application you're using, and whether you're on Mac or Windows.
    (I have a vague memory of having read something about 1x, 2x, 3x being intended for different screen resolutions/sizes, which (if I'm remembering correctly) might help explain what you're seeing. But I don't know what/where I read about that. Sorry.)
  25. Like
    davidlower8 reacted to anon2 in Exporting multiple files at smaller sizes   
    .
×

Important Information

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.