NSW – The Tweed Railway, Byron Bay to Murwillumbah and Condong.

[PGibbons]

Strange Merge happenings

Ive also seen some strange issues in routes following the merge function as described above. Godfrey I gat a similar trench at the merge of the Ballina branch. Its strange because the Kyogle end loop baseboard was added in TRS2006 as was the one at the Grafton end.

Fortunately most problems can be repaired without too much work.

1. In Trs2006 there are two problems Still happening , these have been around for ages.
a) The 'AJS station' assets in the incoming route disconnect from the track.
b) At the eastern and southern edges of every baseboard join in the incoming route the elevation is set to zero causing a 'V' in the ground along the map edges.
2. TRS2010 seems to have some similar merge issues perhaps with the way 'layers' have come into the system. As the merge process was not completely operational in the first builds of '10' maybe there are still some lingering issues. I can only suggest that '10' users check everything carefully and keep plenty of backups.

All I can suggest is that all track be checked after a merge, if you do a test run in Driver from end to end and it wont work, then some track is disconnected somewhere.

Its a shame that these annoying bugs persist when you merge routes but from a builders perspective building a large route in sections, I think, is a more productive way of doing things.

Hopefully the bugs do not distract people from enjoying the routes. I'll try to identify any issues and eliminate them if possible in future routes.

Peter.

 

[PGibbons]

More Information on Merging in TRS2010

After some more experimentation Ive found a way to merge routes in TRS2010 which seems to eliminate all of the problems raised earlier. Perhaps some people have been doing this already but it doenst seem to be documented anywhere. Only the dummies like me who havnt really moved into TRS2010 fully yet don’t know this.

1. Import or Download the routes into TRS2010
2. Open the Layers tab in Surveyor and rename the Route layer from ‘route-layer’ which appears to be the default to some unique name eg merge1
3. Save the route under a new name.
4. Repeat 2 & 3 for each route you intend to merge. This will produce new routes with unique route layer names (merge1, merge2, merge3 etc)
5. Open the first route and begin the merge process, save under a temporary name after each merge. This eliminates the step where you get the duplicate 'route name' issue in the merge.
6. After all routes are merged you can then go into the layers tab and you will see all of the route layers listed. You can use the Merge Layers function (the funny little arrow button at the bottom of the Layers Tab) to merge the layers into a single layer again. You can then rename it to whatever you want.
7. You can clean up the track connections etc and whatever else after each merge and save or right at the end.

As I havnt seen much documentation on layers or how they interact with merging the point is to make sure any routes to be merged in TRS2010 have unique route layer names first.
I can continue to build in TRS2006 knowing that the routes will easily convert into '10'
Hope this helps and makes sense.

Peter

 

[harpman]

As a total noobie, I tried a variety of ways to merge these four routes in 2010. I simply don't understand the route merge I guess. When I try to merge the first two routes, it won't let me because the route layers have the same name. So I changed one of the route layer names and merge them together...say route layer into route layer 1. Exit Surveyor, try to go into Driver and look at the map to see if the route has expanded or grown...NOT!

What is the correct sequence to merge these routes. Which route should one start with. Do you rename the route after each merge? A step by step walkthrough would help OR....is it possible to post the .cdp of the entire merged route?

I'm a bit frustrated, but it's noobie frustration due to the steep learning curve. Any help would be most appreciated.

Bill

 

[PGibbons]

Merge disgrams

Bill
You are on the right track -so to speak...
Read the post above about renaming the route layers.
Save each as a new route name each time after you merge then open that route and do the next merge. Delete all the unwanted routes after you check the final one for accuracy.

There is a post earlier in this forum (on page 2 now) with some maps about how the 4 Tweed routes fit together.

good luck
PG

 

[mattm]

Pete,

DL'd the final installment of the Tweed Railway, and had a quick look at the end product. Nice work, very well done. Haven't yet run a train down the entire length of the line, but i shall be doing that, as soon as i get some loco's and rollingstock moved into the district:hehe:

Looking forward to the next planned extension to Kyogle, if and when this eventuates.

