DTG Matt can PC users has some assurances please Matt that this blur issue isn’t going to dilute our experience of TSW by using lower res textures across the game to fix an issue that mainly seems to plague console users. thanks
Matt, as allready mentioned by others, turning off substitutions helps to prevent bluryness. However, I don't want to loose all substitutions. Is it possible to add and option to disable certain substitutions, like you can already with layers? It will not only helps with blurryness, it's also nice to prevent some locos from being visible on a route, when they don't match the era.
The reductions we're doing are because the textures are inefficient and pointlessly large. If we see a visible reduction then we reverse it. In a recent case with the 807 I spoke to AABS about the low res textures that appeared there and it was simply an oversight they are correcting. So no, no intention to reduce quality for anyone, this is about just finding where the textures are simply over the top for no benefit. Matt.
Indeed, substitutions will massively contribute - the worst offenders are the multiple versions of identical things. each one taking up its own unique memory, and bringing nothing of value to the visual table. So yes, on the list to look at that too. Matt.
That would be really great if this can be accomplished. The many 143, 146 and 185 in game are not needed for substitutions and for example, I do not want to see the DB Vectron on Bremen - Oldenburg or the BR 110 from Linke Rheinstrecke on Dresden - Riesa.
I have the impression that not only 807, but also 805 have a very reduced texture, perhaps by mistake, but maybe that's just my impression. However, the latest optimization on Pendolino 390 also seemed to me to have reduced the quality of external textures, but maybe I just didn't notice it that much before? Otherwise, we are curious about further results and developments in this area on PS5.
Can you please Change the whole System to include only 1 Class 66 or BR 185 to the Game It make no sense to have 20 different Versions of the Same Train, all with Bugs and issues
Personally I never had any issue with blurry textures. As others said above, I just hope the effort to reduce texture size will not reduce the quality for those of us with high end PCs.
My thinking is that fixing the substitution issues will have more of a benefit than we think. The reason behind my thinking on this is if you drive with just the default stock you don't get blurry textures on the routes. Another reason being if you drive SKA new journeys timetable no blurry textures only the revamped is affected same with BCC, Cathcart, GWE. No issues with the original TT's.
You don’t Need multiple Versions of the Class 66, DB BR 146 or the Dostos. It’s enough to have 1 Version with working Perfectly in different Liveries. But that each Route has a new version is Bad Memory use, plus many Versions are broken
Oddly I’ve never had any issues on Cathcart with the updated timetable. Ran into a packed GC with both Pendos and an Azuma on the platforms upon arrival to test but it behaved itself.
Thing is the response brought back by the staff team is often "If someone doesn't have the 66 that was added with (insert route here), they won't be able to play that service." And? That's no different to not being able to drive any service if the player doesn't have the relevant DLC. Trim the number down, get rid of the substitutions.
Just filled out the poll. Really hope this can finally get sorted, at least to an acceptable level in the meantime, as there are many routes I enjoy and would like to keep enjoying, but don't play anymore due to the frustration of blurry textures.
When i first got the 380 i got blurring but there was a patch that happened later on and it pretty much fixed it and its a non issue now.
I actually just played Cathcart yesterday on Xbox series X , updated TT with the 380 counter clockwise service and received blurries soon after departing Maxwell park station
Thats OK the other 2 Scottish routes are going to be the same after the update with the new timetables turns them to a blurry mess. And it sure doesn't sound like it will be fixed before TSW7 as was promised back in December.
May sound silly but if youre are on a XBOX the full list is suffering from blurry textures sofar i can understand..... Or is this a bit overdone?!
Since the new Fife Circle update, I've had issues with Blurry textures from Haymarket and onwards on PS5.
This thing is like an infection Wish I could say this will be fixed but thinking that DTG have lost control of the situation and dont have the necessary people in the talent pool available to fix it This thread is proof of that as they dont even know what route is even affected
And that they are still investigating now 8 months later. Sorry but if it was a priority you would have solved it by now even 1 person with 8 months worth of work hours should have figured it out. So obviously its not really a big priority. I think the solution is a bigger task than they thought and are trying to find an easy fix.
Wasn't it mentioned in a roadmap beginning of this year that they wanted blurry textures rid of by end of March? It must be a concern for DTG that the issue is still here and if things go like they usually do, the next TSW will be here.
Just wanted to make my request clear... Every route has the potential to have this issue, the poll is not so I can find out which routes have the issue, depending on what you do, how busy it is with train types etc, any route can experience this - memory is finite and busier timetables are going to constantly put that under pressure. The poll was there to help me understand which ones are bothering you the *most* so I can prioritise the fixes on those *first* there's no point me starting with routes that aren't bothering people as much as others and there is a clear priority that comes out of the poll, so it's been very helpful in that respect, thank you. In terms of timings, no, nothing about this has been ideal. The aspiration to get rid of blurry textures by end of March was a real one and we didn't meet it, it was a bigger problem than that and needed more in depth understanding, more testing and so forth. The texture pool isn't a straight forward chunk of memory - and what doesn't help any of this is that if you repeat the circumstances that cause texture pooling within the editor, they don't show the texture pool anywhere near capacity. This has caused many problems in trying to understand what's going on. Since then we've done experiments working with other partners like All Aboard and Firefly, and some optimisations have been delivered such as on Southeastern which have demonstrated that they are the right path to follow. We have a tool which has run over the thousands of textures in the game, analysed them to work out their function and then created a report of all the myriad of different configuration settings on each texture and other parameters for them and produced a list of all textures that now need to be reviewed and fixed if found to be an issue. The current task is assembling those into work packages to get them done, and that's where the poll comes in, because with this we can start working through routes and trains and getting them out to you as soon as they're done knowing we're focusing on the stuff that's hurting the most, first. Matt.
Agreed, no disrespect to Matt or the team now working on the issue, I think this problem is beyond permanent fixing. At this point the best we can hope for is that routes eventually get sorted out, but if the recent releases are anything to go by, they clearly don’t have enough of a grip of the issue to prevent it from the get go. I’ve said this before but now just look at the massive backlog of routes with this issue, if they’d have got on top of this issue in the first place, even if the problem couldn’t be prevented in the first instance, the retroactive fixes could have been implemented much sooner. We have a route that doesn’t have the problem, we get an update & then surprise, blurry textures - It’s so disappointingly predictable. Even now, knowing they have a huge backlog of this issue to get through, they aren’t dealing with the problem before releasing yet another thing to add to that list. Ultimately it’s just put me off new content & the longer that’s gone on, the less interested I’ve become in TSW & the less I’m buying, even if the content does eventually turn out well.
