Trainz Plus Beta TLR Phase 3 - 132833

WestSideRailways said:
Nothing was disabled. I selected a line from Main Yard Station and adjusted the order of the stations and added some others. The train started from one of the stations in the loop.
and ended at the last station before the first station it started from.

The loop consists of the following stations. From Main Yard Station then heading East it goes to Refinery, Westside Station, Coal Burning, Hyde South and then back to Main Yard.
It is a closed loop. There are 2 tracks one clockwise and one anti-clockwise. These are Platforms 1 & 2 . Platform 3 is for the local country lines.

If I make a passenger line a loop, and there are 5 station on that loop. Do I have to tell it to go back to the station it started from to achieve the loop.?
Click to expand...
As per ColPrice2002 comment, did you set the Passenger Line as "Loop" type?
 
iPortalBasic fails with a script error now.

Code: 
- <kuid2:30671:23501:1> : File scenerywithtrack.gs, Line 82, ER_NullReference
  ; <kuid2:30671:23501:1> : Script class: iPortalBasic
  ; <kuid2:30671:23501:1> : MeshObject: <kuid2:30671:23501:1> "iPortalBasic"
  ; <kuid2:30671:23501:1> : Script callstack
    ; <kuid2:30671:23501:1> : function $string@SceneryWithTrack::FindTriggerContainingNode(int,bool), mobj{id=533580150, ScriptableObject{0x1da7e2500; asset:SpecReference{<kuid2:30671:23501:1> "iPortalBasic"}, class:GSClass{0x1ae5fcb20: iPortalBasic}, refcount:11}}function $void@iPortalBasic::EmitTrain(), line 1581 iportalbasic.gse, mobj{id=533580150, ScriptableObject{0x1da7e2500; asset:SpecReference{<kuid2:30671:23501:1> "iPortalBasic"}, class:GSClass{0x1ae5fcb20: iPortalBasic}, refcount:11}}function $void@iPortalBasic::CheckEmitTrains(), line 1861 iportalbasic.gse, mobj{id=533580150, ScriptableObject{0x1da7e2500; asset:SpecReference{<kuid2:30671:23501:1> "iPortalBasic"}, class:GSClass{0x1ae5fcb20: iPortalBasic}, refcount:11}}function $void@iPortalBasic::ThreadEmitTrains(), line 1843 iportalbasic.gse, mobj{id=533580150, ScriptableObject{0x1da7e2500; asset:SpecReference{<kuid2:30671:23501:1> "iPortalBasic"}, class:GSClass{0x1ae5fcb20: iPortalBasic}, refcount:11}}

When sending trains between iPortals, the interface is still broken. This was reported already, though. They worked okay otherwise in automatic mode in SP4, and I didn't test in SP5 or SP6 due to personal issues getting in the way, however running in SP6 they no longer worked.

This version produces this error now and only the first locomotive from a "sent" consist appeared on the destination route and is not the rest of the consist. The consist never got pushed completely out and the loco remains on the portal track. It appears that the process failed with the error shown above and the process halted.
 
Last edited:
n3v_laurence said:
As per ColPrice2002 comment, did you set the Passenger Line as "Loop" type?
Click to expand...
The line is assign as a loop, But the driver will stop at the stop before the first stop. So it does not do the loop.
IE... if the line has 5 stops, the driver will stop at all 5, BUT will not continue to the first stop again to complete the loop.

If you edit the line so that the 1st stop is assigned twice (once at the beginning and once at the end) the line become RED and can not be assign a driver.
 
I had a crash to the desktop (CTD) today after spending time in Surveyor doing what we usually do. I trimmed and merged in a route and then replaced the track to match what is on the rest of the route. During the track replacement, everything disappeared to the desktop.
 
Just ran a test on merging two large routes in both the retail (132284) and beta (132833) versions of Trainz Plus.

The original starting route is 194.5MB (with a 3.3MB session) and the second route is 210.4MB in size, with no session, in both versions of Trainz Plus as reported by CM.

The merged routes (with the first routes session included) sizes as reported in CM are:-
  • 404.4MB for the route and 3.9MB for the session in the non-beta Trainz Plus, and
  • 1163.5MB for the route and 760MB for the session in the beta Trainz Plus
I checked that the original and merged versions are using 10m resolution and not HD.

Is this blowout in CM file size a beta property, i.e. no compression is being used in the beta version? Nothing on this is mentioned in the "Known Issues" in the first post. Or is it a bug, in which case I will submit a report? Naturally I did try compressing the beta route file into a .cdp but that operation failed as the file size was over 1GB.
 
pware said:
Just ran a test on merging two large routes in both the retail (132284) and beta (132833) versions of Trainz Plus.

The original starting route is 194.5MB (with a 3.3MB session) and the second route is 210.4MB in size, with no session, in both versions of Trainz Plus as reported by CM.

The merged routes (with the first routes session included) sizes as reported in CM are:-
  • 404.4MB for the route and 3.9MB for the session in the non-beta Trainz Plus, and
  • 1163.5MB for the route and 760MB for the session in the beta Trainz Plus
I checked that the original and merged versions are using 10m resolution and not HD.

Is this blowout in CM file size a beta property, i.e. no compression is being used in the beta version? Nothing on this is mentioned in the "Known Issues" in the first post. Or is it a bug, in which case I will submit a report? Naturally I did try compressing the beta route file into a .cdp but that operation failed as the file size was over 1GB.
Click to expand...
That sounds like a bug. Get a report in please.
 
