In Captivate Classic, create your simulation project.
- Captivate User Guide
- Get to know Captivate
- Adobe Captivate releases
- Adobe Captivate 13
- Adobe Captivate 12
- Project setup
- Import from PowerPoint
- Import from Captivate Classic
- Generative AI in Adobe Captivate
- Generative AI overview
- Generative AI FAQs
- Generative credits
- Generate text
- Generate images
- Generate avatar
- Generate transcripts
- Add and edit text
- Add and edit images
- Add and edit media
- Interactive components
- Create quizzes
- Add widgets
- Interactions and animations
- Enhance your e-learning project
- Simulation projects
- Timeline and TOC
- Review and collaborate
- Preview and publish
- Accessibility
- Design options in Adobe Captivate
- Additional resources
Adobe Captivate 13.1 now supports importing simulation projects created in Captivate Classic. This feature is currently available as a beta release to enable early evaluation and feedback. Supported scenarios are limited, and imported projects may require review and adjustment before production use.
Adobe Captivate 13.1 supports importing projects created in Captivate Classic, including simulation projects (software demos and training simulations). Simulation projects are partially supported: highlight boxes, click boxes, input fields, and typing text objects are imported, but full-motion recording (FMR) content may not import as expected and some simulation formatting may require manual adjustment after import.
This article focuses on simulation-specific preparation, supported components, limitations, and workflows so you can successfully migrate Classic simulations into Adobe Captivate 13.1 (beta) and review results using the Import Logger utility.
Why use this feature for simulations?
Problem statement
Many organizations have software training and demos built as simulations in Captivate Classic (click boxes, text entry, highlight boxes, typing text). Re-recording every simulation is expensive, and staying on Classic is not sustainable.
Problem: You need to move Classic simulation projects into Adobe Captivate 13.1 (beta) without re-recording and with as much automation as possible.
Solution: Use the Classic project import with simulation-specific preparation: open and save the simulation in the latest Classic version and then import. Supported simulation components are converted; use the Import Logger to fix or redesign elements that need attention.
Prerequisites: prepare before import
Before importing a Captivate Classic simulation project:
What's supported and what's not supported
Project type: Simulation
Simulation projects are partially supported:
- Full-motion recording (FMR) content may not import as expected.
- Some simulation formatting may require manual adjustment after import.
Supported simulation components
Component |
Support |
Notes |
|---|---|---|
Highlight boxes |
Yes |
Imported and editable. |
Click boxes |
Yes |
Imported and editable. |
Input fields |
Yes |
Imported and editable. |
Typing text objects |
Yes, with condition |
Imported only if they exist in the original recording. Typing text objects are created only when you type text during the recording; that is the only time they can be created. Once the project is created, you cannot add a typing text object—they cannot be added manually after importing. |
Partially supported or may need adjustment
- FMR content may not import as expected
- Some simulation formatting may require manual adjustment after import
Not supported
- Virtual Reality (VR) slides
- SWF or Flash-based content and widgets
- Drag-and-drop interactions
- Motion paths
- Themes and master slides (master slide objects import as individual objects on slides)
Beta limitations (simulation impact)
- Complex animations may not map accurately.
- Objects set to display for the rest of the project import as separate objects per slide.
- Multi-state objects are imported as view-only and cannot be edited.
Prepare and import a Captivate Classic simulation
-
-
Open Adobe Captivate.
-
On the home screen, select Import > Captivate Classic Import (Beta).
-
Read the beta information if desired, then select Continue.
-
Browse to and select your simulation CPTX file.
-
Wait for the import to complete.
-
Imported slides are marked with the Captivate Classic icon.
-
Save the new project.
Review simulation project import with Import Logger
-
After importing a simulation (Workflow 1), select the **Flag** icon to open the Import Logger panel.
-
In the Active tab, review issues. Filter by error type, severity, or object type if needed.
-
Select an entry to view details and navigate to the affected slide.
-
For simulation-specific issues (for example, click boxes, input fields, FMR):
- Apply the suggested workaround when available.
- Or redesign the element using native Captivate 13.1 components.
-
For typing text: Remember that typing text objects can only be imported if they existed in the original recording; they cannot be added manually after import.
-
Archive resolved issues to keep the log organized.
-
Resolve critical issues before publishing.
Import simulation, fix formatting, and publish
-
Prepare and import the simulation (Workflow 1).
-
Open the Import Logger (Flag icon) and address Active issues (Workflow 2).
-
Manually adjust any simulation formatting that did not import as expected (for example, sizes, positions, timing).
-
Preview the simulation (current slide, from current slide, or entire project).
-
Go to Publish and select output (HTML5, SCORM, xAPI). Configure and publish.
-
Test the published simulation in target browsers and devices.
Handle FMR or unsupported simulation content
-
Import the simulation.
-
In the Import Logger, identify any FMR or unsupported simulation elements.
-
For FMR that did not import as expected: re-record in Captivate 13.1 or replace with supported media (for example, video).
-
For unsupported interactions: replace with native Captivate 13.1 interactions on new or existing slides.
-
Save, preview, and publish.
Limitations of the feature
Simulation-specific limitations
- Simulation projects are partially supported. Not every simulation behavior will have a one-to-one equivalent.
- Full-motion recording (FMR) content may not import as expected.
- Some simulation formatting may require manual adjustment after import.
- Typing text objects are imported only if they exist in the original recording; they cannot be added manually after importing.
General beta limitations
- Complex animations may not map accurately.
- Objects set to display for the rest of the project import as separate objects per slide.
- Multi-state objects are view-only and cannot be edited.
Best practices
Before import (simulation-specific)
Practice |
Why |
|---|---|
Open and save in latest Captivate Classic version |
Reduces import errors and improves conversion. |
Back up the original CPTX |
No round-trip to Classic after import. |
Verify external assets |
Prevents missing media in the simulation. |
After import (simulation-specific)
Practice |
Why |
|---|---|
Review Import Logger after every import |
Catch FMR, formatting, and component issues early. |
Do not ignore warnings |
Simulation behavior may differ even if the slide looks okay. |
Adjust simulation formatting manually |
Sizes, positions, and timing may need tweaks. |
Re-record or replace FMR if needed |
When FMR does not import as expected. |
Archive resolved issues |
Keeps the log focused on what's left to fix. |
Resolve critical issues before publishing |
Ensures reliable simulation behavior. |
Typing text and components
Practice |
Why |
|---|---|
Ensure typing text exists in original recording |
Typing text objects cannot be added manually after import. |
Verify click boxes and input fields |
Check actions and validation after import. |
Test highlight boxes |
Timing and appearance may need adjustment. |
Frequently asked questions
Yes. Simulation projects are partially supported. You must open and save the simulation in the latest Captivate Classic before importing. Then use Import > Captivate Classic and select your CPTX.
Highlight boxes, click boxes, input fields, and typing text objects. Typing text objects only if they existed in the original recording. You cannot add typing text objects after import; you can add highlight boxes, click boxes, and input fields after importing.
FMR content may not import as expected. Use the Import Logger to identify issues. Re-record in Captivate 13.1 or replace with supported media (for example, video) if needed.
No. Typing text objects are created only when you type text during the recording in Classic—that is the only time they can be created. They are imported only if they exist in the original recording. Once the project is created, you cannot add a typing text object; they cannot be added manually after import.
Some simulation formatting may require manual adjustment. Use the Import Logger to locate affected slides, then resize, reposition, or adjust timing as needed.
Troubleshooting
Issue |
What to do |
|---|---|
FMR slide is blank |
FMR (full-motion recording) content is not supported; FMR slides may appear blank. Review Import Logger; re-record in Captivate 13.1 or use alternative media (for example, video). |
Click boxes or input fields broken |
Verify in Import Logger; reattach actions or validation. Manually adjust formatting if needed. |
Typing text missing |
Typing text is imported only if it existed in the original recording. It cannot be added manually after import. Re-import from a Classic project that includes the typing text, or recreate with native Captivate text or effects. |
Simulation formatting off |
Some simulation formatting requires manual adjustment after import. Use slide references in the Import Logger and fix sizes, positions, and timing. |
Issue |
What to do |
|---|---|
Missing media |
Verify external assets are available and relink if necessary. |
Advanced actions behave differently |
Review triggers, variables, and timing in the new project. |
Animation differences |
Replace unsupported effects with supported alternatives. |
Report issues and provide feedback
When reporting a simulation import issue, include:
- The original CPTX file (if possible)
- A brief description of the import behavior observed
- Screenshots of Import Logger entries, if available
Use community forums or feedback channels (for example, User Voice) to report findings.
Reference tables
Benefit |
Description |
|---|---|
Reuse simulations |
Bring highlight boxes, click boxes, input fields, and typing text from Classic without re-recording. |
Transition to new authoring |
Maintain and publish simulations in the current Captivate environment. |
Identify simulation issues |
Use the Import Logger to view which simulation elements need workarounds or redesign. |
Prerequisite |
Details |
|---|---|
Latest Classic version |
Open and save your simulation in the latest version of Captivate Classic before importing. |
Backup |
Keep a backup copy of the original CPTX file. |
External assets |
Ensure all external assets (images, audio, video) are available. |
Area |
Details |
|---|---|
FMR (full-motion recording) |
FMR content may not import as expected; FMR slides can come as blank because FMR video is not supported in the import. Review in Import Logger and re-record or replace with supported media if needed. |
Simulation formatting |
Some formatting may require manual adjustment after importing (for example, caption background transparency may not be fully compatible). |
Additional objects on simulation slides |
After importing, you can add additional objects on simulation slides in Captivate (for example, text caption, images, video, media), unlike in Captivate Classic, where simulation slides had limited editing. |
Advanced actions |
Imported but must be verified (triggers, variables, timing). |
Animations |
Map to nearest supported effect; complex sequences may lose fidelity. |