NSW Great Northern Railway

I think the best solution is to edit both routes and create a copy under your own Id (Use save as: ) Keep the original routes as backup so if (or when) you stuff up you can start again.
Check in Content manager to see which is the largest route in Mbytes.
Open this route in Surveyor and use the Merge to select the other. You will probably have to have a couple of tests to see if any baseboards need to be deleted. The delete of baseboards can be done in either of the routes. If all works then save and edit the merged route to clean up and check.
WARNING: you need at least 32Gb of RAM for the Merge process to be successful.
I havnt tried this myself yet but probably will at some stage.
Good luck.
 
Hi Peter,

I just installed this into TANE SP4 and I have two missing assets. One is by Steve123 kuid2:208722:22459:1 and another by a bloke named pgibbons kuid:68830:40004 which appears to be a billboard. I looked on the DLS and steve123 only has one item uploaded and it is a different KUID. Maybe you can contact the pgibbons fellow and ask him to upload the billboard, please.

William

I just checked steve123 assets in my files and the missing asset is <kuid2:208722:22459:1> NSW Electrical Cable Trough

Roy
 
As far as I am ware, you still can't merge payware routes, even if you clone them. Cloning allows you to edit them, but not merge them (unfortunately).

I have a couple of payware routes that I really wish I could merge, but can't. It's also why I probably won't get any more payware via N3V.

Cheers,
Piere.
 
As far as I am ware, you still can't merge payware routes, even if you clone them. Cloning allows you to edit them, but not merge them (unfortunately).

I have a couple of payware routes that I really wish I could merge, but can't. It's also why I probably won't get any more payware via N3V.

Cheers,
Piere.

I feel the same way. It's too bad because there are some nice routes that would work really nice merged together, but that's now useless in this case.
 
I feel the same way. It's too bad because there are some nice routes that would work really nice merged together, but that's now useless in this case.

Hi John,

Is it not possible to make a personal copy/clone or the payware route, edit the config.txt to remove payware tags, allocate it a fresh kuid number using your own number, change the route name slightly, then import it as a content folder?
 
What you are discussing is a violation of the CoC. Please delete your post.

9. Giving, discussing, requesting, or linking to information that is either directly or indirectly related to obtaining pirated or unauthorized copyrighted materials, serial numbers, serial number generators and No-CD patches may result in an immediate ban.
 
Looks like my sign at Wallangarra was rather prophetic...
End-of-the-line.jpg

It seems that the line stops here unfortunately.
However I cant see the problem if you have paid for an item its yours for personal use only so no need for the lawyers to get involved..
I'll never make a route again which connects to any payware so they can all keep their $'s.
PG
 
But the funny thing Peter is that I never paid for the Warwick to Wallangarra route because it comes with an automatic free download with Tane & TRS19.Who ever composed that route,
why cannot they do a free version on the DLS because of that.
Robert2004-1
 
Hi John,

Is it not possible to make a personal copy/clone or the payware route, edit the config.txt to remove payware tags, allocate it a fresh kuid number using your own number, change the route name slightly, then import it as a content folder?
It won't work as the Payware route and dependencies reside in a separate folder to DLS and modified assets and cloning the folder will break the deps.
Graeme
 
What you are discussing is a violation of the CoC. Please delete your post.

9. Giving, discussing, requesting, or linking to information that is either directly or indirectly related to obtaining pirated or unauthorized copyrighted materials, serial numbers, serial number generators and No-CD patches may result in an immediate ban.


Er..........no.

You are assuming that the original payware route that we are discussing cloning has been illegally obtained by the user. This has never been suggested in this thread. We are discussing making an editable/mergeable copy of a route properly obtained and for personal use, not distribution to others.

Don't get jumpy there fella !
 
Er..........no.

You are assuming that the original payware route that we are discussing cloning has been illegally obtained by the user. This has never been suggested in this thread. We are discussing making an editable/mergeable copy of a route properly obtained and for personal use, not distribution to others.

Don't get jumpy there fella !

Yes exactly.

But, sadly it still doesn't work. I tried.
 
Stunner of a route!!!!!! I've driven two daylight passenger expresses hauled by a 48. The changes in gradients make it a challenge, as was the original prototype. The inclusion of Bald Blair station (Bald Blair Cattle station is owned by my mate Sam) is a great piece of whimsy. Your scenery work is great. I have a three missing assets but I'll clean them up as per your instructions. I also have seven faulty signals (Trainz 2019 Build 111951) Seems to be to do with failure on the signal and mesh - I don't design yet so I don't have a clue what it means. I can PM you with the errors if you like to take it off line.

