Troubleshooting · Straight answers

Troubleshooting & FAQ

Most surprises in MuirWave aren't faults — they're the app being honest about what it knows. Here are the questions that come up most, with a plain answer to each.

§01

A control or toggle is greyed out

That control belongs to a paid edition you don't currently have. MuirWave never hides features — it shows them dimmed so you know they exist. Tapping one opens a screen explaining what it unlocks.

If this is greyed out…You need…
Live data chips (SSP · WIND · CURRENTS)MuirWave Live
Regional Forecast packs (live ocean-model data)MuirWave Live
Propagation Report · Impact Assessment · any Markdown / CSV / GeoJSON / Figure (PNG) exportMuirWave Pro
Offline Climatology & Bathymetry packs · watermarked Brief SheetFree — never greyed out
Already purchased but still greyed out? Use Settings → Restore Purchases (see §05). A restore re-checks your Apple ID and re-enables anything you own.
§02

Working offline / no signal at sea

MuirWave is offline-first. Every core prediction — ray paths, transmission loss, the sound field, detection and impact ranges — runs entirely on data bundled in the app, with no connection needed. You can work all day at sea with the network off.

● Works fully offline
  • Placing pins & running predictions anywhere on Earth
  • Global bathymetry, sediments and WOA23 climatology
  • All readouts, plots and impact ranges
  • Any regional packs you downloaded while online
● Needs a connection
  • Fetching live ocean/weather conditions (the LIVE chips)
  • Downloading new regional data packs
MuirWave never silently guesses. When it can't reach live data it falls back to the built-in climatology and labels the readout so you always know whether a number came from a live feed or the climatological baseline.
§03

A live-data chip shows "fallback" or looks dim

The chips at the top (SSP, WIND, CURRENTS) report where the current reading comes from. This is a feature — it keeps every prediction honest and auditable.

Chip stateMeaning
● LIVEA fresh real-time reading is in use (requires MuirWave Live + a connection).
CLIMATOLOGYUsing the built-in WOA23 baseline — either offline, no Live subscription, or the live feed was unreachable.
If a chip is on climatology when you expected live data, check: (1) you have an active MuirWave Live subscription, (2) the live toggle is on, and (3) you have a connection. If all three are true and it's still falling back, the source feed may be briefly unavailable — MuirWave keeps working on climatology meanwhile.
§04

A readout is blank or a plot is empty

Depth Excess shows nothing

This is by design. When Depth Excess is negative (a depth deficit), MuirWave shows no number — it's a well-defined state that doesn't need a figure. Any positive value is shown and colour-coded (see Reference → Depth-Excess bands).

The acoustic results are empty

A prediction needs a complete scenario. If you haven't set the source and the key geometry yet, the solver waits rather than showing a half-finished answer. Fill in the remaining inputs (the app marks which are still needed) and the results appear.

§

Measured entries: unit traps & staleness

The two mistakes that put a wrong number into a measured-noise entry, and what the STALE chip actually means.

Band level ≠ spectrum level
MuirWave wants spectrum level (dB re 1 µPa²/Hz). If your display reads a band level, subtract 10·log₁₀(bandwidth in Hz) first. Worked example: 74 dB read in a 100 Hz analysis band is a 54 dB spectrum level — entering 74 would overstate the noise floor by 20 dB.
Directional displays already gained
A level read off a beam-formed / directional display already contains the array's gain. Entering it while DI stays in the sonar equation double-counts roughly 5 dB. Use an omnidirectional reading, or back the gain out first.

The chip says STALE — is my prediction broken? No. A measured entry older than 24 hours is flagged amber ◆ SSP · MEASURED · STALE but keeps driving the solver — MuirWave never blocks or pops up. When you're ready, tap the chip and choose REVERT TO MODEL (your entry is kept), or just enter a fresh observation. The same token ambers on distance once you're ~30 nm from where you measured.

§05

The paywall says “Prices aren't available right now”

This means MuirWave asked the App Store for MuirWave Live's prices and didn't get a complete answer back — a connection hiccup or a brief App Store outage, not a problem with your account or your device.

  • Check your connection, then tap Try Again on the paywall — it re-asks the App Store and the buy button reappears the moment prices arrive.
  • MuirWave keeps retrying quietly in the background too (on launch, roughly every six hours, and whenever you open Settings or a paywall), so leaving the app open on a connection often clears it without you doing anything.
  • The rest of the app is unaffected — every free capability, and anything you already own, works normally while prices are unavailable.
This is different from a control that's simply greyed out because you don't own MuirWave Live or Pro (§01) — that's an honest "you'd need to buy this" state. "Prices aren't available" specifically means the purchase price itself couldn't be fetched yet.
§06

Restoring a purchase on a new device

Your purchases are tied to your Apple ID, so they move with you. On a new iPad, or if an upgrade looks missing:

  1. Sign in to the same Apple ID you purchased with.
  2. Open MuirWave → Settings → Restore Purchases.
  3. Your MuirWave Pro and/or active MuirWave Live entitlement re-enable within a few seconds.
Subscriptions are managed in iOS Settings → your name → Subscriptions, not inside MuirWave — that's where you change or cancel MuirWave Live.
§07

“Your projects library was reset”

If MuirWave ever shows this message at launch, it found that the file holding your saved projects had been damaged — usually by a device running out of storage mid‑save, or a shutdown during a sync. Rather than refusing to open, MuirWave sets the damaged file aside and starts a clean one.

  • If you use iCloud — your saved projects sync back down on their own. Give it a minute on a connection and check Saved Projects again.
  • If you don’t use iCloud — the damaged file is still on your device, and it may be recoverable. Contact support before you delete or reinstall the app, because reinstalling erases it for good.
A different message — “Projects aren’t being saved” — means MuirWave couldn’t create a projects file at all, so nothing you save will survive quitting. Everything else in the app still works normally. This one is worth emailing us about: it usually points at a full disk or a permissions problem we can talk you through.
§08

Still stuck?

If something here didn't cover it, we'd genuinely like to know — it's how the app and this guide get better.

Email [email protected] with what you were doing and what you expected. Include your device model and app version (Settings → About) and we'll get back to you.