Help in lowering the altitude of the route

makaron1970

New member
Hey.I need your help. I am looking for an experienced user of the TransDEM program who will lower the map by 120 meters. The map is a fragment of a larger route, and due to this hopeless difference in altitude, connecting the routes is impossible at the moment. I talked to Roland Ziegler about it, he said that it is technically possible, provided that the map is not created in T: ANE SP2 upwards, because after changing the format of the TransDEM map files, it does not convert them for some reason. Fortunately, the map is handcrafted probably in TRS2006 SP2 or TRSClassic, and I have the original CDP file for the map.Roland suggested that I write here on the forum, and in case of doubt for anyone willing to help me, he agrees.The only condition - you must have a TRS version lower than T: ANE SP2So who will help me with this project and lower the map height for me?:o

1.jpg



 
I had been asked first in this case and have suggested this request. The task on hand looks like a single invocation of TransDEM and I don't think there is a need to buy a license for this one usage. Raising/lowering a route is one of TransDEM's "icing on the cake" functions which unfortunately doesn't work with the more recent versions of Trainz. Of course, things may go wrong, as they almost always do, but it should be doable. TransDEM users have helped each other in the past in such situations and I do not consider help here as a breach of license terms.
 
Well i am terribly sorry that I was unable to read your mind and recommend something that you would be happy with (if that is at all possible). But these forums are read by many different people some of whom may have similar problems so while suggestions that are posted may not suit you, they could suit others.

Have a nice day:)
 
[QUOTE = pware; 1855823] Jeśli fizyczne obniżenie lub podniesienie odcinka trasy jest niepraktyczne, znajdziesz porady dotyczące innych rozwiązań pod adresem http://online.ts2009.com/mediaWiki/index.php/How_to_Merge_Routes [/ QUOTE ]

If the solutions recommended by the producers were satisfactory to me, I would not write a request on the forum. These solutions are a lame joke.

If you are asking people for help and you want somebody to do a fairly complex task for nothing, I'd be moderating the tone of your remarks, perhaps there is a language difficulty, but a response like the one you just made probably isn't going to endear you to other forum members, if its indicative of the way you treat people who offer you help, its more likely to put people off .
 
If you are asking people for help and you want somebody to do a fairly complex task for nothing, I'd be moderating the tone of your remarks, perhaps there is a language difficulty, but a response like the one you just made probably isn't going to endear you to other forum members, if its indicative of the way you treat people who offer you help, its more likely to put people off .

Sorry. Maybe it's true that the linguistic difference causes the intention to be misread (especially since I am writing with google translator). I had no bad intentions when I responded to @pware's comment, and I have no grudge against it, I should even thank you for your good intentions.
@Pware - I am so sorry, I never thought you would read my answer as malicious.:o

This manufacturer's solution is a lame joke, not the users who recommend it. I haven't played Trainz since yesterday, but I have been playing for 13 years and I know these methods inside out. The theme of changing the altitude of the route is repeated endlessly. I wanted to avoid rolling it over again and again, so I wrote a request for a specific solution to the problem. It seemed obvious to me that I don't need to mention that half-measures that do not bring the desired results do not interest me. That's why I wrote to Roland and that's why I wrote here to TransDem users.
 
I accept your apology and no harm has been done.

To correct one error in your posts. Most of the pages on the Trainz Wiki have been created by users, like you and I, and not by N3V. To be fair they are a very small operation and really do not have the staff to develop and maintain an extensive and highly informative Wiki. The suggested solutions in the link I provided were created by Trainz users based on their experiences in merging routes.

You, and all Trainz users, are more than welcome to add new pages and to update existing pages.

Regards
Peter
 
I have older Trainz installed and TransDEM, so I can try help.
Most likely not today, Friday, 29th of January, but maybe this evening or at least this weekend.
If all else fails.

Linda
at cripplecreekrailroads.com
 
Hey.I need your help. I am looking for an experienced user of the TransDEM program who will lower the map by 120 meters. The map is a fragment of a larger route, and due to this hopeless difference in altitude, connecting the routes is impossible at the moment. I talked to Roland Ziegler about it, he said that it is technically possible, provided that the map is not created in T: ANE SP2 upwards, because after changing the format of the TransDEM map files, it does not convert them for some reason. Fortunately, the map is handcrafted probably in TRS2006 SP2 or TRSClassic, and I have the original CDP file for the map.Roland suggested that I write here on the forum, and in case of doubt for anyone willing to help me, he agrees.The only condition - you must have a TRS version lower than T: ANE SP2So who will help me with this project and lower the map height for me?:o

You can edit the config.txt of the route section to the altitude you want. Follow link below and read the help at bottom of page. In your case you will uncheck the Auto Populate for Altitude. I'm pretty sure it will work in your case.

https://cdetrainz.com/tutorials_latitude_longitude_conversion.aspx
 
You can edit the config.txt of the route section to the altitude you want. Follow link below and read the help at bottom of page. In your case you will uncheck the Auto Populate for Altitude. I'm pretty sure it will work in your case.

https://cdetrainz.com/tutorials_latitude_longitude_conversion.aspx

Thank you, but I know this method. The configuration of the geographic location and height of the terrain is just a gadget in the game, it is apparent, it only affects the position of the sun and the imitation of chiaroscuro, and has absolutely no effect on the actual height of the grid. ;)
 