WestSideRailways said:
The line is assign as a loop, But the driver will stop at the stop before the first stop. So it does not do the loop.
IE... if the line has 5 stops, the driver will stop at all 5, BUT will not continue to the first stop again to complete the loop.

If you edit the line so that the 1st stop is assigned twice (once at the beginning and once at the end) the line become RED and can not be assign a driver.
Click to expand...
I've clarified this with the team.

Loop and Terminate will visit each station only once (per task). Reverse will drive up and back. Loops can start anywhere. Reverse can start at either end. Terminate can only start at the first station.

There is a setting for Dispatch Manager to allow mid-line start, which by default is set to loops only.

To have the Passenger Line re-issued to the driver once the task has been completed, you will need to enable Dispatch Manger (and remember to disable auto line generation if you only want that passenger line dispatched). Alternatively you can manually reissue the task once complete. There is no auto-repeat function.
 
I tried to create a line Kings X to York, kept telling me it was invalid under Dispatch Manager.
Yet when i claimed the task and started running it manually. With the green path indicator showing in driver, it created the path perfectly as far as Grantham.
Which is where i saved it. Also the only auto paths created from Kings X are local runs to Moorgate. Why are there no main line passenger lines auto created.
Everything is marked as invalid or station unreachable.

Mike.
 
IsambardKingdomBrunel said:
I tried to create a line Kings X to York, kept telling me it was invalid under Dispatch Manager.
Yet when i claimed the task and started running it manually. With the green path indicator showing in driver, it created the path perfectly as far as Grantham.
Which is where i saved it. Also the only auto paths created from Kings X are local runs to Moorgate. Why are there no main line passenger lines auto created.
Everything is marked as invalid or station unreachable.

Mike.
Click to expand...
Did you change the maximum station distance and/or the maximum Line Length? These settings can be reach by clicking on the down arrow then selecting Show Advanced Dispatch Settings. Line length is based on the maximum number of stations.
 
pware said:
The merged routes (with the first routes session included) sizes as reported in CM are:-
  • 404.4MB for the route and 3.9MB for the session in the non-beta Trainz Plus, and
  • 1163.5MB for the route and 760MB for the session in the beta Trainz Plus
I checked that the original and merged versions are using 10m resolution and not HD.
Click to expand...
N3V QA have confirmed that this is a bug.
 
n3v_laurence said:
I've clarified this with the team.

Loop and Terminate will visit each station only once (per task). Reverse will drive up and back. Loops can start anywhere. Reverse can start at either end. Terminate can only start at the first station.

There is a setting for Dispatch Manager to allow mid-line start, which by default is set to loops only.

To have the Passenger Line re-issued to the driver once the task has been completed, you will need to enable Dispatch Manger (and remember to disable auto line generation if you only want that passenger line dispatched). Alternatively you can manually reissue the task once complete. There is no auto-repeat function.
Click to expand...
It appears that your definition of "LOOP" and mine are two different things?

To me a LOOP should be continuous.. ie Never Ending.

If a passenger line is to be defined as a LOOP, the program should ask for the start station and the finish station.
Then those stations would constitute the LOOP and would be stopped at until told to stop.!!

Have said this before, IF a loop can be program with Driver Commands, THEN why is it so hard to do with the Dispatch Manager.??

Also there is a Driver Command that allows you to REPEAT COMMANDS..... WHY is this so hard for Dispatch Manager.
 
WestSideRailways said:
It appears that your definition of "LOOP" and mine are two different things?

To me a LOOP should be continuous.. ie Never Ending.

If a passenger line is to be defined as a LOOP, the program should ask for the start station and the finish station.
Then those stations would constitute the LOOP and would be stopped at until told to stop.!!

Have said this before, IF a loop can be program with Driver Commands, THEN why is it so hard to do with the Dispatch Manager.??

Also there is a Driver Command that allows you to REPEAT COMMANDS..... WHY is this so hard for Dispatch Manager.
Click to expand...
Loop line is defined as a series of stations that loop back around. If each station is visited once, it will complete the loop regardless where it starts (hence why by default mid line starts are allowed for loop types). If you wish it to start at one specific station and finish at another, perhaps its best you run as type terminate or disable the midline start for loop.

Once a passenger line task has completed, Dispatch Manager can re-issue the task to the driver, effectively driving the passenger line on repeat. This applied to all passenger line types (not just loop).
 
Thanks for the info on the loop lines and terminate. That would explain why all 3 ai drivers ended up trying to reach the same destination! I had allocated one to carry out a loop service (terminus to a mainline station), another to run an express service (point to point with a stop at the mainline station - as above) and a third to run a stopping service. Obviously, all 3 reached a common station and were then reallocated…
Is there a way to run a passenger line without reallocation?
 
You must log in or register to reply here.

Similar threads

n3v_laurence
  • Locked
Trainz Plus Beta TLR Phase 3 - 132513
3 4 5
Replies
94
Views
6K
n3v_laurence
n3v_laurence
n3v_laurence
  • Locked
Trainz Plus Beta TLR Phase 2 - Mac 128359
Replies
5
Views
1K
n3v_laurence
n3v_laurence
n3v_laurence
  • Locked
Trainz Plus Beta TLR Phase 2 - 128449 & 128443
2
Replies
30
Views
5K
JCitron
J
n3v_laurence
  • Locked
Trainz Plus Beta TLR Phase 2 - 128360
2
Replies
20
Views
3K
n3v_laurence
n3v_laurence
n3v_laurence
  • Locked
Trainz Plus Beta TLR Phase 2 - 128230
Replies
11
Views
2K
n3v_laurence
n3v_laurence
Back
Top