...
Rick, you should avoid such words about the gorilla if at all possible.
DCC can run DC locomotives on most of the command stations, there's a method to doing it; to say you can't is outright erroneous. So too is this statement that DCC equipped locomotives cannot run on DC; the standard decoder nowadays is indeed a DC/DCC decoder that can switch between sources.
The main problem with RCC right now is indeed the interoperability issue. Until that is fixed, DCC is and will remain the 800 lb gorilla for precisely this fact:
I can run my Brand W locomotives [Athearn, Bachmann, Atlas], equipped with brand X decoders [QSU, Soundtraxx, Digitrax], on my Brand Y Command Station [Digitrax, NCE], using my Brand Z throttles [smart devices if the command station has JMRI support enabled].
This is Huge.
The solution for the RCC manufacturers is simple: their systems Must as a matter of interoperability play well with not only each other but with DCC in mind as a base level operability state. This is not hard; if Ring had come out first with a LM-1 with X number of locomotives assigned to it, where every locomotive variable is a different throttle-selectable DCC address, and then plugged this decoder into the standard command station [via Loconet, for instance], Ring would have made their product suitable for Everybody in the room.
How? Using this device, I could use their throttle to access and run my DCC locomotives. I may not have all of their operability that comes in a Ring decoder [since Ring uses a 2-Way decoder and most DCC decoders are still 1-way devices] but I would still be able to use One throttle to access my entire motorpool.
Going one step further, if this slaved LM-1 has the ability to act as a transmitter, and thus communicate with all of my RCC equipped locomotives, and it was JMRI friendly, then I could use my Smart Phone to access my RCC equipped locomotives as I access my DCC locomotives. Hence, I may not ever buy the Ring power modules or even their throttle, but I would then be buying their "LM-1 Command Station" and happily add their decoders to my inventory. As it is, no dice. And this is without even going into their insistence that we are not smart enough to upload our own pictures into their database infrastructure. Sorry Charlie, but a trillion pictures on the internet speaks otherwise!
Instead, they tried to do what every little new guy has tried to do with their new bread-slicing mechanism. Look no further than MTH and their DCS system to see how that fares over the long haul!! [from what I understand, MTH now makes their decoders more DCC compatible than ever before - this after they insisted they would NOT make their decoders DCC accessible - that turned into "A little accessibility" and now "a lot of accessibility."] You CANNOT "force" or even "compel" the DCC masses to give up that which works 90-95% of the time!
In the end, you do not move the 800lb gorilla by pretending to be the next 800lb gorilla. Rather, you find a way to become part of the 800lb gorilla without the gorilla ever even realizing you've added your virus to it's DNA. If you are incompatible with the gorilla, the gorilla's immune system will wipe you out and then develop antibodies to snuff you out any time you come back. Sound decoders, for instance, have been successful because they work right alongside non-sound decoders. If RCC wants to be serious, then they have to find a way to incorporate the pre-exisiting Gorilla into their architecture.
I personally really like where RCC will take us. My personal issue with DCC is the level of cleanliness necessary for any sort of reliable operation. As a matter of finishing my test loop yesterday, I pulled up as many locomotives as I could and ran them. These things had everything from nice nickel silver plated wheels to the grundgiest brass wheels you ever did see. Without cleaning wheels once, those that could run all ran around the layout without issues.
With DCC, when the decoder can no longer understand the communication, it shuts off, leaving your locomotives stalled wherever it is. RCC lifts the communication up and puts it right to the decoder where it needs to be, properly separating our power from our information. However, whatever steps RCC takes, it MUST work well with the gorilla or it will remain like all of the other fringe technologies that have ever come along. DCC has it's place: it's Very good for operating in static settings where everything is hardwired, be it switches, crossing gates, or semiphores.
Until the wireless providers learn to work together on one protocol, the ocean will remain very wide and very deep.