GregR posted:MartyE posted:GregR posted:Meanwhile, this same app has a severely crippled implementation of Legacy control. It is not unreasonable or conspiratorial to state that a business motivation exists to diminish the appeal or function of a competitor’s product.
How so? I find the MTH app pretty good for running Legacy. While it's not fully compatible with LCS and some functionality of Legacy yet it does a very good job at offering a uniform control application. I'd be interested to hear why you feel it "crippled" your Legacy implementation.
The app does a great job making an engine move forward and backward. And to be fair, bell and quilling whistle functions also work. However, automatic ramping of diesel RPM’s has been disabled in the software. All you get is the flat sound of idle RPM’s, unless you go to the hassle of switching screens to make a manual adjustment to RPM for each increase in speed. Automatic RPM ramping is a basic feature that has been available since the early 90’s, even on some of the cheapest engines with Trainsounds or Locosounds chips. It’s like MTH has pushed Lionel products 30 years into the past. You might as well have the flat buzz of an E-unit. Others have noted the absence of other Legacy features like squeezing brakes, and the train brake function. Therefore, yes, I do call this a “crippling” of the Legacy system. In fact, the MTH app meets every classical definition as “crippleware”. Why? Because it not only disables Lionel features, but also disables many other functions as part of an effort to “induce” a purchase of “premium” versions for more and more money. I had to dish out money twice before I got software that even nominally functioned.
Hi GregR,
Well, from the horse's mouth (or maybe arse?) I can tell you we definitely do not want to sabotage TMCC or Legacy operation in DCS. Any bugs or anomalies are merely just that. Of course, the focus is on our own products and features first but, we would love to have every TMCC/Legacy engine run under DCS.
We did struggle with deciding which features were most important to Legacy operators. Further, and even with much appreciated assistance from Lionel, some features didn't make the cut. There are some aspects of Legacy operation that are not well documented and have been lost or forgotten by staff long gone. We have the same issue with some low level aspects of DCS. Luckily for us, the same employees and contract engineers who developed things are still on the job for the most part.
With regard to all the discussion about app updates, generally speaking, the DCS should update exactly like any other app on your device. We've not done anything different in that respect. I would shy away from deletion and reinstall except as a last resort. Most users simply get a notification of an update and update through the App Store. In the case of Android users, most seem to leave their apps set to auto update so, it just happens. At least that's how the Android guys around here operate.
Stay tuned for continued enhancements and expansion of the DCS system including TMCC/Legacy operations. The place to start is for Legacy users to chime in and and make sure we're clear as to what your priorities are. If you ask us to vibrate your phone when accelerating, we may pass on that. Let's stick to running the trains how you want to run them please. We know train brake is of strong interest. However, this falls into the category of lots of unknowns, apparently. Of course, we could figure it out if sales support the effort.
