Z fighting is still an issue mainly on the flixtrain vectron it's horrendous around the screen on the right its so distracting just like the original vectron. It's happening on the 350 too but not as bad . Hopefully dtg will get it fixed soon. Maybe microsoft or epic can help with the issue.
Disappointing to hear this is still an issue with new models. From the last roadmap, more care was supposedly being taken to avoid this. I know I've said it before, but I'll say it again, it only started after the engine upgrade around rush hour time.
Always seems to affect thw same areas of cabs too. Namely around screens as the OP describes. Also text under buttons or switches.
There's some also on the new 350. See the little rivets on the right hand side. https://youtube.com/shorts/g6sGIMijIS4?si=AGasR4_gwXUxil7d
This all sounds to me as if the Xbox has a very low z buffer precision, and models need to be adapted specifically (i.e. decals need a bit more distance to the surface, slightly floating). Just a thought, may be wrong.
It's really irritating. I posted about z fighting last week. Doesn't seem to be something dtg are keen on talking about as they admitted a couple of roadmaps ago that a fix involves looking at the individual dlc affected and fixing each. When they're not keen on doing something, they go quiet
There have been numerous threads and posts, ever since it became a problem. Unfortunately, they all seem to lead to nothing. The last mention of it was in a roadmap. Apparently it appears each loco would need to be individually fixed, rather than a core fix. Well maybe if it was fixed when it was first highlighted (several years ago) then there wouldn't be such a long list of affected locos now!
What makes this frustrating in particular is that judging by DTGs words the Vectron actually has been in development since then. There would have been the perfect opportunity to adjust the affected shapes during development, not post-realease-support, especially as changes to the cabs were being done anyway... if it isn't done during that opportunity then - well - never? Consoles and xbox specifically got a really short straw with this release. Despite the store issues being mostly sorted this has CP2077 vibes - sorry.
100% agree with you. If they can't or wont fix the back catalogue (although they really should as some are really bad) Then at least ensure it doesn't happen going forward. Prevention is better than a cure, as the old saying goes.
At least CP2077 had a warning to prospective players in the end, on the store page. New players of this will be going in blind. Also, conveniently enough, the locos included in the free starter pack are of the few that don't seem to suffer from any z fighting (the 323 does, but only really on the back wall fuse/breaker text, where it wouldn't really be noticed) imagine the joy of new players as they decided to buy new dlc....
This is one of the drawbacks of playing more on the xbox than on the PC as it really is frustrating to have it flickering as you're trying to concentrate.
I mean with Mildmay and another Star member hopefully it doesn’t suffer but the vectron is a one that suffers badly
It's one of those issues that have been in the game for a while like audio popping that's also been in the game for a while and not sorted out and that's a Xbox problem
**Sigh** And it was stated that going forward, they knew how to stop this from happening. Yes, it absolutely should be fixed.
Agreed, DTG Matt has now mentioned it more than once across several roadmap streams that they know the cause of the issue and that it won't be seen going forward. And then what happens? New DLC releases, and we continue to have it assault our eyeballs. This is why I can no longer 100% trust what is said in response to any question in the live streams with regards to bugs and fixes.
It seems they are still in the stage of, ignoring the issue, maybe players will forget about it. What's more frustrating is they now claim the know the cause and th fix. They just choose not to fix it.
... and not (or not enough) to communicate the fix to third party developers apparently, since much of the recently affected seems to be from those....
Yes, I was thinking the same. I watched the live stream for Cardiff yesterday. It was stated that a 3rd party built the new model..... Zfighting here we come. But don't worry, they will ensure it doesn't happen going forward.
How on earth these issues are coming back is god knows how cause I thought it was patched in 4 and the arose again for 5
Zfighting has been there since tsw rush hour. Unfortunately, no matter how often it's raised, there seems to be 0% interest to sort it.
