Before we dive into the list, we need to define what "verified" means in the Plotagon ecosystem. A verified glitch is a repeatable software malfunction that meets three criteria:
These are not subjective issues like "the app feels slow." These are objective, verified malfunctions.
Severity: Low
Frequency: ~15% of scenes with 3+ characters
Steps to Reproduce:
Status: Verified (Windows/Mac) Description: You delete Scene 5. But during export, Scene 5 still appears for 0.5 seconds as a flash frame before Scene 6 begins. plotagon glitches verified
Why it happens: Plotagon’s timeline compression fails to fully purge deleted scenes. The renderer finds residual keyframes.
Verified Fix:
Plotagon has a memory leak. After 45 minutes of active editing, performance degrades, and glitches become more frequent. Verified glitch #3 (Vanishing Props) almost never occurs in the first 30 minutes of a session. Save, close, and reopen the app every hour. Before we dive into the list, we need
This is painful but verified. Plotagon’s undo history is corrupt. If you use Ctrl+Z (or Cmd+Z) more than 5 times in a row, you will trigger Glitch #2 (Lip-Sync Mismatch) or Glitch #6 (Duplicate Character). Instead of undo, delete and re-do manually.
Status: Verified (iOS particularly) Description: Subtitles appear 1–2 seconds before the character speaks, spoiling the joke or dramatic reveal.
Why it happens: iOS’s text rendering engine calculates word-wrap length differently than Plotagon’s Android and Windows engines. Long words cause a pre-calc lag. These are not subjective issues like "the app feels slow
Verified Fix:
To understand the glitches, you have to understand the architecture. Plotagon was originally designed as a simple text-to-movie tool for schools. Over time, they added:
The core codebase, however, was never rebuilt for these additions. As one former developer noted anonymously on a forum: “Plotagon runs on a unity engine wrapper from 2014. Adding new features is like building a skyscraper on a marshmallow foundation.”