Cheers,

Matt.

 

[Puffingbilly]

Hi Peter,

Have so far managed to merge the 4 routes into one and the only minor hiccup to date is that quite a few of Rail-built cattle grids need to be adjusted plus a couple of the placed horn sound & whistle indicators but not a major drama .

None of the industries or rail xings show any signs of 'dislodgement' or miss-alignment and I have run one train from Casino to Lismore without any problems picking up and off loading passengers (session ended abruptly due to drive error .

Hope to run the entire route tonight.

Cheers

Ron

 

[iure]

@PGibbons or others in the know,I dl'd and installed the route to 2006(latest u'date) and the route is listed and shows in surveyor but upon opening the route I get the black screen with message "no map selected.....".Does anyone know the solution to this?I have noticed that in the config file that the trainz vers n. is 2.7 whereas the others are 2.6.Is this maybe the prob?
thanks in anticipation

 

[PGibbons]

TRS2010 happenings

Ive noticed a couple of things in build 44088 after merging routes which I cant recall happening in 43434.

1. As mentioned above some of the Cattle grids have moved
2. Some of the bridge abutments have moved and some have been rotated.
3. Some of the Tunnel numbers have also moved.
4. Some sound Horn triggers also moved.
As these are all items connected to the track perhaps there is still some underlying bug in build 44088.

Ive checked other track items such as Stations and X-ings and these all seem to be OK, I also havnt noticed yet if any signals are effected but I'll check.

Another issue is that the Auto-pilot signal distance seems to have been reset. This is evident is you attempt to run a train between Mullimbimby and the Dunbible loop track. Ai issues a 'track unsignalled' error. This section is about 30Km and is too far for the AI engine to 'see' the next signal. I ran this route in TRS2006 without any issues so this is another annoying bug. The solution to this is to install a passing loop somewhere - I suggest at Mooball.

Also, I'm not aware of any issues with version numbers in TRS2006.

Its disappointing that these little bugs continue to appear and seem to be different in the various builds of the system. Perhaps the implementation of 'layers' is pushing the software limits, and I really cant see a valid reason for having them anyway. (end of rant)

I hope these bugs dont detract people too much from enjoying the routes.

PG

 

[Puffingbilly]

Ive noticed a couple of things in build 44088 after merging routes which I cant recall happening in 43434.

1. As mentioned above some of the Cattle grids have moved
2. Some of the bridge abutments have moved and some have been rotated.
3. Some of the Tunnel numbers have also moved.
4. Some sound Horn triggers also moved.
As these are all items connected to the track perhaps there is still some underlying bug in build 44088.

Ive checked other track items such as Stations and X-ings and these all seem to be OK, I also havnt noticed yet if any signals are effected but I'll check.

Another issue is that the Auto-pilot signal distance seems to have been reset. This is evident is you attempt to run a train between Mullimbimby and the Dunbible loop track. Ai issues a 'track unsignalled' error. This section is about 30Km and is too far for the AI engine to 'see' the next signal. I ran this route in TRS2006 without any issues so this is another annoying bug. The solution to this is to install a passing loop somewhere - I suggest at Mooball.

Also, I'm not aware of any issues with version numbers in TRS2006.

Its disappointing that these little bugs continue to appear and seem to be different in the various builds of the system. Perhaps the implementation of 'layers' is pushing the software limits, and I really cant see a valid reason for having them anyway. (end of rant)

I hope these bugs dont detract people too much from enjoying the routes.

PG

Hi Peter,

I have now run the entire merged route (including the Ballina section) about 180 KMs in all and all interactive stations work and no issues with disconnected track/xings.

