Princess Maker 3 (Gainax) is the raising simulation in which you guide a young girl’s upbringing — lessons, jobs, encounters — toward one of many futures. Its original Windows release was a Japanese Windows 95 program (PM3WIN.EXE) that was never officially published in English, which is why its DxWnd saga is equal parts locale problem and sound problem. The SourceForge forum thread devoted to it runs to well over a hundred posts and is still active: ghotik, DxWnd’s developer, spent years of releases picking the game apart, and eventually wrote sound code specifically for it. This guide follows that thread.
Problem one: Japanese text and the title bar
A Japanese Windows 95 game on a non-Japanese system starts with the classic symptoms: garbled or blank text where Windows guesses the wrong codepage, and a window title that does not render. DxWnd’s answer is its locale emulation — the profile can present the application with the Japanese locale and codepage it expects, whatever your system locale is; locale emulation in DxWnd explains the mechanism in general. For this game specifically, ghotik noted in the v2.06.12 release cycle that a fix to draw window titles under a custom locale and codepage finally got the Princess Maker 3 title bar printing correctly — so a current DxWnd build is not optional here. If you are on an old build, update first (latest version) before touching anything else.
Problem two: turning on the voices freezes the game
The thread’s original report is precise: with the game’s PCM sound and voice acting enabled, Princess Maker 3 halts. The cause, as the investigation pinned it down, is in how the game drives sound output through waveOut callbacks — a pattern modern Windows and DxWnd’s hooking both handle differently than Windows 95 did. Two ways forward are documented:
- The community stopgap. The player who reported the issue found the game stable with sound effects on if the voices specifically are silenced: in the game’s own configuration, enable DirectSound output but set the character voices (“lines”) to not speak. You lose the voice acting and keep a playable game.
- The developer’s real fix. Ghotik built two dedicated sound tweaks for this game — AsyncWaveOutOpen and AsyncWaveOutClose — and reported a session in which clicking sounds, bells, the girls’ voices and MIDI music all played together. That work was developed through the release-candidate builds and folded into the release line during 2026, which is the second reason this guide insists on the current build. He also published a ready-made Princess Maker 3 profile in the thread: import it with File → Import as described in how DxWnd profiles work, and correct the game path to your install.
One caveat from ghotik about that profile: it locks the sound configuration through DxWnd’s virtual registry entries. If you want to experiment with sound settings yourself, turn the virtual registry off in the profile (or edit those entries) first — otherwise the game sees the profile’s frozen values no matter what you change in-game.
How the fix evolved — and why old advice conflicts
If you research this game elsewhere, you will find older forum snippets recommending an option called MW2WaveOutFix. That was an early milestone in the same thread: it reduced how often the sound halted, but did not eliminate it, and the investigation continued past it. The AsyncWaveOut tweaks came later and supersede it. This is worth knowing because Princess Maker 3 advice on the wider web froze at various points in a three-year investigation — a 2023 answer and a 2026 answer describe different DxWnd builds with different capabilities. The thread, read from its most recent posts backwards, is the reliable order. The same applies to MIDI: the game’s music is MIDI-based, and ghotik’s successful test session specifically lists MIDI playback working alongside the voices and effects — earlier reports in the thread had treated music and voices as an either/or.
Setup summary
- Current DxWnd build, run with the profile pointed at PM3WIN.EXE via the standard flow.
- Enable locale emulation for Japanese in the profile so text and the title bar render as intended.
- Start from ghotik’s thread profile (or enable the AsyncWaveOut tweaks in yours), and keep voices off in the game’s configuration until the sound setup proves stable on your machine.
- To quit and relaunch the game repeatedly without restarting DxWnd, enable the global “Allow multiple hooks” option — a quirk the thread found specific to how PM3WIN.EXE exits.
Known issues
Even with the dedicated tweaks, ghotik’s testing noted that clicking rapidly in quick succession could still block the game — the fix targets the freeze-on-voice behaviour, not every sound edge case. The Korean edition of the game was reported by one tester to behave better than the Japanese original in this respect; that is a single report and is included here as such. Set your expectations by the documented bar: the developer’s own success report describes a full playing session with clicks, voices, bells and MIDI all alive at once — that is what “fixed” means in the record. Stability across very long sessions, or across every regional edition, is simply not something the thread has established, and this guide will not pretend otherwise. And none of this changes the language barrier itself: DxWnd makes the Japanese build display correctly, it does not translate it.
Where to get Princess Maker 3 legally
The original Windows 95 release is not sold digitally — legitimately, it is a second-hand market item. Be aware that the game you will find on Steam, Princess Maker 3: Fairy Tales Come True, is CFK’s later remake: a newer build, officially translated, which does not need DxWnd at all. If you simply want to play Princess Maker 3 in English, buy the remake. The DxWnd setup above is for owners of the original Japanese Windows release.
More game-specific setups live on the DxWnd games hub. Sources: the “Princess Maker 3” thread in the DxWnd forum and the v2.06.12 release-candidate notes, on SourceForge.