Warframe (230410) #167
Comments
kisak-valve
added
the
Game compatibility - Unofficial
|
gentoo 17.0 same thing https://appdb.winehq.org/objectManager.php?sClass=version&iId=29230 Warframe/Downloaded/Public/Tools/ |
|
i tried the proton env variables one by one to see if it worked that way and it doesnt |
|
Someone on Warframe forums found a workaround. Fix seems to be something easy on dev side, altho probably not too hard on Steam's side. |
|
Same here. Using Arch Linux with the latest proprietary nvidia drivers. Huge compliments to the Proton team for making this possible! |
|
@XANi i ran that script and it clearly did something but still i cant get warframe to run :( now it gives a wine debug error if i launch it from the terminal |
|
Runs perfectly on Lutris with this workaround launcher shellscript. But obviously this is about steam. The game does not start because of the launcher. This script mentioned above replaces the launcher and updates the game. The developers should just implement this script or make their launcher linux/wine compatible. |
|
Just to note: The game itself is broken in proton, this is on proton's end, as it runs perfectly fine in wine staging with the appropriate winetricks. For any Proton devs looking into this: when Warframe.exe tries to launch, it thinks it's offline and can't download the cache manifest in needs to continue loading: The launcher issue is something DE would have to fix, which I've posted about here: Who knows if I'll actually get a response though.. I've posted about this before. This is why I ended up just making my own launcher. Here is my launch script (with README) which is a drag and drop solution if you have the game installed: |
|
Issue exists on Solus w/AMD RX 580 |
|
Figured out the WINE bugs that break the game and the patches that fix them!
FIX: Fixed by staging patchset wuauserv-Dummy_Service, which I believe ZF (another staging maintainer) is working on getting merged to wine mainline.
If 3 gets fixed in wine this game will not rely on any MS native libraries |
|
Even more digging.. this is the last thing xaudio2 tries to do before spoamming a bunch of CreateFX is in xapofx.c EDIT: and both have A quick fix can probably be added by just allowing them to be identified like so: along with some mumbo jumbo that makes them do nothing, but idk right now. 7:30 am now, time for some zzz's. Hope someone's able to do something useful with my blabber |
|
alright, I've managed to create a patch that implements FXEcho, which fixes the bug listed above: https://gitlab.com/snippets/1748561 The game also needs xaudio2_7-OnVoiceProcessingPassStart xaudio2_7-WMA_support xaudio2_CommitChanges However now IXAudio2Impl_CommitChanges needs to be implemented as it's currently just a stub that returns S_OK, which results in the game crashing due to not knowing how to properly commit the changes which pass WMA audio to ffmpeg to be converted for OpenAL. By default CommitChanges returns a stub and E_NOTIMPL, the xaudio2_CommitChanges patch in staging makes it return S_OK, which allows the game to start, but it then crashes when trying to do any wma->openal decoding: EDIT: I'm not sure if CommitChanges needs to be implemented. The stub may work just fine, but the WMA patch for xaudio2 causes |
|
warframe doesnt load from me as well |
|
at the moment I've got a workaround for the launcher and xaudio2_7 that allows proper updating, cache defragging, and getting in game and logging in. After that, for some strange reason proton just forces the client closed? I've tried turning debugging on but it doesnt show anything useful, just immediately closes, not even a safe shutdown. If anyone's willing to try to figure out why proton's straight up closing the app here's my repo, just follow the readme: https://gitlab.com/GloriousEggroll/warframe-linux/tree/steamplay-proton Some dev input would be really useful here as to why proton just straight kills the running client |
|
@GloriousEggroll i tried running your script but if i append --firstrun to the launch options it doesnt recognize it and if i dont do it it doesnt update the laucher, got any help? |
|
@davidbepo for any issues regarding my launcher please use the issues section of my gitlab as the official launcher bug and in-game bugs reported here are not related to my launcher, for the sake of keeping this bug report on point |
|
With the patched wininet dll, my own launcher executable, and a bit of tinkering, I've gotten it to go ingame and run at near native performance. On a i7-7700K and a RX 580 with Mesa 18.1.6. Something seems to cause the game to freeze after a while though, leaving it just sitting there eating two full cores worth of CPU. Edit: |
|
welp. as of latest update I can't get the game to launch at all any more. keep getting @ananace I'd much prefer your solution to mine as bash script and a ghetto wrapped fake exe are not exactly ideal, how would one go about compiling it? (edited original comment as I realized it was for a win executable to be wine friendly) as for the asset loading - thats actually the shader cache filling up, its fine after that |
|
@GloriousEggroll hmmm Still works here with your scripts. I am running the steam version but instead of renaming the Launcher.exe I just added it as Launcher-Lutris.exe and Launcher.sh (also create a Launcher-Lutris.bat so wine can run it through CMD, which I could've done straight with the exe). Anyway, I don't execute it through steam, so I don't have to deal with the naming convention and etc (also the binaries are available to me through my windows install, so this was easier). I do get a stuck screen on a CMD like shell, which I just press ctrl+c and it starts warframe, eventually |
|
@llitz the lutris wine-steam version is not the same as the steamplay-proton version. they launch in very different ways, with proton having many more environment variables passed from native steam. additionally proton launches things a much different way then just using wine whatever.exe -some -arguments. its a lot more annoying :/ |
|
I have been running it manually and mixing some libraries, I should have
thought about that: it has been a long day. I will report back if I can
pinpoint what makes it run.
…On Fri, Aug 31, 2018, 12:24 AM Thomas Crider ***@***.***> wrote:
@llitz <https://github.com/llitz> the lutris wine-steam version is -not-
the same as the steamplay-proton version. they launch in very different
ways, with proton having many more environment variables passed from native
steam
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#167 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AVbEO2fCQcu-Ha0-CR1_tcYyTKZ84ZgPks5uWNaOgaJpZM4WIbhT>
.
|
|
@GloriousEggroll The project should just be a regular Visual Studio 2017 solution, the code's a bit of a mess though as I just grabbed an old launcher from an abandoned MMO I helped develop - which as it turns out chose an almost identical method of distribution as Warframe did. The only thing that executable doesn't do is run the DX redistributable setup, the wininet DLL replacement, or the xaudio override. And I somehow get the feeling that you don't particularly want to do such things through a native PE, probably better to keep them as a Linux bash-script. I did render two minutes of video before bed. Mainly to have an example of the choppiness I'm experiencing, though I later found out that an application was loading the disk rather heavily in the background, so it might actually be much more playable than it looked at first. |
|
So I've been working with ananace on his launcher and we have it working very well. I've also discovered WHY warframe was randomly closing - turns out if I plug a controller in then start the game - it magically stays open. If I don't start the game with a controller plugged in.. it closes after a short time. Both my launcher and ananace's had this same problem so it seems like it's something to do with how controllers/controller profiles are handled on steams end. also, the game benefits a lot from the PoE stutter patch on dxvk as well. |
|
i finally got the game to run with @GloriousEggroll launcher but there are a lot of issues
|
|
@davidbepo I've stated this once already - any problems with my launcher please post on my gitlab issues section. NOT here. |
|
@GloriousEggroll i think the issues that im having might be valuable for proton developers specially since some of them are not because of launcher |
|
the language problem is due to my launcher |
|
@braiam wf is pretty shader heavy, it's been that way for as long as I can remember, at least a few years even off fresh installs |
|
@andrewgrasman correct, but I don't expect to download the complete shader archive for a game that I just played yesterday. It's supposed to download new shaders, not all of it. |
|
It contains shaders precompiled for many different GPU architectures and revisions. And they also go over your local cache to see if there are any you've produced that are worth uploading to their collective database. It appears to re-verify the entire cache periodically, sometimes almost daily if new shaders are being discovered by players. Edit: Also, for example, A Hat In Time also has a 12-13GB shader cache, dwarfing the game's total install size. |
|
@kode54 correct again, except that today is downloading 13GB again when it downloaded 12 less than 24 hours ago. The game had no updates between yesterday and today, there's no way there are already 13GB worth of shaders. |
|
Warframe was the reason I turned off shader caching on my Steam Deck because it was a pain. |
|
I have to keep it on for some games, as it also downloads transcoded videos for some games. The issue appears to involve it just indiscriminately redownloading the entire cache every time. I guess they don’t know how to parity check and use delta updates? With the data sets being so sparsely unrelated, perhaps they should just poop out millions of hash named files instead of trying to maintain a gigantic mono file blob per game. |
|
So this might not be useful to everyone but was crucial for me to launch the game properly. I have two RTX Titan GPUs but they are not connected thru NV-Link. To run most games with DXVK, I have to force the game to run on the GPU connected to the screen. For that, I use vkdevicechooser which allows me to set launch option as such:
Without those env. variables, I get the famous black screen after clickling "play" in the launcher. So if you also have multiple unconnected GPUs and you get a black window when running the game, try to disable hardware acceleration in the launcher, stop the process, set the above mentioned environment variables (after installing vkdevicechooser). You can now re-launch the game and it should work properly. |
|
Warframe takes an absurd amount of time to process it's Vulkan shaders on my PC (about 7 hours!) and it does this every single time an update to both the game's shaders and my PC happens when I'm using arch based distros. This is a problem because it means my CPU usage is extremely high on steam due to having background shader processing enabled. Is there any fix to this? If I skip the shader caching, it's like it forgets the current shaders, and stutters on new assets all over again. Current setup: |
|
@WMan22 try turning off "Shader pre-caching" all together and see if that affects your gameplay at all. |
I did try skipping it, and the thing is, as stated in the post you're replying to, the game won't remember the shaders it does cache unless I let this do its thing. If I don't let steam process the vulkan shaders for like 7 hours, then every time I boot up warframe, it has to heavily stutter on new asset load every time, rather than just every time my drivers update. This happens whether I turn off shader pre-caching in the actual warframe launcher (I.E. not steam) or not. |
|
About shaders cache - I figured out that you can disable shader cache option in launcher and gigantic 10+ gb downloads (in my case it was 16+) seems to gone. Now it downloads 400-500mb. |
|
Hey guys, looks like this thread has been pretty active for the last 6 years... I've just bought a 1TB OLED Steam Deck and cannot get this game to launch at all on Valve's Proton 8.0-5, 9.0-3, or Experimental. On these versions the WF launcher will not appear. Both Steam's stdout/stderr and the proton log file appear to indicate some kind of segfault. I am able to get the launcher to start on Valve Proton 7.0-6 but WF crashes as soon as I hit "Play". Since this thread is quite long and extends over multiple years I'm having a tough time piecing together what steps I should take next. Anyone got a summary of the current status of WF support on Linux/Deck? I really don't understand what I need to do to make this work. Edit: switching to the beta channel and letting the system update complete seems to have fixed whatever was the issue. I'm now able to launch and run on proton experimental. |
|
@tekulvw To be fair, I do not own a steamdeck myself and I have switched to Proton GE for most games quite a long time ago, but Warframe is usually one of these perfect games on stock settings as well. Anyway, I'm glad you got it working eventually. The only thing that I could think of is to ensure you're running the most up to date os version as the game should run perfectly on all included Proton versions. |
|
@tekulvw I would try to get the logs out of the system. The launcher is just a chrome screen. |
|
Using gamescope to workaround a crash caused by tabbing out of the client, I've seen lighting effects being too bright, in a way that doesn't match the scene. I've seen examples of certain features being a bit too bright, or green, or flashing, last of which I have a video of. Restarting usually fixes this, but it shouldn't happen.
|
|
#167 (comment) |
|
Fcitx5 (input method) can't put text into in-game chat or any in-game text box. Copy and paste text from another app is possible. But sometimes ctrl+v also doesn't work. |
|
Are you by any chance using bigpicture / gamepad when this is happening? |
Keyboard and mouse only. And no big picture because I need to alt-tab to copy text from somewhere else. |
|
Does anyone have the black texture in front of the gate in Cetus?
|
|
Daily 20 GiB shader download are back. @Postnozet I've only seen that when players use specific aesthetics items. On rare occasions, the "next" room doesn't load, and I'm stuck at the door. |
|
Warframe (230410) - Unstable frame rates after 40 minutes Issue transferred from #8245. Compatibility Report
System Information
I confirm:
SymptomsAt the patch where the Warframe 1999 demo released I started experiencing frame rate issues in Warframe but only after about 30-40 minutes of playing. Up to then I get solid 60 frames per second then suddenly it becomes a laggy mess. I have checked for back ground processes starting or something similar but a simple quit and restart of Warframe resolves the issue. All game modes affect solo or online. I have tried Proton Experimental and 9.0-3. Changing graphics settings to minimum does not resolve the issue either. Verified PC is not overheating, max core temp was 55 so well below anything I would worry about, immediate restart also gives another 30-40 minutes of play before issues start again so 99% sure its not heat related. Uninstalled and reinstalled Warframe completely. Let shaders precompile in steam, skip shaders, disable shaders, all the same result. DX11 and DX12 same result. Issues are not present when running the game in windows. ReproductionStart game, begin playing after about 30-40 minutes begin experiencing major frame rate instability resulting in very poor game play |
|
Hello @NoviceOtter, your symptom reads like ValveSoftware/steam-for-linux#11446. Check if the Steam overlay is enabled and working, otherwise, the workaround in that issue report might avoid the issue. |
|
Thanks for pointing me to that thread. Definitely looks like the same issue as what I’m experiencing. Will try the work around tonight and will report back if it fixes it. |
|
@NoviceOtter I believe I ran into the same issue, and was able to solve it by disabling steam game recording for specifically Warframe, without losing the steam overlay. I'm not personally sure how different that is from adding the LD_PRELOAD="" launch option, but it may be worth trying |
|
@atimeofday @kisak-valve LD_PRELOAD="" and turning the steam overlay back on resulted in a complete fix |
|
Before it was 12-14GB of shaders, now it is 24GB of shaders. I only opened warframe last night after 3 days of not playing, why is this still happening? I am using Proton 9.0-3. |
|
Anyone else having trouble loading after the game today, takes like 15 minutes to launch then fails to desktop. |
|
Nope, works fine. Only FPS is lower on new location (or tile set), but it is about DE optimizations. |
and others
as per title i installed warframe and it doesnt work, if you want me to provide any log files tell me the instructions and i will do it
system and os specs
apu: ryzen 5 2400G using the vega 11 integrated graphics
os: manjaro linux
mesa: 18.1.6
llvm: 6.0
kernel: 4.18.3
using proton 3.7 from the steam beta client
by the way huge thanks to valve for bringing this huge advancement for linux gaming
The text was updated successfully, but these errors were encountered: