Hi guys really would like to know how you are going to fix the 805 because it still CTD on most of the that go from euston. That last update did nothing performance wise or I would able to play with out issues the only thing that changed was the buttons look like black squares now. And b2c route is just blurry all the time and thats on the new timetable you released. Ok that doesn't CTD as much now I give you that one. Im sorry to winge about but its so annoying because I really enjoy them but lately not so much. This all xbox series x.
I haven't found to have anywhere near the amount of blurry textures I once had on this route before the patch, maybe I have less content installed? Not sure. Not noticed a CTD either yet but maybe thats happening only on certain services
May seem like a daft question but are you sure you're using the correct timetable? The update added a reduced timetable to the route, but it has the same name as the old one ("GJR Modern Timetable"), so if you accidentally use the old one you'll encounter the same issues as before. When you click on the new / reduced one, the details pane on the right should show "Services completed : 0 / 575". That's currently the only way to know you're using the reduced timetable. DTG have said they're going to issue a patch to fix the naming problem.
Yes I used the the timetable witch had jobs played. Was going good got out of new street tunnel and was blurry all they way to Crewe.
Yes so this is why you're seeing the issues. You need to use the other timetable to see any improvements. I can understand DTG not wanting to just delete the full timetables, as it would probably mess up everyone's stats, but for consoles they should either have merged the service pattern from the new one into the old timetable, or figured out a way to hide the old timetable.
Sorry i was ment to say I was using the timetable that had NO jobs played witch i assumed was the new one.
Ah, well then your assumption is correct - that is the new timetable - and iit's a bit worrying that you're not seeing any improvement. Before DTG get back in the morning, it's probably worth clarifying which model of Xbox you're on and providing an example of a timetable run that systematically causes a CTD, so that they can try to reproduce it.
Yesterday I tried Birmingham - Crewe on PS5 Pro after the last update, I only had Pendolino and 220 Voyager as add-ons ....... I tried 350/2 from Wolverhampton to Birmingham and it was blurry on the way ......... so I guess so........ practically it can't work without blurring even in the basic version, because I don't consider the Pendolino and Voyager add-ons to be that massive, plus they say the Pendolino has had its textures optimized ......... I've been saying this from the beginning, those 350 series trains from AAS are weird
I do have to admit it doesn't seem as bad as it was but its still there down to 8 layers. Now I find instead of the inside of the train going blurry its the outside scenery. And it flickers low res/high res.
For console, I think that’s going to be the trade off for not getting blurry textures in the train. Scenery isn’t the main attraction and unless you walk around the platforms a lot, those types of things won’t be noticeable vs. it being extremely noticeable in the train cab where you need to see text and the buttons.
Regarding the recent update, I notice this line from AABS “lower-memory Xbox Series X configurations” and wondered what they mean by this. As I understand it there is only one Xbox Series X memory configuration.
Thanks for the clarification, I was considering buying some additional storage space but I don’t think that would make any difference. It shouldn’t be necessary to run a reduced timetable on a Series X.
Thats correct Series X cannot handle TSW at its fullest, it never could. Neither can PS5. Consoles have default settings lower than Ultra on the PC. Both are set to High settings by default and the Series X has a medium level LOD. Its the way the RAM is set up is different Xbox is set up that of the 16GB it split into 2 10GB is fast RAM and 6GB is slow RAM. So technically we only have 10GB of RAM for the game, while PS5 uses the full 16. But in order to say something runs at the fullest then it has to be Ultra settings. And the consoles have never had Ultra settings.
the patch was supposed to fix blurry textures but they’re actually worse than before, lasting an entire hour between birmingham and crewe. it’s a real shame because b2c is probably my favourite route, but it just looks awful with blurriness
I watched the stream and Matt said removing layers doesn't stop the route from loading those layers in the memory (the removed layers wouldn't show on the route) hence the reduced timetables being developed.
The RAM situation on Xbox is not really like you described. Series X has still 16GB or RAM and not 10. PS5 also cannot use the full 16GB for a game or everything for textures, there is an OS running and other processes also needs memory. On Xbox you'll use the fast memory for the processes who needs the speed the most, the OS and things like audio and scripts can run in the slower memory. Fun fact, the fast memory of Series X is faster then the memory on PS5: 10GB at 560 GB/s and 6GB at 336 GB/s, PS5 16GB at 448 GB/s. In the end the difference in speed is not that much between both, the combined speed on Series X is even higher then on PS5. There are just 2 different memory pools, something like you have on PC with RAM and VRAM with different speeds. Besides this, PS5 also has blurry textures, in general and with the class 805 timetable. This game really needs serious optimization, a reduced timetable and deleting static stock is not optimizing and solving the root issue.
I find it does actually help with it to be honest. As I’ve said elsewhere AAS 350’s are a nightmare for blurring & turning them off resolves it. To be honest I find DTG are regularly contradicting themselves. Remember how many times they told us route length didn’t matter in terms of performance, but then the reason gen8 isn’t getting content is because it can’t handle the length of the route. They always used to say that once you add one train in, duplicates of it were essentially inconsequential, but then we’ve had them talking about how reducing the size of the 390 memory is a good thing because they can add more. DITTO for layer selector, you can go back to streams where they discussed the ability to improve performance by disabling layers. I think a lot the time they’re just saying the first that comes to mind when presented with a difficult question they can’t really answer, something that usually gets them off the hook with the least blame possible. I kind of wish I never watched the Trent Valley stream to be honest, there were a lot of things said that really rubbed me the wrong way, you really get the sense they’re building up to saying the console issues are unsolvable because of the consoles.
Exactly, in the last stream Matt mentioned, longer route are consuming more memory, before they told longer routes are no issue. They told us to disable layers to avoid blurry textures, but now disabling layers does not work anymore, because trains are loaded in anyway, as they're in the timetable. So why on earth are those trains loading in, when the layer is disabled? The class 350 is a memory hog, also the one from WCML south. As soon as I have installed this route, I get blurry textures on GWE with the 350 driving around.
They’ll never say that though because console users must make up most of their buyers? I mean from what I’ve seen if you’re on PC you’re probably going for TSC with its much larger amount of content. So DTG you need to fix this console issue. And I’d suggest doing it fast.
Yes it is exactly as I described. Xbox is faster but the memory pool structure is a split assymetric on 10GB at 560 GB/s and 6GB at 336 GB/s. PS5 is the full 16GB at 448 GB/s. Look it up.
I will quote your original text: "So technically we only have 10GB of RAM for the game, while PS5 uses the full 16." This is not true, also your own screenshot proves this: "requires targeted asset location". You have the full 16GB available, you only needs to target which memory pool you're gonna use for what. The fast memory pool is faster then the memory on PS5, the speed over both memory pools combined, is also still faster then PS5. So the OS runs in the slower memory, you can put things like sounds in the slower memory and the stuff really needing speed, goes to the fast memory pool. If you do this right, Series X even has advantage because this faster memory, but yeah it's a bit more work. DTG and doing things right, is also questionable.
The slow RAM is not used for the game its for background processes. So games only utilize the fast RAM. So again what I said is fact look it up yourself. Matt said the exact same thing on the MK to Crewe preview stream. 2:50:30 if you would like a timestamp. https://www.youtube.com/live/L_I-aEYfrDY?si=Lx2g149NpbDMYmZU
Part of the "slow" RAM is used for games, there is 2.5GB reserved for the OS, the remaining 3.5GB is usable for devs. The fast 10GB is intended for use of GPU data, the remaining 3.5GB is intended for CPU data like audio. Also the PS5 has an OS running, so on PS5, devs do also not have 16GB of RAM available to use. Besides this, also on PS5 there is memory used for CPU and things like audio, so it's not like the 16GB minus the amount of RAM used by the OS is available for GPU data. If a game is not using that much memory for the CPU, theoratical the PS5 could have left some more memory then 10GB for GPU data, however from what I get, the remaining 3.5GB of "slow" RAM could be used for GPU data too. If you look at the Steam page, the minium TSW6 requirement for VRAM is a card with 2GB, 5 times less then the 10GB fast memory of Series X. Ofcourse, that's just a joke, as that 2GB is never enough to run a full route. In conclusion, no the PS5 does not have full 16GB memory available for games and it's also not that black and white, Series X only has 10GB available. Both consoles suffer from blurry textures, it's about time DTG is gonna optimize TSW, because that's the only solution.
The numbers AI is giving are correct, but making the conclusion PS5 can use 16GB of memory and Series X only 10GB is incorrect.
To get back to the point, instead of arguing over numbers, the resolution to the problems for console owners is solely in the hands of DTG and there is nothing the consumer can do themselves other than switch to HD and remove layers (neither of which we should need to do)
I agree that disabling layers definitely has an effect on texture blurring, we can't say how much it is directly proportional to disabling a given layer, but it helps and it works. Turning off 350 from B2C, I agree that they are a big problem in themselves, but I completely disagree that if you just turn off 350 (AAS) the problem is gone, I tried leaving only the original 350/1 (EMK) and there is slight blurring, however, even in this case I don't have all the layers installed. Simply put, the Birmingham - Crewe map is a problem on PS5 consoles. And I don't understand the latest Evero 805 update at all, black squares on buttons, as was mentioned in the cockpit on the buttons and the external textures are also several levels worse resolution, especially on the driver's cars in the cabin area....... should I add this to a new product I might buy tomorrow? And today I'm watching streams from Britisch Ace on YT and I would say that the exterior texture on the 807 will be similar, I was waiting to see if there would be a more detailed view of the front area around the side window and it wasn't, as if it was intentional, he always quickly ran the camera through it, because otherwise he takes pretty detailed shots in PhotoMode etc.....
