The second I go onto the scenario editor, BOOM! The whole game just crashes, I get "Failed to create vertex buffer" "DBGHELP.DLL not found" and "OUT OF MEMORY" as soon as I get into the scenario editor everytime. It happens constantly and it's annoying because I have spent 2 hours on my scenario and it is nowhere near finished!
Crashes happen, there's lots of threads about it. Only thing I can say when using the editor, press F2 to save your work often. The vertex buffer thing... Do you use Fullscreen? If yes then try switching to Borderless Window.
To Fix a Vertex Buffer Error see the DTG support articles for an explanation. Usually an error between the CPU and gpu buffers – many causes. The following are hacks/fixes: · Close TS20XX · Run a Command prompt (cmd.exe) as administrator · Type · disable vertex buffer objects=1 · close · run TS20XX Plus · Using the command line launch options in TS - · -force -d3d9 · and/or try · -nomemorybias · -dxlevel 90 Geek Notes: Simply, Vertex buffers are used to optimise or share processing by both the CPU and the GPU. Vertex Buffers provide us with a mechanism of being able to load vertex buffer data into the CPU (and RAM), while at the same time allowing the GPU to process an earlier batch of vertex data. This gives us a good image at reasonable frame rates. The problem can arise if the gpu bottlenecks the CPU or vice versa, and then you get the error 'failed to map the vertex buffer . . . '. It can be caused by quite a few things including too high settings in the game, driver issue, weak CPU and strong gpu and vice versa, corrupt file(s), faulty gpu (maybe), not enough RAM, not enough VRAM and of course other hardware/software issues.
I had a memory dump on a scenario I did, busy AI etc, was working fine until I wanted to carry on the next day only to find I d could no longer do anything, it would crash out all the time! I even did the trick of hiding all the scenery (changing folder names temporarily) which has worked if scenery is and mass amount of AI is causing the issue but it still crashed out within 5 seconds of clicking Edit to get into the editor. Then I'd go in to another scenario, and try loading from the scenario icon but would crash again. In the end I went into RW Tools and manually removed probably about 10 - 15 AI services, something like that, saved it and went back in to try, guess what it loaded fine and I got into the editor! Annoying that I had to reinstate manually the 10 - 15 services I deleted, but oddly enough I restored* them all and managed to add more * - now I say that BUT I did alter one as I wasn't quite sure if the AI dispatcher would be giving the priority to the service that I wanted it to do, since altering it I had no problems, deleting a batch of trains meant I wasn't sure if any of them was actually causing a problem, I was more thinking of removing trains to see if that would actually help in anyway, and it did. That may not be your case specifically but maybe its worth a try?
