East Kentucky
- Thread starter Dermmy
- Start date
Hello!
I know, long time no hear. First, some hacker destroyed my Windows system, and I didn't want to buy another license for Windows Vista. Now I am on a Mac Mini. I downloaded EK3ST and played the session with US content. There are a few flaws there:
On the westbound trip the train uses the eastbound mainline track in Jeff yard. Could be repaired by an additional track mark and the corresponding driver command.
On the eastbound trip first the train got stuck because a three-headed signal at a trailing end of a junction didn't know what to do; clicking on the signal told me it was in an unknown state. Finally I opened its property page and turned restrictive mode on. Then the train got moving. Wouldn't a one-headed signal have done?
At the end the train went through Daisy Tipple and loaded there - another missing track mark command. At Beechfork Tipple it didn't have to load and started on the next eastbound trip pushing the train; you forgot to insert a runaround command somewhere at the end of your command chain.
All in all, it's a grand route, and I am waiting for EK4 now.
I shall correct these things in my computer and then try to satisfy the other waybill request where Leatherwood needs Diesel fuel.
I would like to know whether anybody else has met with the same problems.
Dralex
I know, long time no hear. First, some hacker destroyed my Windows system, and I didn't want to buy another license for Windows Vista. Now I am on a Mac Mini. I downloaded EK3ST and played the session with US content. There are a few flaws there:
On the westbound trip the train uses the eastbound mainline track in Jeff yard. Could be repaired by an additional track mark and the corresponding driver command.
On the eastbound trip first the train got stuck because a three-headed signal at a trailing end of a junction didn't know what to do; clicking on the signal told me it was in an unknown state. Finally I opened its property page and turned restrictive mode on. Then the train got moving. Wouldn't a one-headed signal have done?
At the end the train went through Daisy Tipple and loaded there - another missing track mark command. At Beechfork Tipple it didn't have to load and started on the next eastbound trip pushing the train; you forgot to insert a runaround command somewhere at the end of your command chain.
All in all, it's a grand route, and I am waiting for EK4 now.
I shall correct these things in my computer and then try to satisfy the other waybill request where Leatherwood needs Diesel fuel.
I would like to know whether anybody else has met with the same problems.
Dralex
Hi Drelex - sorry to hear about your computer mishaps.
To the best of my recollection no-one has complained of these issues previously. The sessions were tested to death in TS10 and pretty sure in TS12 also. All thee issues are easy fixes and they would have been fixed had they shown up. The sessions were not tested on a Mac: Trainz for Mac is a new innovation since the route was released. I have also had a report of an issue with a Clovis session in a Mac where there is no issue in other Trainz versions.
While there may be a need for additional driver commands but there should be no need for additional trackmarks to make the AI hold the main, every main line loop has a TM at least at both ends - unless I missed one! But generally a single command to the near end of the loop takes the AI through the required road.
Not sure which triple-head caused you grief, but whichever it was triple-heads are only used on multiple-lever interlockings so a one-head would not really be correct. Again none of the Interlocking Signals cause issues in other Trainz versions, but these signals are scripted so there could possibly be a Mac v script issue, though I lack the technical expertise to really comment on that one way or the other...
Andy
Last edited:
Thank you for your quick response. The issue of trains using the wrong track is well known and due to the fact that the Artificial Incompetence always tries to find the shortest way (as the crow flies) between two points. And when there is a long bend between the train may well (and evidently does) use the wrong track because it is the shortest route. That is why additional driver commands are certainly necessary (and even recommended) in such cases. I will of course use the trackmarks that are already there for this purpose.
The signal that caused me grief is S240.9E, right between trackmark EKPower_EastLead_Long and junction EKP_01 (should have told you that before, mea culpa). After browsing the WWW for American signalling practices, particularly at http://www.lundsten.dk/us_signaling/signalbasics/, I think that this junction does not need a three-head, as the next facing junction is HZ33B, which is already protected by three-headed S241.4E. If this signal were not there, then S240.9E has to be indeed three-headed.
What does the option 'allow restrictive aspect' mean? It is off at the signal in question, and there might indeed be a difference in the reaction of a Windows and of a Mac PC. I think I better get me the Clovis route and its sessions and try to reproduct this problem.
If you want anything tested on a Mac I'll be happy to do it for you.
Greetings,
Dralex
The signal that caused me grief is S240.9E, right between trackmark EKPower_EastLead_Long and junction EKP_01 (should have told you that before, mea culpa). After browsing the WWW for American signalling practices, particularly at http://www.lundsten.dk/us_signaling/signalbasics/, I think that this junction does not need a three-head, as the next facing junction is HZ33B, which is already protected by three-headed S241.4E. If this signal were not there, then S240.9E has to be indeed three-headed.
What does the option 'allow restrictive aspect' mean? It is off at the signal in question, and there might indeed be a difference in the reaction of a Windows and of a Mac PC. I think I better get me the Clovis route and its sessions and try to reproduct this problem.
If you want anything tested on a Mac I'll be happy to do it for you.
Greetings,
Dralex
For the 'missing' bridges there is a fix on the checkrail download page, but to save you going back simply remove the
name
line from the bridge configs. If you need the bridge kuids you will need to refer to the download page. Be sure to remove the entire line including (invisible) spaces.
For the bogie issues what kuid(s) are reported missing?
name
line from the bridge configs. If you need the bridge kuids you will need to refer to the download page. Be sure to remove the entire line including (invisible) spaces.
For the bogie issues what kuid(s) are reported missing?
and what name am I suppose to delete,
kind "bridge"
type "Bridges"
length 4
height -3.006
istrack 1
bendy 1
width 3
rgb 200,100,0
repeats 1
trackoffsets 0.01
bridgetrack <kuid:35412:38051>
region "JJS"
obsolete-table
{
}
trainz-build 1.3
category-region-0 "to"
category-era-0 2000
asset-filename "JJS_Pratt_Truss_Deck"
category-class "TB"
kuid <kuid:46819:38132>
description "l"
username "JJS_Pratt_Truss_Deck"
thumbnail
author
organisation
contact-email
contact-website
license
kuid-table
{
0 <kuid:35412:38051>
}
kind "bridge"
type "Bridges"
length 4
height -3.006
istrack 1
bendy 1
width 3
rgb 200,100,0
repeats 1
trackoffsets 0.01
bridgetrack <kuid:35412:38051>
region "JJS"
obsolete-table
{
}
trainz-build 1.3
category-region-0 "to"
category-era-0 2000
asset-filename "JJS_Pratt_Truss_Deck"
category-class "TB"
kuid <kuid:46819:38132>
description "l"
username "JJS_Pratt_Truss_Deck"
thumbnail
author
organisation
contact-email
contact-website
license
kuid-table
{
0 <kuid:35412:38051>
}
It's deleted!
There is a blank 'name' tag in the original config that causes the no-show. The suspect assets are <Kuid:46819:38129> and <Kuid:46819:38132>. I haven't done a full config check on your edit, but if it's still no-show either you have deleted something in addition to the blank 'name' tag - or - the edited asset is still under the 'Open For Edit' tab in which case Trainz will continue to load the un-fixed version, that being the last version committed. If it is hung up in Open For Edit, highlight it then Ctrl+M...
There is a blank 'name' tag in the original config that causes the no-show. The suspect assets are <Kuid:46819:38129> and <Kuid:46819:38132>. I haven't done a full config check on your edit, but if it's still no-show either you have deleted something in addition to the blank 'name' tag - or - the edited asset is still under the 'Open For Edit' tab in which case Trainz will continue to load the un-fixed version, that being the last version committed. If it is hung up in Open For Edit, highlight it then Ctrl+M...
NickieFoenshauge
New member
I was very pleased, when EK3-ST turned up again on checkrail. The screenshots are just awe-inspiring. But, it has left me with a few 'unknown' assets.
Unknown Location: <kuid2:50567:12644:2>
This is by idiotbuoy - a dependency of PL JohnDeere,<kuid2:30671:27388:1> - but I haven't been able to track it down.
Unknown Location: <kuid2:30671:27375:2>
Unknown Location: <kuid2:30671:27383:1>
Unknown Location: <kuid2:30671:27384:1>
These three are part of ProtoLARS MegaPack 1.1 (actually, <kuid2:30671:27375:1> is listed as belonging to the pack and not <kuid2:30671:27375:2>), but I have no idea how to unpack the .man file, I downloaded. Any ideas about this?
Never mind. I found a direct link to the ProtoLARS assets on the EK3 page. Both route and sessions now show up as having no unknown dependencies, despite the still missing <kuid2:50567:12644:2>. I suppose everything is OK then.
Thank you Andi for sharing this magnificent route with us! :Y:
Thanks, Nickie
Unknown Location: <kuid2:50567:12644:2>
This is by idiotbuoy - a dependency of PL JohnDeere,<kuid2:30671:27388:1> - but I haven't been able to track it down.
Unknown Location: <kuid2:30671:27375:2>
Unknown Location: <kuid2:30671:27383:1>
Unknown Location: <kuid2:30671:27384:1>
These three are part of ProtoLARS MegaPack 1.1 (actually, <kuid2:30671:27375:1> is listed as belonging to the pack and not <kuid2:30671:27375:2>), but I have no idea how to unpack the .man file, I downloaded. Any ideas about this?
Never mind. I found a direct link to the ProtoLARS assets on the EK3 page. Both route and sessions now show up as having no unknown dependencies, despite the still missing <kuid2:50567:12644:2>. I suppose everything is OK then.
Thank you Andi for sharing this magnificent route with us! :Y:Thanks, Nickie
Last edited:
NickieFoenshauge
New member
No, I suppose not, but I thought PL JohnDeere,<kuid2:30671:27388:1> was. On the EK3-ST page it said to download <kuid2:30671:273***:*>, so I did (I didn't realize it was a direct link to the three <kuid2:30671:273***:*> assets.
I thought it would send me off to the TPR site to search for the assets like the other three TPR links ). And <kuid2:30671:27388:1> turned out to have a missing dependency. But, I've since then deleted <kuid2:30671:27388:1> again and both route and sessions are still OK, so all is fine. 
Last edited:
NickieFoenshauge
New member
No worries, mate. When the end is good, all is good, and this sure is good! :Y:
:Y:
bump...
...Andy
Nice /bump Andy! :Y:
