Looks like this game would benefit from Media Foundation support.
I was unable to get this game to start. Other people have said to run this in fullscreen mode, however I could not a settings file where I could change that.
I was unable to get this game to start. Other people have said to run this in fullscreen mode, however I could not a settings file where I could change that.
The game ran for me, but all the models/textures failed to show. Just the menu appeared.
To change to fullscreen without opening the game Right Click Outward > Properties > Local Files > "Browse Local Files..." > Open OptionSettings.oos with an editor > Change (line 7 for me) <Windowed>1 OR 2</Windowed> to <Windowed>0</Windowed>
Hopefully that works for you. If not you'll probably need to post your steam-794260.log(?).
I tried editing that, but I don't have a OptionSettings.oos file in <steamdir>/data/Steam/steamapps/common/Outward/. I'm not sure if there is another place settings files are stored.
Quite probably that file isn't created until first run... Here's mine: https://gist.github.com/HanFox/01111fe6a2c5c9ff01bc2a7af1d82809
That didn't work, unfortunately. When I try to run the game, I get this error. I'm not sure where to find the steam-794260.log file you asked about, but this is the output_log.txt generated by the game.
Edit: strangely, it seems to be working if I just run the exe through my system's wine version (4.3). It seems like the menu is broken for me though, so I can't do anything.
Interesting, that it works via your system's Wine. All the more reason to get the Proton specific log, I guess.
To get the steam-794260.log you need to change the Launch Options to PROTON_LOG=1 %command% and it'll output the log to your home directory.
I guess you should also supply your System Information from Steam's Help menu, too.
Using esync crashes the game when I use RADV/ACO and crashes my graphics driver with RADV/LLVM. Using fsync yields better performance, than esync disabled, but esync was the fastest.
Gentoo x64
Kernel 5.4.3
RX Vega 64
Mesa 19.3.1/LLVM 9.0.1
(If this is the wrong place for this feel free to delete) Anyone have any insight or issues with controller support and this game? I'm unable to get the game to recognize a wired Xbox 360 Controller thru steam. Other games detect the controller just fine.
I cannot run this game through Steam Play with Proton. It apparently starts, spawns a few processes, then stops automatically after a few seconds.
Here is my Proton log for the game.
Here is the STDOUT from Steam when the game is launched.
My config:
I have a friend with a very similar system and he can run the game without problems using Proton 5.0-9, as reported on ProtonDB.
I can start the game with Wine, but the start menu does not appear. I also tried creating the OptionSettings.oos manually (using @HanFox's file), to no avail.
Hello @adrfantini, ~are you using vulkan-icd-loader 1.2.153-1 or 1.2.153-2? (if you're using 1.2.153-1 then update your system)~ you're definitely using vulkan-icd-loader 1.2.153-1 and this is your problem. Update your system packages.
Looking at the log, Vulkan failed to initialize with err:vulkan:wine_vkCreateInstance Failed to create instance, res=-6. Also, your system information tells us you don't have 32 bit vulkan drivers for the Intel chipset as well. Please install lib32-vulkan-intel if you want to experiment with that.
@kisak-valve Wow, that was quick and accurate. Good job!
You are completely right. I updated the day before so I did not think it could be an issue. Indeed updating and installing lib32-vulkan-intel fixed it; I can now start the game. I'll test a bit more in the upcoming days.
In the meantime, I thank you very much.
Outward (794260)
Issue transferred from https://github.com/ValveSoftware/Proton/issues/4679.
@HenryJk posted on 2021-03-19T20:27:45:
Outward794260GTX 1650 Max-Qnvidia 560.565.11.7-arch1-1File is too big
Memory leak and performance degradation every time loading new area. It seems that rendered objects are not culled properly when changing area.
Start a new game, go in and out of the starter town back and forth. The memory spike is the highest the first time going out and in the starter town.
Hello,
I am not sure whether this is correct place to ask, as it looks like more of an issue with steam deck gamemode.
I am playing Outward on steam deck, with default proton version.
Performance is reasonable, and control with controller works.
But when I tried connecting keyboard and mouse (while running through gamemode), I am not able to control camera correctly with mouse. It only spins and looks up to the sky. I cannot lower it and look normally around me. In menus mouse works correctly.
In desktop mode keyboard+mouse works as expected.
EDIT: Controls with steam deck emulated wasd+mouse also works in gamemode, but not physical mouse.
steam-794260.tar.gz
system info
For me its not black its pink and changing screen method doesn't work. full screen, borderless or windowed is the same.
Pink screen at starting game, i use the definitive edition.
the games and start menu is working fine.
my hardware info => https://gist.github.com/BipB0p/fa28928b8dd75a920e56088b97f5c058
getting this as on terminal => winegstreamer warning: videobox0: not negotiated
winegstreamer warning: videobox0: ../src-gstreamer/libs/gst/base/gstbasetransform.c(1431): gst_base_transform_reconfigure_unlocked (): /GstBin:bin0/GstVideoBox:videobox0:
not negotiated
proton 5.0-9x1 2020-09PROTON_LOG=1x1 2019-04PROTON_USE_WINED3Dx1 2019-04
Compatibility Report
System Information
I confirm:
steam-794260.log
Symptoms
Reproduction
For the videos just run the game, and instead of company logos it will be black for ~10 seconds before loading the menu.
For the black screen open Settings scroll down to Display > Windowed Mode and set to either Borderless or Windowed.
In relation to SS Shadows make sure they're enabled in Settings > Click computer screen icon > Scroll down to "SS Shadows" and make sure they're on. A Graphics Quality setting of Medium or higher is preferable for testing (I use High as a base).
Go somewhere with torches (such as the Cierzo Storage under the starting town) and stare at the torches for a while. See GPU % climb.
I suspect this is just a performance issue between RADV vs the Windows driver.
Using
PROTON_USE_WINED3Dcauses noticeable jittering and the general GPU usage is the same.