Install and configure
Studio is the desktop app you review recordings in. The Unity package is the recorder inside your playtest build. Recording exists only in builds compiled with the MULNO_PLAYTEST define, so your normal builds are unaffected.
1. Install Studio
- Sign in at the Download page to get
Mulno Studio_0.4.2_x64-setup.exefrom the web app, takeSHA256SUMS.txtfrom the same page (it is public), and check the hash before you run it. - Windows shows a SmartScreen warning ("Windows protected your PC"): Mulno doesn't sign its installer yet, and we will at our first paying customer. Select More info, then Run anyway.
- The installer works for your Windows user only (no admin) and registers the
mulno://link scheme, so moment links open straight in Studio. - Some antivirus products flag a new, unsigned recorder-plus-uploader combination on a first run. If yours does, allow
mulno-studio.exeand, later, your game's own build.
2. Add the Unity package
In your game's project use Window › Package Manager › + › Add package from tarball… and pick com.mulno.playtest-0.4.1.tgz. Make a playtest build with Tools › Mulno Playtest › Build Playtest Player (Windows x64), or on Unity 6 with Tools › Mulno Playtest › Create Playtest Build Profile. Project Settings › Mulno Playtest shows whether this Editor has recording compiled in, and lets you create and edit a PlaytestConfig.
3. Recording quality
Every preset is 1080p, H.264 High profile, with quality-mode encoding: picture quality stays steady and the size follows the scene. The sizes below are one real session re-encoded and measured; a busier 3D game runs two to four times larger at the same preset.
| Preset | Frame rate | Roughly per hour | Size ceiling |
|---|---|---|---|
| Small | 30 fps | 270 MB | 6 Mbps |
| Standard (default) | 30 fps | 760 MB | 15 Mbps |
| High | 60 fps | 1.7 GB | 30 Mbps |
| Maximum | 60 fps | 2.1 GB | 40 Mbps |
| Custom | Frame rate and quality by hand. | ||
A busy scene (dense particles, film grain, heavy noise) is held under its preset's ceiling: the recorder quietly lowers the quality level for a while, and every step down or back up is a capture.quality event in the session. Recording quality is verified on NVIDIA GPUs only; AMD and Intel are expected to work but are unverified.
4. Consent, NDA and the indicator
- Consent Mode: Screen (the default). The consent screen asks before anything records.
- Record Mic and Record Webcam are off by default, and a tester turns them on for themselves.
- Show Recording Indicator stays on. The tester always sees REC while anything records.
- Events Only is off by default. Turn it on for a build that should never record picture, sound, mic or webcam, only markers, spans, regions, positions and the automatic events.
- Show Watermark is on by default: the generic PLAYTEST BUILD mark in a corner.
This is not legal advice
You are the controller of your testers' recordings. Read your own privacy notice and consent text against Mulno's privacy notice and have your lawyer confirm what applies to you before a real tester plays.
5. Upgrading
Studio 0.4.0 and later look for updates themselves: once at start, and from the update banner's own button, against updates.mulno.com. A new version is offered only once we promote it, and Studio installs it only if its signature matches the key built into the app. Studio 0.3.0 and earlier can't: run the new installer over the old one by hand, once. By hand or by the banner, the installer replaces Studio's files and leaves your library, index (%LOCALAPPDATA%\Mulno) and bucket keys (Windows Credential Manager) alone. Sessions recorded by an older release open unchanged.
Replace the whole Unity package, then rebuild your playtest player. mulno_capture.dll, MulnoUploader.exe and the C# are one unit and must come from the same release. A stale DLL under a newer package is refused at startup: the game logs an error that the DLL's ABI version doesn't match, and no recording starts. Config assets you made earlier keep working; a field added since takes its default.