Does anyone know what definitely causes them and how to fix them consistently? A few of my routes including the Chatham Main Line crash when loading in Quick Drive regardless of train, always spouting a vertex buffer error. I also see lots of questions about them popping up on here and on the ATS Facebook group. Whenever I see them, the answers are quite inconsistent and mean don't seem to work for the people who are affected. I would assume the way to fix them in most cases is by uninstalling the broken route(s) and reinstalling it, but I have no idea if that would fix the issue for everyone and it wouldn't explain what actually causes the issue. As it isn't an out of memory error (in fact the game only closes once the error pop-up is closed) there is no cause given for the error, and I don't really know how to get LogMate working so I don't have much to work with. The vertex buffer name at face value would seem to be a lead, but like the out of memory errors that don't really have anything to do with RAM it may be a red herring. If I can get LogMate to work I'll try to get some data to work with, but I have a feeling it won't come up with any useful information.
Atm only one solution. Run the game in Borderless, not Fullscreen. As Steve Dark pointed out in the Beta thread, they haven't found a definite solution in the code yet - it might be related to one of the plugins, not the core code itself. Borderless runs fine.
I´ve been running borderless for years... whats the problem with it? I never noticed a difference to full screen.
And I also spend a lot of time in TS and get the crashes consistently on a couple of routes, so that establishes that borderless mode is neither the cause nor the fix of the issue.
Stable (v75.8a) or Beta (v76.3c)? DX12 or DX9? I am only aware of crashes in the beta dispatcher module (and I think I know why). Vertex buffers crashes have only been reported for Fullscreen so far, so I am surprised it crashes for you and it might have other reasons found in your PC setup. I'd advise you to revert to 75.8a by opting out of the Beta in Steam, as the beta is currently not fully backward content compatible. (ultra strict on correct route building, trackrules and asset blueprints - it now uncovers a lot of content flaws).
Can't adjust brightness in game and it's really dark. This isn't really the point though is it. It has a full screen option, and it crashes. Either fix it, or just remove it as an option, because an option you can't use reliably may as well not be an option.
We as players cannot fix it, we can only tell you what works. When I play in Borderless or Windowed, it is not dark actually.
Other people use Borderless without a problem DTG should remove it because it causes some problems for some people? A bit unfair on those people.
DTG won't remove Borderless. It's become pretty much a standard option for many newer games, as it has a lot of advantages.
I was referring to @Pookeyheads comment about screen settings I thought he has a problem with Borderless?
If it is too dark then there is something else interfering with your brightness. Check your driver settings. This is out of the box TSC, it's even a tad brighter in Windowed/Borderless than Fullscreen (depending on your gfx driver settings, mine are unchanged). (Default Ambient/Contrast/Sunlight). Borderless runs absolutely flawlessly. Don't get me wrong, I'm not saying anyone is making things up, it's just I heard of no one else having a) Vertex buffer crash in Borderless, because simply put: Windows handles the buffer storage when another app is on top, which is left to the game to do correctly when in Fullscreen, or b) Too dark display in Windowed modes. There is something else at play on your system I presume. The only thing DTG stated is that it's not an issue with the core code. So it might be related to third party plugins used. They're working on it.
No... I was saying if full screen is broken, and the only fix available is using borderless, what's the point of full screen?
Everything is hardware calibrated at the monitor's LUT level. There is no software adjusting my brightness or gamma.
I use and need it. On my config, I can only force FPS limit in full screen, doesn't work in borderless. Of course there are many games capable of V-Sync in borderless, so I would settle for that. In fact, it would be ideal also for me.
What strange config are you running TSC on? Limiting FPS through your GFX driver is not tied to the rendering mode, it doesn't matter if Fullscreen, Windowed or Borderless... Set MaxFPS to you refresh rate (or 1 frame below) and you got your VSync.
Slight aside on this - what version is the beta? I have 76.3a (std DX9) - is there a later version or was the 76.3c just a typo? I'm online and have cleared all pending downloads on Steam.
Latest Beta is 76.3c iirc (removed it as I'm testing the Alpha). I would recommend not to use it, as it's highly incompatible with a lot of scenarios and crashes even freeroams depending on selected paths. If you want to test and report go ahead, but it's not usable if you just want to play.
I didn't spot that specific one. I only have VSync enabled, nothing else. Might try for a number of reasons eventually. Thanks. I'm still a bit worried about tearing and smoothness, though. Will see. In any event, I just don't like posts about removing features. Like me saying, nobody needs AP or RWE or Reshade. I don't, so you don't.
