Engineer-Joe posted:When you build a lash-up, the volume at start is very high, if not 100%. When you touch the volume down button, it seems to jump down a significant level.
I'm not sure if this is what is exactly being discussed. It happens every time I build one. It's not a big deal for me. I'm just trying to clarify what I see myself.
I too look forward to seeing the accel/decel rates available to be set on consists.
I'm having different issues with large consists of mixed PS2 and PS3 engines after power cycles. I noticed it with the remote too so I was leaning towards this DCS version. I gave up searching and try to limit it's use. Overall, my app is working very well. Our grandson still prefers the app so it must be good.
The lash up volume behavior you are experiencing is normal. Or, at least by design. When you initialize a lash up, that is build it for the first time, we send a set of default values to have a known starting point. The volume is cranked up to 100% which, can be annoying but, I just drag it back down to where I want it. Thereafter, it should start up at the level previously set.
Large consists can get finicky. If you have 4 or 5 engines lashed together then sometimes, timing gets a little difficult especially if one of the engines isn't a great signalling engine. The TIU has to tell each engine in a lash up everything. So, just a simple speed command is sent to all engines sequentially. If one engine is not receiving signaling well (dirty pick-up roller, dirty track, weak ground, etc.) then the TIU has to try to tell that engine what to do a bunch of times. This delay can cause quirky behavior. It's a little bit nature of the beast. We could probably do some things to overhaul the system but, it gets involved and isn't really backward compatible. Wanna hear folks scream? Tell them something isn't backward compatible.
