msmith4000 wrote:It will not take long for the frequenters of these forums to realise that I have little tolerance of poor customer service
Hang on... I wasn't aware that Hagen-Siegen was the IP of German Railroads... just the stock...?
Certainly not the less than satisfactory half-hearted brush-off answer/solution I would have expected from the German's who I generally associate as a nation who prides themselves as an exporter of high quality, luxury, reliable goods
Now I'm *really* confused... My experience with most German manufacturers and their products is that the manufacturers are usually very eager to ensure that the "customer experience" is a positive one, especially in the (usually rare) circumstance where the product has failed and let the customer down for fear of tarnishing the image of "the brand". You're saying that you *expect* poor service from Germans...? And then you contradict that...
Did you really mean that?
I'm left wondering what the whole wall of text was actually about, tbh; GR say that RSC have altered the code which breaks their (GR's) scenario...? If true, then RSC would do well to advise the community at large of such changes with additional information/advice on what this means to those affected. Why would GR then be in any way obliged to offer a "voucher which will entitle you to a 50% discount off any of the Railworks DLC currently available on steam." ??? Fix it, yes, but why would they give money away for something that's not of their doing?
it will be scant thanks for spending a good 1.5 to 2 hours of my time to help them out, running through the scenario three times and sitting and waiting for five services to pass in the other direction to see if the route clears
Should have used the AsyncControlKeys flag to speed up the process...
On a related note, though, whilst this may sound like stating the bleedin' obvious, but as has been commented elsewhere, RSC hardly help themselves by not utilising Steam's ability to provide change-release notes. On the rare occasion where they do state what's been altered (sporadic, at best), it's often in the form of "We changed a widget" which, unless you're au fait
with what widgets do, could potentially be meaningless. Even in cases of widget-awareness, unless detail is provided as to what changes have been made and therefore what the consequences are/are likely to be, this sort of "detail" itself can be less than useful. In other words, their change-control documentation is inconsistent.