Thanks once again for a a fantastic route.

Cheers
Steve
 
Steve
Thanks for the comments. I was surprised that the earthworks for some of the Guyra/Dorrigo connection were still visible in Google Earth they only got as far as Bald Blair before the works were canned in 1930's due to the world wide depression.
I believe the signal errors may be due to the script or mesh files specific to TS2019, do a 'list asset versions' in Content Manager and get the latest updates which should work.
Hope this works.
PG
 
Peter,
I've just uploaded your TANE route and mate, you've captured it beautifully - I was drawn into every curve and cutting to find new things to see at each turn.

Your overall detailing is superb and I have to say, the planting of Red Gum in just the right places, must have taken you months to complete. I picked up a few tips on the journey.

Fantastic work and something to be proud of.

Cheers mate,
Roy
 
They built the easy part :). When you consider the terrain they would have needed to go through to get to Dorrigo it would have been an engineering marvel. And then the idea was to extend the line from Guyra to inverell once that was done! Guyra would have been quite a busy place. The cut and fill is all quite visible on the ground but I don't believe they built bridges - at least I haven't seen the remnants when I've walked the route. They got to Shanahans Road and from there I can't find any remnants.

The signals that are bothersome are:

<kuid2:209857:71117:1> NSW SL | 2a 2r T | LH
<kuid2:209857:71106:1> NSW SL | 2a Auto | LH
<kuid2:209857:71107:1> NSW SL | 2a Auto | RH
<kuid2:209857:71109:1> NSW SL | 2a Dist | LH
<kuid2:209857:71103:1> NSW SL | 2a | LH
<kuid2:209857:71104:1> NSW SL | 2a | RH
<kuid2:209857:71136:1> NSW SL | 3a 2r | LH

When I do "List Asset Versions" I get
<kuid2:209857:71117:1> NSW SL | 2a 2r T | LH
<kuid:209857:71117> <Unknown Asset>

which I take it means there is only one asset. Same for all of the above, with different kuid's


The error messages are as follows (same type for each signal)

; <kuid2:209857:71117:1> : Validating <kuid2:209857:71117:1>
- <kuid2:209857:71117:1> : VE18: Attachment point 'a.name0' referenced by tag 'att' in 'mesh-table/target/effects/name' was not found.
- <kuid2:209857:71117:1> : VE132: The attachment point 'a.name0' must belong to the parent mesh of the effect (mesh=model/target.trainzmesh).
- <kuid2:209857:71117:1> : VE18: Attachment point 'a.light4' referenced by tag 'att' in 'mesh-table/target/effects/s1' was not found.
- <kuid2:209857:71117:1> : VE132: The attachment point 'a.light4' must belong to the parent mesh of the effect (mesh=model/target.trainzmesh).
- <kuid2:209857:71117:1> : VE18: Attachment point 'a.light5' referenced by tag 'att' in 'mesh-table/target/effects/s2' was not found.
- <kuid2:209857:71117:1> : VE132: The attachment point 'a.light5' must belong to the parent mesh of the effect (mesh=model/target.trainzmesh).
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'bracket0-lod0' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'bracket0-lod1' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'bracket0-lod2' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'bracket1-lod0' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'bracket1-lod1' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'bracket1-lod2' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'bracket2-lod0' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'bracket2-lod1' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'bracket2-lod2' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'bracket3-lod0' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'bracket3-lod1' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'bracket3-lod2' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'head0-lod0' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'head0-lod1' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'head0-lod2' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'head1-lod0' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'head1-lod1' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'head1-lod2' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'head2-lod0' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'head2-lod1' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'head2-lod2' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'head3-lod0' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'head3-lod1' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'head3-lod2' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'screen-overlay3-lod0' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'headback0-o' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'headback0-s' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'headback0-r' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'name0-lod0' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'name0-lod1' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'name0-lod2' must be found in mesh 'model/target.trainzmesh'.

Beats Me!!!! :)

Cheers
Steve
 
Steve.
IN Content Manager select one of the signals listed above and do a 'shuw dependancies'
This display should show an asset something like 'signal library' or 'mesh library'
Then select this asset aand do a list asset versions.
This will show various versions either on the DLS or installed on your machine. Make sure you have the latest version of the library/mesh installed .
I know from posts on the forum relating to Ranger_51 signals there have been issues so may be worth checking the forum as well.
Hope this helps.
PG
 
Just finished my first drive along this route, well done PG. The gradient changes are very noticeable and make driving a route much more realistic, so it is definitely worth the time required to do this. There is no such thing as a truly flat railway and this route feels right. The scenery is quite representative of the area too.

