Back to DC

[Ed Kapuscinski]

Because like so many enthusiast-developed software "packages", refinement stops the moment functionality is achieved. The UI is infuriating, the learning curve steep and strewn with rocks. The mere issue that objects cannot be edited or modified, but, rather, must be deleted and re-entered tells this professional developer that nobody wants to take on the chore - and it is a chore - of coding true editing capability.

Classic software designed by developers.

[Denver Road Doug]

Here's my two cents...

(1) This is an excellent thread.
(2) I share the "requirements-based" mantra that many have mentioned.  I'm pretty pro-DCC generally, but I do recognize that there are instances it isn't the right call.
(3) I'm not knocking anything anyone is doing, or any decision DC or DCC.   But when asked the question, I'm gonna provide *my* suggestion even if I do recognize other paths are equally legit.
(4) Having said all that...

...buy an NCE and move forward.

If you were *only* doing the passing sidings "all the world's a stage" concept and nothing else, I still might say go DCC but I could maybe acquiesce considering power routing turnouts etc.

But I seem to recall that you do have some semblance of ops involved too.  (potato train??? or something like that comes to mind)   In my mind, if you are doing anything that involves a way-freight/local like that and/or especially any yard ops at all then that would make it not even a question in my mind.