Revision X1928
#1
Posted 08 January 2014 - 04:06 AM
X1928 seems to cause sounds attached to the cloning vehicle to also be attached to the clones. When running an act that has a Player DMU and many AI trains formed from the same DMU, the Player DMU has sounds totally unrelated to it. I have verified that it is caused by X1928 by reverting back to X1927.
Dennis
#3
Posted 08 January 2014 - 08:45 AM
gpz, on 08 January 2014 - 07:51 AM, said:
I've just done a clean checkout of the code at X1927 and the effect does not happen with this release. I followed that by another clean checkout at X1928 and confirmed that the extraneous sound does occur there. Using the Sound Debugging form, I have identified the source of the extraneous sounds as an AI of identical stock to the Player train entering the station at the very start of the activity. The Player train is stationary with throttle closed but with the engines apparently loudly audibly running from the cab and outside. As the AI approaches and comes to a stop, the audible engine sounds rise and fall in the cab of the Player train as though the Player thrain throttle is being opened and closed. Operation of the throttle on the Player train, although causing a rise in tractive effort does not affect the sounds audible in the cab. About 5 or 6 minutes after the AI has vanished, Player train sounds revert to normal - apparently.
Dennis
PS: Just to confirm the releases I've just tested were absolutely clean from the SVN server - all copies on my system were completely deleted before both checkouts and no personal mods on anywhere.
#4
Posted 08 January 2014 - 10:44 AM
in r1928 the following line was removed:
DieselEngines = new DieselEngines(locoCopy.DieselEngines, this);
and was inserted a new line elsewhere:
DieselEngines = locoCopy.DieselEngines;
However this new line seems to be incorrect. DieselEngines is a class, so assigning it by the latter way only assigns the reference of the locoCopy.DieselEngines, so in fact they will be exactly the same objects, referenced by two variables. The first way of copying is the correct one.
This commit is Robert's one, so he could explain what was the idea behind the change.
#5
Posted 08 January 2014 - 10:52 AM
Thanks for the prompt attention to this problem. Knowing that people do investigate these glitches is another of the reasons I am an OR supporter.
Dennis
#6
Posted 08 January 2014 - 01:34 PM
gpz, on 08 January 2014 - 10:44 AM, said:
in r1928 the following line was removed:
DieselEngines = new DieselEngines(locoCopy.DieselEngines, this);
and was inserted a new line elsewhere:
DieselEngines = locoCopy.DieselEngines;
However this new line seems to be incorrect. DieselEngines is a class, so assigning it by the latter way only assigns the reference of the locoCopy.DieselEngines, so in fact they will be exactly the same objects, referenced by two variables. The first way of copying is the correct one.
This commit is Robert's one, so he could explain what was the idea behind the change.
There were a lot of duplicate lines in there, so I cleaned it up and messed that one up. I'll fix that tonight, and restore the correct copy assignment...
Robert
#7
Posted 09 January 2014 - 02:22 AM
gpz, thanks so much for checking this out, and explaining the correct method.
Robert
#8
Posted 09 January 2014 - 03:04 AM
Thanks very much for your efforts. I'll check that the problem has gone as soon as I can. Housework today, must have the place looking presentable when my wife gets home. (I'm retired but my wife still works)
Dennis
#9
Posted 09 January 2014 - 06:34 AM
dennisat, on 09 January 2014 - 03:04 AM, said:
Thanks very much for your efforts. I'll check that the problem has gone as soon as I can. Housework today, must have the place looking presentable when my wife gets home. (I'm retired but my wife still works)
Dennis
Yes, please. Then we can put this bug to bed, er the roach hotel, or, er, wherever dead bugs go... :lol2:
Robert
#10
Posted 09 January 2014 - 07:58 AM
Dennis