Notice to all visitors and members of the Train-Sim.Com message forums: If you plan on using a signature banner in your posts, we would like to remind you that there is a maximum size for banners. That maximum is 450 pixels wide by 120 pixels high, and not to exceed 25k. Your compliance is appreciated. FORUM RULES Problems? There are two common reasons for problems with logging in and posting messages. The first is that you are running a firewall that prevents your messages from being sent to the server. The other is that you have cookies disabled; the DCForum software requires cookies to work properly.
Fellow Train Simmers,This one has me scratching my head.You'll see in the first screenshot below that there's been a landslide across the tracks. "No problem", says I. "Just needs a bit of terrain adjustment in the Route Editor."Unfortunately, as you'll see in the second screenshot, it looks fine in the Route Editor (notice Error Bias is set at zero). Also looks fine in wireframe view (screenshot three).I tried readjusting the terrain in this area anyway, just in case -- but no joy.Saving in RE has no effect, nor does rebooting MSTS or the computer. Anyone ever encountered this type of thing before? Any suggestions? -JF-ps: This section of track was originally OK. But I don't know whether this problem just appeared for no reason or if I might have been adjusting the terrain there recently to get rid of floating track.
Even with ZERO bias it does this? Strange....My best suggestion is to widen the embankment to 16.0 and increase the cutting setting to 85.0. That should cut this back sufficiently. I've run into this problem and that seems to be the only way around it...JBD
Thanks, Jim -- that fixed it quickly and painlessly.I don't know enough about the subtleties of MSTS to understand how or why your fix worked, but I guess the main thing is that it did. Fortunately it was in an area of my route where changing the embankment width was no big deal. Other places, it would have been a major pain.For what it's worth, that was on a 500 metre track piece that crosses a blue tile boundary (although that lump of rogue terrain was nowhere near the boundary). Maybe that had something to do with the glitch?Thanks again. -JF-
That happens sometimes along tile boundaries, and it looks like that's the situation here. The best you can hope for is to hand adjust using the terrain edit mode rather than relying on the "Y" key and error mode at zero.When you first edit the terrain, it'll come out OK, as you noted. But as you work your way along and do more editing, it'll pop out of place again. I think the way I've addressed this particular problem is to save these guys for the very last step in the route, so that you don't do any further modification to the tile after adjusting the terrain. That means you'll have to live with it for a while, until you're ready to say you're finished with all the other steps. Just before doing any packaging of the route, go back in and adjust the terrain one more time. Even then, I don't know that you'll completely get rid of it when someone else loads the route and has to build the terrain buffers.Another fine bug from your friends at Kuju.Andy
Thanks, Andy. You posted your message just as I was writing the one above. It WAS near a tile boundary, as I mention in my replay to Jim Duncan.The tile it's on is now "finished", but the truth is that I'll likely tamper with it many more times and I'll keep an eye out for that lump to reappear. Call me crazy, but the fun I have in route building is in continuously tweaking to make it look more real. I'll never be completely satisfied, so the route will never really be finished. -JF-
>Call me crazy, but the fun I have in route building is in >continuously tweaking to make it look more real. I'll never be >completely satisfied, so the route will never really be finished.I know the feeling. They're never really finished, but it does get to the point where I've had enough! Andy
