Coupling problem
Moderator: Moderators
Coupling problem
Downloaded a scenario from steam workshop for the new WHL route. Sleeper service to Fort William. As the scenario had the incorrect sleeper stock, I cloned the scenario with RW-tools.
I substituted two mk3 sleepers with the correct FSR Caledonian ones and changed the rear two coaches to MK2e RLO Scotrail. When running the scenario the mk2e's are left behind and the HUD shows 0mph and all 4 coaches present.
Never had this problem before with swopping stock, as I have to do with most scenarios using sleeper stock.
On UKTS today was the first scenario for the Windermere extension, so gave it ago. Between Oxenholme and Preston I noted my 4 car class 170 had become 1, left the other 3 behind somewhere.
Any advice or assistance would be appreciated.
I substituted two mk3 sleepers with the correct FSR Caledonian ones and changed the rear two coaches to MK2e RLO Scotrail. When running the scenario the mk2e's are left behind and the HUD shows 0mph and all 4 coaches present.
Never had this problem before with swopping stock, as I have to do with most scenarios using sleeper stock.
On UKTS today was the first scenario for the Windermere extension, so gave it ago. Between Oxenholme and Preston I noted my 4 car class 170 had become 1, left the other 3 behind somewhere.
Any advice or assistance would be appreciated.
Re: Coupling problem
Don't have any helpful advice but it seems that the Digital Traction coaches have this as I've suffered it with their mk1s and mk2s, not tried the 170s yet.casrtt wrote:Downloaded a scenario from steam workshop for the new WHL route. Sleeper service to Fort William. As the scenario had the incorrect sleeper stock, I cloned the scenario with RW-tools.
I substituted two mk3 sleepers with the correct FSR Caledonian ones and changed the rear two coaches to MK2e RLO Scotrail. When running the scenario the mk2e's are left behind and the HUD shows 0mph and all 4 coaches present.
Never had this problem before with swopping stock, as I have to do with most scenarios using sleeper stock.
On UKTS today was the first scenario for the Windermere extension, so gave it ago. Between Oxenholme and Preston I noted my 4 car class 170 had become 1, left the other 3 behind somewhere.
Any advice or assistance would be appreciated.
Matthew Wilson, development team at Vulcan Productions
http://www.vulcanproductions.co.uk
https://www.facebook.com/VulcanFoundry/
http://www.vulcanproductions.co.uk
https://www.facebook.com/VulcanFoundry/
-
gptech
- Very Active Forum Member
- Posts: 19585
- Joined: Fri Oct 10, 2008 5:48 pm
- Location: Wakefield, West Yorkshire
Re: Coupling problem
Yes, I've had this issue reported to me as happening on a consist containing a reskinned DT Mk2 we've been playing around with. As the problem hasn't manifested itself on my system I've been clutching at straws, but following investigative work to narrow the issue down to the DT coach (or rather how TS2015 now deals with couplings; can't fault the coaches as they've worked beautifully in previous incarnations of the game) we're now trying a revised .bin file with the coupling pivot points edited to match the Kuju defaults.
If you want to give it a try, and it'd be helpful if somebody (anybody) would, the edited value is the next to bottom one in the coupling pivot point matrices. Changing this to 9.78 for the front pivot and -9.78 for the rear has had no adverse effects on my setup, I'm hoping when Mark gives it a thorough test it will fix the 'elastic coupling' issue.
I've not tried the 170s either, so can't offer any help on that one.
If you want to give it a try, and it'd be helpful if somebody (anybody) would, the edited value is the next to bottom one in the coupling pivot point matrices. Changing this to 9.78 for the front pivot and -9.78 for the rear has had no adverse effects on my setup, I'm hoping when Mark gives it a thorough test it will fix the 'elastic coupling' issue.
I've not tried the 170s either, so can't offer any help on that one.
-
gptech
- Very Active Forum Member
- Posts: 19585
- Joined: Fri Oct 10, 2008 5:48 pm
- Location: Wakefield, West Yorkshire
Re: Coupling problem
I've just run the 170 from Windermere scenario and I'd suggest trying one of the default liveries rather than a reskin.
Admittedly he FTPE version I used didn't 'drop to bits', but my money's on a slightly awry .bin file---probably not the reskinners fault, he will have used what he had available and obviously it worked in TS whatever-it-was-at-the-time so any error could have been built in before he got near it.
Trying a default item, and if it works comparing the .bins could shed more light on it.
Admittedly he FTPE version I used didn't 'drop to bits', but my money's on a slightly awry .bin file---probably not the reskinners fault, he will have used what he had available and obviously it worked in TS whatever-it-was-at-the-time so any error could have been built in before he got near it.
Trying a default item, and if it works comparing the .bins could shed more light on it.
Re: Coupling problem
Thank you for your help.
I have tried out scenarios that I modified with these DT mk2e's prior to TS2015 and they work fine. This is the first time I have swopped them using RW-tools in TS2015.
With the Class 170, have tried a few scenarios and they have not come apart yet, although I have not used the FTPE repaint.
I have tried out scenarios that I modified with these DT mk2e's prior to TS2015 and they work fine. This is the first time I have swopped them using RW-tools in TS2015.
With the Class 170, have tried a few scenarios and they have not come apart yet, although I have not used the FTPE repaint.
- 37180sirdyfed
- Well Established Forum Member
- Posts: 546
- Joined: Thu Sep 12, 2002 3:29 pm
- Location: Berkshire & South Wales
Re: Coupling problem
The same thing happened to a scenario I just made... using the same stock... the Mk2e DT.. just got left behind... 
Re: Coupling problem
Just thought I would update now that I have finally tried, I adjusted the coupling pivot points in the bin files and when I put them in a Quick Drive with a Class 50 on the front the consist just instantly exploded!
Matthew Wilson, development team at Vulcan Productions
http://www.vulcanproductions.co.uk
https://www.facebook.com/VulcanFoundry/
http://www.vulcanproductions.co.uk
https://www.facebook.com/VulcanFoundry/
-
gptech
- Very Active Forum Member
- Posts: 19585
- Joined: Fri Oct 10, 2008 5:48 pm
- Location: Wakefield, West Yorkshire
Re: Coupling problem
Did you use a mix of First, Second and Brake?deltic009 wrote:when I put them in a Quick Drive with a Class 50 on the front the consist just instantly exploded!
Could you try it in a conventional Free Roam?
and with a different loco?
- mikesimpson
- Very Active Forum Member
- Posts: 6361
- Joined: Mon Dec 03, 2001 12:00 am
- Location: Southern Hemisphere Penal Colonies
- Contact:
Re: Coupling problem
There does appear to be a problem using the DT MkII coaches in TS2015 - I saw a post somewhere else about this, with a fix, but can't find it today.
Mike
Mike
Mike in OZ - Author of TS-Tools & Route-Riter.
http://www.agenetools.com
I'm not arguing (just explaining why I'm right).
http://www.agenetools.com
I'm not arguing (just explaining why I'm right).
-
markpullinger
- Very Active Forum Member
- Posts: 3105
- Joined: Sun Jun 08, 2003 6:24 pm
Re: Coupling problem
Hi, I think the fix was to tick the kuju box in the world editor for that route.
- 37180sirdyfed
- Well Established Forum Member
- Posts: 546
- Joined: Thu Sep 12, 2002 3:29 pm
- Location: Berkshire & South Wales
Re: Coupling problem
Thanks a million for that!!! It now works a treat!markpullinger wrote:Hi, I think the fix was to tick the kuju box in the world editor for that route.
Re: Coupling problem (Solved)
Thanks that has solved the problem.markpullinger wrote:Hi, I think the fix was to tick the kuju box in the world editor for that route.
Re: Coupling problem
Okay, so now we have a fix we need to work out why, as in find out what file to move/duplicate in order to remove the tick requirement. I'll fire up RW tools when possible but thanks for the solution in the meantime.37180sirdyfed wrote:Thanks a million for that!!! It now works a treat!markpullinger wrote:Hi, I think the fix was to tick the kuju box in the world editor for that route.
Matthew Wilson, development team at Vulcan Productions
http://www.vulcanproductions.co.uk
https://www.facebook.com/VulcanFoundry/
http://www.vulcanproductions.co.uk
https://www.facebook.com/VulcanFoundry/
-
gptech
- Very Active Forum Member
- Posts: 19585
- Joined: Fri Oct 10, 2008 5:48 pm
- Location: Wakefield, West Yorkshire
Re: Coupling problem
Ticking Kuju\RailSimulator fixes the QD issue, but it apparently persists in Standard scenarios.
Re: Coupling problem
The standard scenario I edited using RW-tools works fine now, the mk2's are not left behind. I will do some more editing later to see if the problems totally cleared or if it returns.gptech wrote:Ticking Kuju\RailSimulator fixes the QD issue, but it apparently persists in Standard scenarios.
The fix appears to work for 37180sirdyfed, who was creating a scenario.