So where are all these bug fixes you promised us then DTG

[37114]

mmmmm...I've just looked at the Engine Driver article referenced:

We are not just looking forward and working on new products. A key part of my role is investigating bugs and glitches which are reported in existing products, and this is something we have already started to focus on in earnest’. The Isle of Wight add-on: one of Adam's current projects undergoing upgrade and bug-fixing work. A number of trouble-shooting projects are underway with Adam and his team at this time, including some which go back to the earliest products ever released. Test Trak, a kind of proving ground route included with original the RailWorks series, is undergoing work to resolve some problems experienced by long-standing users and to make it independent of the route assets originally provided with RailWorks. The Isle of Wight add-on is receiving a makeover, bringing it up to date with sound and weather occlusions (this means you get echoes inside a tunnel, but not rain, for example), tutorial scenarios and updated TS2014-standard platform characters. Some outstanding problems reported with the Isle of Wight scenarios are also being investigated and fixed. ‘The Isle of Wight is our oldest add-on but also still a firm favourite, and we are working hard to bring it up to standard’, said Adam of this very popular add-on route. Other routes new and old are also being reviewed, updated and fixed where required, including Munich-Augsburg, GEML: London - Ipswich and ECML: London – Peterborough. The Class 466 and Class 101 DMU add-ons are also receiving some TLC to fix minor glitches. Class 101 DMU: another add-on currently receiving minor fixes and improvements. ‘It is part of an on-going process to track and resolve outstanding issues with older products. Some core changes which were made to improve the simulation over the last couple of years have impacted on older add-ons. We now have a dedicated team working fulltime to resolve these kinds of issues and to keep watch for any such issues in future.

I may have missed it, but I couldn't see any promise relating to any release of any fix, only that they were looking at a number of issues.

By all means let's knock them for not being quick enough; for not implementing the simplest of fixes, but when discussing/arguing about it let's be accurate in what we're talking about.

If only DTG could be relied upon as well as we can you being pedantic Gary . Yes the word promise doesn't feature but what's the point in saying to your customers that you're going to do something (twice in this instance as there was an article on the same subject again in March) and then not delivering upon it?

[gptech]

So the dedicated team is working full time to resolve the issues but not going to issue any fixes? OK, the word promise doesn't appear but I think the meaning of the article is clear.

To be fair GPTech, the line from RSC stating "we have a dedicated team working full time on this" rather suggests imminent and regular action.

If you think from a logical point of view 6months ago they were probably working on TS2015. The bug fixes and the long list of fixes the german community gave them probably included the requirement of the core codebase/engine to be altered. Instead of introducing these bug fixes to the core piecemeal its better option to work on them over the span of 6months and fold them into the release of TS2015 thus doing a large bugfix sweep and also allowing for any requirements to the core to be changed instead of doing them earlier in the year which would probably have required additional work should something have broke seriously.

There's no argument that we've had to wait, possibly even wait a wee bit too long, and the lack of any further word from RSC does rather aim the gun at their own feet but the fact remains that no date was set for a release.
Has anybody questioned them or are we just working on that one (or two) particular article(s)?

[37114]

So the dedicated team is working full time to resolve the issues but not going to issue any fixes? OK, the word promise doesn't appear but I think the meaning of the article is clear.

To be fair GPTech, the line from RSC stating "we have a dedicated team working full time on this" rather suggests imminent and regular action.

If you think from a logical point of view 6months ago they were probably working on TS2015. The bug fixes and the long list of fixes the german community gave them probably included the requirement of the core codebase/engine to be altered. Instead of introducing these bug fixes to the core piecemeal its better option to work on them over the span of 6months and fold them into the release of TS2015 thus doing a large bugfix sweep and also allowing for any requirements to the core to be changed instead of doing them earlier in the year which would probably have required additional work should something have broke seriously.

There's no argument that we've had to wait, possibly even wait a wee bit too long, and the lack of any further word from RSC does rather aim the gun at their own feet but the fact remains that no date was set for a release.
Has anybody questioned them or are we just working on that one (or two) particular article(s)?

There seems little or no point communicating with them, they just say the same things over and over again. M8 patch is an example. I've lost count of the amount of times I've read it's in testing on their FB page.

[gptech]

There seems little or no point communicating with them, they just say the same things over and over again

There's no argument on that point either; sadly their customer support/query resolution is rather woeful.

[mikesimpson]

I gave up on reporting bugs, there is an easy to fix bug in the World Editor which was introduced in TS2012 (not there previously), I reported it for TS2012/13/14 and nothing was done, so I gave up.

Mike

[secludedsfx]

Also I'm sure to put an update up you'd need to pay steam to do so, so putting a huge block of bug fixes together instead of dribs and drabs of them does make sense.

[Easilyconfused]

OK thats enough guys. Lots of assumptions being made. Some closer to reality than others.

Official route is to contact DTG via their support mechanism since they don't respond here so any discussion just goes in circles getting more and more personal until people step outside the boundaries and then get the moderator sanctions which causes grief all round.