Jump to content
Our response time is longer than usual currently. We're working to answer users as quickly as possible and thank you for your continued patience.

Dan C

Moderators
  • Posts

    11,096
  • Joined

Everything posted by Dan C

  1. Thanks for your report and our sincerest apologies for the delayed response here. We are exceptionally busy following the release of V2 and we thank you for your continued patience and understanding here. Just to confirm, this issue is logged with our development team and I will be sure to 'bump' this with them now to bring it to their attention once again. I hope this helps
  2. Hi @haGi, Thanks for your report and our sincerest apologies for the delayed response here. We are exceptionally busy following the release of V2 and we thank you for your continued patience and understanding here. I can confirm this issue is logged with our development team, I will be sure to 'bump' this issue with them now to bring it to their attention once more. I hope this helps
  3. Hi @PJ design, Thanks for your report and our sincerest apologies for the delayed response here. We are exceptionally busy following the release of V2 and we thank you for your continued patience and understanding here. I can confirm I recently discovered this issue and it is logged with our developers, it seems to occur when quickly returning through at least 2 'sub levels' of the Text Studio, as shown here - RPReplay_Final1675269348.MP4 Hopefully this should be fixed in an upcoming update
  4. Hi all, Thanks for your report and our sincerest apologies for the delayed response here. We are exceptionally busy following the release of V2 and we thank you for your continued patience and understanding here. As can be seen from the following link - https://support.dxo.com/hc/en-us/articles/4409304781201-Nik-Collection-compatibility-with-OSes-third-party-software - Unfortunately only the NIK collection 5 is compatible with Affinity V2 at this time, my apologies.
  5. Thanks for your report and our sincerest apologies for the delayed response here. We are exceptionally busy following the release of V2 and we thank you for your continued patience and understanding here. I can confirm this issue is logged with our developers and I will be sure to 'bump' this with our team now to bring it to their attention once again. I hope this helps
  6. Hi @Florida, Thanks for your report and our sincerest apologies for the delayed response here. We are exceptionally busy following the release of V2 and we thank you for your continued patience and understanding here. I can confirm this issue is logged with our developers and I have 'bumped' this with the team for you now. I hope this helps
  7. Hi @Friedrich Huchting, Thanks for your report and our sincerest apologies for the delayed response here. We are exceptionally busy following the release of V2 and we thank you for your continued patience and understanding here. I believe I have discovered the cause of this issue with .PEF files in Affinity - can you please open Affinity Photo, then navigate to Affinity Photo 2 > Preferences > Assistant. In this dialog, please select Develop Assistant and you should see a new window open. I suspect here you should see the option Exposure Bias set to 'Apply exposure bias as initial state'. Please change this to 'Take No Action', then try loading your .PEF files once again. I will be logging this as a bug with our developers now, as enabling this option does not affect other RAW formats in the same way. I hope this helps!
  8. Hi @TEcHNOpls, Thanks for your report and our sincerest apologies for the delayed response here. We are exceptionally busy following the release of V2 and we thank you for your continued patience and understanding here. I can confirm I have replicated this issue here and I have logged it with our developers, I hope this helps.
  9. Thanks for your report and our sincerest apologies for the delayed response here. We are exceptionally busy following the release of V2 and we thank you for your continued patience and understanding here. I can confirm this issue was resolved in version 2.0.3 - please ensure you have updated your Affinity app to apply this fix
  10. I'm not currently certain which is correct, the helpfile seems to indicate these should be present (and personally I would expect them to be) however from my testing it doesn't appear as though these options are available in the app, though it may be the helpfile which is wrong. I'll be logging this with our developers now and I will be sure to update this thread, with any further information I am provided
  11. Thanks for letting me know and the information provided here, I have logged this information with our team for further investigation as unfortunately I don't personally have a HDR monitor for testing. As you've mentioned, I'd recommend keeping Hardware Acceleration disabled until our team can resolve this issue, many thanks!
  12. No problem at all, many thanks for the further information and screenshots provided! I'd like to try changing the following settings, to see if this reduces the crashing behaviour. Under Preferences > Performance, please untick Hardware Acceleration, then change the Display to OpenGL. Restart the app as prompted and then try loading/editing your documents once again - does this help stop this crashing occur please?
  13. Apologies, thanks for confirming that for me - further down this page the following is shown, indicating the Collection 4 is unfortunately not compatible with Affinity V2: I hope this clears things up.
  14. I have hidden multiple posts from this thread, please remind yourselves of the Forum Guidelines before posting.
  15. Apologies for the delayed response here & thanks for the further image provided - I can confirm I'm seeing the error with the second file provided and I will be sure to log this with our developers to see if we can handle this type of file better in the future, however as Richard has mentioned this appears to be an underlying issue with the DNG files that Topaz is generating, and not with the Affinity app directly.
  16. Hi @RM f/g, Thanks for your report and our sincerest apologies for the delayed response here. We are exceptionally busy following the release of V2 and we thank you for your continued patience and understanding here. I can confirm I've replicated this issue and a few others when using long sidenotes & therefore I have logged these with our developers for you now. I hope this helps
  17. Hi @Gchurchley, Thanks for your report and our sincerest apologies for the delayed response here. We are exceptionally busy following the release of V2 and we thank you for your continued patience and understanding here. I can confirm that version 2.0.4 has since been launched, which has resolved documents crashing on load for other users - can you please try updating to this version and letting me know if this helps? Secondly, when the app crashes, is a crash report generated? If so, can you attach a copy of this here for me? Many thanks in advance
  18. Hi @pirochan_whwm, Thanks for your report and our sincerest apologies for the delayed response here. We are exceptionally busy following the release of V2 and we thank you for your continued patience and understanding here. I can confirm that I have replicated this issue with your file and have logged this with our developers to be resolved - I believe it is due to the 'transform="translate' values in the file, as there are some known issues in Affinity when using these. I hope this helps
  19. Hi @Ebru, Welcome to the Affinity Forums, sorry to hear you're having trouble and our sincerest apologies for the delayed response here. We are exceptionally busy following the release of V2 and we thank you for your continued patience and understanding here. It's unfortunately unlikely that our team are able to recover these files, as missing information is as described, and therefore usually cannot be 'found' - however we can certainly look into this for you. Are you able to attach a copy of the file that shows this error here for me? Many thanks in advance
  20. Thanks for your report @NotMyFault - interestingly I can replicate this without the need to use artboards, and I believe it is due to the same issues raised in your thread here: Therefore I have updated the development log report for that thread, with the information here
  21. Thanks for your report here and our apologies for the delayed response! I have logged this issue with our development team to be investigated further and hopefully resolved asap. I hope this helps
  22. Hi @NotMyFault, Thanks for your report - I've replicated this on Windows with both Hardware Acceleration enabled and disabled - indicating this is an underlying issue with the compositor and not Metal etc, so I will log this with our developers now
  23. Hi @catlover, Apologies for the delay here - I can confirm that when using the Node Tool with a Curve layer selected directly, the Transform Studio does not display information, as the information in the Transform Studio is representative of the 'bounding box' shown for your active selection, and a bounding box is not displayed when selecting a Curve directly with the node tool. As mentioned above, with Transform Mode enabled and more than 1 node selected, a bounding box will now show and therefore this information is reflected in the Transform Studio. I will however move this thread to the Feedback section of the forums for our devs to see and consider changing the Node Tools behaviour in the future, such that this information is shown in the Transform Studio. I hope this helps!
  24. Hi @MatPen, Thanks for your report and our sincerest apologies for the delayed response here. We are exceptionally busy following the release of V2 and we thank you for your continued patience and understanding here. I have tested this in 2.0.4 with 5 PDF files, and 'Automatically update linked resources when modified externally' disabled in Publishers preferences - I was able to place, edit the PDF files externally and then update all file at once with no crash/hang shown. Can you please confirm for me, what location are these PDF files saved to on your mac? ie is this a 'cloud synced' location, a local folder, etc Does this occur with any PDF files, or only those being generated/updated by your musical application? Many thanks in advance!
  25. Please see my post above, as sansnom has requested this and I've explained the current behaviour, based on the thumbnail size the Affinity document generates. I'll be sure to add your vote to the feature request described in the above post
×
×
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. 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.