Just loaded up TSC after a short absence and when I try to run a standard scenario using the AP 142 V2, the game crashes and creates this error. I haven't touched TSC for a few weeks and it ran fine when I last played it. Any help or ideas please?
yeah I'm getting this a lot now. If AP weather uses variable patterns, when it shrinks the game to the taskbar, it crashes. It never used to... I just clicked on it and back it came... I get this exact same error every single time lately. I hate borderless as well. It's kind of ruining the sim for me actually. I'm not using it anywhere near as much as I used to due to this. I can find no fix for it either.
How does Borderless affect the game for you that you can't play it? It's looking the same, only graphics output is handled differently internally. I always use it for every game that offers it, and most modern games do now. The only thing that's different to FS is that the Brightness control is locked to your desktop settings, but Contrast is working as it is shader-based.
Is that a known problem causing this error? Mine does it no matter what train I use. Unless having that installed is enough to cause the issue. I can't see it actually being that train though in my case. Worth a shot though I suppose.
Which version of TS are you using? The current build of the public beta? I've reverted back to the current build as the public beta seemed to be causing slightly more crashes. I don't have AP weather installed and generally things are quite stable, unless tabbing between applications while running TS.
I was also seeing this issue a lot recently but since i changed to Borderless, it hasn't re-occured (fingers crossed!)
For me borderless and full screen look the same, or almost - I noticed that upon exiting, the main menu gets brighter. Do you have increased the gamma to bring out low colors and then enhance it from there? I noticed the competition shots are pretty bright. For me the issue with borderless is the lack of V-Sync which means it's not smooth even at 140 fps. Also, I don't need 140 fps and 60 fps is just as stuttery. I do get this Vertex Buffer error since the latest production version, I absolutely never had it before. It works without so aside from the time it takes to change the setting, it's a workaround for sessions where alt-tab or popups happen.
No, I've not changed gamma, or anything else. It just goes noticeably darker when in borderless. I suppose I could try increasing brightness in ReShade to compensate. I'll play with it this weekend and see what I can do.
Well, I tried loading TSC again after I got annoyed with it and went to drive a truck 1500 miles across the US. When I tried to start TSC it did it again, without even entering the menu screen. I finally got back into the game/sim and tried another route with another AP unit (class 158). This time there was no vertex buffer error.
I've just noticed that it does this if I click on my other monitor as well. Anything that makes it shrink to the taskbar gives this error. I've got other full screen games that don't do this, so it's not just because I have it in full screen. This is a bug that needs fixing. There's obviously been an update that's caused this, as it never used to happen. I could always collapse it to the task bar and bring it back again.
Can't say about the AP Weather thing because the only scenarios I've played lately have not been changing weather ones but I've had no crashes when minimising TS or clicking on my 2nd monitor. I'm not using reshade presently and I don't have the AP 142 or 318 but other than that there's probably not a whole lot different between our installs.
Does anyone know if this occurs with GSync/FreeSync monitors? Does it occur at all DEFAULT refresh rates ie 60, 75, 120 Hz etc? I haven't seen it with either of these on my setup (GSync, 144Hz) when using Full Screen or certain DLC.
My TSC seems to always get shrunk to taskbar or hidden somewhere as soon as it's launched from Steam. It started doing it after an update a month or so ago (was before the one that basically wiped all AP and external developer stuff). I have a second screen plugged into one of the DP ports but I usually only use screen 2 when I'm going to do a live stream (which is not that often). As you say, running other games in fullscreen mode doesn't do this.
I am running 2 monitors in extended desktop, the second monitor on my IGU the primary monitor on my GPU and in borderless. And am not getting any issues. Check my signature for system specs.
I missed the part where you said you were running in Fullscreen, I am running in Borderless. And this is the reason why... I assume you are aware of this issue with the SWEP? My best guess is that the minimisation caused by the .ap cp window is triggering the TSC crash, you might have to grin and bear Borderless and adjust your screens brightness accordingly until it's acknowledged as a TSC fault and fixed (unlikely if it's pinned on 3rd party software triggering it but you never know).
It's a core issue. Happens without any modifications whatsoever. It has been caused by recent changes as it didn't happen with the previous production iteration. It was also a known issue with plenty of people reporting it in the beta section. I suppose there are only a few people who can't / won't use borderless. Given all the other issues I am convinced that DTG must reorganize the installation and provide various binary versions separate from data, including past ones with tiny modifications to support the altered folder structure.
I know this, it doesn't here either, but this isn't the point. It shouldn't be doing this in fullscreen. Saying "run in borderless" is a bit like going to the hospital with a broken leg, and the doctor telling you "It's Ok... just use the other leg then, that's not broken".
It crashes when just sat at the menu if I so much as click on the other monitor. I know that variable SWEP weather patterns in a scenario causes the game to shrink to the taskbar when loading. It's always done this with SWEP2.0, but I just clicked on the taskbar and the game just carried on. It now crashes. It crashes even if I'm not running a scenario at all. Something's changed. I can uninstall AP weather and see if it still crashes to establish if it's that or not easily enough though. I'll try later.
As said, Borderless is rendered on the desktop so it uses your desktop brightness settings. For me, it is slightly brighter than Fullscreen, but better and I use some additional contrast in TSC. It is smooth also as I have capped the FPS to my refresh rate, 75. Andras, use -FPSLimit=70, that should be smooth on your 140Hz monitor (halved).
I can't adjust that. It's calibrated to correct levels for work.. I can't just turn the monitor brightness up or I'll be out of calibration. I would have to see if I can sort it out using ReShade. It's clearly still a fault though. Games shouldn't crash like this just because you click on something else.
Is it case sensitive? For the umpteenth time, my game doesn't respect it. Edit: Apparently, yes. I crashed with a vertex buffer error so I could test it My screens are 60fps by the way. What I mean is, V-Sync is smoother than FPSLimit for some reason. On my TV now and it's tearing badly.
It's case sensitive, yes. I have no tearing in Borderless. Monitor 75Hz, FPS limited to 75. Shmoooth... During all the stuff I was doing today, checking the camera bug on SC and Tehachapi, making a Warship soundmod, testing camera values on Ruhr Sieg and Academy, I was alt tabbing a thousand times and not once quit TSC in the last eight hours.
I haven't played TSC for a couple of weeks and I got the same vertex error message as the op when I tried to run it today. I don't ever recall having one of these in my 14 years of running TSC. The only thing that has changed on my computer is installing the latest Nvidia drivers. I have run system file checker which found some driver issues and also verified the game files on Steam and it did find some errors and fixed them.
You must run in Borderless - which is the modern de facto standard for gaming. Many modern games don't even provide a DX Exclusive Fullscreen option any more, as it has restrictions and comes from a time where you'd look for every MByte of RAM to save. Fullscreen is outdated. The APSWEP2.0 manual even tells you to play the game in Borderless, which allows better interaction with the OS. Just a random post that google gave... ALT-Tab caused a lot of headaches in for DX9 games. Lots of games would crash on ALT-Tab even back on Windows XP (I knew of a few games that tried to hook ALT-Tab to prevent you from doing it). Most likely what's happening is the Lost Device behavior in Win10 is a little different than what it used to be back on XP or whatever OS the game was originally developed for, and they don't handle the new behavior correctly. It can also be an issue in newer versions of Nvidia/AMD/Intel drivers, and might not have anything to do with Win10. Anyhow, this is a programming forum, and isn't really the place for tech support for getting your games to work. If you want to keep discussing the technical aspects of DX9 and Win10 that's fine, but if you just want to get your games running then you'll want to go elsewhere. Some advice: you'll probably have more luck if you actually name some of these games that are crashing for you, instead of just saying "DirectX 9 games". There are probably hundred or even thousands of DX9 games in existence, and you'll probably want to narrow it down from that. ?
Like Pookeyhead, I am unwilling to run in borderless due to how washed out the colours become. For him the colours are too dark.
That's probably something to do with your RWE / ReShade settings? For me the game looks the same. Exactly like the screenshots I'm posting. Or have you tweaked these settings? This is what TS is using in Borderless (just like any window). I'm using the default settings. So I think the problem is more to find out what you and Pookeyhead have in common that it looks bad for you. Just testing an APC142V2 scenario, no problems. Ingame options Sunlight def/Contrast +2/Ambient def. No ReShade or RWE.
I started getting this Vertex Buffer error after a recent Nvidia Driver update TSC would only load as far as the small startup screen and when it went to the main screen the vertex buffer error would pop up. It turned out that a program I run Asus GPU Tweak III was causing it. When I disabled it TSC would load. With help from Nvidia Support, they asked me to uninstall it and see if there was a later version of this program which there was. I installed the new version and I stopped getting the error. Asus Tweak III monitors your GPU and allows you to OC your graphics card. Mine is OC but just by using the default OC setting in Asus GPU Tweak III. Why OC your GPU read here. https://www.tomshardware.com/how-to/overclock-graphics-card-gpu I don't know whether updating to TSC2024 will stop this error only time will tell.
Where's the "why"?...I only see "how to"...and in all honesty "and these days I just don't find GPU overclocking to be particularly important. Applying upscaling of some form (DLSS, FSR2, XeSS, or even just a spatial upscaling filter) can provide a much larger performance improvement without increasing power use or affecting system stability." suggests that it isn't worth doing anyway!
I don't use RWE or ReShade, just SWEP V2.0. My monitors colour settings as as they were from when I got it a year ago. I don't think it's anything we've done, it just seems that for most people, for whatever reason, Borderless looks different to Full Screen whether it be brighter, darker, different colours etc. But the fact is, full screen used to work fine when alt-tabbing but since an update early this year it doesn't so something in the code has been broken to cause this problem that wasn't a problem before.
Fixed what.. vertex buffer issues, or putting brightness back as an option for borderless? I'm gonna assume the former, not the latter. Not sure. Not seen the issue, but then again, I'm not using TSC anywhere near as much right now as I'm super busy. I'll try and get some time in this weekend and test it.
