I'm on the Flash side of writing some 2D components going into CryEngine. Fonts are embedded in the FLA I'm delivering, and the textfields are created w/ actionscript.
Everything works fine as long as the embedded fonts are the regular version of the font. It even works if I pick random opentype fonts off the internet and embed them. I can embed Arial without a problem. But if I embed subfonts from the same family (e.g. Arial Bold, Helvetica Bold Condensed), I get a "Missing font" error.
Hum...odd. I have never had this issue before. Are you embedding it right? Select your textbox, press Embed... then select Numerals, Uppercase, Lowercasse, Punctuation , click OK. let us know
The issue does pertain to having multiple members of the same font family. The fonts were properly embedded (for an SWF that would play in Flash Player), but Scaleform was unable to read them. Resolution was to uninstall all other fonts from that family on the compiling machine, then create a font lib for import using the desired faces. Only one per family seems to be allowed, still.
That's very weird. What version of flash do u have? I made 3 texboxes, one with Arial Regular, one with Arial Bold, and one with Arial Rounded MT Bold, and I don't having any issue.
This is scaleform gfx 3.3x - not running in flash player. The compile was done in CS5.5, and fonts do embed for FP and web. The issue is when running under gfx in CryENGINE.
This is not a Flash player issue, it's a scaleform problem.
Unfortunately I don't know anything about cryEngine.
Perhaps you could edit the typefaces you need with a font editor so you can export the different font families as actual fonts. Then you can import the different fonts and you won't be having the issue that removes the font variants.
Unfortunately I don't know anything about cryEngine.
Perhaps you could edit the typefaces you need with a font editor so you can export the different font families as actual fonts. Then you can import the different fonts and you won't be having the issue that removes the font variants.
Thanks. Actually, that was basically what we did. Uninstalling all the other fonts in the family from the compiling machine seemed to do the trick for almost all the fonts in question. Not a great solution, but it works...
Good to hear you have found a solution. Still a strange issue, and I agree it isn't ideal this way, but it looks like the kind of bug you have no control over.
Reply With Quote
Something better now, let's code! )
Originally Posted by koenahn
