Proton: PC Building Simulator (621060)

Created on 4 Nov 2018  路  25Comments  路  Source: ValveSoftware/Proton

Compatibility Report

System Information

  • GPU: RX480
  • Driver/LLVM Mesa 18.2.2 /LLVM 7
  • Kernel version: 4.18 Ubuntu 18.10
  • Link to full system information report as Gist:
  • Proton version: 3.16-4 beta

I confirm:

  • [x ] that I haven't found an existing compatibility report for this game.
  • [x ] that I have checked whether there are updates for my system available.

Symptoms

PC Building Simulator crash on exit
steam-621060.log
error.log
capture d ecran de 2018-11-03 18-11-57

Reproduction

Game compatibility - Unofficial

All 25 comments

same in other unity games

@matou68 Were you successful at least after trying to launch the game? Because I couldn't.
Either launching it normally or with OpenGL support, all I get is a pop up window with the logo of the game and a progress bar that, once it reaches the end, that's it. Then the application syncs up and nothing else happens.
I've attached the log:
steam-621060.log

@rdlf4 Are sure that you have installed your GPU driver's correctly?

@rdlf4 Are sure that you have installed your GPU driver's correctly?

@Alexander88207 I am sure my laptop does have the drivers to handle things accordingly. Problem is, it may have _too many drivers_, so to speak.
For example, if I look up 'xserver-xorg-video' using Synaptics, it will return me that my system has these installed:
xserver-xorg-video-all
xserver-xorg-video-amdgpu (which is the one that I do need for gaming)
xserver-xorg-video-ati
xserver-xorg-video-fbdev
xserver-xorg-video-nouveau
xserver-xorg-video-qxl
xserver-xorg-video-radeon
xserver-xorg-video-vsa
And finally xserver-xorg-video-vmware
In case you're wondering, yes, this is a laptop. It's an AMD A12 (Carrizo) APU-based laptop with a Radeon RX540 (Polaris) dedicated GPU.
Terminal output:
`rodolfo@rodolfo-Aspire-A515-41G:~$ xrandr --listproviders

Providers: number : 2

Provider 0: id: 0x79 cap: 0x9, Source Output, Sink Offload crtcs: 3 outputs: 2 associated providers: 1 name:AMD Radeon R7 Graphics @ pci:0000:00:01.0
Provider 1: id: 0x44 cap: 0x6, Sink Output, Source Offload crtcs: 5 outputs: 0 associated providers: 1 name:Radeon 500 Series @ pci:0000:03:00.0
`
I run less-demanding games like Don't Starve, Crashlands, Ultra SF IV with no launch options because then, Steam will let my iGPU (Radeon R7) handle the rendering.
For more demanding games, such as Helldivers, Euro Truck Simulator 2, CS:GO, Metro 2033 Redux, Tomb Raider, I add this to the launcher options: DRI_PRIME=1 %command%, so that Steam offloads the task to my beefier Radeon RX 540 (2GB of GDDR5 memory, 6Ghz @128-bit) dGPU.
I wonder why you mentioned my graphics drivers, is that because of the log I attached to my previous post? If so, how exactly can I check what driver my system is using for this game? Could you point me to the right direction and shed some light into this?

videodriver

@rdlf4 ah i see solus :) maybe open a ticket in their forum.. I have not dealt with such setup's like yours sry :(

@rdlf4 ah i see solus :) maybe open a ticket in their forum

Nope. Linux Mint.

@rdlf4 ups sry your terminal looks like the default of solus

After getting rid of ati driver (only the amdgpu one works) and rebooting, I get the following error message when launching the game with Proton 3.16-4, 3.16-5 Beta, 3.7-8, 3.7-8 Beta:

ERROR: ld.so: object '/home/rodolfo/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Any ideas?

@rdlf4 this error message can be ignored you get it because you run steam as 64bit... On my github profile is the link to steam add me and wie can try together to solve your Problem

with proton 3.16-5 beta, Ubuntu 18.10 , Mesa 18.2.2 on my Radeon RX480, i was able to start the game (normal and OpenGL)

PC Building Simulator is stuck on initial screen

Issue transferred from https://github.com/ValveSoftware/Proton/issues/2326.
@rdlf4 posted on 2019-02-09T22:43:22:

Compatibility Report

  • Name of the game with compatibility issues: PC Building Simulator.
  • Steam AppID of the game: 621060

System Information

  • GPU: AMD Radeon RX540 (Mobile dedicated Polaris 12 GPU)
  • Driver/LLVM version: Mesa 18.3.3 (Padoka PPA) / LLVM 7.0.0
  • Kernel version: 4.15.0-45-generic
  • Proton version: 3.16-6 Beta

I confirm:

  • [OK] that I have checked whether there are updates for my system available.

Symptoms:

Once the game is launched, I can see the logo of the game with a red exclamation point on the top left corner*. After that the game thinks some more and then it gets stuck on this screen:
20190209193316_1
Music plays, but that's it. The game won't do anything after this point.
I tried clicking everywhere, Pressing Tab, Enter, space, you name it. Nothing happens after this screen is displayed.

* = that popup with the exclamation point shows up only for the first time the game is launched. After that, Steam launcher jumps straight to the screen above.
Proton Log file is attached:
steam-621060.log

