It is worthy to note that it is Scott Thornton, not a DCC system manufacturer, collaborating on MRH to build the throttle stand.
You do bring up a good point. The rule of thumb is 10% of readers post on forums meaning the audience is 10x what it appears to be on any given forum. Considering the number of eyeballs one would think any manufacturer would benefit from engagement on the forums. Minus posting time it is free product awareness and free market research. Look how much goodwill Joe Fugate gets for MRH by being active on his own forum. With Bill being generous in setting up this forum dedicated to RP, without cost to Ring, it almost seems like a slap in the face that Tim doesn't at least pop in once in a while with a comment.
I bought RailPro because I didn't want to control my trains with the technology equivalent of a 1970's calculator. I am a satisfied RP customer. That said, I am less than impressed with Ring Engineering as a company. Not unhappy but not impressed. Kudos to Tim for being extremely responsive to email communication however the responses are always light on content. His responses leave me feeling like Tim isn't the one actually doing the work, as if he has only a superficial understanding of the product. His message phrasing doesn't give one the sense you are speaking to someone with a deep thorough understanding of the product's innards. Maybe I am expecting too much or maybe he doesn't want to reveal anything technical. The RP documentation clearly demonstrates the latter. It is so weak.
The inaction on reported software bugs supports my suspicions. I do a little PHP MySQL web app work myself for select clients of the company I work for. When someone reports a bug I fix it. Because I wrote every line of every script I have a complete understanding of where to look and what is likely the issue. Even if the problem is so tangled it will take considerable work to rectify it I at least temporarily fix it with an ugly collection of if else statements.
I can't understand why Tim doesn't do the same unless, as I suspect, he isn't actually writing the code himself and instead is reliant on someone else to get around to it. Perhaps at a cost. Or it could be the revenue is coming in so why bother! Another piece of evidence... consider Ring's first product was a blinking end-of-train device. The second product was a complete DCC replacement control system. That's one hell of a leap in product development. Not the course one expect an evolving product engineer to take. Unless, the leap was purchased instead of developed.
I'll stop rambling as I am starting to sound like a conspiracy theorist.