Test DotFlow on the published page. Editor preview confirms the structure, but final fonts, viewport width, links, images, and CMS data can change the result.
The track is empty
Confirm that DotFlow contains at least one child item. For Total CMS 3 content, verify that the collection returns published objects and that the fields used by the loop are not empty.
The loop jumps or has a visible break
Shorten unusually wide items, then adjust Gap and the separator. Check that every generated CMS item produces valid content. Test with PingPong Mode off and on to isolate the motion behavior.
Text is difficult to read
Reduce the speed.
Increase contrast between dots and the background.
Reduce glow, glare, or dot softness.
Try Crisp Mode.
Check font size, weight, letter spacing, and line height.
Images are unclear
Use a simpler or larger source image, adjust dot size and spacing, or disable Pixelate Images. Do not depend on a detailed image as the only way to understand an item.
Reduce unnecessary work
Enable Pause Offscreen, limit long CMS result sets, and avoid excessive glow or multiple large DotFlow sections on one page.
Accessibility checks
Do not place essential information only in a moving banner. Repeat important announcements in stationary page content. Keep link text descriptive, preserve strong contrast, and use a moderate speed. Pause On Hover helps pointer users, but it is not a complete control for every visitor, so keep the content short and nonessential.
If a problem remains, email support@stackswork.com with the DotFlow version, content source, motion settings, a public test URL, and screenshots at the affected viewport size.
Related: Adding child stacks and Total CMS 3 content and Controlling motion and dot-matrix rendering.