EmoTracker v2.1 Release Notes

September 13, 2018

Important Note

The first time you open the Broadcast View in 2.1, you will be asked to allow it to access the network by Windows Firewall. This is required for NDI® Support (see below), and it does not communicate with any outside network service.

EmoTracker 2.1 has just been released! As always, your tracker will automatically prompt you to install it the next time you start it, or you can find “Check For Updates” in the gear menu!

Read on for the details on what’s included!

For Users

Save/Load Support

Version 2.1 brings support for saving and loading your progress to EmoTracker. Enjoy your ridiculously long games - just make sure to save… Loading a save file will bring you right back to where you left off!

You can find the open/save/save as commands bound to the usual keyboard shortcuts, or at Gear Menu > Application > File.

Invalidating Saves

Your save files will fail to load if any of the following things occur since saving…

  • You update the pack used in the save
  • You make customizations (overrides) to the pack that affect items or locations
  • You uninstall the pack used in the save

Make sure to finish your run before doing any of these things.

NDI® Support

2.1 adds support for NDI® - an IP video distribution standard gaining ground quickly in the broadcast world. It allows for multi-source video distribution over a conventional IP network, just like the one you have in your home. More importantly for EmoTracker, it allows us to finally capture the Broadcast View in EmoTracker with a transparent background, eliminating the need for color-keying.

EmoTracker will automatically start sending the Broadcast View over NDI® when the source is open in at least one active view. You can tell it’s active when the NDI® logo appears in the extension bar at the bottom of the tracker.

ndi extension screenshot

The latest versions of XSplit and XSplit Broadcaster support NDI® sources out of the box.

Using NDI® with OBS requires the installation of a plugin, which you can find (along with installation instructions) here: https://obsproject.com/forum/resources/obs-ndi-newtek-ndi%E2%84%A2-integration-into-obs-studio.528/

Known Issues

Capturing via NDI® does cost a bit more CPU than normal window capture, as its encoding a video stream in realtime. I have tried to ensure that you will not experience any slow down in the tracker, but you will notice higher CPU usage.

Additionally, the following issues are known.

  • NDI® video encoding does poorly with small red text. I am tring to work with them on this, but if you use pinned locations in your broadcast view, you may notice that red section names are less readable.
  • The perceived frame rate of ChatHUD animations - e.g. !hud rain ... - may be slightly lower on stream than with window capture.

To enable transparent capture via NDI®, you may need to create a broadcast layout override or edit your existing one, depending on which pack you’re using. The required change is as simple as removing the background property from whatever element (usually near the top) is adding it. You can additionally enable "dropshadow": true to activate drop shadows, since you no longer need to worry about the color-keying issues.

For more help with customization, see #customization-support in the Discord.

Package Variant Support & New Official LTTP Pack

Since EmoTracker launched, pack developers - myself included - have offered multiple packs supporting various modes or versions of different games. As our game list grows, and so do the number of variations each game offers, we are taking the first step towards simplifying this in 2.1 with the addition of variants.

Variants mean that we can ship you a SINGLE pack, that supports multiple variations of the game. This saves us time, and helps to make our packs easier to maintain and fix bugs in. For users, it will reduce the amount of data you download, because expensive assets like images that were previously duplicated across packs can now be shared. Packs with variants look like this in the package manager, and will show as additional options inside of the pack itself in Gear Menu > Installed Packages.

pack variant screenshot

As part of the migration to variants, I’m releasing a new version of my official LTTPR pack. The old versions have been removed from the package manager. If you already have them installed, you are free to continue using them, but they will not receive updates.

When moving to the new package, please be advised that you will need to recreate your overrides. If you find yourself needing help with this process, please see #customization-support in the Discord.

Override Export Mark II

As more and more users become interested in tweaking their packs by exporting overrides, and as we move to more advanced pack structures allowed by variants, it became clear that we needed a more flexible solution that helped them pick what they wanted. To that end, the existing file-specific “Export …” commands are gone, and in their place is a new file list that allows to pick and choose what to override. It supports searching by name, just like the pack manager, and additional show you previews for images you may be trying to override.

Give it a try at Gear Menu > Advanced > Export Overrides.

export override screenshot

Initial Window Size Override

Some of you have experienced issues with the default window size being too large for your screen. While I want to work on a more automatic solution to this in the future, you can now set the size manually in your Documents/EmoTracker/application_settings.json file, by adding the following properties.

    "initial_width": 800.0,
    "initial_height": 600.0,

For Developers/Customizers

Minimal developer documentation here this time. Please see the developer Discord for more information.


This is a big one, obviously. See my updated LTTP pack for information on authoring, and the Discord for details on required repository data.

New Style Pack Loading

We’ve added support for a new, more flexible pack loading system that is driven by Lua scripting. This gives you substantially more flexibility in how you load packs, respond to variants, etc.

Full documentation is coming, but please see my updated LTTP pack and the developer discord for more information.