GPWS in FS2004 (and the “FSUIPC key” confusion)
Hi all — Ian Stephens here.
A couple things to clear up, because this thread has kind of mixed two different issues: getting GPWS callouts vs. moving a GPWS gauge from one panel to another.
1) “Can I just copy the GPWS from another panel?”
Usually, no — not as a simple copy/paste job.
Most GPWS implementations in FS2004 fall into one of these buckets:
- A panel gauge (a .gau or .dll) that must be referenced in panel.cfg and may require accompanying sound/config files.
- A sound module/app (like PMsounds) that runs separately and “listens” to sim data.
- Something integrated into a bigger package (aircraft/panel suite), where copying just one piece breaks dependencies.
So when people “rob” a GPWS from another aircraft panel and it doesn’t work, it’s typically because:
- the gauge depends on other gauges/modules that weren’t copied,
- it expects certain filenames/paths,
- or it’s coded to only work with that developer’s panel.
2) The practical solution in FS2004: use PMsounds (or similar)
Elkin’s suggestion was actually the most realistic path for FS9: PMsounds gives you the GPWS callouts without having to hack the panel.
If you’re using PMsounds and it’s asking for FSUIPC access, here’s the key point:
FSUIPC itself installs and works “free” for most add-on programs.
What you pay/register is the user features (joystick assignments, button programming, etc.). Most external programs that read data through FSUIPC do not require you to purchase/register FSUIPC.
So if you’re being asked for a “key,” it usually means one of these:
- You’re trying to register the user options portion of FSUIPC (not required for most GPWS tools), or
- You’ve got an incorrect/old key (random keys posted around forums rarely apply to your setup), or
- FSUIPC isn’t installed correctly / wrong version for your FS2004 build, so the add-on can’t see it.
3) Basic step-by-step to get PMsounds/FSUIPC-style GPWS working
- Confirm you’re on FS2004 (FS9) and that FSUIPC is actually loaded.
- In FS9, go to the menu bar and see if you have an FSUIPC entry under Modules (wording varies slightly). If there’s no Modules/FSUIPC entry, it’s not installed/loaded.
- Check you have this file in your FS9 folder:
...\Flight Simulator 9\Modules\FSUIPC.dll
- If PMsounds is installed, make sure you followed its readme regarding where it installs (some of these tools want to live in their own folder and run alongside FS9).
- Don’t try to “enter a key” unless the documentation specifically says you must. In most cases, for GPWS callouts, you just need FSUIPC present and running.
4) About the “ticket” question and the bump
To speedbird_481_papa: if you mean a “ticket” as in a key — there really isn’t a universal “ticket” that everyone shares for FSUIPC. Keys are typically tied to a specific registration/purchase, and the “free” part shouldn’t need one for basic external add-on use.
To Solotwo: yeah… digging up a 2004 thread in 2006 just to ask for a key isn’t the best look, but there’s a legit technical confusion behind it (FSUIPC’s free-vs-registered features).
Quick questions so I can give an exact fix:
- Which GPWS tool are you actually trying to run right now (PMsounds, Turtlefx’s TSR, something else)?
- Do you see an FSUIPC entry in FS2004 under the Modules menu?
- What exact message are you getting when it asks for a key (and who is asking — FS9, FSUIPC, or the GPWS program)?
- What operating system are you on (XP was mentioned earlier — still XP, or something else)?