Skip to main content

🎓 Lesson 19: Software Simulation, VR / 360 & Interactive Objects (Classic)

To close your Classic tour Classic, we look at three things Classic has long done well: its mature software-simulation workflow, immersive VR/360 projects, and the interactive objects that make screens respond. You already know the ideas — now you'll recognize Classic's versions and know when they justify reaching for the older tool. Then we wrap Part 4.

📚 What You'll Learn

By the end of this lesson, you will be able to:

  • Recognize Classic's software-simulation workflow and its long-standing View / Try / Test heritage
  • Explain what a VR / 360° project is — 360 scenes, hotspots, guided vs. exploratory
  • Name common interactive objects: click boxes, buttons, text-entry boxes, learning interactions
  • Judge when these strengths justify choosing Classic today Win + Mac
  • Look back and see that you can now navigate Classic and know when to reach for it

⏱️ Estimated Time: 30 minutes

🎯 Project: Sketch a small VR/360 lesson or plan a short Classic simulation, and write one sentence on why Classic fits that job.

In This Lesson

Classic's Mature Software Simulation

Back in Lesson 11 you learned Captivate's signature move: record your screen once and generate three learning modes from it — View (watch), Try (do it with hints), and Test (do it, scored). That concept is the same in Classic; what's notable is that Classic has been doing it for years, so its simulation tooling is deep and battle-tested.

🎬 The View / Try / Test idea, recapped

View — the learner watches the task performed, guided by highlights and captions.
Try — the learner performs it with prompts and a safety net.
Test — the learner performs it unaided and is scored.
One recording, three outputs. Classic auto-generates captions, highlight boxes, click boxes, and text-entry boxes from what you did on screen — then lets you edit every one on the timeline.

Because those recorded pieces land as editable objects on Classic's timeline, you get frame-level control over pacing, highlights, and feedback — the same timeline strength from Lesson 16, now doing real work. For long, detailed application training with lots of steps, some teams still prefer Classic's simulation editing. The all-new tool also does simulation (that was your primary path in Part 3); Classic's is simply the older, very mature sibling.

💡 Don't relearn the concept — map it. Everything you know about View/Try/Test transfers directly. If you open a Classic sim, you'll recognize the click boxes and text-entry boxes immediately; they're the same learning ideas wearing Classic's interface.

VR / 360 — Immersive Learning

Here's a capability that's genuinely a Classic hallmark today: VR / 360° projects Classic. Instead of flat slides, you build from 360° images or video — a panorama the learner can look around inside, on a phone, a desktop, or a headset. Onto those scenes you place hotspots: tappable points that reveal information, play audio, pose a question, or jump to another scene.