As you have indicated there are a couple of minor issues with the 'track unsignalled' error as there is one between Booyong Junction and Byron Bay (can't recall the exact one) signal stays red and when you hover your mouse over the signal you get the 'unsignalled' error.

All other issues noted so far are just cosmetic :hehe:

Oh, I love the little 'PG' in map view to!


Cheers

Ron

 

[big_b]

I have had this problem in TS2010 on routes made in ts2006 & had the same thing occur whether the route was merged in 2006 & imported or merged in 2010.

The effected track could not be deleted or replaced when this happened it was as if Ts2010 didn't know it was there.This also affected some bridges & the track attached to them back to the closest spline point.

My work around was to remove the bridge & place track ends or replace the bridges with another bridge prior to merging & as for the track as in your pick to break the track & put tracks ends on them which will hold them in place then after the merge remove them & rejoin the track.

dave

 

[seeseeme]

Ive noticed a couple of things in build 44088 after merging routes which I cant recall happening in 43434.

1. As mentioned above some of the Cattle grids have moved
2. Some of the bridge abutments have moved and some have been rotated.
3. Some of the Tunnel numbers have also moved.
4. Some sound Horn triggers also moved.
As these are all items connected to the track perhaps there is still some underlying bug in build 44088.

{SNIP}

I hope these bugs dont detract people too much from enjoying the routes.

PG

I had these sorts of issues when I merged the Southline suite of routes and that was before SP3.

These are only minor issues and certainly do not change my mind about the quality of the routes and work put into them.

I agree about the layers as well Peter, I can do without them and can not see a reason why I would use them.

Craig

 

[harpman]

I managed a good merge of the 4 routes, began at Casino and drove as far as Byron Bay, took the Byron Bay North and encountered a problem just prior to a bridge trestle. There was a track stop or bumper on the track, on the other side of the trestle was a length of track missing. So I could not proceed to Murwillumbah.

What's the fix for this?

Bill

 

[NormP]

Bill.
Just grab the end of track (Mulumbimby side)and drag it to connect to the short track of the trestle bridge ,you may/maynot need to realign tracks ?

Norm.

 

[harpman]

Thank you! That fix worked well and I'm able to drive through that area now. Well, I've placed several engined consists around the route and several consists of loose freight cars. Time to go explore the entire route. This time out, I'm starting at Murwillumbah.

I already know to take it slow through that area surrounding St. Helena. It is windy and an engine will pick up speed in a hurry through there!

This is a great route, very well done. Tip o' the hat to the author of this route!

Bill

 

[iure]

I had no problems whatsoever in merging the various routes in 2010 ver.43434 (as i don't have the latest patch installed nor will I probably do so) but I still cannot launch the latest extension Byron Bay to Murwillumbah in surveyor of 2006 , I always get the "no map selected" error.I've tried launching it on another install of 2006 on a different computer but the result is the same.Can anyone help me out please?

 

[PGibbons]

Unusual problem.

Lure.
Ive not heard of similar problems with the routes and can only suggest that you just use the routes in TRS2010 as it has all worked there.

The route was built in TRS2006 2.6 build 3092 and even though the route config file has been changed to version 2.7 as the DLS apparently no longer accepts 2.6 and this still works on my system.
However the error message 'no map ...' seems to indicate that your '06' cannot read the file for some reason.
I'll do some more checking on this.

Peter

 

[iure]

Thanks Pete, AND for the marvellous routes you spend so much time in creating/re-creating.I have had occurances of the "no map selected" with other layouts(not yours) and these were for TC or higher.I'd like to utilise the route in '06 cause I can't get most of the NSWGR steam locos to install in 2010, but maybe there's a fix for this too?

Much appreciated

 

[Dougea]

I also get the "No map......" error with 2006 build 3335 with the BB2M map. Edited.


Doug.

 

[godfrey]

Post deleted

 

[Petan]

NSW – The Tweed Railway, Byron Bay to Murwillumbah and Condong

The Crabbes Creek loop where the narrow gauge sugar line interchanged with the NSWGR can be found on Google Earth using the plug in available from Railpage.
http://www.railpage.com.au/f-t11349045.htm

Check the green narrow gauge line south of Mooball for the line location. Crabbes Creek station is marked on this GoogleEarth plugin. It is this traffic that used the extension from Murwillumbah to the Condong mill.

The locations of narrow gauge mill lines at the Condong mill itself are also shown via this Google Earth plugin from Railpage.