Leaving my train behind in quickdive

[Varney]

I've just encountered this too...

Quick drive on the Riviera Line, from Paignton to Exeter St. Davids using the Class 50 (Consist: NSE Revised Livery + 8 Mk1 Coaches).

HUD shows train as all together and clicking to uncouple results in crash to desktop.

I can replicate this after rebooting PC.

[NeutronIC]

Do you have any custom mods installed or was this a different consist perhaps?

I've just tried exactly that, using the consist that comes with the class 50, plus the riviera line and the start/end points you describe. The 3d model for the coupling is there, the consist shows up coupled ok on the hud and when i pull away it all comes with me correctly.

Hmm. I thought we might have had a repro there

Thanks
Matt
Dovetail Games

[Varney]

I've just tried it with the first consist (50007 GWR Green + 8 Mark 1 Coaches), and get the same result.

Only mod installed is the AP Pro soundpack.

Edit: When the quick drive loads there is a big coupling "clonk" sound.

Further edit: Can replicate with the same consist on other newer routes. Older routes such as ECML & S&D don't cause the issue.

[NeutronIC]

Very odd, it's working just fine here.

Matt
Dovetail Games.

[31160]

Hi all if it helps I will describe my problem along this thread

My problem was on the AY Valley line on a standard scenario going from the scenario editor then pressing the play button before this though I did the click and shift to make sure the train was complete and stable

The train was formed as

1 a class 421 driving trailer with the motors isolated and coupling edited
2 a KUJU MK 2 FK
3 a DT MK2e
4 a KUJU MK3
5 a class 73

All show as coupled in the HUD
As the train started to move it splits into three,the first 2 veihicles then the MK2e then the rear two after the train has split you can still go from the cab of the 421 to the 73 I will swap it from driver to AI to see if that makes a difference
And has been said before if you click on the couplings it crashes

[sean53]

Not having the problem myself but something popped into my head. Would it be something to do with aliased Kuju couplings. just a thought

[markpullinger]

Hi, had another thought - does the `allow any coupling` function, work in quick drive? - one for Matt and the team!

[crumplezone]

I poked around in the editor on the Wycombe and joint railway route from SSS where i've had the issue of the coupling with the Jinty and Gordon's P3s, going into the provider tab and going to RSDL -> then toggling on railsimulator in the first box option seems to have fixed the issue with the coupling.

I don't actually have the EU legacy pack from what I can tell unless its under another developer as it wasn't under RSC or DTG maybe its under RSDL, I think with my install being RW2 era and upgraded since then I might not have that file.

What this means I believe is possibly the file structure has been changed and its no longer referencing properly, maybe the kuju coupling is now in a .ap file and some .bin files don't know where to look and are throwing this tantrum and causing the coupling to not work even tho it shows connected in the HUD. This had happened in the past and people opted making there own coupling but in general it wasn't really a issue in TS2014 and as I said in previous post the P3s were working fine with the Jinty, but it seems to have thrown a wobbly with the upgrade and no longer likes it.

Slightly annoying, but it means that provider needs to be enabled in my case to make things work correctly.

[sean53]

You may well be right, so in 2015 the Kuju couplers are not referenced correctly for some

[crumplezone]

I've just actually checked over the class 50 as per Varney's comments and the route to, I'm getting the same result no coupling showing and the coaches being left behind. I think this is actually a kuju coupling issue which by default the new routes are not going to have since there now standalone .AP files, but it means also something has changed in the upgrade to make this all invalid all of sudden.

Edit: I have to enable Kuju -> Railsimulator in provider tab to fix the class 50, so its deffinately a kuju coupling issue at this point.

[NeutronIC]

Well, it's good news at least that we might have some way forward on what fixes it - so I can raise that as an issue in the fault database and the developers can see whether this area of the code changes has had an unexpected side effect.

I'm signing off my support shift now - Neal and Joe are taking over for the graveyard shift, and i'll be back online at 2pm Sunday.

Matt.

[Varney]

I've just actually checked over the class 50 as per Varney's comments and the route to, I'm getting the same result no coupling showing and the coaches being left behind. I think this is actually a kuju coupling issue which by default the new routes are not going to have since there now standalone .AP files, but it means also something has changed in the upgrade to make this all invalid all of sudden.

Edit: I have to enable Kuju -> Railsimulator in provider tab to fix the class 50, so its deffinately a kuju coupling issue at this point.

i have just done the same and enabled the Kuju -> Railsimulator in the provider tab. Fixed the issue with Class 50 for me too.

[hertsbob]

For reference, I had a go with the same Class 50 setup as mentioned earlier and have no issue with couplings at all.

[crumplezone]

For reference, I had a go with the same Class 50 setup as mentioned earlier and have no issue with couplings at all.

It could depend on age of installation or some other factor related the the recent reshuffle of the route information section. You might be able to fill me in or someone else, but isn't the information for which providers are being used stored in the route information folder?

From what I saw wrote the other day when we had the upgrade on the monday the route information folders got deleted and then replaced with new files, just throwing it out there but previously in TS2014 the kuju setup was probably fine and already toggled, now if the new route information is only referencing to the new .ap files where most of the kuju stuff now resides if you do fresh install/verified cache then I would take a educated guess and assume the kuju folder would no longer be referenced instead the EUlegacy pack instead.

This would make sense on my older install which still has most of the kuju folder intact and why say on the riveria line the coupling doesn't work with the 50 and the blue and white mk1s as I'm quite sure the mk1s reference kuju and not the new .ap file format. Since the new routes now are self contained .AP files then stuff referenced to kuju isn't going to load properly e.g. coupling, because the provider isn't even there in the first place and would be pointing to EU Legacy pack instead of kuju -> railsimulator in the new .AP format.

Lets for arguement sake say you have a install from TS2012 when DTG started to split the default up into legacy packs then any install later isn't going to have a issue since it would reference to the new EU legacy pack. Anything which pre-dates that shuffle over or didn't get its .bin file references updated to the new format is naturally going to bug out and do what its been doing.

In a nutshell, my install and probably Varney's to and anyone got a install going back to atleast RW2 might encounter this problem with any rolling stock which was originally kuju or has kuju references to them, especially because now most routes are self contained .AP files and will reference EU legacy over kuju.

I don't know if a verified cache would resolve this issue, it may do, but I think it won't unless the relevant .bin files are overwritten with a new one which references to the new files.

Not sure what DTG could do besides check the EU legacy rolling stock all is referenced in .bin files to EU legacy and not kuju and then push the update to ensure all users have there rolling stock singing from the same hymn sheet.

[sean53]

Must be affecting other Kuju aliased stuff as well such as sounds. Surprised it did not fall over when certain sounds were called