@MTH RD I have a few suggestions:
1. Can we please move the + and - speed control buttons down the screen by about 1/4" to 3/8"? They are not in the way for DCS, Legacy, or TMCC32 speed dials. However, for default TMCC, R100, and TAS speed control displays, both the + and - buttons overlap and conflict with the dial operation. It seems like every time my finger tries to latch onto that finicky speed dial needle, these buttons are in the way. This would also help solve a nasty issue for DCS and Legacy operation because the + button, at its present location, is just WAY WAY too close (within a hair of touching off a 200 mph speed request). Every couple of days, I get an engine racing off when I accidentally miss the + button by a millimeter. Don't need the heart palpitations.
2. Can we get an option for linear (up-down) speed dials, similar to the variable voltage slider? I can't draw a perfect circle staring at a piece of paper, let alone trace a circle on my phone while looking up at a train. Don't get me wrong, the speed dials are beautiful, but a simple up-down motion of the thumb is more reliable for those of us who would rather look at our trains than a tablet or phone display.
3. Lashups: Can we please get the ability to EDIT lashups that have already been created? Every time I create a lashup, it takes multiple attempts and permutations of forward/backward, head/middle/rear before everything works. Wouldn't it be nice if we could click edit, and get back to that nice screen where we choose the components of the train and set positions and directions. Mistakes could be quickly corrected, instead of having to delete the whole lashup and start the entire process all over again.
4. Lashups Again: Can Lashups be identified with bold text, or a symbol next to their name for easy identification in the engine list?
4. Volume Control: The volume up/down buttons located at the bottom of the screen below the rev up/down and boost/brake buttons do not work for TMCC locomotives, but they do work for Legacy locomotives. Can these buttons please be programmed to increase/decrease volume by sending the commands AUX1-1 and AUX1-4 respectively, when a TMCC locomotive is in operation?
OK, I'll try to reply to your list. Please remind me of your device platform again. Are you iOS or Android?
- It is certainly possible to move the "+/-" speed buttons down or, wherever. The problem becomes, if we move them down, they will be very close to the direction buttons on phones. There seems to be room on tablets but, for phones, things get crowed. For DCS engines, you can set a max speed that avoids the 120 smph tap on the speedo bezel. With regard to "infinite" dials like default TMCC, R100, and TAS, the needle doesn't interfere with the "+/-" buttons. Once you have control over the needle, the buttons are ignored. I can see if you stopped the needle directly on one of the buttons but, in this case, if you just tap an hold the needle slightly above the buttons, it works just fine. I'm not sure how many people use the "+/-" buttons to run their trains but, I certainly agree, it would be nice if there were more room. I suppose, we could look at reducing the relative size of the speedometer but, many/most really like this form of control. I've looked at it again at your suggestion and can see your point. Let me soak on this one and get some more feedback from other users.
- Sure, linear speed control options would be relatively easy. We could use the conventional control sliders for example. There is probably around $5K in software time to offer this option. So, this is where the steel hits the rails. And it sparks. There is a ton of really cool stuff, options, etc., we could do if only our budget was unlimited. I hear you on this preference but, I have to say, it would take a lot more customers requesting it to make the light of day. Sorry.
- The same cost barrier in #2 above applies to editing lash ups. It takes seconds to build a DCS lash up. If I screw it up and have to build it again, it's really not that cumbersome. Again, I hear you though and appreciate your suggestions.
- The volume buttons on the secondary control screen (below the main engine control screen) work OK on our TMCC test engines here in both iOS and Android platforms. There are only like 4 volume steps but, they work the same as using the aux1-1 (vol up) and aux1-4 (vol down) buttons.
Again, please help me out and give me more details about your device, OS, revision level, etc. We only have a cross-section of TMCC and Legacy test engines. We see behavior vary across them depending upon when they were built, etc. In the current app and using current Lionel engines, things seem to work OK. Well, we confirmed the labor bias is broken in Android. While doing so, we found a couple of other little cuties that we'll fix as well. I'm surprised nobody reported them.
Again, I thank you for your patronage and taking the time to make suggestions. It's not that we won't do any of them but, I hope you can understand that we are unable to do everything anyone requests. It just isn't feasible.