A good result ! Thanks for sharing it.

A71
 
I have the same issue as sjcampbell. All of the assets and dependencies and mesh files show as the latest version. I did not see anything mentioned on Rangers thread in the Freeware forum, they are dealing more with positioning and actions. I will just run it under "Create Session" and not worry about existing sessions or AI. If I have trouble I can maybe delete the faulties and see if I can run it with manual switching. Sounds like this is another SP3, where they seem to fix some stuff and break others.
 
It's a very nicely done route. I digress though. I converted to a North American route and changed the location to south-central Texas. NSW and Texas look a lot alike. On a storm-chase down to Eagle Pass, located on the Mexican border, the road passed through an area that looks much like the Blue Mountains. The differences being the thickness and kind of foliage. TX has mostly oak trees, creosote, and some acacia, while NSW has palms, acacias and eucalyptus among other plants. When I saw this route, I had to do the conversion, but of course I kept the original as well so I can run trains in NSW as well.
 
They built the easy part :). When you consider the terrain they would have needed to go through to get to Dorrigo it would have been an engineering marvel. And then the idea was to extend the line from Guyra to inverell once that was done! Guyra would have been quite a busy place. The cut and fill is all quite visible on the ground but I don't believe they built bridges - at least I haven't seen the remnants when I've walked the route. They got to Shanahans Road and from there I can't find any remnants.

The signals that are bothersome are:

<kuid2:209857:71117:1> NSW SL | 2a 2r T | LH
<kuid2:209857:71106:1> NSW SL | 2a Auto | LH
<kuid2:209857:71107:1> NSW SL | 2a Auto | RH
<kuid2:209857:71109:1> NSW SL | 2a Dist | LH
<kuid2:209857:71103:1> NSW SL | 2a | LH
<kuid2:209857:71104:1> NSW SL | 2a | RH
<kuid2:209857:71136:1> NSW SL | 3a 2r | LH

When I do "List Asset Versions" I get
<kuid2:209857:71117:1> NSW SL | 2a 2r T | LH
<kuid:209857:71117> <Unknown Asset>

which I take it means there is only one asset. Same for all of the above, with different kuid's


The error messages are as follows (same type for each signal)

; <kuid2:209857:71117:1> : Validating <kuid2:209857:71117:1>
- <kuid2:209857:71117:1> : VE18: Attachment point 'a.name0' referenced by tag 'att' in 'mesh-table/target/effects/name' was not found.
- <kuid2:209857:71117:1> : VE132: The attachment point 'a.name0' must belong to the parent mesh of the effect (mesh=model/target.trainzmesh).
- <kuid2:209857:71117:1> : VE18: Attachment point 'a.light4' referenced by tag 'att' in 'mesh-table/target/effects/s1' was not found.
- <kuid2:209857:71117:1> : VE132: The attachment point 'a.light4' must belong to the parent mesh of the effect (mesh=model/target.trainzmesh).
- <kuid2:209857:71117:1> : VE18: Attachment point 'a.light5' referenced by tag 'att' in 'mesh-table/target/effects/s2' was not found.
- <kuid2:209857:71117:1> : VE132: The attachment point 'a.light5' must belong to the parent mesh of the effect (mesh=model/target.trainzmesh).
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'bracket0-lod0' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'bracket0-lod1' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'bracket0-lod2' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'bracket1-lod0' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'bracket1-lod1' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'bracket1-lod2' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'bracket2-lod0' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'bracket2-lod1' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'bracket2-lod2' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'bracket3-lod0' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'bracket3-lod1' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'bracket3-lod2' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'head0-lod0' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'head0-lod1' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'head0-lod2' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'head1-lod0' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'head1-lod1' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'head1-lod2' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'head2-lod0' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'head2-lod1' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'head2-lod2' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'head3-lod0' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'head3-lod1' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'head3-lod2' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'screen-overlay3-lod0' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'headback0-o' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'headback0-s' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'headback0-r' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'name0-lod0' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'name0-lod1' must be found in mesh 'model/target.trainzmesh'.
- <kuid2:209857:71117:1> : VE15: Attachment point 'att' in 'name0-lod2' must be found in mesh 'model/target.trainzmesh'.

Beats Me!!!! :)

Cheers
Steve


I have the same effed up signals as you do.

Both the mesh and script libs are up to date.

DBR does nothing.

There are way too many threads about Rangers Signals, and way too many posts about script issues and effed up functionality.
Not going to mull through all those to find an answer. Meh. :p


Rico
 
Last edited:
Back
Top