You need to add your google maps key on the end, or remove "&key=" part.Marcdk wrote:1: For the Google map textures. I read in this thread that it can take some time to load, but in your experience how long is "long"? Cause I tried loading both Raster Images Z17 and Z18 (not quite sure what the difference is) But when I do so, I just get a "Wait..." message that sits there forever.
In the settings file, I have said: imageMapsUrl = http://maps.googleapis.com/maps/api/sta ... &size={res }x{res}&maptype=satellite&key=, which as far as I know is correct?
You propably tried to edit route that is not compatible with your current tsection.dat. I know Protrain uses old tsection.dat.Marcdk wrote:2: Do you have any advice on how to approach editing of existing routes. I tried testing on routes that were not too heavy on Xtracks, such as the Protrain routes, just to mess around. I got some very interesting errors.
One one route, the editor would simply crash if I used the "X" key to position a track. I could lay as much track as I wanted to, but as soon as wanted a curve to point left instead of right, the editor would crash upon hitting "place new" after adjusting with the X key. Then I tried an experiment. I added two 100m tracks, and then added a curve-track. Then I deleted the 100m track that connected the rest of the track network with the other 100m track. So now I had a seperate 100m track attached to a curved track. Tried the X key, and I could adjust it left and right with no crashes. Then after doing so, I tried adding the deleted 100m track back, to connect the tracks again, and BAM, crash again. Have no idea what could be causing this problem.
3: Another issue I had with a route was that as soon as I deleted the buffer tracks in order to make a route longer, most of the platform markers dissapeared from EVERY station on the route, AND the entire track database was completely broken when inspecting it in MSTS. I have no clue why deleting a buffer would mess up the entire database and delete interactive objects, but perhaps there is a no-no rule that I overlooked?
You need to convert your route to your tsection.dat. TSRE can't do it now. You need to use Horace or something.
