Jump to content

Sean P

Staff
 View Profile  See their activity

  • Posts

    10,297

  • Joined

  • Last visited

 Content Type 

Everything posted by Sean P

  1. Sean P
    Hi Razvantudor, Sorry for the delay in responding to your post. Affinity Designer is currently beta software which means there are likely to be some bugs and crashes - which is what we are trying to iron out. Have you encountered this issue using 1.5.0.7? With regards to graphic card - the only minimum spec we have is that the card itself supports the DirectX 10 Feature set. If your card doesn't support this you will be informed when trying to run the software.
  2. Sean P
    Hi Willabong, Sorry for the delay in responding. Is this still an issue for you in 1.5.0.7?
  3. Sean P
    Hi mhpembe, Sorry for the delay in responding to your post. Is this still an issue for you in the latest 1.5.0.7 build?
  4. Sean P
    Hi 3DM, Sorry for the delayed response. Unfortunately I'm unable to reproduce this (using build 1.5.0.7). I've attached a screenshot showing the drawing in AD and also the exported PNG im GIMP, as well as my AD file and the AD's Export (after selecting sRGB profile in the PNG export). Is this still an issue for you in 1.5.0.7? ICCTest.afdesign
  5. Sean P
    Hi EricS, Sorry for the delay in responding to your post. This was known issue with some of the earlier builds, however this should now be resolved in the latest 1.5.0.7 build available here.
  6. Sean P
    Hi FPilou, Thanks for letting us know! I've passed these onto the translation guys! :)
  7. Sean P
    See attached GIF
  8. Sean P
    Hi Ophie, Sorry you haven't had a response to your issue. Would you be able to install the new 1.5.0.7 build and see if you are still getting the same issue as 1.5.0.5 Thanks!
  9. Sean P
    Hi ygoe, Sorry your post has not had a reply. Do you have a copy of your ai file that shows the issue so we can take a closer look? Feel free to either PM me a Dropbox link or WeTransfer link. Thanks!
  10. Sean P
    Hi adreamer, I'll get this reported and passed on to the developers! Thanks
  11. Sean P
    Mark, When using the Microsoft Pinyin IME I do not get any prompts to select the characters either. S7venYoung Along with the Pinyin IME what keyboard layout are you using?
  12. Sean P
    Hi Andre, Could you attach the file shown in the screenshot please? ---- Oi Andre, você pode anexar o arquivo mostrado na imagem, por favor?
  13. Sean P
    Hi Alfred, I've passed this over to the developers.
  14. Sean P
    Hi af-user, Glad it has now been sorted for you! :)
  15. Sean P
    Thank you very much for the font - I can now reproduce it so there is definitely something odd going on there - I'll get it reported! In the meantime I would suggest uninstalling the font if you need to use Arial! :) EDIT: In fact there looks to be serious issues with this font - Font Book on the Mac actually see's it as a duplicate of the Arial Regular font - which would explain why it is behaving the way it does.
  16. Sean P
    Thanks for the file - unforrtunately I'm not able to reproduce the behaviour. However it looks like it is applying a font called 'Beck Sonderzeichen' to that piece of text. Would you be able upload that font (filename is BCDings.ttf I think) to WeTransfer and PM me a link please? I can then install it and see what happens. In the meantime if you could try uninstalling and see what behaviour you get. Thanks.
  17. Sean P
    Thanks for the images Tomcat, The two screenshots featuring English translations will be fixed in the upcoming build 6. With regards to the mistranslated 'Shift' I will get that reported!
  18. Sean P
    Hi Michail, 1. Could you attach the AFDesign file that you took this screenshot from please? Very strange you're getting that with Arial! 2. The font is actually there, however it appears as just 'Futura' in the list. There have been a few issues similar to this reported that are with the developers - however this is the way Font Book on the Mac also lists the fonts.
  19. Sean P
    Hi afuser, I've been able to reproduce this on both Mac and PC - I'll get it reported to the developers.
  20. Sean P
    Thanks dewaberlin, I've reproduced this and passed it on to the developers!
  21. Sean P
    Hi Hansjörg, As I previously said by default RWL files do not display (because RWL file format is not in the list which is with the devs), instead you have to type *.rwl in the open dialog first and then select your RWL file. I have used the RWL files in the from Photographyblog.com as I originally linked to in my first post and they open for me without a problem. What I'm most concerned about is the crash you are getting with the converted DNG. I understand you do not use cloud-based services however WeTransfer doesn't require you to sign up or input any personal information so if you could upload there that would be great, alternatively send me a PM and i'll drop you my email address to send the DNG file too. Thanks
  22. Sean P
    Yes please, once reproduced please save and attach the offending document! It sounds as though an action inside the application is making it happen instead of hardware.
  23. Sean P
    Hi Lilpri, Would you be able to give a bit of information on your machine at all please - as I don't believe we have encountered this yet! What OS, CPU and Graphics card are you running? Would you be able to attach a document when it is in that state please? Thanks
  24. Sean P
    I've now removed the fonts from the post - however they are vital for us to resolve the issues.
  25. Sean P
    Hi Michail, Would you be able to show a screenshot of the issue you are getting with the Arial font please? Currently Type 1 fonts are not supported in Affinity and there is an issue where they are incorrectly showing. What fonts do you have installed that are not appearing in the list - could you attach some of those for us please?
×
×
  • 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.