Skip to content

WestPlay 2.4.0

Choose a tag to compare

@enes-less enes-less released this 13 Nov 11:37
· 1 commit to main since this release
  • The Coaches DLC: WestPlay on the screens of the Scania Touring and the MAN Lion's Coach, shaped to each and drawn sharp. The game's parking camera shows over WestPlay, as on the game's own screen, and WestPlay under it takes no clicks while it shows. The Volvo 9700 keeps the game's navigation (its real one has no CarPlay); the WestPlay tablet in its dashboard shows WestPlay.
  • The coaches play through their own speakers, from the moment you get in: the MAN Lion's Coach and the Scania Touring (both lengths each) and the Volvo 9700. The driver's pair, or every speaker over the passengers' seats, heard from the driver's seat: a choice in the companion (Truck Screen › Coach speakers), greyed out in a truck. In a coach it says how many speakers that coach's passengers' set plays at once, which a weak processor can feel.
  • The screen's brightness on keys: Alt+4 darker, Alt+5 brighter (with WestPlay's key), shown at the top of the screen as the volume is. Both can be changed in the companion's Controls; a key you had already put another keybind on stays yours.
  • Holding Volume up or Volume down changes the song after one second (it took two).
  • The sidebar laid out as CarPlay's: its apps in the very middle of it on every screen, the clock at the top, the truck and Home/Dashboard buttons together at the bottom (a gap of most of a button stood between the two). Its buttons are larger, about half an app icon as on CarPlay (the tablet's stay as they were). The Scania 7" shows three apps (it had two).
  • The map's speed limit sign keeps its figures inside its red ring at every Text Size, three-digit limits too (they grew with the Text Size and ran through the ring).
  • Swiping the Home screen's pages no longer sticks when the mouse is let go at the screen's edge.
  • Maps (and the Dashboard's map) move smoothly at 60 frames a second on every display: on displays faster than 60 Hz the game was handed as few as 45 new map frames a second (36 at 144 Hz), the map holding still up to 40 ms at a time, "moving like steps" whatever the graphics card. The map is now drawn evenly, so each of the 60 frames a second the game takes is a new one.
  • Through every toll plaza and border crossing the route runs through the booth or gate the game's route drives through, wherever it stands: on many it ran straight through between the booths (south of Innsbruck), and where a booth or gate stood off the plaza's middle, beside it. On ETS2's map the line now passes through the booth on all 449 ways through toll plazas (252 before) and the gate on all 181 through border crossings (95 before).
  • The game no longer crashes a while after it starts when the Steam overlay's code is in it (even switched off in Steam) and something makes another swap chain, as Trucky's app does as it connects: where the overlay had hooked the game's picture before WestPlay, the two called each other round until the game's stack ran out. WestPlay now leaves the overlay nothing to hook again.
  • WestPlay starts its cab's browser again if it doesn't start the first time (up to three tries), instead of stopping with "WestPlay engine stopped: … the timeout period expired". When it does stop, app.log now says why.
  • Every map is prepared again once with this update.
  • A map with a map mod made of older models (Oyuncuyusbis map) no longer fails to prepare: an older model's parts were read as the game's current ones, and the build asked for 13 GB at once. Models in the game's three older formats are now read as they are, so their buildings, stations and roads are on the map too (on the Oyuncuyusbis map, 702 of its 4,523 models).
  • Map mods whose definitions are written scrambled, encrypted or binary (as the game reads them) are read: their roads' looks, junctions and water were left out without a word. Whatever still can't be read is named in app.log.
  • A map mod with damaged map files is left out and named, instead of the whole map failing to prepare or the preparation sitting still (a zip cut short, damaged sectors, junctions or models, a road of impossible length, ground placed nowhere; where a mod's sector doesn't fit the game's own, that mod is left out). A damaged or protected archive can no longer make a preparation ask for gigabytes at once ("memory allocation of … bytes failed").
  • A map whose parts lie far apart (map mods across the world's oceans, or a DLC far from the rest: one player's spans 1,561 x 1,389 km) no longer needs tens of gigabytes of memory, or hundreds of thousands of files of open sea on disk, and its sea comes out right. Small lakes and islands far from the map's middle are drawn the right way (a lake could come out as land, an island as a hole).
  • Prepare Maps Faster no longer runs out of memory on PCs where other programs use a good part of it (a laptop of 16 GB failed with "memory allocation ... failed"): it now counts everything the PC uses. Preparing a map also takes less memory and less time on its own.
  • Starting the game while a map is being prepared stops the preparation, and the companion says so: it went on under the game, taking the PC's memory and processor from it. It starts again from the beginning once the game is closed.
  • The map bar moves the whole way through, at the pace the work really goes ("stuck at 92%" for minutes), and gives each map an equal share however many profiles play it.
  • A map that fails ends with what went wrong, and the next profile's map is prepared: it could sit still at a percentage for ever. A failed map says the fault itself, not "a scoped thread panicked", and one that couldn't get the memory it needed says how much it asked for.
  • A preparation that's stopped or fails no longer leaves gigabytes of unfinished files behind.
  • Maps prepared by an older WestPlay are prepared again when the map builder changes: a map prepared by 2.2.0 that left no mod out was taken as up to date, so ATS's start at San Francisco (2.2.1) never reached it.