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

NathanC

Staff
  • Posts

    2,522
  • Joined

Posts posted by NathanC

  1. Thanks for following up, looks like you're trying to re-sample an image layer rather than a pixel layer, before you re-size the document, right click the layer > rasterise to convert your image to a pixel layer and then try resizing the document again using 'Nearest Neighbour' and this should retain the hard edges.

    Image layers retain all the information on their original colour space, resolution etc. so increasing the size of your document which contains an image layer isn't taking into account the re-sampling method used in the document re-size menu, it's just increasing the size of your placed image layer on your canvas similar to if you were to just drag the image handles to increase the layer's size.

    https://affinity.help/photo2/English.lproj/pages/Layers/layerImage.html

  2. Hi @dpeters911,

    I've not been able to reproduce this on a test document containing one of each of the linked resources you've outlined, after I saved my document I closed it down, moved the resources from 'Documents' to 'Desktop' and then opened the same doc again and ignored the remap resource locations prompt the file stayed open as expected. This was on Publisher 2.1.1 and Ventura 13.4.1.

    Could you possibly provide us with the files used in your example which are resulting in the crash when the resources are moved? I have provided a private upload link below if you do not wish to share them publicly.

    https://www.dropbox.com/request/XdYjsaCmOVOfrnJ4D79Z

    Also, do you have your desktop synced to iCloud? I've linked a guide here on how to check this if you're not sure: https://support.apple.com/en-gb/HT206985

    Many thanks

  3. Hi @amoraleite,

    Any chance you could provide us with your document so that we can investigate further? If you do not wish to share it publicly I have provided an upload link below.

    https://www.dropbox.com/request/8GAyfmSaA2IJMIzEXNbb

    Could you also confirm the following:

    - What Operating System and version are you using?

    - What app version are you using?

    Many thanks!

  4. Hi @Truc Pham

    I think i've spotted what's causing this, your digital planner and the teacher's planner have different document DPI values in document setup which is affecting the images on export when using the same preset. The digital planner has a document DPI of 72 while your teacher's planner has a DPI of 300, so when you're exporting your Teacher's planner document to PDF using the Digital (high quality) preset the images are retaining their existing placed pixel resolution in line with the document DPI which is resulting in a low quality result. However, on the digital planner which has a doc DPI of 72 all your images are being upscaled to 300DPI. 

    On your Teacher's planner under 'Document Setup' try changing the DPI to 72 and then exporting again to PDF Digital HQ, i've attached the result for comparison. It's also worth noting that your images in the teacher and digital planners have two different original pixel resolutions prior to being placed in the doc, so this is another factor to consider.

    Teachers Planner 72DPI exported to PDF Digital HQ Preset.pdf

  5. Hi @design punch

    There is a currently logged issue in regards to the default bracket keys to resize brushes not working on German keyboards, as ALTGR + 8/9 does not invoke the bracket key shortcut when it should be, however I've just tested the ALT modifier key with 1/2 to increase/decrease brush width on a standard English keyboard and this also doesn't appear to work any longer while it is working in V1, so I'll be logging this with the developers, other modifier keys such as CTRL + 1/2 to increase the brush size are working as expected.

    Edit: Just tested the ALT modifier key to re-size the brush in v2.0.4 and it is working as expected, so it looks like this is a regression between 2.0.4 and 2.1.

     

  6. Hi @Truc Pham,

    Are you referring to some of the image resources used in your exported PDF appearing blurry? Your PDF appears to have been exported with the images being downsampled to 300DPI which has drastically affected the overall quality of some of the images, particularly since some of these images are 4000x4000 that have been scaled down.

    I've attached a copy of your file which has been exported using the default PDF (For Export) preset which does not downsample images and the overall quality of the images is significantly better as their original DPI has been retained, however this comes at the sacrifice of a larger overall file size.

    I've highlighted the setting I'm referring to on the screenshot below.

    image.png

    Teacher Planner-Linked (test).pdf

  7. Thanks for confirming along with the recording, I recently logged a bug with the developers in regards to the paint brush tool (along with other similar brush tools) failing to retain assigned key bindings between app sessions in the Photo persona of Publisher, based on your screen recording this is exactly what's happening.

    I've now bumped the existing issue with your report.

  8. Hi @V_rob,

    When you launch the affinity applications, do you do so from the 'Applications' folder in finder, or does it launch from a DMG (Virtual Disk Image) file each time? Are the apps even present in the Applications folder? Launching the app from the .DMG file is essentially loading the app in using your Memory/RAM which isn't the correct environment and can lead to issues such as the app failing to update or retain custom user settings which are normally held on your local disk.

    If they are installed correctly and being launched from Applications, you mention that your shortcuts are gone, do you mean that all shortcuts have disappeared completely or have they just reverted to the serif defaults?

  9. On 6/20/2023 at 7:23 PM, Alex_M said:

    I've just installed the final 2.1.1 release (not the beta). The problem is still there. :(

    Ah, after testing this again looks like app version doesn't matter, but it's actually having Hardware acceleration disabled which causes the issue, as soon as I restart the app, enable H/A and restart again, it no longer occurs on your document with the mask layer.

    I'll get this logged.

  10. Hi @Lvictor welcome to the forums,

    Sorry to hear that, could you possibly provide me with one of the documents that's giving you this error when attempting to open it so I can investigate further? If you do not wish to share the file publicly I can provide a private upload link.

    In addition to providing the file, could you confirm the following:

    • What iPad model are you using?
    • What iOS version are you running?
    • Where are the files being opened from (E.G Files app, iCloud)?

    Many thanks

  11. Hi @AlanPickup,

    I've just downloaded a copy of the original Mike's Styles .afstyles file and compared the import results between V1 and V2, it appears that many of the effects settings (Bevel, Outline, Inner Shadow, Inner Glow, Outer Shadow) which have a px value are dropped down to a fraction of what they should be, for example 'Outer Shadow' Radius and Offset has been dropped to 0.01px instead of the expected 9px. FX adjustments which don't have a pixel setting such as Gradient overlay are not affected by this which is why it's still intact.

    Back in December I did log this with the developers but it doesn't appear to have been fixed yet and affects any FX adjustment with a pixel value applied, i'll update the existing issue with this example along with the additional findings.

     

    Mike_styles.afstyles

  12. Hi @Return,

    Warp group's don't currently change their bounding box to accommodate for the warp that has been applied the objects inside it, which has the knock-on effect that applying a text wrap rule to a warp group only applies to the original boundaries of the object prior to the warp, this is expected behaviour but does certainly leave room for improvement.

    In a similar thread linked below @Dan C logged an improvement with the developers for warp groups to offer an option to cycle the selection box to one which reflects the warped object's boundary, not the original so i'll update this improvement to also request that this should affect text wraps. 🙂

     

  13. 4 minutes ago, snh2058420972 said:

    I can confirm what you're saying partially, because while after an app restart the document renders the correct font, but fonts still don't appear in the Fonts section in options.

    In the app, the font is now shown not in red, but in dark colour and no other font can be selected (see attachment). 

    Strange, I'm not seeing that behaviour, after I install a Font in CC and add some text to a frame using that font (used Bilo to test) it will appear in red as an unrecognised font, after I restart the app and re-enter the document my text has changed to the correct font and i can go into the character panel and change the font without any issues. What about if you create a new document, add a text frame and change the font to Bilo along the context toolbar?

    This was done on an M1 ipad Pro running 16.5, what iOS version and iPad model are you using? Also, is there any difference following a reboot of your iPad?

  14. Hi @Yasha welcome to the forums,

    I've bumped the existing issue with your report, you should be able to keep your Bluetooth mouse connected but just finger tap on the export options to prevent the issue (try to avoid dragging your finger across the different export buttons as this can also trigger it).

    The OP in the thread I originally logged the issue in also mentioned that by turning off 'Reduce Motion' in the iPad accessibility settings this may also prevent the issue from occurring when selecting the export options with a Bluetooth mouse. 

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