Mods, please note: I did my research about existing topics for this game, but the only one there is on Github/SteamPlay is the one that reports a problem _when quitting_ the game.
This topic aims at addressing the issue there is after starting it.

Anyone else with the same issues?

After opening Steam from the terminal and then launching the game, this is my terminal output:
pcbsissue.txt
No progress so far. I thought this would've been taken care of after this game left BETA. I guess I was wrong.

I was told upgrading the kernel could do it, despite the fact most reports from ProtonDB that say this game works under OpenGL were based on the same Kernel version as mine. So I went from 4.15 to 4.18 and guess what: yeah. It doesn't work. After launching it from Steam, this game will go straight to the brands screen and just sit there, playing some music.

After all this time I have waited and the game has left the Beta stage and is now considered a "Stable" release. But that doesn't change anything, at least for me.
See, I have even gone as far as getting rid of my amdgpu driver and now I'm using the Mesa driver ver. 19.1.0 (Padoka PPA), I tried my luck with several different Proton Launch options only to realize I'm pretty much stuck where I was 4 months ago: brand screen with a music playing in the background.
I used all versions of Proton from 3.7-8 all the way up until 4.2-7.
I'm out of ideas, I guess I should just give up.

The game runs fine for me, however, the game completely refuses to stream video using remote play. All I get is a screen with the game's banner art in the background and a spinning circle on the bottom right. Strangely, the game's music plays fine.

For me since I'm running an arch based distro I'm facing the same issues as the reports on protondb that others have mentioned recently you run arch. https://www.protondb.com/app/621060 Both that the game freezes when quiting and the black screen when doing in game 3dmark testing.

These issues didn't exist a few months ago but I guess the updates have caused issues.

Compatibility Report

System Information

I confirm:

  • [x] that I haven't found an existing compatibility report for this game.
  • [x] that I have checked whether there are updates for my system available.

steam-621060.log

Symptoms

1 - The PCMark program stopped working completely inside the game simulation with the version 1.7 of the game. Versions older than that worked fine, as the "test" ended, but without video of the test running (just the basic counters like FPS, Frame counter and Time);

image

2 - The video in the PCMark prorgam doesn't appear because of an apparent dependency on mfplat. I tried running latest Proton GE that added some mfplat support but it didn't worked completely;
3 - The program crashes at exit. Again, this doesn't happen on versions older than the version 1.7 of the game;
4 - Curiously, if you open the "System Info" program before opening PCMark ones, the counters in the HUD that appear inside the game still show and run fine:

image

Reproduction

1 - Build a PC inside the game;
2 - Install PCMark in the PC you just built in the game;
3 - Open PCMark (that you just installed);
4 - Click "RUN" in the PCMark program. You'll notice the numbers of the PCMark program aren't visible (only the labels of the numbers) AND the test never finishes;
5 - Try to close the whole game. It'll crash;

Hello, just adding for the comment above: I just tested and the game works fine when mfplat is installed correctly. Proton GE with Wine's implementation of mfplat still don't work, but I'm very curious to test new versions as they release.

Keep the good work. :)

@fjorgemota could you please attach +mfplat,+seh log when running with GE build?

@nsivov Hey! Sorry for the delay in the answer.

Here are the logs with just the environment variable WINEDEBUG set to +mfplat,+seh running on Proton GE 5.6-2 (the latest with compiled assets available).

I hope this helps: steam-621060.log

Any further questions or requests related to this issue, please feel free to ask.

@nsivov

Thanks so much for giving this issue attention if this could get working again it would make my week. XD

<Workaround removed by moderator>

@fjorgemota
Not sure why you thumbed me down. I can only assume it's because you wish I help to contribute. As much as I'd like to I don't have the time to.

Hello @codeman101, that workaround is legally problematic and has been removed. It's not okay to tell other people to use it.

@codeman101 if you don't have the time to contribute, I really understood you, but please don't spam the issue with comments not only tagging developers but also not adding ANY useful information to help to fix the game.

Please, remember: THIS IS NOT A CHAT, the idea of these issues is to add useful logs, reports and workarounds (that aren't legally problematic as the one you suggested other users to use) so developers have a easy way to get information to TRY to fix issues, without anything being guaranteed (so please, don't create big expectations just because someone apparently is working on a fix..).

Any comment on a issue immediately spams anyone that's subscribed on the issue, and pollutes the issues as a whole, so please keep that in mind before commenting on any issues without adding useful information/reports.

Finally, I need to remember that this doesn't mean you can't send a good "thank you" to the developers working on the fix, BUT please do that with the reactions you can send by clicking on the emoji face on the comment the developer made, because if for example 100 users decide to send a "thank you" to the developer, the whole issue becomes a BIG mess and it's way harder to find useful information to work on.

@kisak-valve My apologies I didn't realize it was legally problematic but also when I said hope this helps I was referring to the developers editing the proton code. (as in giving a direction to what to fix)

@fjorgemota Thanks for pointing that out I'll to emojis from now on. Also

(so please, don't create big expectations just because someone apparently is working on a fix..).

My apologies I never meant to imply this.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

CodingKoopa picture CodingKoopa  路  1158Comments

MagicRB picture MagicRB  路  531Comments

StructByLightning picture StructByLightning  路  241Comments

leillo1975 picture leillo1975  路  235Comments

trymeouteh picture trymeouteh  路  525Comments