-
Posts
15 -
Joined
-
Last visited
Posts posted by GRSJeremy
-
-
I have attached the Photo File which has that problem. Designer gives me exactly the same issue as well.
My understanding is now that those fonts are just not well made...
-
On 5/26/2020 at 9:38 AM, Sean P said:
Hi GRSJeremy,
Would you mind attaching a copy of the Quicksand versions you are using please? I've downloaded the current ones from Google from the link below and they're v3.004 which are all fine.
https://fonts.google.com/specimen/QuicksandSorry for the lat response, but I have had some stuff going on in life with the current Virus situation. I am back working now. The files I have attached are the ones causing the issue.
-
The text is still a text and has not been converted to paths.
I did eventually change it to paths to patch it up... I have never came across such a problem... Affinity Photo does the same with that particular font.
-
Hello everybody!
I couldn't find a similar problem on this forum, so I started this thread.
I am currently working on a project which relies on Google Fonts, and I am using the "Quicksand" font, but for some reason it has got some issues (holes) and I have to patch them by hand every time I am using that font. That problem does not occur on all other Adobe products or in Office, it is very unique to the Affinity suite.
Does anyone know what that could be?
If you look at that screenshot; the letter "A" has got those issues.
-
-
On 6/25/2019 at 11:45 AM, R C-R said:
Yes that might be correct and I have seen it :), but I am just not used to the fact that staff are so approachable, that's all... I am in different forums, and the forum staff is getting called "staff" there too, but they are not directly involved with the product itself, as the company structures are usually way bigger and less approachable... I am just pleasantly surprised, especially coming from Adobe where it is really the opposite... The staff on their forums is not really the staff working on the product... That was my point really
-
21 hours ago, Murfee said:
Callum is staff, he has said he will look into this on Monday
Oh Sorry, I never realised that the moderators are staff too Normally the forums are not that integrated with the staff in there
-
How do I know that the staff knows about this bug? I am still a little bit confused, because I am trying to find a contact on the affinity website, but all it says is to post in this forum
-
52 minutes ago, HVDB Photography said:
HI @GRSJeremy,
I'm on Windows 10 and I had no problems developing your DNG-file.
I exported it as a TIFF-file (98 MB)
Thanks for the efforts Well I think it will be a Mac Issue I take it? As far as I know both the Windows version and the Mac version are treated seperately. So I just hope that someone can shed some light into this at some point .
I am also open for a Teamviewer session if it helps the Affinity people
-
This is certainly pretty cute and very clean looking! Nice job!!
-
14 minutes ago, Murfee said:
@GRSJeremy while you are waiting for this to happen you can manually make adjustments like distortion etc then save as a preset for use on all your other files taken with the same lens. Not the same as automatic but pretty quick if you label each preset for each lens you use.
Yes thanks for the tip! I shall do that! I will not let it deter me from being Adobe free
-
Oh sorry, I didn't see the replies as I did not get an email notification and I just checked on the off chance. Yes of course I can provide you with the DNG file. I use multiple cameras, but I always convert to DNG for compatiblity issues.
When I switch it to the Apple RAW engine it displays it just fine, which is good in the meantime. But the problem with that is, that I cannot do the lens specific adjustments like the Serif engine can do.
-
-
Hello!
I have just bought Affinity Photo because I wanted to switch from Photoshop. But unfortunately I can't use it at the moment, because all the DNG files are showing up yellow and are missing (?) a blue channel? I tried changing the colour profiles etc, but nothing works at all.
I have found a similar thread from 2016 with the Windows version of Affinity Photo, but it does not really help me.
Has anyone got any ideas in how to resolve this?
Google Font "Quicksand" is not displayed correctly
in V1 Bugs found on macOS
Posted
I just checked back in here to see how the thread is doing!
I did not convert the font to paths, but that has been discussed anyways.
I resolved the issue with the Github font, I have not tried the latest google font now as it gave me so much grief last year...
I am intrigued to try it again with the Google version now and see if it has been fixed...