I accept your apology and no harm has been done.

To correct one error in your posts. Most of the pages on the Trainz Wiki have been created by users, like you and I, and not by N3V. To be fair they are a very small operation and really do not have the staff to develop and maintain an extensive and highly informative Wiki. The suggested solutions in the link I provided were created by Trainz users based on their experiences in merging routes.

You, and all Trainz users, are more than welcome to add new pages and to update existing pages.

Regards
Peter

Sorry, I didn't know that, I was convinced that this was an electronic production manual compiled from all versions of Trainz to the wiki. :o
 
I have older Trainz installed and TransDEM, so I can try help.
Most likely not today, Friday, 29th of January, but maybe this evening or at least this weekend.
If all else fails.

Linda
at cripplecreekrailroads.com

Thank you very much. I sent you a private message. :)
 
Thank you, but I know this method. The configuration of the geographic location and height of the terrain is just a gadget in the game, it is apparent, it only affects the position of the sun and the imitation of chiaroscuro, and has absolutely no effect on the actual height of the grid. ;)

It is not a gadget, the world-origin of each section merged are a real thing. You can not change the altitude of the world origin (x,y,z) with z being the altitude 'in game'. It must be done by editing the config.txt file. So your DEM piece must be saved as a route, edit the config.txt file, Then merge it into your other pieces. Your other 'pieces' may need to go through the same process.

Each merge section/route should have a section in the config.txt file like this;

Code:
world-origin
{
  latitude                              39,44.3541,1
  longitude                             104,59.415,1
  altitude                              1382.932617
}
My help page explains on how to find the 'True' world-origin of each route you will be merging;
https://cdetrainz.com/tutorials_latitude_longitude_conversion.aspx
 
It is not a gadget, the world-origin of each section merged are a real thing. You can not change the altitude of the world origin (x,y,z) with z being the altitude 'in game'. It must be done by editing the config.txt file. So your DEM piece must be saved as a route, edit the config.txt file, Then merge it into your other pieces. Your other 'pieces' may need to go through the same process.

Each merge section/route should have a section in the config.txt file like this;

Code:
world-origin
{
  latitude                              39,44.3541,1
  longitude                             104,59.415,1
  altitude                              1382.932617
}
My help page explains on how to find the 'True' world-origin of each route you will be merging;
https://cdetrainz.com/tutorials_latitude_longitude_conversion.aspx

Well, I don't really want to argue with you, just try to build two independent segments with different real heights yourself, and then connect them together on one ground level. If you fail, change this apparent height in config.txt and try to connect again. Come back afterwards and show off the result.


Nothing will teach you as well as your own experience
best regards :)
 
Nothing will teach you as well as your own experience

You are correct. I just tried it.

Route A (a single bare baseboard) - I raised the terrain height to 50m.
Route B (a single bare baseboard) - I left the terrain height at the default 0m.

I did a "control" test merge of the two routes without altering their config.txt files and the two baseboards had a height difference of 50m, as expected.

I edited the config.txt file of Route B to change its altitude setting to 50, as recommended in one of the above posts and performed the same merge test. The two baseboards still had a height difference of 50m.
 
You are correct. I just tried it.

Route A (a single bare baseboard) - I raised the terrain height to 50m.
Route B (a single bare baseboard) - I left the terrain height at the default 0m.

I did a "control" test merge of the two routes without altering their config.txt files and the two baseboards had a height difference of 50m, as expected.

I edited the config.txt file of Route B to change its altitude setting to 50, as recommended in one of the above posts and performed the same merge test. The two baseboards still had a height difference of 50m.

I am glad I could help you :p:hehe:


It really would be great if the game had an option to actually change the altitude of the terrain, because since the developers created the map merging feature, they should also have made the ability to adjust their height when merging, it seems logical, right?
Unfortunately, we all know Trainz is a big mess, and I still wonder why I love him so much. :)
 
Hi makaron1970,

I have changed the route with TransDEM and sent the files back as a zipped folder file.
I did however mess up 1 thing. :-|
I though adding leading zeros would create a new KUID, that did not work when I tested when I finally got my old TRS12 to respond again.
So, the zipped file I sent will overwrite the original route unless you enter the config file and replace the first 0's I added with a number of 1 (or any other but 0).
Other then that, the default opening location was reduced by 120 meter as wished for as when using the "Read Topology height" thingy it changed from 69 meters on the original map to -51 on the TransDEM worked map.

Hopefully all is working as it should in your end.

Best Regards

Linda Irene Tingvik
 
Hi makaron1970,

I have changed the route with TransDEM and sent the files back as a zipped folder file.
I did however mess up 1 thing. :-|
I though adding leading zeros would create a new KUID, that did not work when I tested when I finally got my old TRS12 to respond again.
So, the zipped file I sent will overwrite the original route unless you enter the config file and replace the first 0's I added with a number of 1 (or any other but 0).
Other then that, the default opening location was reduced by 120 meter as wished for as when using the "Read Topology height" thingy it changed from 69 meters on the original map to -51 on the TransDEM worked map.

Hopefully all is working as it should in your end.

Best Regards

Linda Irene Tingvik

Linda, you are great! :clap:
Thank you!:)
 
Back
Top