This issue is known and we have some ideas on how to deal with it.
First, let me try to explain what is going on here. Simply stated, the engine and app get out of sync. The playable whistle setting is not perpetual in the engine. So, each time the engine is shut down and restarted, the whistle defaults back to standard. The app is still set to playable and so, sends playable commands. The whistle in the engine doesn't work since the engine is in standard whistle mode and just ignores the playable commands. Clear as mud, right?
Ideally, we would have the playable feature perpetuate in the engine. That ship has sailed. It was done this way since the thumbwheel on the remote is multi-purposed. The remote has to be toggled in and out of playable mode. Thus, the engine is toggled as well.
So, there are a couple of steps we plan to take to clean this behavior up a bit. First, the playable whistle setting will be perpetual in the app. Next, if the app is set to playable whistle, pressing start up will result in setting the engine to playable mode. The result will be as if the engine is constantly in playable mode.
As a further enhancement, we are looking at ways to both activate and indicate playable whistle mode on the main control screen. For example, maybe double tapping the whistle pull would toggle playable/standard whistle. Also, we could change the color of the "wood" so its obvious when the app is set to playable mode.
One of the many great things about technology is that generally, ongoing incremental improvements can be made. Hang around, Wi-Fi DCS is only going to get better. We've begun working on the premium version of the app in earnest only recently. Our developer was busy on other projects. We are designing the preliminary implementation now and let me just say two words. Very. Cool. Stay tuned.
