Rusty Traque posted:jonnyspeed posted:Example: I spoke with Andy E. of MTH at the big show in Cleveland a few years back. I asked him why he thought MTH would be successful re-releasing the same products that had been on the market for years? He was quick to say DCS and ProtoSounds. He felt that once S modelers got their hands on MTH electronics that they would gladly buy the same products again. I thought that was a bad idea then. I think it is even worse idea now because DCC sound has caught up to and well surpassed DCS or RailSounds. So now MTH is going to release a run of F's with a control system nobody wants that has sub-standard sound. AND they will likely take away the ability to easily swap electronics like Don designed. So the only options will be to live with it or gut it.
As I said before... S is different than O or HO and I still don't think they fully grasp it. But you can count on them force feeding the market what they want to sell us.
DCS 3.0 is DCC compatible. It's used in MTH's HO line (where DCS was snubbed) and also loaded in current O Gauge production.
Rusty
Fully aware of that. Doesn't change anything I said. They have the same problems as Lionel.
1. They employ a watered down basic DCC implementation. Not full blown DCC
2. They do not use a DCC socket for easy removal/upgrades (MTH remains to be seen)
3. Sounds are not as good as best DCC decoders
4. When DCS 4.0 comes out you probably won't be able to upgrade your 3.0 engines. See #2
5. With MTH's DCS/DCC implementation in my HO models there are some features/settings that can not be changed under DCC control. You HAVE to have a DCS system to make certain changes. Trust me, this one is a pain.
