Why do overlapping curves cause overlap region to disappear?

I’m very confused. I have two closed curves and when one I overlap them the overlapped region disappears (is invisible). Why would this be? Presumably a related phenomena, when I try to use join on the two curves thinking this would solve the problem both curves effectively disappear, and where they were there are just a few dots in free space. Likely it’s important to note that these curves were created via the import image feature. I tried optimizing the curves to see if maybe something was weird that that might fix.

Also, presumably related, since the 10.1 update today many characters in my font which looked fine suddenly have regions of hollowness, again, as though curves are overlapping and being made invisible for some reason.

Any help? What am I not understanding and how can I fix this? Thanks.
overlap.png

Overlapping contours (intersecting contours) should be joined, or you fonts will look like this if exported with CFF Postscript outlines. Earlier versions of FontCreator did not make it obvious that this is a potential problem.

Use the Get Union of Contours command to join them. If the curves still disappear, share the image that you’re importing and someone else can try to reproduce the problem. It does still happen sometimes.
Intersecting Contours.png

So this is weird… the problem has suddenly disappeared… And it disappeared immediately after my virus scanner deleted FCOutDrw.dll because it thought it was the Trojan-Banker.Win32.Banbra.vdfk malware/virus (I posted about that issue in this thread). In that thread they mention that deleting that file may change how the font is rendered on screen…

This explains why this is now happening…

Have not yet been able to properly resolve the actual overlap, but I’ll give it another shot.

We usually don’t like duplicate posts, but in this case this post so relevant:

FCOutDrw is a new dynamic linked library (DLL) which is used to draw smooth glyph outlines. If the file is removed, FontCreator will use the old drawing method. To apply this workaround, do close FontCreator and then delete the file FCOutDrw.dll which can be found in Windows system folder. E.g. here:
C:\Windows\SysWOW64\FCOutDrw.dll

The new method uses the even-odd rule when it comes to determining whether an area is inside or outside while the old method uses the non-zero winding rule.
See: https://en.wikipedia.org/wiki/Nonzero-rule

The new method uses the graphical device interface to draw outlines, which should be faster, and is smooth. The downside at the moment is the fact we can’t change the fill mode.
oldnewdraw.png
The first line is drawn with the old method, the second line is the improved one.

The “F” consist of a single contour that is self-intersecting.

If the overlap is related to a composite glyph, you will need to make it simple, but you can also decide to ignore this white overlap, as the exported font won’t change.

Right now overlapping contours should be avoided with fonts containing CFF based outlines, but we suspect this will no longer be an issue in the near future.

So we will try to find a solution which allows you to show overlapping contours the way they used to be.

The update released earlier today solves the issue.
improveddraw.png
You can now set the fill mode through the Options dialog:
fillmode.png

Great! Thanks for the speedy fix.