search

ValveSoftware / Proton

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

Project Winter (774861) #3812

Open Raboebie opened 4 years ago

Raboebie commented 4 years ago

Compatibility Report

System Information

I confirm:

Log File attached. Worth mentioning the game uses vivox for in game chat functions. Could not find any relevant errors in the log. But did find lines mentioning the dll file being loaded as native. steam-774861.log

Symptoms

Game runs perfectly in every aspect except for voice chat and in game chat functions. This all seems te be related to vivox not loading correctly.

Reproduction

1) Install and run game 2) Go to settings -> Audio 3) Voice and chat will show as "Disconnected" and you cannot test you input device. 4) Pressing the P2T button while in game does nothing and text chat does not send or appear for anyone in game.

rstrube commented 4 years ago

@Raboebie does rebuilding FAudio with FFMpeg / WMA support fix this issue for you? Please see: https://github.com/FNA-XNA/FAudio/wiki/FAudio-for-Proton for more information. In the past this has helped me with several other games where audio support was lacking!

Raboebie commented 4 years ago

Thanks for the info @rstrube. I will give that a go and see what it does. Although I don't know if this is a WMA codec problem.

rstrube commented 4 years ago

@Raboebie yeah it's probably a long shot. The other thing I thought of is if a Windows install of the game copies the vivox DLLs somewhere else. If we can get hold of those DLLs, we could place them in the bin folder for the game and set them to "native" in the wine prefix. This has helped me in the past, but it's definitely a trial and error approach!

Raboebie commented 4 years ago

They seem to live here on a windows install Steam\steamapps\common\Project Winter\ProjectWinter_Data\Plugins

VivoxNative.dll vivoxsdk.dll

I'll give that a go as well. Just not at me rig for a while so will test this as soon as I am back.

Raboebie commented 4 years ago

Reporting back. Tried both building fAudio and using the latest GE build of Proton.

Also tried marking libs as native. Didn't change anything for me unfortunately.

abriasffxi commented 4 years ago

Did you put the libs in the directory with the bin when you marked native?

I was going to start looking at this a little tomorrow, but the VivoxNative.dll has a lot of functions and it's hard to tell where to start. The logs are going to be brutal.....

Raboebie commented 4 years ago

Hello,

Yes I did indeed! Ket me know if I can help you in some way.

On Sat, 25 Jul 2020 at 09:22, Chuck notifications@github.com wrote:

Did you put the libs in the directory with the bin when you marked native?

I was going to start looking at this a little tomorrow, but the VivoxNative.dll has a lot of functions and it's hard to tell where to start. The logs are going to be brutal.....

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/Proton/issues/3812#issuecomment-663822100, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABGCYYQ27BGKGFXUSOF7WJ3R5KB3RANCNFSM4MSIFPEA .

abriasffxi commented 4 years ago

Ok thanks - I made it past that. There's a few people in the Project Winter discord (they created a Linux troubleshooting page for us) who are working on the vivox issue.

On Sat, Jul 25, 2020 at 3:00 AM Dihan Kapp notifications@github.com wrote:

Hello,

Yes I did indeed! Ket me know if I can help you in some way.

On Sat, 25 Jul 2020 at 09:22, Chuck notifications@github.com wrote:

Did you put the libs in the directory with the bin when you marked native?

I was going to start looking at this a little tomorrow, but the VivoxNative.dll has a lot of functions and it's hard to tell where to start. The logs are going to be brutal.....

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub < https://github.com/ValveSoftware/Proton/issues/3812#issuecomment-663822100 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/ABGCYYQ27BGKGFXUSOF7WJ3R5KB3RANCNFSM4MSIFPEA

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/Proton/issues/3812#issuecomment-663825533, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE5W3DP5AZLE3EX3FA5QBDDR5KGITANCNFSM4MSIFPEA .

-- Charles Anderson abriasffxi@gmail.com

Bluenix2 commented 4 years ago

Yes, but we're not having much luck other than "conspiracy theories" and thoughts basically. But please join if you'd like to have any form of discussion in there: https://discord.com/invite/projectwinter

Raboebie commented 4 years ago

Excellent. Thanks for the update!

On Sat, 25 Jul 2020 at 23:01, Chuck notifications@github.com wrote:

Ok thanks - I made it past that. There's a few people in the Project Winter discord (they created a Linux troubleshooting page for us) who are working on the vivox issue.

On Sat, Jul 25, 2020 at 3:00 AM Dihan Kapp notifications@github.com wrote:

Hello,

Yes I did indeed! Ket me know if I can help you in some way.

On Sat, 25 Jul 2020 at 09:22, Chuck notifications@github.com wrote:

Did you put the libs in the directory with the bin when you marked native?

I was going to start looking at this a little tomorrow, but the VivoxNative.dll has a lot of functions and it's hard to tell where to start. The logs are going to be brutal.....

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <

https://github.com/ValveSoftware/Proton/issues/3812#issuecomment-663822100

, or unsubscribe <

https://github.com/notifications/unsubscribe-auth/ABGCYYQ27BGKGFXUSOF7WJ3R5KB3RANCNFSM4MSIFPEA

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub < https://github.com/ValveSoftware/Proton/issues/3812#issuecomment-663825533 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/AE5W3DP5AZLE3EX3FA5QBDDR5KGITANCNFSM4MSIFPEA

.

-- Charles Anderson abriasffxi@gmail.com

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/Proton/issues/3812#issuecomment-663905619, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABGCYYVHSBZJIP4QRLJZFB3R5NB2NANCNFSM4MSIFPEA .

Bluenix2 commented 3 years ago

With the most recent update, as of yesterday, a fix has officially been made. So that all Vivox verification is done server side, and is no longer handled by the client. This means the token is generated by the server and for our case, it means we always get a successfully generated token.

A few users have reported being able to launch the game and use voice since this update. So I ask everyone to help verify that this is fully fixed and try to launch the most recent update and connect to Vivox.