crash occuring during painting terrain

[gwgardner]

Having upgraded to 16 gig memory and an Nvidia 1060 card, I had hoped that my problem crashing during painting terrain would end. Alas, no.

I can cause a crash in just a few seconds when painting by pressing the left mouse button nine orten times quickly, while attempting delicate painting. It's a bad technique, I suppose. I need to remember to 1)save before painting; 2)SLOW DOWN.

In discussion about this in the past it seems there is no solution. Any new ideas on this?

[buzz456]

Yes if you look back here's what I do. First hit the F2 button often. That will make a save even if you then get a crash. Second there is a free program out there called Iobit Advanced System Care. It has a little app in it called performance monitor. It has a button that says clean cache. Get used to figuring out when it's about to hit 300megs and hit that button and you will almost never get a crash using these methods. As far as your fast finger...........

[Ericmopar]

The easiest way to deal with this problem, is to create an empty free roam with no engines, cars etc in it.
Then start that empty free roam scenario when you want to paint terrain, and go into the world editor from there.
I figured out some time ago, it has to do with whatever scenario the world editor goes into from the Build Tab and then how many rolling stock items are placed. The more rolling stock items, especially steam engines, the more likely a crash while painting terrain.
I think from something Bob said once, he had figured that out before me.
The more particle emitting assets, the worse the crashing gets for some reason.

Another way to do this, is to clone the route in question with no scenarios and do scenery development there. Then copy and paste the Scenery, Mixmap, Networks and Terrain folders to the actual working route periodically. Preferably more often than not so often.
This way the clone acts as a place to develop without endangering the original copy.

I periodically back up the clone and the working version of the route, in case of disaster.

[gwgardner]

Thanks to both.

[gwgardner]

Thanks to both. I'll give the suggestions a try.

[artimrj]

What helped me most was updating my NVidia drivers, but that was back with a 760. Then what I always do is create a blank free roam where I am working. Then run that and press control E to get to the editor. 16 gig of ram means nothing to RW. If you have 2 monitors hooked up or work in window mode you have your Task Manager up and look at the memory usage. When the ram usage starts getting close to 3 gig, time to save and shut down and restart. Going slower also helps. I also found if you stop painting for a w hile and place some objects, the ram will slowly get freed up to where you can paint again. It seems like painting does not clean up after it self.

[Bananarama]

+1 above.

For advanced users:

• If you happen to have an old copy of Rail Simulator (RS), copy the route folder with ONLY the following files and directories: Networks\tracks.bin and roads.bin + track and road folders, along with Terrain and MixMap. Do NOT copy the scenery or scenario folders, as these will likely contain items not supported in RS.
  
  
• Copy the Environment, RailNetwork, TemplateRoutes, TimeOfDay and Weather from the Assets folder in TS that the route uses.
  
  
• Open RS (it will automatically creates a freeroam scenario at the starting tile) and paint the ROW and anything else you like.
  
  
• Once complete, copy ONLY the MixMap folder back to you route's main folder, overwriting what's already there. Open TS and check your work. If adjustments are needs, either work from there or go back to RS to finish (don't forget to copy the contents of the RS MixMap folder back to your TS copy).
  
  
• If you run into problems opening the route in, create a blank route in RS using any other template, and simply copy the Assets/Networks and Environment folders over (the latter needed for the terrain textures), along with at least the mixmap and terrain folders, and copy to the blank route you created in RS. Note: instead of using track (which may or may not be supported in RS - ScaleRail is though), use the route markers used to create your TS route in RS. They will work just fine.

Have fun! You'll never run out of memory.

[gwgardner]

Thanks again. Just to clarify, by 'blank freeroam scenario' I think you mean one with no consists or drivable locos. Correct?

[buzz456]

Thanks again. Just to clarify, by 'blank freeroam scenario' I think you mean one with no consists or drivable locos. Correct?

Yes.