As title: Recently, TSC when in full screen mode, crashes if you shrink the game to the taskbar, even momentarily. It never used to do this. It delivers the following error.
PLease read what I just posted in reply to you on this other thread, only way to really test my theory is try it on a vanilla version of TSC without the AP SWEP and see if it still happens?
Not sure why we have muliple threads on this, but anyway. Yes, it happens on vanilla. I didn't ever have it but since the latest production release I do. DTG is aware and decided not to roll back. Hopefully they'll release a fix for it soon.
> Not sure why we have muliple threads on this, but anyway. Because moderators do not merge threads in these forums and posters do not read all posts before they post.
As the problem does not exist for those people without the AP Weather files should DTG roll their software back? A Roll back could effect a lot of people for the sake of a Third Party Software add-on that not everyone has. When AP updates a Loco Pack it breaks third party reskins - Vulcan Productions comes to mind. Do AP roll back their software?
Does this affect the original AP weather pack or just V2? I only have V1 of the weather pack and I also have not updated any loco packs recently.
I think DTG decided to not rollback, because: - you can use Borderless - AP is modifying blueprints at runtime - team is working on the FullScreen issue. Someone seems to have found the problem lies in the SilverLining plugin. Those affected might try if this helps: Make sure DynamicClouds are disabled (don't need them when only using AP weather) rename RailWorks\data\SilverLining folder
But it does. Check the post you quoted. I am well known for not using any enhancements and yet I have the issue. Regarding SilverLining... what's funny is I also just use 2D weather except in official / workshop / quick drives scenarios using it. Also the menus don't use it. Nor does AP, correct?
Just different, so the .dlls won't be found. SilverLining_ would already suffice to check if it's related to these dlls.
Just renamed the SilverLining folder, and TSC refuses to work at all. Just quits after a couple of seconds of trying.
Test & confirm I installed fresh TSC with just the old ECML and its scenarios on my laptop. Started the game. Survived the first alt-tab. I didn't have a train selected in a free roam and I didn't pause. Crashed on the second. I was driving. After restart, survived the first again, this time while driving.
Have you got a backed up copy of the silverlining folder from an older build? Maybe you could try swapping them out?
Btw, here's the post that suggested this. https://forums.dovetailgames.com/threads/public-beta-build-76-3a.76989/#post-767427 But I don't think there's any other way for those who need Fullscreen than to wait for the next phase of the upgrade, when we can hopefully leave DX9 behind and really increase performance. Or downgrade by retrieving an older version of the 24009 core from Steam via "download_depot" console command.
I could roll back, but it will constantly just be overwritten and updated at some point. Oh well.. you never know... DTG might actually fix it!!! LOL
I wonder where the problem comes from if we are all running the same version of Railworks/TSC but only some people are affected?
That's the real question. We're all running so many addons and stuff, I bet this will never get resolved.
No idea. Pretty much nothing in common... My desktop is an old (2015) Intel-nVidia using Windows 10, installed 2023-03. My laptop is an (Asus ROG Zephyrus G14, 2022) AMD using Windows 11, installed 2023-07. I suspect a lot of people just use Borderless without being particularly conscious about it. And of course those using old copies. Also, Windows 8.1 (on the desktop) did behave a little different compared to Win10. The Win11 is also quirky, for the first minute or two of a scenario, it renders for half a second, than stops for half a second. I didn't notice anything like that in other games.
I think for most Borderless is not a problem at all (like me) and many prefer it over FullScreen, which was needed to free some resources to gain performance (some 20 years ago). You don't use Borderless without being conscious because it is not the default option. Though, many recent games I've installed automatically select Borderless (Windowed Fullscreen) by default now. It is more system-friendly to say so, and allows the use of overlays (I have a small YT player window open when driving long US scenarios...)
