List of RSC DLC bugs

[nobkins]

I think that is probably a good idea. Once the update is out I will go through the reported bugs and make a thread on the FAQ that is easily searchable and give instructions on how people can report bugs etc.

It is VERY important that bugs are reported in the correct way so that the list is accurate. If only a few mistakes are in the list then it will significantly reduce it's trustworthiness.

Just to re-iterate here is the format proposed:
Synopsis:
Class 47 train brake can not be controlled using the mouse

Description:
When in the cab of a class 47 it is impossible to move the train brake lever (and thus use the train brake) with the mouse.

Reproduction:
With any class 47 locomotive simply enter the cab and try to move the train brake lever with the mouse

Workarounds:
Use something other than the mouse to control the brakes (Keyboard, F4 HUD, RailDriver etc)

Reported-By: Nobkins
Report Date: 11 June 2012
Reporter Game Version: TS2012 11.7b
Verified-By: firetrap1
Verified Game Version: 11 June 2012
Verified Date: TS2012 11.7b

Here is a code block to make it easy to copy and paste the format to a new post replacing the relevant text as appropriate:

Code: Select all

[b]Synopsis:[/b]
**Replace with a single sentence**

[b]Description:[/b]
**Replace with a description of the bug**

[b]Reproduction:[/b]
**Replace with a instructions on how to replicate the bug**

[b]Workarounds:[/b]
**Replace with a details of any methods of working around the bug**

[b]Reported-By:[/b] **Replace with your UKTS username**
[b]Report Date:[/b] **Replace with the current date**
[b]Reporter Game Version:[/b] **Replace with the game version (shown at the top of the TS2012 launcher)**
[b]Verified-By:[/b] **Replace with the UKTS username of the verifier**
[b]Verified Game Version:[/b] **Replace with verifier game version**
[b]Verified Date:[/b] **Replace with the date bug was verified**

[gptech]

Cracking idea, would seem a bit silly reporting issues that are fixed by SP1

[FoggyMorning]

The only drawback I can see with this proposal is that putting it in the FAQ section limits who can contribute. A thread in the General Discussion forum would seem a more accessible alternative.

[ProRail]

Class 377 (All White Livery), one carriages doors disappear before the train when moving view away.

Check, it indeed does. Same problem also occurs with the FCC sets which are based on this model.

[gptech]

The only drawback I can see with this proposal is that putting it in the FAQ section limits who can contribute. A thread in the General Discussion forum would seem a more accessible alternative.

I think the answer is to have the verified issues in the FAQ, but reporting of issues/fixes/workarounds to be open.

[nobkins]

The only drawback I can see with this proposal is that putting it in the FAQ section limits who can contribute. A thread in the General Discussion forum would seem a more accessible alternative.

I think the answer is to have the verified issues in the FAQ, but reporting of issues/fixes/workarounds to be open.

That is the plan as it stands

Reports on a normal thread or via PM and then once verified in the FAQ thread the go using the standardised format making it easy to search.

I have some stuff prepared that is just waiting for the service pack to happen before I do anything else.

All ideas gratefully received though if anyone has a a better technique.

[mervyn61]

Here is another bug which stood out to me in The Woodhead Route because of the large amount of complex trackwork, but I then started to notice that it is present in most routes to a greater or lesser extent, both payware and freeware.

Synopsis:
Crossing Vee on turnouts, crossings and slips is not properly formed.

Description:
The crossing vee in many turnouts and other pointwork is corrupted with the gap closed between the swithblade and the vee on one side.

Reproduction:
Seen on a lot of pointwork in most routes.

Workarounds:
None

Reported-By: Mervyn61
Report Date: 14 June 2012
Reporter Game Version: TS2012 11.7b

This is not meant as a criticism of route builders, but I suspect it is a bug in the route editor that stops joints from being welded correctly or consistently to form pointwork.

Mervyn

[transadelaide]

Here is another bug which stood out to me in The Woodhead Route because of the large amount of complex trackwork, but I then started to notice that it is present in most routes to a greater or lesser extent, both payware and freeware.

Synopsis:
Crossing Vee on turnouts, crossings and slips is not properly formed.

Description:
The crossing vee in many turnouts and other pointwork is corrupted with the gap closed between the swithblade and the vee on one side.

Reproduction:
Seen on a lot of pointwork in most routes.

Workarounds:
None

Reported-By: Mervyn61
Report Date: 14 June 2012
Reporter Game Version: TS2012 11.7b

This is not meant as a criticism of route builders, but I suspect it is a bug in the route editor that stops joints from being welded correctly or consistently to form pointwork.

Mervyn

Should be...

Workarounds: Split and re-weld tracks in World Editor, works for most cases other than slips.

On some routes this is done well across the board, on some routes it is not done at all.

[mervyn61]

I would really describe that as a fix rather than a workaround, and it is not a practical solution for those of us with no experience of tracklaying or route building (probably the vast majority of users). Going through a route like Woodhead and fixing all the "faulty" crossings would be a major job anyway, even for someone who knows what they are doing.

While it would be unrealistic to expect any existing routes to be fixed any time soon, it would be nice if RSC could fix the problem so it doesn't occur in any new routes.

Thanks for the comment anyway, at least it shows someone reads it!

Mervyn

[bdy26]

The splitting technique doesn't always work, especially will more complex slip and double slips. It is more likely to show when using a track rule with the correct BR separation of 3.24 m rather than the 3.5m used by Kuju and RSC.

The splitting often causes check rails to either partially render or to form a continuous check rail between cross overs.

In my experience it can be difficult to get correctly rendered complex trackwork within the space confines of the prototype.

B

[Kariban]

Should add "checkrails and frogs are shiny when they should be rusty" . Having been 50% of a team trying to make some new track ( actual track, not laying track ) I think the entire process of constructing s&c from track parts needs a little going over. Hopefully that will be someone's little pet project one day...

[rivimey]

I can confirm what bdy26 says, and it's not the route-layer's fault, as far as I'm concerned. Although sometimes the track does form "properly" the conditions under which it does so are far from clear and on many occasions it is quite hard enough just getting a correctly operating switch to form at all.

I too would like to see properly discoloured check rails - and for that matter, check rails as a track property rather than as completely assets - and for point formation to include some representation of the tiebar and locking gear. However, these all count as enhancements...

What I do consider a point bug is the discolouration to the track base that is applied to track that is part of a point, even if previously it was fine - so, for example, you can join two tracks with different texture (e.g. yard & main line) in a crossover and the texture from the yard "leaks" onto the main line. Not good.

[Kariban]

The way the roadbed blends ( or doesn't ) is the biggest issue I'm wrestling with at the moment - ballast beds have to be all one colour or pointwork looks terrible, and the patch technique to cover the central section up doesn't work very well with 3d track. Anyway that's getting off topic.

[TheTazman]

With a couple of super elevated bends some times the cab really bounces quite hard. For the part they are fine. Just wondered what causes the hard bounce?

[FoggyMorning]

What I do consider a point bug is the discolouration to the track base that is applied to track that is part of a point, even if previously it was fine - so, for example, you can join two tracks with different texture (e.g. yard & main line) in a crossover and the texture from the yard "leaks" onto the main line. Not good.

That sounds like you are trying to form points using two different track types. Points should use the same type of track for each divergence and the different track type should begin (if desired) beyond the frogs. The "Blend" tool can then be used to create a more subtle transition.