Buying Guide
How to Use the AstroEquip Telescope Simulator — Complete Guide
The AstroEquip Telescope Simulator is a live deep-sky atlas that previews exactly how a target will frame in your camera — for your specific telescope, sensor, and mount — plus a sub-exposure calculator that tells you how long to expose and how many subs to stack, an upgrade-comparison overlay, a mosaic planner, and a location-aware HUD that knows whether your target is even up tonight. This guide is the complete desktop reference: every toolbar button, every panel, the calculator, five pre-session workflows, and five gear-upgrade workflows. On a phone? See the mobile guide instead — the UI is laid out very differently.
In this guide
- The desktop layout — toolbar, sky, sidebar
- The sky viewport & surveys
- Searching for a target
- Setting up your gear — autofill, manual, custom
- Imaging trains & the node designer (Combine vs Compare)
- The live-stats strip
- Settings ⚙ — filter, projection, pixel, Bortle, location & time
- Rotation modes (FOV / POV / FOV+POV)
- Tools ▾ — Compare, Mosaic, Exposure brightness
- The HUD & the ⓘ object popup
- The Stats tab — sampling, trailing, light budget
- The Calc tab — sub-exposure & SNR calculator
- Saving setups, snapshots & share links
- Help ▾ — Tutorial, Feedback, About
- Picks and the Gear Finder button
- Pre-session workflows (5 scenarios)
- Gear-upgrade workflows (5 scenarios)
- Tips, gotchas & keyboard shortcuts
1. The Desktop Layout — Toolbar, Sky, Sidebar
The desktop UI has three persistent regions:
- Two-row toolbar at the top. The first row holds the AstroEquip brand, Tools ▾, the Settings ⚙ button, Help ▾, Save snapshot (📷), and a setup-info (ℹ) button. The second row holds the object search box, the Catalog filter dropdown, the Survey picker, and the Rotation input + three rotation-mode buttons (FOV / POV / FOV+POV).
- Sky viewport in the middle — the dark area where Aladin Lite renders the live sky. A teal framing rectangle overlay shows exactly what your sensor will capture.
- Right sidebar — three tabs across the top: Setup (gear cards + live stats), Stats (all the readouts), Calc (sub-exposure / SNR calculator).
Above the sky, on the left edge, a small location pill shows your current location and time ("Stockholm · Live"). Click it to jump straight into the Location & Time block in Settings.
2. The Sky Viewport & Surveys
The middle area is a live, deep-zoom view of the real sky, rendered by Aladin Lite from the configured sky survey. The teal rectangle overlaid on the sky is your framing rectangle — exactly what your sensor will capture given the focal length and sensor format you've chosen.
- Drag anywhere on the sky to pan. The framing rectangle stays centred as you move.
- Scroll wheel to zoom. The sky survey re-renders seamlessly down to deep-zoom resolution.
- Right-click anywhere on the sky → opens a What is this? popup that names whatever catalogued object is nearest the cursor and lets you center on it.
- Click a recognised object for a name pop-up.
Switching sky surveys
The Survey button on the toolbar (second row, after the Catalog dropdown) opens a modal where you can switch between background imagery sources. Different surveys reveal different wavelengths and have very different aesthetics:
| Survey | Wavelength | Best for |
|---|---|---|
| DSS2 Color (default) | Visual (optical) | The most familiar look — what most published reference images use. |
| DSS2 Red / Blue | Optical, single band | Higher-contrast B&W for faint structure. |
| 2MASS | Near-infrared (J/H/K) | Cuts through dust — great for embedded clusters and the galactic plane. |
| Mellinger | Visual all-sky | Wide-field colour mosaic from DSLR all-sky photography. Beautiful for context. |
| PanSTARRS | Optical (deeper than DSS2) | Northern sky only, but deeper than DSS2 — finer galaxy structure. |
3. Searching for a Target
Type any object name into the search box on the toolbar's second row. The simulator resolves it against Simbad and re-centres on it.
| What you type | What it does |
|---|---|
M31, M 31, Andromeda
|
Resolves Messier 31. |
NGC 7000, North America Nebula
|
NGC and IC by number or common name. |
Sh2-155, IC 1396, B33
|
Sharpless, IC, Barnard catalogues. |
05 34 31 +22 00 52 |
RA/Dec coordinates (also has a dedicated entry in the Stats tab). |
The Catalog dropdown next to the search filters the autocomplete to one of: All, Messier, NGC, IC, or Barnard. Useful when you're browsing rather than hunting.
4. Setting Up Your Gear — Autofill, Manual, or Custom
The right Setup sidebar is where you describe your imaging train. Three layered ways to fill it: autofill from the AstroEquip catalogue, edit the spec tiles directly, or add a custom entry that the simulator will remember locally on your machine.
Imaging goal — sets the engine's frame of reference
At the very top of the Setup pane, an imaging-goal selector picks what you're trying to photograph: Deep-sky (general), Galaxies, Nebulae & wide-field, Planetary & lunar, Solar, or Visual / casual. The selection drives two things:
- Filter recommendations. Narrowband-bias for nebulae, broadband-bias for galaxies, neither for planetary.
- Build-self warnings. The simulator scores your current gear combination against the selected goal and flags mismatches: oversampled for galaxies, fast f/<4 paired with non-coma-corrected sensor for wide-field, alt-az mount on a long-FL goal that needs autoguiding, etc. The warnings appear in the Stats tab next to the relevant readouts.
Without a goal selected, the simulator still renders the framing but can't warn you about the kit. Setting it once at the top is the cheapest input the engine takes.
Autofill — fastest
The Setup sidebar has three gear cards: Telescope, Imaging Camera, and Mount. Each starts with a text input. Type the model name you actually own — e.g. "Esprit 100", "ASI2600", "AM5", "RedCat 51" — and the autocomplete dropdown shows matching products from the AstroEquip catalogue. Pick one and the simulator fills in:
- Telescope: focal length, aperture, focal ratio, design (refractor, RASA, SCT, Newt), weight.
- Camera: sensor format, pixel size, sensor dimensions, camera type (OSC / mono / DSLR).
- Mount: mount type (EQ GoTo / tracker / Alt-Az), payload capacity, weight.
The framing rectangle, the Stats tab, and the Calc tab all update instantly. Click SWAP to change the selected product, or × to clear the slot and return to the autofill input.
The editable spec tiles — manual fine-tuning
At the top of the Setup sidebar, a grid of spec tiles always shows the active values: Focal, Aperture, f/ratio, Design, Sensor, Mount. The Focal and Sensor tiles are editable inputs: click and type to override directly. Useful for:
- Simulating a focal reducer or extender ("Esprit 100 at 385mm with the 0.7×").
- Trying an unusual sensor crop without a full custom-gear entry.
- Comparing two close models that differ only in pixel pitch — change Pixel from Settings ⚙ instead.
Editing a tile doesn't break the autofill — it just dissociates the slot from the catalogue model. The card name clears so you remember you've changed it.
Add custom gear — for what's not yet catalogued
If a product you own isn't in the AstroEquip catalogue, click the small + Add custom gear link that appears below the autofill input. A modal opens with the relevant fields:
| Custom gear type | Fields |
|---|---|
| Telescope | Name, focal length (mm), aperture (mm), optical design (Refractor APO/ED/Achromat, Newt, SCT, Mak, RC, RASA, Hyperstar), weight (optional). |
| Camera | Name, sensor width × height (mm), pixel size (µm), camera type (Color OSC, Mono, DSLR, Mirrorless). |
| Mount | Name, mount type (EQ GoTo / Star Tracker / Alt-Az), payload (kg), weight (optional). |
Custom entries are stored in your browser's local storage on this device only — they're not synced to your account or shared with other users. They appear in the autofill dropdown next time you type.
5. Imaging Trains & the Node Designer
Everything above describes a single imaging train: one telescope, one camera, one framing. The simulator can also model several trains at once, so you can plan a dual-rig night the way you'd actually shoot it. A short refractor for the wide view and a long scope for the small galaxy, side by side on the same mount. Or two cameras on two scopes chasing two targets in parallel. Each train is a full rig with its own telescope, camera, accessories, focal length, and sensor.
The Imaging trains panel
An Imaging trains section sits at the top of the Setup sidebar. It holds a + New train button (each new train starts as a blank rig you fill from the gear cards, exactly like the first), the list of your rigs, and an Import from Rig Planner button at the bottom. The list opens with an All trains (combined) row, then one row per train. In the list you can:
- Click a row to select that train — or the combined view. The row you're editing is flagged editing; the rig the sky follows carries a sky ★ badge.
- Double-click a row to rename the train in place; right-click it for Rename, Save as setup, or Remove.
- Use the ⧉ on a row to open that train in the node canvas, or the × to delete it (shown once you have two or more trains).
The node canvas
For a visual builder, switch to the Node view — the Sim / Node tabs sit at the top-right of the app bar (you can also use Tools ▾ → ⧉ Open node designer). The canvas draws each train as a chain of nodes over the sky: telescope → camera, with any accessories spliced in between, and a guide scope or guide camera hanging off as a side branch. From here you can:
- Select a train by clicking any node on it. The Setup sidebar, the Stats tab, the Calc tab, and that train's framing rectangle all switch to it. Change the focal length from 700mm to 500mm and you're editing that train, not the others.
- Reorder or splice the chain. Drag one node onto another to reorder the optical train, or click the connector between two nodes to splice a new part — a spacer, filter, or reducer — in at that seam.
- Park an accessory. Detach an accessory and it drops off the chain into a holding area; drag it back onto a train to re-insert it. Useful for A/B-ing a reducer or filter without deleting it.
- Share a mount across two scopes. Right-click a mount node to share it between trains — the canvas then totals the combined gear weight against that mount's payload capacity, so you can tell whether one mount can actually carry both rigs.
- Rename, save, or remove. Double-click a node to rename its train; right-click a node for Save as setup or Remove.
By default the sky re-centres and rotates to the framing of whichever train you select. To keep the sky fixed and move only the toolbar and that train's FOV outline, flip Settings ⚙ → Selecting a train to "Sky stays put."
Combine vs Compare — the all-trains view
Click the empty sky background — or the All trains (combined) row in the sidebar — to deselect every train and open the all-trains view. This is where two rigs stop being two separate framings and get answered as one question about the pair. A segmented Combine | Compare control — in the node toolbar and at the top of the Stats tab, with an ⓘ that explains it — switches how that question reads:
| Mode | What it shows |
|---|---|
| Combine | Treats the trains as one system pointed at the same target: combined integration time, the √SNR gain from stacking both, total light-gathering area versus your largest scope, and how many cameras collect in parallel. |
| Compare | Lays the trains side by side with no merging: each train's focal length, f-ratio, field of view, and sampling, so you can see how they differ at a glance. |
Use Combine when both trains shoot the same object all night and you want the payoff of running them together. Use Compare when you're deciding which rig suits a target, or planning to send each train to a different object. The small ⓘ button beside the control opens the same explanation inside the simulator, with a link back to this guide.
The trains on the Calc tab
With two or more trains built, the Calc tab grows a Your trains panel. It lists each train's sampling, f-ratio, and the time it needs to reach the same target SNR, then states the combined payoff two ways:
- One target, all trains. Roughly how long the pair needs together to reach the target SNR, and how much faster that is than your quickest single train.
- Targets in parallel. If you split them instead, each train reaches the target in its own time from the list above, in one night.
The single-train fields at the top of Calc always follow whichever train is selected, so switch trains to read each one on its own before you check the combined number.
6. The Live-Stats Strip
Just below the spec tiles in the Setup sidebar, a thin live-stats strip always shows the three numbers that matter most as you change gear or pan the sky:
| Stat | What it tells you |
|---|---|
| FOV | Field of view — width × height in degrees or arcminutes. |
| Sampling | Image sampling in arcsec/pixel, with a colour chip (Over / Excellent / Good / Coarse / Very coarse). |
| Max sub | Longest sub-exposure your mount can take before stars streak. |
You don't have to switch to the Stats tab for the headline numbers. The strip surfaces what you actually need while framing.
7. Settings ⚙ — Filter, Projection, Pixel, Bortle, Location & Time
The gear icon on the top toolbar opens the View settings modal. This is where most of the display-side configuration lives, grouped into two blocks: imaging parameters and location & time.
Imaging parameters
| Setting | What it does |
|---|---|
| Filter | Filter preview mode — see the next section. |
| Proj | Projection. TAN is the default and matches what most refractors / Newtonians produce. Switch only for fisheye lenses or hyperbolic correctors (RASA / Hyperstar). |
| Pixel | Pixel pitch in micrometres. Drives the image-sampling readout in the live-stats strip and the Calc tab. |
| Bortle | Local sky brightness, 2 (rural-dark) → 8 (heavy LP). Drives the light-budget estimate and the sky-noise contribution in the Calc tab. Look up your value at lightpollutionmap.info. |
Filter preview modes
The filter selector changes how the sky is rendered. These are approximations based on the bandwidths of common filters and the spectra of catalogued objects — useful for planning ("would dual-narrowband help me here?") but they aren't photometrically accurate.
| Mode | Simulates | Best for |
|---|---|---|
| Broadband (default) | Natural DSS2 colour | Most flexible for framing decisions. |
| Hα | Hα narrowband (~6nm) | Mono cameras building SHO / HOO palettes. |
| OIII | OIII narrowband (~6nm) | Planetary nebulae, supernova remnants. |
| SHO (Hubble palette) | SII / Hα / OIII → R / G / B | Classic Hubble look. |
| HOO | Hα → R, OIII → G+B | OSC-friendly bicolour. |
| 2MASS | Near-infrared | Dust-penetrated views (works on infrared catalogue data). |
| PS1 (PanSTARRS) | Deep optical (north only) | Galaxy detail under good seeing. |
When you pick Hα, OIII, SHO, or HOO, a band-intensity bar slides in just under the toolbar with sliders for each band — drag them to see how the image responds to different channel weightings. The closest you can get to previewing a processed image before collecting a frame.
The Filter gear-card ON / OFF toggle
Once a filter is selected from Settings ⚙, a dedicated Filter gear card appears in the Setup sidebar showing the chosen filter. The card's section label carries a small ON / OFF button (top-right of the card header). The toggle flips the filter render on the sky without un-selecting the filter product itself — so you can A/B the visual difference between "filter applied" and "naked broadband" in one click, without losing your filter choice.
Useful for: deciding whether the filter actually helps a particular target (some galaxies look better without the narrowband cut), or for showing someone "this is what your Hα filter is doing for the framing." When OFF, the Calc tab still treats the filter as installed for the sky-noise math; the toggle is purely visual.
Location & Time
The second half of the Settings modal lets you tell the simulator where (and when) you image from. This is what makes the HUD warnings, the ⓘ object info, and the field-rotation row in Stats actually useful.
- Where — pick a preset city, type latitude / longitude directly, or click Use my location to read it from your browser (one-time prompt, never leaves your device).
-
When — three modes:
- Live — uses real-world time. The HUD warnings reflect what's currently happening in the sky.
- Tonight — jumps to the next astronomical-dark midpoint at your location.
- Pick… — choose a specific date and time. Useful for planning further out (or looking up where the Moon will be in three weeks).
- Horizon — degrees of obstruction from trees, buildings, etc. Lifts the visibility cutoff so "best months to image" reflects what you can actually see from your spot.
- Enabled — toggle off if you'd rather work without any location-aware behaviour. Everything silently degrades to "no location data" with no warnings or visibility numbers.
What changes once Location is on
- The compass overlay labels the altitude of the celestial pole (Polaris / Sigma Octantis) so you see how tilted your mount needs to be.
- The ⓘ object popup in the HUD adds current altitude, tonight's transit time, rise / set times, and the best months of the year to image the target from your location.
- The Stats tab adds a Field rotation row when you're on an Alt-Az mount, with a suggested unguided-sub limit.
- HUD warnings flag when the Sun is up, the sky isn't astronomically dark, or the Moon is bright and close to your target.
8. Rotation Modes — FOV / POV / FOV+POV
The three rotation-mode buttons next to the rotation input answer different planning questions.
| Mode | What rotates | Use it when… |
|---|---|---|
| FOV | Just the framing rectangle, on top of a fixed sky. | You want to see how the target fits with the camera rotated. The sky stays the same; the rectangle pivots. |
| POV | The sky and the framing rectangle, together — frame stays anchored to the same stars. | You want to preview what the field looks like from your camera's perspective with the sensor twisted to a chosen angle. |
| FOV+POV | Just the sky; the framing rectangle stays pixel-locked on screen. | You want to simulate slewing across the sky with the camera locked. The frame's on-screen orientation never changes; the stars rotate behind it. |
The reset button (curved arrow) next to the rotation input returns to 0° = celestial north up, the convention every published reference image uses.
9. Tools ▾ — Compare, Mosaic, Exposure Brightness
The Tools dropdown on the first toolbar row holds three planning tools that don't fit on the main toolbar.
Compare overlay — gear upgrades visualised
Click Set current while looking at your existing gear's framing. The simulator captures a dimmed overlay of that framing rectangle. Now swap to a different scope or sensor and you'll see both rectangles on the same target — old in dim teal, new in bright teal. The label next to the button shows what was captured ("520mm · APS-C"). Clear removes the overlay.
Concrete use: "How much more sky do I get if I move from 700mm to 380mm on the same camera?" Compare answers that in one glance.
Mosaic planner — multi-panel framing
Pick the number of rows and columns (up to 4×4) and a percentage of panel overlap. The simulator draws a grid of FOV rectangles around your centre framing — the centre tile is bright, the surrounding tiles are dimmer. You see at a glance how many panels you need and where the seams fall.
Use it to plan mosaic projects (Veil Complex, Orion to the Running Man, North America + Pelican, the whole Heart + Soul region) before you commit nights to capturing each panel.
Exposure brightness
A slider that brightens or dims the rendered sky image. Useful when surveys come out too dark or too bright at high zoom. Purely cosmetic — doesn't affect any of the calculated numbers.
10. The HUD & the ⓘ Object Popup
Two HUDs float over the sky viewport:
Target HUD (top-left)
Shows the current target name and the field of view in degrees (width × height). Buttons next to the name:
- ◎ Field — toggles between Field mode (auto-picks the most notable DSO inside your current view as you pan) and Locked mode (stays on whatever you last searched for). Field mode is invaluable while exploring — you can pan over an area and instantly see what notable objects you're passing.
- ⓘ — opens the object info popup for the current target.
The ⓘ object info popup
Pulls live data from Simbad and overlays it with your location-aware visibility. Includes:
- Object name, primary identifier(s), and object type.
- Right Ascension and Declination.
- Apparent magnitude (when catalogued).
- Apparent size (when catalogued).
- Tonight's altitude curve — when the target rises, transits, and sets at your location.
- Best months to image — months when the target transits during astronomical dark at your latitude.
- A link to Google for image references and more context.
Nearby HUD (bottom-left, when applicable)
When you're framed near a notable deep-sky object that isn't your primary target, the nearby HUD names it. Useful for spotting opportunistic neighbours — "M81 is right next to my M82 frame, I could mosaic them" — which is the kind of insight a real plan benefits from.
HUD warnings
When location is enabled and the target you're looking at has visibility issues, a warning chip pops in:
- "Below horizon" — the target is currently below the local horizon (or under your custom horizon cutoff for trees / buildings).
- "Sun up" / "Twilight" — sky isn't astronomically dark right now.
- "Moon close, bright" — bright Moon within a problematic angular distance.
11. The Stats Tab — Sampling, Trailing, Light Budget
The right sidebar has three sub-tabs: Setup, Stats, and Calc. The Stats tab is the planning numbers panel.
Image sampling (arcsec/pixel)
Your focal length and pixel size combined into one number. Tells you how much sky each pixel sees and whether that resolution matches typical atmospheric seeing.
| Sampling | Verdict | Meaning |
|---|---|---|
| < 1.0"/px | Over-sampled | Too fine for typical seeing — consider a reducer. |
| 1.0–1.5"/px | Excellent | Ideal for high-res deep sky in good seeing. |
| 1.5–2.5"/px | Good | Well-matched to typical atmospheric seeing. |
| 2.5–4"/px | Coarse | Fine for large nebulae and wide-field targets. |
| > 4"/px | Very coarse | Better suited to very wide-field targets only. |
Star trailing limit
Maximum sub-exposure length (in seconds) before stars start to streak at your current focal length and mount combination. EQ GoTo with guiding is effectively unlimited; a star tracker at 600mm is around 60s; alt-az at 1000mm is essentially unusable for deep sky. A planning estimate — your specific tracking, polar alignment, and seeing will push the real number around.
Field rotation (Alt-Az only, with Location on)
When you've selected an Alt-Az mount and Location is enabled in Settings, Stats adds a Field-rotation row. It shows the current rotation rate (arcsec/min) for your target's altitude / azimuth at your location, plus a suggested maximum unguided sub before rotation visibly smears stars at the frame corners.
Light budget
Suggested total integration time given your target, your Bortle value, and your filter choice. A galaxy under Bortle 6 with no filter needs roughly 3–5 hours; the same galaxy under Bortle 3 needs 1–2 hours. Narrowband targets need 3–5 hours per channel even under good skies because the filters discard most of the incoming light.
Go to coordinates
An RA/Dec entry pair at the bottom of the Stats tab. Useful when you've found a target in a planetarium app or paper plan and want to centre the simulator on its precise coordinates without name-resolving.
12. The Calc Tab — Sub-Exposure & SNR Calculator
The Calc sub-tab is a full sub-exposure and SNR calculator that pulls live values from your current simulator setup. It answers the most common planning question: how long should each sub be, and how many subs do I need?
The four camera preset buttons
One-tap presets that set sensible read-noise + dark-current values for your camera class:
Modern cooled CMOS
ASI2600MC/MM, ASI533MC/MM, ASI6200, QHY268. RN ≈ 2e⁻, dark ≈ 0.001e⁻/s at −10°C.
Older cooled CCDs
QSI, SBIG, Atik, older Moravian. RN ≈ 3.5e⁻, dark ≈ 0.002e⁻/s.
Uncooled CMOS, mirrorless
Sony α7, Canon EOS R, ASIair OSC bodies without cooling. RN ≈ 5e⁻, dark ≈ 0.01e⁻/s.
Older / modified DSLRs
Canon EOS Ra, modded 600D, etc. RN ≈ 8e⁻, dark ≈ 0.05e⁻/s.
What you set yourself
| Input | What it is | Typical values |
|---|---|---|
| Read noise (e⁻) | Electronic noise added every time a sub is read off the sensor. Lower is better. | ASI2600/ASI533: 1.5–3e⁻ · Modern DSLR: 4–8e⁻ · Older DSLR: 8–12e⁻. |
| Dark current (e⁻/s) | Thermal electrons accumulating per pixel per second. Lower with cooling. | Cooled CMOS at −10°C: ~0.001e⁻/s · Uncooled DSLR: ~0.05e⁻/s. |
| Sub length (s) | Your target individual exposure time. | 30–300s typical for deep sky. |
| Number of subs | How many you plan to stack. | 30–200 depending on session length. |
| Narrowband toggle | "Hα / OIII / SII (÷20 sky)" checkbox. When on, divides the sky-background contribution by ~20×. | On for narrowband, off for broadband. |
| Target class | Faint nebula / dim galaxy → Very bright. Sets the assumed target signal strength. | Pick the category that matches your subject. |
| Desired stack SNR | The signal-to-noise ratio you want in the final stack. | 20 = visible · 50 = clean · 100 = magazine quality. |
What's pulled from your simulator setup
- Bortle scale — from Settings ⚙.
- Pixel scale — from your focal length × pixel size (the live-stats Sampling number).
- Sky background brightness — derived from Bortle + pixel scale.
What the calculator gives back
Total integration to hit your SNR
How many minutes (or hours) of integration you need to reach your desired stack SNR, given target class, sky brightness, and your sub plan.
Sky-noise-limited target length
The sub length at which sky noise dominates read noise by roughly 10×. Shorter than this and your stack is read-noise-limited (longer subs would help more than more subs). Longer is fine for tracking convenience but gives diminishing returns and risks saturated stars.
What your plan actually delivers
Total session time = sub length × number of subs. Stack read noise = R / √n. SNR gain shown vs. a single sub — going from 25 to 100 subs only doubles SNR.
The Required Integration ↔ Predicted SNR pair
Two of the result cards run in opposite directions and are designed to be read together:
- Required integration answers "given my chosen target SNR, how much total time do I need?" — i.e. you fix the quality bar, the calculator returns the minutes / hours.
- Predicted SNR answers the inverse: "given my planned sub length × number of subs, what stack SNR will I actually reach?" — i.e. you fix the session length, the calculator returns the quality bar.
Use Required integration when you're planning a multi-night project ("I want clean galaxy detail, how many nights?"). Use Predicted SNR when the session length is fixed by clouds or work the next morning ("I have three hours tonight, what's the realistic stack quality?"). A Read-noise-limited hint surfaces below either readout when your subs are short enough that more subs won't help much — longer subs would.
Noise breakdown bar
The horizontal bar at the bottom shows, per sub, what fraction of total noise comes from each source: read noise, dark current, sky-background shot noise, and target shot noise. Use it to diagnose:
- Read-noise-dominated bar? Your subs are too short for your sky brightness. Lengthen them until sky noise overtakes read noise.
- Sky-dominated bar? Welcome to the optimal-sub regime. More subs help; longer subs help less. This is what you want.
- Dark-current significant? Either you're shooting at warm sensor temperatures or your subs are much longer than they need to be.
13. Saving Setups, Snapshots & Share Links
Save a snapshot (📷)
The Save camera button on the top-right of the toolbar opens the Snapshot modal:
- Resolution — 1× (screen), 2× (retina), or 3× (print-ready).
- Format — PNG or JPG.
- Watermark — toggle the AstroEquip watermark on or off.
- Overlays — include the compass + FOV labels or get a clean sky-only image.
The output is a PNG / JPG of the current framing — sky, framing rectangle, any filter rendering — saved to your downloads.
Share a link
Help ▾ → Share. Copies a URL that re-creates the current view. The URL encodes target, focal length, sensor, pixel size, mount, Bortle, rotation, filter mode, and the visible band-intensity sliders. Anyone who opens it sees exactly what you see. Useful for forum questions or coordinating with an imaging partner.
Save the full setup
Below the Setup tab, the 💾 Save current setup button stores the entire gear configuration — plus the current target, rotation, filter mode, and narrowband channel mix — to your AstroEquip account (signed in) or to local storage (signed out). Saved setups sync across devices once you sign in, so you can plan on desktop and pull up the setup on your phone at the imaging site.
14. Help ▾ — Tutorial, Feedback, About
The Help dropdown on the toolbar holds the meta actions:
- Tutorial — replays the in-app guided tour. Always available.
- Send feedback — opens the feedback page. Use it to report bugs, request gear catalogue additions, or suggest features.
- Share — the same share-link button covered above.
- About — small popup with the current simulator version.
15. Picks and the Gear Finder button
The simulator and the AstroEquip gear finder share one data model, so two integration points live inside the simulator UI on the desktop.
- Gear Finder button in the toolbar's first row, at the far left next to the AstroEquip brand. One click opens the gear finder wizard in a new tab. Use it when the simulator surfaces a compatibility issue you want to redesign around — for example, the framing is too tight at your focal length and you want to see which wider scopes the wizard would suggest for the camera you already have. The text label collapses to an icon below ~1180 px; the destination is always the same.
-
Picks flyout in the right sidebar shows your My Picks list — the comparator at
/pages/picks— inside the simulator. Tap a pick to swap that telescope, camera, or filter into the current setup without leaving the page. The flyout follows the resizable right sidebar (drag the divider on its left edge to set a width; the choice is persisted across sessions). A chip count next to the flyout title updates live as you add to Picks elsewhere on the site. - Reset view button in the toolbar recenters on the current target and restores the default zoom — useful after panning around to scout neighbouring objects, or after a rotation experiment that left the framing tilted.
Both integrations stay in sync without any extra setup. A pick added from a wizard result card appears in the flyout the next time you reload the simulator. Signed-in customers get cross-device sync via the Shopify customer metafield (astro.picks); anonymous visitors get same-browser sync via localStorage. The chip count and flyout refresh automatically when the underlying list changes — even from another tab in the same browser, via the storage event.
16. Pre-Session Workflows
Five concrete walkthroughs for using the simulator before a session. Each takes 2–5 minutes and answers a specific planning question.
Workflow 1 — "It's clear tonight, what's worth shooting?"
Open the simulator and autofill your gear.
Type your telescope, camera, and mount into the Setup sidebar. The framing rectangle takes its true shape.
Open Settings ⚙. Set Bortle, enable Location, choose Live time.
The HUD will now warn you about Sun/Moon issues and the ⓘ popup will tell you whether each candidate is even up tonight.
Click ◎ Field on the target HUD to enable Field mode.
The HUD will name whatever notable object is at the centre of view, automatically, as you pan.
Pan across tonight's visible sky.
If you don't know what's up, type a known reference (M31, Cygnus, Orion) and pan from there. Field mode will surface neighbours you didn't think of.
Use ⓘ on candidates to confirm visibility and check Stats → Light budget.
Pick the target whose transit window fits your session length and whose light budget you can actually meet.
Workflow 2 — "I have 3 clear hours. What fits?"
Set up gear, Bortle, and turn Location on.
For each candidate, search by name and check Stats → Light budget.
Targets where light budget ≤ 3h will produce a clean image. Targets at 4–6h will be usable but noisy. Targets at 8h+ aren't worth attempting in one night unless it's a multi-night project.
Check star trailing.
Stats → Star trailing limit tells you the longest sub you can take. Divide your session time by that number + 30s (dither + download) for a rough sub count. Fewer than ~30 subs → noisy stack regardless of light budget.
Open the ⓘ popup on each candidate.
Make sure the target transits during your session window. A target transiting at 4 AM when you plan to image 23:00–02:00 will spend its best hour low and dim.
Cross-check in the Calculator.
Switch to the Calc tab. Set your camera preset, type your sub length and count. The optimal-sub number tells you whether you can shorten subs (if tracking is imperfect) or need longer ones.
Workflow 3 — "Planning M31 in late autumn from a Bortle 6 site"
Search for M31. Autofill your gear. Settings → Bortle 6, Location on.
Settings → Filter → try each option in turn.
Broadband: lots of LP gradient. Hα: bright in Hα regions only — M31 is a galaxy, narrowband is the wrong tool. Confirms what theory says: use a broadband LP filter on M31 from a polluted site.
Frame the galaxy at your sensor size.
APS-C at 600mm: snug fit. Full-frame at 600mm: breathing room. APS-C at 1000mm: overflows. Try FOV rotation 30–45° if you want M31 + M32 + M110 in the same frame.
Check ⓘ for tonight's transit time and best months.
M31 transits late autumn near midnight from northern latitudes — confirm the session window covers transit ±2h.
Save the setup.
Now your phone at the imaging site will have this exact framing, rotation, and filter mode pre-loaded.
Workflow 4 — "Comparing two framings with the Compare overlay"
Set up framing A — say, the Rosette Nebula on APS-C at 530mm.
Tools ▾ → Compare → Set current.
The current framing is captured as a dim overlay. The label next to the button shows "530mm · APS-C".
Change focal length to 380mm (simulate a reducer).
The new framing rectangle appears in bright teal; the old one stays in dim teal. You see the difference in one glance.
Decide between the two and clear the overlay.
If the wider field captures the structure better and your sampling stays in the "good" band, the reducer earns its keep.
Workflow 5 — "Mosaic plan for the Veil Complex"
Search for "Veil Nebula" and centre between the East and West Veil.
Tools ▾ → Mosaic → 2 rows × 2 cols, 10% overlap.
Four FOV rectangles tile around the centre. Check whether the four panels cover the entire complex or you need 2×3 or 3×3.
Set Filter to Hα and check each tile's Light budget.
Narrowband × Veil = bright. Each tile probably needs 3–4h of Hα + similar OIII. Multiply by tile count to estimate the project size.
Save the setup as "Veil mosaic (NW tile)".
Centre on each tile in turn and save each with a name — gives you a per-panel framing to load at the telescope.
17. Gear-Upgrade Workflows
The simulator is the cheapest way to test whether an upgrade is worth it. Five common upgrade questions and how to answer them in 5 minutes:
Upgrade 1 — "Should I go to a faster scope (lower f/ratio)?"
Autofill your current scope. Tools ▾ → Compare → Set current.
SWAP to the faster scope you're considering — e.g. swap an f/7 Esprit 100 for an f/5 Esprit 80, or an f/5 Newt for an f/2.8 RASA 8".
Search a representative target (say IC 1396).
Compare overlay shows old vs. new framing in one view. Check sampling, FOV, and the star-trailing limit in the live-stats strip.
Switch to Calc and run on both setups.
Faster scopes need shorter subs to reach optimal exposure. A RASA 8 might let you stack 30s subs on an unguided EQ — your tracking budget becomes much easier. That's where the value of a fast scope shows up.
Decide.
If the upgrade gives you significantly more usable subs per session at your tracking precision, it's worth it. If sampling becomes coarse (over 4"/px), you've gone too fast — beautiful for wide nebulae, less ideal for galaxies.
Upgrade 2 — "Should I go from APS-C to full-frame?"
Same focal length, just swap the sensor.
Search M31 or NGC 7000 at your focal length, autofill an APS-C camera (e.g. ASI2600MC). Tools ▾ → Compare → Set current.
Swap to a full-frame body (e.g. ASI6200MC).
Same scope, same target, but the frame is roughly 70% bigger in area. Compare overlay shows both.
Check image-circle compatibility.
Full-frame sensors are ~43mm diagonally. Many small refractors won't cover full-frame. The simulator shows the framing but doesn't show vignetting — check your scope's spec sheet.
Re-run the Calculator.
Pixel size matters more than sensor size for SNR — but more sky per sub means wide targets finish faster.
Upgrade 3 — "ASI533 vs ASI2600 — which dilemma am I in?"
Autofill the ASI533MC. Compare → Set current.
1" square sensor, 3.76µm pixels, ~3e⁻ read noise. Smaller field, very low read noise.
SWAP to ASI2600MC. Same focal length.
APS-C, 3.76µm pixels, ~1.5e⁻ read noise. Bigger field, same sampling, even lower read noise.
Compare in the Calculator.
The ASI2600's lower read noise lets you stack shorter subs without becoming read-noise-limited — useful if your tracking caps you below the ASI533's optimal sub length.
Decide on framing.
If your most-shot targets fit cleanly on ASI533 (small nebulae, galaxies), the smaller sensor's centre-only image circle is forgiving on cheap optics. If you want big nebulae (Heart, Veil, North America), the ASI2600 gives breathing room you'd otherwise need a wider scope for.
Upgrade 4 — "Will a 0.7× focal reducer help?"
Autofill your current scope. Compare → Set current.
Click the Focal tile and edit the value to focal × 0.7.
An Esprit 100 at 550mm becomes 385mm with a 0.7× reducer. The framing rectangle grows by ~2× area; the Compare overlay shows the original.
Check sampling in the live-stats strip.
Make sure you're still in the "good" or "excellent" sampling band for your target — galaxies want fine sampling, nebulae are happier coarse.
Re-run the Calculator.
The faster f/ratio (~30% more light) lets you cut sub length by ~50% while collecting the same signal — a significant tracking-budget win.
Upgrade 5 — "From a Star Tracker to an EQ GoTo mount"
Autofill your scope, camera, current mount (Star Tracker).
Stats → Star trailing limit might be 30–60s at your focal length.
SWAP to an EQ GoTo (HEQ5, EQ6-R, AM5, etc.).
Star trailing limit jumps to "unlimited" assuming you add guiding. The Calculator's optimal sub becomes achievable — typically 120–300s.
Look at total session efficiency.
Going from 30s subs to 180s subs is 6× fewer dithers and downloads. That's an extra 15–25% of session time recovered as actual on-target integration. Mount upgrades aren't just deeper exposures — they're not wasting clear sky.
18. Tips, Gotchas & Keyboard Shortcuts
Use Field mode while panning.
Click ◎ Field in the target HUD. As you drag, the HUD names whatever notable object is in view. Fastest way to discover targets you didn't know existed near your planned framing.
Right-click is the fastest way to identify a faint object.
If you spot a smudge you don't recognise, right-click it. The "What is this?" popup names it and offers a centre-on button.
Compare overlay before any gear-upgrade decision.
Side-by-side framing answers most "is it worth it?" questions in 30 seconds. Cheaper than buying and returning.
POV before you take the shot.
POV mode shows you what your screen will look like with the camera in its actual orientation. Catching framing surprises here is much cheaper than catching them after a 4-hour integration.
Calculator first, then plan.
It's tempting to "just shoot all night and stack later." But if you're read-noise-limited, you'll learn this only after processing. The Calculator catches it in 30 seconds before you set up.
Filter previews are guidance, not gospel.
The narrowband renderings are based on bandwidths and target spectra in published catalogues. Real results depend on your filter brand, camera QE curve, and sky transparency. Use them to compare options, not to predict pixel-level output.
Keyboard shortcuts
| Key | Action |
|---|---|
| → | Next tutorial step (when the tour is open) |
| ← | Previous tutorial step |
| Esc | Close the tutorial or any open modal |
| Mouse scroll | Zoom the sky in/out |
| Drag | Pan the sky |
| Right-click on sky | "What is this?" popup — identifies the nearest catalogued object |
Open the simulator and plan a session
The fastest way to learn the simulator is to open it with a target you care about and walk through your gear. The Gear Finder will pre-fill the simulator with whichever rig it recommends for you.
Open the Telescope Simulator →