Liskeard to Looe

[HPL]

This issue didn't exist some time ago (before route update to :11 and Build 117092):

 

[amigacooke]

That'll teach those fare dodgers

 

[G.M.]

Are these AJS hidden passenger stations?
What I learned here, once a route has sessions
you have to set the height of the passengers in the session and save

 

[pware]

I created the Looe to Liskeard Passenger Run session. They are AJS stations and my copy of the route and session (installed from the DLC) is showing OK - passengers standing on the platforms not buried by it.

There was an update released to the route and sessions. Check the Updates Icon in the Trainz launcher Content Store because there was a height problem with the AJS platforms in the original release - although that height problem would have had the passengers floating above the platforms.

 

[HPL]

Check the Updates Icon in the Trainz launcher Content Store because there was a height problem with the AJS platforms in the original release.

It is precisely since the route has been updated to version :11 that the issue occurs.

 

[pware]

I have the updated package with <kuid2:179051:102285:11> Liskeard to Looe installed in build 117092 and it is working fine.

The AJS asset installed is <kuid2:122285:3401:22> AJS Invisible Station 1T 3.5, check that yours is the same.

 

[pware]

An Update: Just to test it out I installed Liskeard to Looe from the content store on a second computer, also with build 117092, and the result is the same. The passengers on the platforms are standing normally in all 3 sessions.

 

[HPL]

They do in packaged sessions, but not in my own sessions since version :11 of the route. The AJS Invisible Station is :22 ("Packaged") and was installed in 2018, so something has changed in :11 versus previous versions.

 

[pware]

They do in packaged sessions, but not in my own sessions since version :11 of the route.

OK, I was not aware that you had used the route to create your own sessions. I thought that you were referring to the supplied sessions.

Staring with the :11 version of the route, I created a new session and added a rail car at the Liskeard branch line platform. I switched to Driver mode and checked the platforms - all passengers are positioned correctly.

I have no explanation for what you are seeing.

 

[HPL]

Patch to Build 117092 and version :11 of the route came simultaneously. I suspect the issue araised with one of them, or both.

 

[stagecoach]

What version of the route was your session made in? It maybe that the mesh is saved in the session in a different way than before.

 

[HPL]

Session was created on 6th September, 2021. I don't know what was the version at this time.

 

[stagecoach]

The upload dates I have are
<kuid2:179051:102285:7> Liskeard to Looe 2021 19 DEC 2020
<kuid2:179051:102285:10> Liskeard to Looe 16 FEB 2022
<kuid2:179051:102285:11> Liskeard to Looe 25 MAR 2022
This means your session was created using version 7 or earlier

 

[HPL]

No issue with a session of another route using the same AJS asset, so this confirms the issue is due to the last version of Liskeard to Looe.

 

[JCitron]

I can confirm the route and sessions are fine in Trainz-Plus 117092. The passengers "stand" on the platform and are not buried up to their necks.

 

[ZecMurphy]

Hi HPL
Could you please tell me what you currently have the 'compatibility mode' setting in the Dev tab of the Trainz Settings set to? If you have this set to 'maximise performance', then could you please try changing it to 'maximise compatibility' and then restart Trainz and see if you still see this issue.


Please also ensure that you do have the latest update for this DLC pack installed; you can check this by opening the Content Store and then locating the DLC pack and see if it shows 'update' on the button for the DLC pack.

Regards

 

[HPL]

Hello Zec,

I always play with "Compatibility Mode" set to "Maximise Compatibility". As said before, DLC version is :11 (the latest), the issue only concerns custom sessions created in a prior version 7) and doesn't exist for custom sessions on another route using the same AJS asset.
The only solution I found is to recreate the sessions from scratch and then the issue vanishes.

 

[Rob]

Hi. I created a session on version :7 which I have installed on build 114022 but was unable to reproduce this problem when moving that session to 117092 on the version :11 route.

Depending on the session it might be easier to check/set the passenger height in the properties for each of the 5 interactive stations under: Station Platforms / Passenger Height.

Looe 1.22
Sandplace 1.18
Causeland 1.15
St Keyne Wishing Well Halt 1.2
Liskeard 1.35