| Previous | Next |
| D2DERR_TOO_MANY_TRANSFORM_INPUTS | ERROR_IO_PREEMPTED |
D2DERR_INVALID_GLYPH_IMAGE
D2DERR_INVALID_GLYPH_IMAGE belongs to Direct2D and DirectWrite text callback contracts. Direct2D or DirectWrite could not decode or parse the requested glyph image data.
Locate the first rejecting layer
Text rendering crosses IDWriteTextLayout, drawing effects, renderer callbacks, COM reference counting, font resources, and optional glyph-image formats. A drawing-effect type mismatch, retained callback renderer, and invalid glyph image are separate failures even though all may occur during one DrawTextLayout call.
font glyph-image format, table data, glyph index, palette, and rendering mode.
Controlled reproduction
Render plain outline text with no drawing effect, then add the effect object, custom renderer, and requested glyph image format one at a time. Track AddRef and Release around callbacks and retain the exact font face and glyph index.
- render an outline glyph from the same font.
- Test another glyph in the same image format.
- Validate the font with a trusted OpenType tool.
- request only formats reported as supported.
Evidence to preserve
- Font file hash and face index
- Glyph index and requested image format
- Color-font tables or embedded bitmap/SVG data
- DirectWrite and Direct2D interface versions
Misleading responses
This is narrower than a general font-loading failure: the face may load while one glyph image representation is invalid. Do not respond with a universal render-target recreation loop unless the returned status specifically documents device-loss recovery; graph, property, numeric, lifetime, and print-state errors require correcting their contract.
Technical references
Looking for a different code? Search another status or error code.