search

ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
24.42k stars 1.07k forks source link

Train Simulator Classic (24010) #791

Open HonkingGoose opened 6 years ago

HonkingGoose commented 6 years ago

Train Simulator Classic

The game had another yearly update, and changed the brand name to Classic.

Train Simulator 2021:

The game had another yearly update.

Train Simulator 2020:

The game had another yearly update.

I no longer have access to a Linux computer to test on, so I can't provide a Proton log for TS2020.

I suspect there will still be a need to unpack the .ap files though. It seems the update to TS2020 was mainly shader work.

New hypothesis for the issue outlined in this post: having a . somewhere in the path causes the game to misbehave. So there might not even be a need to unpack the .ap files anyways...

Train Simulator 2019:

Edit 12th june 2019:

I tested a fresh install of the game, using Proton 4.2-7 and TS 2019 version 66.1b. Results:

Proton 4.2-7 log (64bit version of game): steam-24010.log Environment: https://gist.github.com/HonkingGoose/7936767029a19c23d330970a1a586c45 Missing water picture: Missing_water_Isle_of_Wight_DLC_at_Ryde_Pier_Head

The game has just been updated to the 2019 edition, which is split into 32 and 64 bit versions. So I'm updating the main post to reflect this. I've also edited the title of the issue, because the name of the game changed on the Steam store. The report for the 2018 version can be seen in my edit history.

What's new in 2019:

  1. 32 bit and 64 bit versions are now available.
  2. There seems to be some kind of audio bug in the 64 bit version (for now), search for "Setup_Audio.bat" on the Train Simulator 2019 FAQ for the workaround.

What's still the same:

  1. There is still a need to manually unpack .ap and legacy.bin files.
  2. The same kinds of rendering/graphical glitches are still there.

Environment:

OS: Ubuntu 18.04.1 Gist: gist Proton version: 3.7-8 Beta Game: Train Simulator (2019) Proton log for the 32 bit version steam-24010.log

Expected result:

Actual result:

Steps to reproduce:

  1. Install Train Simulator, with some DLC, from within the Steam client.
  2. Start game.
  3. On the main page of the game, click on “Drive”, this opens a menu in which you can see what content the game has loaded.
  4. Click on the different tabs.
  5. There is missing content (trains/routes/etc.).
  6. A work around is needed which is listed below, to get missing content to work.

What files are not processed automatically?

How to find those files:

The .ap files can be found with the Linux terminal:

cd 
find .local/share/Steam/steamapps/common/RailWorks/ -name "*.ap"

The legacy.bin files can be found with the Linux terminal:

cd
cd .local/share/Steam/steamapps/common/RailWorks/ 
find ../../workshop/content/24010 -name "*_legacy.bin"

Workaround for missing content:

Unzip the .ap files using the Linux terminal:

cd
find .local/share/Steam/steamapps/common/RailWorks/ -name "*.ap" -execdir unzip '{}' ';'

Unzip the legacy.bin files (from the Train Simulator Steam WorkShop), using the terminal:

cd
cd .local/share/Steam/steamapps/common/RailWorks/ 
find ../../workshop/content/24010 -name "*_legacy.bin" -exec unzip '{}' ';'
skinnyraf commented 4 years ago

I'm away for a few days, so I have no opportunity to test it until Sunday. What does it mean that the library "must be set up in the root of the filesystem"? Does it mean it has to be under /steam? If the issue is with the dot, wouldn't ~/TS work? Or have I misunderstood something? I'm hesitant to create non-standard root-level folders.

kisak-valve commented 4 years ago

Hello @skinnyraf, the hypothesis is that having a . somewhere in the path causes the game to misbehave, beyond that it shouldn't matter, so you could have /home/regularuser/testlibrary as a secondary Steam library which does not contain a ..

erkinalp commented 4 years ago

Not working on 5.x.

kisak-valve commented 4 years ago

Hello @erkinalp, please add PROTON_LOG=1 %command% to the game's launch options and drag and drop the generated $HOME/steam-$APPID.log into the comment box.

erkinalp commented 4 years ago

See https://paste.ubuntu.com/p/3CRH2nTw43/

kisak-valve commented 4 years ago

From your log: err:vulkan:wine_vk_instance_load_physical_devices Failed to enumerate physical devices, res=-3 err:vulkan:wine_vkCreateInstance Failed to load physical devices, res=-3

This tells us that Vulkan failed to initialize on your system. Please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

erkinalp commented 4 years ago

See https://gist.github.com/erkinalp/d97b730ceaed47a733be1fc3875b643d

kisak-valve commented 4 years ago

Thanks, your system information tells us that you have an AMD Oland chipset. This is part of the Southern Island (SI) generation of AMD video cards. By default the linux kernel uses the radeon kernel module with this video card generation, which is incompatible with Vulkan. Please give https://github.com/ValveSoftware/Proton/wiki/For-AMD-users-having-issues-with-non-OpenGL-games a read.

Additionally, you do not have 32 bit vulkan support installed. Please run sudo apt install mesa-vulkan-drivers:i386.

anthr76 commented 3 years ago

2021 cannot launch in windowed mode under Wayland GNOME session.

I have deleted the playerprofiles.bin file in order to relaunch the game

AllHafRA commented 2 years ago

Hi all. I came across two errors already discussed here on Manjaro: 1) rectangles instead of menu text 2) Missions don't load, showing a strange screen. Last time you suspected allfonts and steam-native. I really don't want to move to Ubuntu because of one simulator) Please help)