Is there any way to troubleshoot / know / see what the issue is for my interpolation, apart from reading the whole manual and then over time/months etc figuring out what it is?
like a pre-flight panel / modal that says what node is incorrect etc etc???
Cheers
What do you mean exactly? Are you experiencing incompatibility between your masters? Or interpolation issues in your exported variable font?
Reading the manual (at leats a tiny bit) is always a good idea, because you would quickly find this: Multiple Masters, part 2: keeping your outlines compatible | Glyphs
Specifically, you are looking for the section “Compatibility View”.
Between masters, and thank you for that.
My question was more about, not re-reading through the manual and going through all of the possible reasons, but if the software knows it’s not compatible, is there a way for us to like, see what the incompatibility is? Just saving all the time going through the different things, asking back and forth and then just looking at the manual again.
(in this example, i’ve copy/pasted the same glyph into 3 weights and its incompatible, same nodes, same everything. But it’s not really what I’m after, more of an overarching way for users to see what the issue is, not to research all of the issues and going through them one by one, if that makes sense.)
Cheers.
As I said: Specifically, you are looking for the section “Compatibility View”. That is exactly what you are describing.
Yeah im looking at that now, youre missing my entire question, assuming reading the manual is the only thing available to users. thanks anyway
The compatibility view shows you very clearly what the issue is and why your outlines and/or anchors are not compatible.
What information is unclear to you?
It’s very clear to people that have read the manual and interpreted/understood it correctly, and that dont have questions.
My question was not about interpolation itself, but about visual descriptors, modals, windows or anthing showing me what the actual problem (my-file specific troubleshooting not just “make sure to do this” which tells me nothing about my situation) is apart from going back to the manual ad nauseam until im a Glyphs veteran. Is there a legend? It mentions things to me that leave wide open interpretations when it comes to multiple masters…. Im not asking to be difficult but if the manual is all there is, thats all there is, thats why im asking because the manual + youtube trawling is all ive got.
— What is a purple node?
— How could the exact same shape w/ nodes be incompatible over multiple masters
— Yellow or Red segments are sometimes present, but if i copied over the exact same glyph, it has all of the same nodes, exactly, is that the problem, and how could that be?
— It mentions Yellow or Red segments, does it mention anything anywhere about Red handles? Is this a general warning of something or do they also mean incompatibility? and if so, why is that happening with identical copies?
I dont want to bother anyone with these questions, and if there isnt anything apart from the manual + youtube thats fine ill just do whatever
I assume something happened when you pasted. Like open path ends that connected or an accidental double paste.
And compatibility is established between paths, components — and anchors. Compatibility view does mention missing anchors though.
The red lines in compatibility view point to what? Can you share a screenshot?
I just started the faulty glyphs again.
If you can confirm that theres only the manual, and knowledge about most of the colours on nodes/segments etc, than thats my question resolved. Just wondering if there was anything like a preflight panel or modal, anything at all apart from reading things.
All good, cheers!
There are some plugins in Window > Plugin Manager for some additional visualization. For documentation, I recommend the second multiple master tutorial about compatibility:
You only need to read it once.
That’s the one I linked, yes. RTFM really is a good principle and will save you a lot of time.
You’ll see that the compatibility view is essentially a preflight panel, you just need to know how to read it.