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.
Well here's the story.......I was working on the Chama area Monday night (since better scenery objects have been released); I saved it, and it locked up. I restarted it and every object on the tile was deleted. No biggie, I pulled up a backup tile for Chama. Now it won't even let me on that tile! I can get to the Chama River Bridge but then it locks up! Then I try runnig a train starting in Chama, and a Fatal Error ocurrs. The system shuts down. Can someone help me? I can't release the route if it's INFECTED. That's Why if the help I need isn't granted, Cumbres Pass Version 3 will be CANCELED DRGW489
RE: C&TS V3, is troubled: Maybe................CANCELED
LAST EDITED ON Nov-10-04 AT 06:59 PM (EST)
Hi DRGW489> I saved it, and it locked up. I restarted it and every object on the tile was deleted.That's a well known one: Sounds like RE was out of memory. That happens when .w file size becomes to big; RE crashes when it attempts to write the updated .w file. If you still have it, return to the ~w.bk file of the tile in question which RE wrote immediately prior to the crash, because that will be the file the .rdb and .tdb still are in synch with. As Robert Reedy loves to say, the "mileage may vary" for each individual user when it comes to the question at which point the RE runs out of memory on your system. Commonly, a file size of over 500KB for a .w file, or in excess of 1000 objects on a world tile (.w-file) is the line from which problems can start to surface. Depending on the size of the neighboring tiles, the .tdb and .rdb files etc. problems may also occur later. Search this forum for the phenomenon of the RE being out of memory, there are a couple of posts actually.As suggested above, the immediate cure is to delete the corrupt .w file (which you will notice is just 1KB as contains nothing but an unicode header, thus it will be useless anyway), and rename the ~w.bk to .w before continuing to work on your route in the RE anywhere else.If you stay out of synch when even after reverting to the ~w.bk file, and you had no interactive objects installed on your route yet, your chances are pretty intact to run a .tdb rebuilt in order to get back in synch.Otherwise the only option left is to go back to your last full and healthy back-up of the route (I assume you regularily back-up the entire folder to somewhere safe like a .zip file, a CD, a memory stick, whatever), and to re-do everything you had added since.Keep an eye on these large .w files, and watch your object count (RouteRiter can check for you how many shapes each .w file has)Lukas a.k.a Swissie
RE: C&TS V3, is troubled: Maybe................CANCELED
Lukas has it covered on this in my opinion, but I do have a suggestion for future, to save a lot of headaches. I may be preaching to the choir here, but maybe someone new to the RE may catch it and be saved from a lot of headaches.This has been said many different times in many different ways, but Route-Riter has left us with no excuses not to do a clean backup before we start on a new or difficult session - which in my way of thinking is simply opening the RE. As Kip was fond of saying .. it will bite you on the behind the first chance it gets.All it takes is about 1 minute and a couple hundred megs of hard-drive (which can be drastically reduced by both culling out the backups and extra superfluous files and zipping) and you have a good reliable backup for when you will need it. I think I've already told it on here somewhere, but had something very similar happen to me a couple of weeks ago and in one false save would probably have lost the entire thing, or taken weeks to regain even close to where I was. The problem with bringing in an old tile is the 'out of synch' syndrome as Lukas said above. By doing a RR backup (or any type of full backup of crucial files), you can bring the entire set back as a unit and MSTS doesn't even realize it has been fooled.Hang in there, though .. you can get it back one way or another.RobertR .. ADF-M&RM at http://www.adfrr.com
