Activity log for bug #1244273

Date Who What changed Old value New value Message
2013-10-24 15:10:54 Ben Dragon bug added bug
2013-10-30 09:15:27 Ben Dragon description By definition, the "Unit 3" light condition is meant to become "true" only when the Engine is at the rear of the train, as described in several pieces of documentation. Unfortunately, when I experimented around with this condition, there was no way to get the condition to return "true" within reasonable constraints. The closest that I got to getting the desired result was: Conditions ( Control ( 1 ) Coupling ( 2 ) ) Where Control ( 1 ) would check if the player wasn't driving the vehicle and Coupling ( 2 ) would check if there was nothing coupled to the front of the vehicle. The solution above only works with vehicles which are not locomotives but equipped with a .eng file since the control ( 1 ) relies on the player not being in the vehicle. The direct equivalent of the .eng Unit (3) bug, would be seen on the .wag Unit ( 3 ), where it is seen on the default BNSF chemical wagons working as it should be. OR version: X.1829 OS: Windows 7 To replicate the bug: 1: Locate a vehicle within the "Microsoft Train Simulator\TRAINS\TRAINSET" directory which contains a .eng configuration file. 2: Open up the .eng file using a unicode text editor (notepad or notepad++ can be used for this) and locate the light settings within the file. 3: Identify a chosen light to modify on your chosen vehicle and confirm you know which light you are going to be modifying (light type does NOT matter). 4: Replace all of the conditions of your chosen light with Unit ( 3 ) - This will disable any other conditions which would interfere with the tests. 5: Once you've done 4, create / modify a consist which would test all possible conditions. This bug is not limited to any specific activity / route, which would allow "free roam" or "explore" to be chosen when carrying out various tests. By definition, the "Unit 3" light condition is meant to become "true" only when the Engine is at the rear of the train, as described in several pieces of documentation. Unfortunately, when I experimented around with this condition, there was no way to get the condition to return "true" within reasonable constraints. The closest that I got to getting the desired result was: Conditions (  Control ( 1 )  Coupling ( 2 ) ) Where Control ( 1 ) would check if the player wasn't driving the vehicle and Coupling ( 2 ) would check if there was nothing coupled to the front of the vehicle. The solution above only works with vehicles which are not locomotives but equipped with a .eng file since the control ( 1 ) relies on the player not being in the vehicle. The direct equivalent of the .eng Unit (3) bug, would be seen on the .wag Unit ( 3 ), where it is seen on the default BNSF chemical wagons working as it should be. OR version: 0.9 X.1829 OS: Windows 7 To replicate the bug: 1: Locate a vehicle within the "Microsoft Train Simulator\TRAINS\TRAINSET" directory which contains a .eng configuration file. 2: Open up the .eng file using a unicode text editor (notepad or notepad++ can be used for this) and locate the light settings within the file. 3: Identify a chosen light to modify on your chosen vehicle and confirm you know which light you are going to be modifying (light type does NOT matter). 4: Replace all of the conditions of your chosen light with Unit ( 3 ) - This will disable any other conditions which would interfere with the tests. 5: Once you've done 4, create / modify a consist which would test all possible conditions. This bug is not limited to any specific activity / route, which would allow "free roam" or "explore" to be chosen when carrying out various tests.
2013-11-03 13:21:04 James Ross tags graphics
2013-11-03 13:28:21 James Ross or: status New Triaged
2013-11-03 13:28:23 James Ross or: importance Undecided Medium
2013-11-03 13:28:26 James Ross or: assignee James Ross (twpol)
2013-11-03 13:28:55 James Ross summary .eng Unit ( 3 ) Light Fault. Light condition Unit ( 3 ) doesn't work in engine files
2013-11-03 13:29:04 James Ross bug added subscriber James Ross
2013-11-03 16:43:12 James Ross or: milestone 1.0
2013-11-03 16:43:13 James Ross or: status Triaged Fix Committed
2015-05-25 10:52:44 James Ross or: status Fix Committed Fix Released