Problem with the Paint part of scenery

[railduffer]

I have a new computer running with Windows 10 with an upgraded (expensive) NVidia graphics card.
Now when performing a PAINT of Rock over grass on the route I am building, I get a computer crash after entering just a small area. I have tried all of the graphic settings. Is it the program or the computer? Everything worked fine on my old Windows 7 computer.
Scenarios, track work and buildings work fine.
Does anyone have an idea of what is wrong?

Thanks for any help.

[cbff33]

After the last little update that railworks did, I am also getting horrendous amounts of crashes trying to paint terrain. Even turning down the detail to one, buys me about an extra 45 seconds of painting. I fired up my performance screen, and it appears railworks and terrain painting is causing a pretty good memory leak that will shut down railworks in less than a minute. Everything else is just fine, but terrain painting has become unstable in this last week.

[buzz456]

You guys have something else going on. Was was painting for quite a while today with no issues. I do hit the F2 key every few minutes but I've been doing that forever.

[cbff33]

I have noticed that if I zoom in close to the terrain, and paint with a narrow brush, the memory dump is horrific. If I zoom out, and use a wider brush, it's not as severe. Coming from MSTS I know the importance of saving work about every 5 seconds. Now I just keep an eye on the resources monitor, and when I see the memory usage building to high, I hit the yellow arrow on the bottom right, exiting the editor, and immediatly reenter the editor, and was able to have a nice long painting session. I would suggest windowed mode, and positioning it to where you can see your your resource monitor next to it. It helps to reduce the crashing if you do as I state above.

[buzz456]

If you hit the F2 key it never crashes and the work is saved.

[cbff33]

If you hit the F2 key it never crashes and the work is saved.

As I stated above, having worked with MSTS since it's release, I know the importance of saving every 5 seconds. Hence I am hitting the f2 key often. The crash occurs with our without the f2, and also, as clearly stated above, I narrowed down the cause of the repeated crashes, at least in my case, to be caused by a memory leak, that occurs if I am zoomed into the terrain too closely, whilst using a very narrow brush setting, such as 15 or less. So in this case, your statement that if I use f2, the editor will never crash, is wrong. No two computers will behave the same, and I am sure, our computers are very different.

[buzz456]

I have 16 g of ram i5 cpu and am running with a 500gb SSD. I repeat what I said on my rig. I certainly didn't mean that if you are running a inadequate laptop or some inexpensive off the shelf desktop that you would would never have a problem. Sorry if I wasn't clear.

[cbff33]

No biggie. I am finding a wider brush doesn't have as many issues with the white bleedthrough on the ground texturing. So now that I'm not using a narrow brush, the issue is not nearly as bad as it was.