graph TD A["🌐 360° scene
(a panorama the learner explores)"] --> B["📍 Hotspot: info card"] A --> C["📍 Hotspot: audio note"] A --> D["📍 Hotspot: quick question"] A --> E["📍 Hotspot: go to next scene"] E --> F["🌐 Next 360° scene
(a linked location)"] F --> G["🏁 Guided path or free exploration
through the scenes"] style A fill:#bfdbfe,color:#1e293b style B fill:#f1f5f9,color:#1e293b style C fill:#f1f5f9,color:#1e293b style D fill:#fde68a,color:#1e293b style E fill:#c7d2fe,color:#1e293b style F fill:#bfdbfe,color:#1e293b style G fill:#bbf7d0,color:#1e293b

Figure 1 — A VR/360 project: 360° scenes carry hotspots that reveal content, ask questions, or link to other scenes — as a guided path or free exploration.

A VR project can be guided (the learner follows a set route through scenes) or exploratory (they roam freely and discover hotspots). It's a natural fit for a virtual site tour, a safety walkthrough of a real environment, an equipment familiarization, or a soft-skills scenario where "looking around" is part of the learning. And you can even add knowledge-check questions to a hotspot, so exploration is assessed, not just sightseeing.

🥽 You don't need a headset to benefit

VR/360 courses play fine in an ordinary browser — the learner drags to look around. A headset is a bonus for full immersion, not a requirement. That makes 360 projects surprisingly practical for everyday training, not just cutting-edge showcases.

Interactive Objects You'll Meet

Whether in a simulation, a VR scene, or an ordinary slide, Classic gives learners things to do through interactive objects. You'll recognize most from the whole course; here they are in Classic's vocabulary:

Figure 2 — Captivate Classic (a simplified mock-up, not a real screenshot): a click box marks where the learner must click, a text-entry box captures typed input, and a button submits — each with success/attempts/hint settings.

Interactive object What the learner does Common use
Click box Clicks a specific spot to proceed Software sims — "click the Save icon"
Button Clicks a control that triggers an action Navigation, reveal, submit, branching
Text-entry box Types a response Capturing a name, an answer, a command
Learning interactions Uses a prebuilt widget (accordion, tabs, process, and more) Rich content without building from scratch

Each of these can carry an action (recall Lesson 18) — "on success, go to the next slide; on failure, show a hint; after two attempts, reveal the answer." Interactivity plus a little logic is how a Classic slide becomes a genuine practice activity rather than a page to click past.

When Classic Justifies the Trip (Part 4 Wrap-Up)

You've now toured Classic's whole neighborhood: its timeline model (L16), fluid-box responsiveness (L17), variables and conditional logic (L18), and today its simulations, VR/360, and interactive objects. Time to pull the map together.

✅ Reach for Classic when a project needs…

  • VR / 360° immersive learning — a Classic-only capability today
  • Editing an inherited .cptx (a course, or a big simulation, already built in Classic)
  • Deep conditional logic / variables at a level the all-new tool hasn't matched for your needs yet
  • A team standard or client contract that specifies Classic
  • Frame-precise timeline control over a long, tightly synced simulation or narrated lesson

For everything else — especially new, responsive courses — the all-new Adobe Captivate remains your default. Same rule you've carried since Lesson 3, now backed by real familiarity.

💡 Keep re-checking. All-New Captivate keeps absorbing Classic's strengths release by release. A "Classic-only" item on this list can move to the all-new tool at any time. Before you commit to Classic for a single feature, glance at Adobe's current release notes — the badges here are a 2026 snapshot, not a permanent verdict.

🏁 You can now navigate Classic

That's the whole goal of Part 4, and you've reached it. Drop into a Classic project and you'll recognize the stage, timeline, and Properties; understand fluid boxes; read a conditional action; and spot a click box or a 360 hotspot for what it is. You're no longer a stranger there — you're a confident visitor who knows exactly when the trip is worth taking.

🎯 Try It: Plan a Classic-Worthy Project

🏋️ Activity: Pick the project that actually needs Classic (about 15 minutes)

Objective: Practice the judgment call — choosing Classic on purpose. Planning is the skill; building in Classic is optional.

Steps

  1. Choose one: (a) a small VR/360 lesson — say, a safety walkthrough of a room; or (b) a short software simulation of a 4–5 step task. (⏱️ 2 min)
  2. If VR/360: sketch two 360 scenes and mark three hotspots per scene (info, a question, a link to the other scene). (⏱️ 5 min)
  3. If a simulation: list the steps, and note where a click box or text-entry box would go, plus which View/Try/Test mode you'd ship. (⏱️ 5 min)
  4. Write one sentence: "I'd build this in Classic because ______." Make the reason specific (VR is Classic-only; I inherited the file; the timeline control matters). (⏱️ 3 min)
  5. In Classic (optional): start the matching project type and place a couple of hotspots or record a couple of steps to see it live. (⏱️ 5 min)
💡 Hint

If your "because" sentence would work just as well in the all-new tool, that's a signal the project probably doesn't need Classic — pick a different scenario or a genuinely Classic-only angle (VR/360 is the clearest one). The exercise is as much about ruling Classic out as ruling it in.

✅ Activity Complete When…

  • You've planned either a two-scene VR/360 lesson or a short software simulation
  • You've placed the interactive objects (hotspots, or click/text-entry boxes) in your plan
  • You can name a specific reason the project belongs in Classic

🎯 Quick Quiz

Question 1: What is a VR / 360° project in Captivate Classic built from?

Question 2: Which reason most clearly justifies choosing Classic for a new project today?

📓 Learning Journal

Keep your Learning Journal going — a note in your favorite app, a doc, or a paper notebook. It's where you turn "I read that" into "I can do that." After each lesson, jot down:

  • Key concepts you learned
  • Things that clicked for you
  • Questions or confusion points to revisit
  • Ideas you want to try
  • Your progress and how you feel about learning this

✍️ This lesson's prompt: Part 4 is done — reflect on the whole Classic tour. What surprised you most (the timeline? VR/360? that logic isn't code)? Name one real project you'd route to Classic and one you'd firmly keep in the all-new tool, and say why for each.

📝 Lesson Summary

🎓 Key Takeaways

  • Classic's software simulation is the same View/Try/Test idea from Lesson 11, with deep, mature, timeline-based editing.
  • VR / 360° projects — 360 scenes with hotspots, guided or exploratory — are a Classic strength today and play in an ordinary browser (no headset required).
  • Interactive objects (click boxes, buttons, text-entry boxes, learning interactions) let learners do, and pair with actions for real practice.
  • Choose Classic for VR/360, inherited .cptx files, deep logic, team standards, or frame-precise timing — and re-check what the all-new tool now offers.

🎉 What You've Accomplished

You've finished Part 4. You can open Captivate Classic, recognize its interface and its power features, read its interactivity, and make an honest call about when it's the right tool. That's a real, marketable addition to your all-new skills — and it means no inherited project or Classic-only requirement can catch you flat-footed.

❓ Common Questions at This Stage

Do I need to master Classic simulations if I already learned them in the all-new tool?

No. The concept — View/Try/Test — is identical, and that's what transfers. You only need to recognize Classic's version so you can edit an inherited sim or follow a Classic tutorial. Depth is optional and Adobe's docs cover it if you want it.

Is VR/360 worth learning if I don't have fancy equipment?

It can be. 360 courses run in a normal browser — learners just drag to look around — so a virtual tour or safety walkthrough is very doable without headsets. If your training benefits from "being there," it's a genuinely useful, and currently Classic-specific, option.

After all this, should I ever start something new in Classic?

Rarely, and always for a specific reason: a VR/360 project, a Classic-only feature you need now, an inherited file, or a team standard. For typical new, responsive courses, keep starting in the all-new tool — it's faster and it's where Adobe is heading.

🔭 Looking Ahead

Part 4 is complete — nicely done. In Lesson 20 we open Part 5 with an honest look at AI in Captivate: what it genuinely helps with, where human judgment still rules, and how it's priced (credits and add-ons) — no numbers, just the truth.

✅ Before the Next Lesson

  • Do the "plan a Classic-worthy project" exercise if you haven't
  • Write the Part 4 reflection in your journal — biggest surprise, and one project for each tool
  • Take a moment to appreciate it: you now know both Captivates

📚 Additional Resources

🌟 Encouragement for the Journey

You set out to learn a modern authoring tool and ended up fluent in both of Adobe's Captivates — able to tell them apart, work in either, and choose wisely between them. That range is exactly what makes an author valuable. Part 5 and your capstone are where it all comes together. Onward.