You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found an issue that’s preventing me to fence the extremes on this project. Fencing doesn’t behave consistently.
As we did it back in February, for each fence we need to add two sets of mappings for them to work, one pin and one with the value we want to fence an axis. They work like this for opsz 14 and opsz8.
But for opsz144 this does not work even though the geometry looks good in the Fencer app.
In this example, 144 100 1000, the YOPQ value of this is 228, so I try to fence it to 230 with this mapping, but it goes beyond, both in Fontra and the compiled ttf.
What is strange is that this structure worked good for all previous fences on the designspace. @Lorp Do you have any idea of what’s needed to fence this one?
Also, I tried saving the font from the fencer app and it does not generate the full designspace of the font, blended axis doesn’t work and neither the axis, it just moves weird on the current axis combination you had selected while slicking on the “Save font” button.
Any help will be apprecieted, thanks!
The text was updated successfully, but these errors were encountered:
Now, when trying to fence YOPQmax for 144 100 1000, it goes beyond and back, this last fence doesn’t work. At this location, the YOPQmax blended value is 228, so I’m trying to fend it to 230 so the tiny contours doesn't disappear overlapping.
Fencer Issues
When I load the latest VF into fencer, then download font from it, it breaks opsz, weight, width, & slnt that were working on the font that I dropped.
Also, after adding all the mappings, when I download it again with all added mappings it breaks all parametric axis.
The resulting VF from Fencer is different from fontmaker & Fontra.
Hallo,
I found an issue that’s preventing me to fence the extremes on this project. Fencing doesn’t behave consistently.
As we did it back in February, for each fence we need to add two sets of mappings for them to work, one pin and one with the value we want to fence an axis. They work like this for opsz 14 and opsz8.
But for opsz144 this does not work even though the geometry looks good in the Fencer app.
In this example, 144 100 1000, the YOPQ value of this is 228, so I try to fence it to 230 with this mapping, but it goes beyond, both in Fontra and the compiled ttf.
What is strange is that this structure worked good for all previous fences on the designspace. @Lorp Do you have any idea of what’s needed to fence this one?
Also, I tried saving the font from the fencer app and it does not generate the full designspace of the font, blended axis doesn’t work and neither the axis, it just moves weird on the current axis combination you had selected while slicking on the “Save font” button.
Any help will be apprecieted, thanks!
The text was updated successfully, but these errors were encountered: