> For the complete documentation index, see [llms.txt](https://captivatehelp.newbluelive.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://captivatehelp.newbluelive.com/troubleshooting/graphic-flickers-on-playback.md).

# A graphic flickers on playback

A graphic that plays cleanly in the Designer Preview but flickers in Captivate’s Program Monitor almost always has one of two causes. Check each.

## Cause 1: a Pause marker is too close to a layer’s start or end

The Pause marker tells the cache where the graphic’s "hold" state is — what should be on air after the entry animation finishes. If a layer ends or begins within a frame or two of the Pause marker, the cache has almost no content on either side of the pause and the layer can flicker as the cache transitions in or out.

To check:

1. Open the graphic in the Designer.
2. Look at the timeline. Find the Pause marker in the marker strip at the top of the timeline.
3. Walk down each layer and check whether any layer’s start or end sits within one or two frames of the marker.
4. If you find one, either:
   * Move the layer’s start or end further from the Pause marker (drag the edge of the layer track in the timeline), or
   * Move the Pause marker (right-click the existing marker, remove it, then right-click at the new position and add a new Add Pause Point).
5. Re-cache the graphic in Captivate and play it on air to confirm the flicker is gone.

The [Optimize Timing](/design-and-customize-graphics/chapter-index-3/optimize-timing.md) tool also catches this and may automatically move the Pause marker one frame earlier to avoid flicker. If you’ve already optimized and still see flicker, the optimization may have hit a layer that needs manual adjustment.

## Cause 2: two external sources are driving the same graphic variable

Each variable in a graphic accepts one value. If two external sources both push values to the same variable, the variable updates whichever arrived last — and if both keep updating, the layer flickers between the two values.

This usually happens one of two ways:

* A Tables data column has the same name as a variable in the graphic, so it auto-binds; AND a Data Controller variable was also bound to the same graphic variable through **Link Data**. Both push, both win in alternation.
* Two Data Controllers are bound to the same layer, each providing its own value for the same variable.

To check:

1. Stop the playback.
2. Open **Link Data** on the layer (the icon at the left edge of the Preview panel).
3. In the **Link Data** view, find the graphic variable that’s flickering and confirm that exactly one external source is bound to it.
4. If more than one is bound, remove the binding you don’t want.
5. For Tables auto-bind: rename either the data column or the graphic variable so they no longer match, OR explicitly bind the variable in **Link Data** to the source you want (the explicit binding takes precedence over auto-bind).
6. Re-cache and play the graphic on air to confirm.

## Related

* [Optimize the timing of a graphic](/design-and-customize-graphics/chapter-index-3/optimize-timing.md)
* [How Data Controllers work](/play-and-update-graphics/chapter-index-3/how-data-controllers-work.md) (Link Data section)
* [Playback doesn’t behave as expected](/troubleshooting/playback-doesnt-behave-as-expected.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://captivatehelp.newbluelive.com/troubleshooting/graphic-flickers-on-playback.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.