Hi Barry
Your chutzpah is showing. What part? I was from 21th Ave and 60th Street. Ohvey
When I was a kid, I lived in Brighton Beach and then on on Dunne Court at Avenue Y and East 7th Street.
Later, I lived in Sheepshead Bay.
Originally Posted by Barry Broskowitz:
The member engine isn't affected by changes that DCS makes when it builds or breaks down the lashup, only by changes made by the operator.
Barry,
The member engine IS changed by DCS when added to a lashup. Accent sounds, horn and bell are turned off in every engine but the head engine. Certain lights are also turned off in trailing engines when lashups are created.
When the member engines are returned to the active list and run individually,these sounds and lights are NOT turned back on by DCS. They must be manually turned back on by the user.
Dave
Originally Posted by David Minarik:
Originally Posted by Barry Broskowitz:
The member engine isn't affected by changes that DCS makes when it builds or breaks down the lashup, only by changes made by the operator.
Barry,
The member engine IS changed by DCS when added to a lashup. Accent sounds, horn and bell are turned off in every engine but the head engine. Certain lights are also turned off in trailing engines when lashups are created.
When the member engines are returned to the active list and run individually,these sounds and lights are NOT turned back on by DCS. They must be manually turned back on by the user.
Dave
I've found this to be the case. I'm about the only one in the club who consists engines. As standard operating procedure, I do the following and have few problems with the engines (derailments/shorts aside):
- I read my engines on the setup track. This is because we have six TIUs in super TIU mode (two with address 5) on the layout, plus the one on the setup track which is ONLY used tethered (and only powered when in use). Because of multiple trains running (DCS and TMCC/Legacy), all of the commands from other operators and the response latency from communicating with all those TIUs, it's way more efficient.
- When building the consist (done on the layout staging yard), I select and start-up each engine individually, turn off their smoke units, build the consist, then start-up the consist. Works every time.
- When finished, I delete the consist from the remote, then select and feature-reset each of the member engines. Sometimes the engine gets "lost" (super TIU issue, I believe) in which case I'll put it on the setup track and reset it.
I suspect that if I was running in a single-TIU operation the engine behavior would be different.
Now this would be a nice feature is remote, via a sub menu, reads and remembers the loco settings so when you break up consist, you could access a sub menu to restore that loco settings, saving all the menu and finger pushing hassel .
Hey, we can dream, right?
Guys,
I'm running DCS 4.31 beta. In the beta, the sound issues are as I've described them.
However, some lighting issues in lashups remain to be corrected in the beat release.
Brooklyn! that explains a lot.
Explains what?
