It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
When I try to start up a new game of Firewatch It just gives me a black screen with the Campo Santo Logo. It just sits there forever. I am able to get to the main menu which allows me to start or load a game but when I choose a new game this happens. System specs:

AMD FX-8350, 16GB DDR3-2133 CL10, MSI R9 390 8GB (FGLRX drivers), Linux Mint 17.3 64

I have tried open source drivers and the game is too laggy on the start menu to even start the game. I have tried with just one monitor instead of 2, have tried setting all settings to low, turning off vsync, 1024*768 resolution, running the actual file instead of the icon on the desktop, starting the game from different save slots, any ideas ?



I'm pretty sure it is an issue with FGLRX drivers. I have tried on multiple systems that have the same issue and so far that is the only constant between them.
Post edited May 19, 2016 by shylock.596
avatar
shylock.596: When I try to start up a new game of Firewatch It just gives me a black screen with the Campo Santo Logo. It just sits there forever. I am able to get to the main menu which allows me to start or load a game but when I choose a new game this happens. System specs:

AMD FX-8350, 16GB DDR3-2133 CL10, MSI R9 390 8GB (FGLRX drivers), Linux Mint 17.3 64

I have tried open source drivers and the game is too laggy on the start menu to even start the game. I have tried with just one monitor instead of 2, have tried setting all settings to low, turning off vsync, 1024*768 resolution, running the actual file instead of the icon on the desktop, starting the game from different save slots, any ideas ?

I'm pretty sure it is an issue with FGLRX drivers. I have tried on multiple systems that have the same issue and so far that is the only constant between them.
\


It's not an issue with the FGLRX drivers, I'm seeing the same thing on an nVidia GeForce GTX 860m based laptop (core i7 4770HQ) , also 16 GB RAM, running 64-bit Xubuntu 16.04, nVidia driver 361.42.. I edited the start.sh script and changed the line:

./"fw-x86.64"

to

./"fw-x86-64" 1>start.log 2>start.err

and ran it. When I went to start a new game and hit the hang at the camp logo, I hit <Ctrl><Alt><Backspace> (which I have to do to get out of the game), and checked the contents. start.err was empty.

start.log:
Set current directory to /home/hbc/GOG Games/Firewatch/game
Found path: /home/hbc/GOG Games/Firewatch/game/fw.x86_64
Mono path[0] = '/home/hbc/GOG Games/Firewatch/game/fw_Data/Managed'
Mono path[1] = '/home/hbc/GOG Games/Firewatch/game/fw_Data/Mono'
Mono config path = '/home/hbc/GOG Games/Firewatch/game/fw_Data/Mono/etc'
displaymanager : xrandr version warning. 1.5
client has 3 screens
displaymanager screen (0)(eDP-1): 1440 x 900
Using libudev for joystick management


Importing game controller configs

....and that's all i get. I wondered if it had a problem with my external mouse and keyoard, so I tried again without them attached. Same thing happened.

Someone posted something similar in the Steam forums, but never got an answer from either devs or the community as most people were focused on the naming issue Firewatch's linux client had when it first came out.

https://steamcommunity.com/app/383870/discussions/3/412446292776598825/#c412446292776615731
avatar
shylock.596: When I try to start up a new game of Firewatch It just gives me a black screen with the Campo Santo Logo. It just sits there forever. I am able to get to the main menu which allows me to start or load a game but when I choose a new game this happens. System specs:

AMD FX-8350, 16GB DDR3-2133 CL10, MSI R9 390 8GB (FGLRX drivers), Linux Mint 17.3 64

I have tried open source drivers and the game is too laggy on the start menu to even start the game. I have tried with just one monitor instead of 2, have tried setting all settings to low, turning off vsync, 1024*768 resolution, running the actual file instead of the icon on the desktop, starting the game from different save slots, any ideas ?

I'm pretty sure it is an issue with FGLRX drivers. I have tried on multiple systems that have the same issue and so far that is the only constant between them.
avatar
zoward: \

It's not an issue with the FGLRX drivers, I'm seeing the same thing on an nVidia GeForce GTX 860m based laptop (core i7 4770HQ) , also 16 GB RAM, running 64-bit Xubuntu 16.04, nVidia driver 361.42.. I edited the start.sh script and changed the line:

./"fw-x86.64"

to

./"fw-x86-64" 1>start.log 2>start.err

and ran it. When I went to start a new game and hit the hang at the camp logo, I hit <Ctrl><Alt><Backspace> (which I have to do to get out of the game), and checked the contents. start.err was empty.

start.log:
Set current directory to /home/hbc/GOG Games/Firewatch/game
Found path: /home/hbc/GOG Games/Firewatch/game/fw.x86_64
Mono path[0] = '/home/hbc/GOG Games/Firewatch/game/fw_Data/Managed'
Mono path[1] = '/home/hbc/GOG Games/Firewatch/game/fw_Data/Mono'
Mono config path = '/home/hbc/GOG Games/Firewatch/game/fw_Data/Mono/etc'
displaymanager : xrandr version warning. 1.5
client has 3 screens
displaymanager screen (0)(eDP-1): 1440 x 900
Using libudev for joystick management

Importing game controller configs

....and that's all i get. I wondered if it had a problem with my external mouse and keyoard, so I tried again without them attached. Same thing happened.

Someone posted something similar in the Steam forums, but never got an answer from either devs or the community as most people were focused on the naming issue Firewatch's linux client had when it first came out.

https://steamcommunity.com/app/383870/discussions/3/412446292776598825/#c412446292776615731
You are right. I just tried it on my GTX 960 which is in the same system as before and using the 352.63 drivers and had the same issue. I submitted a support ticket to Campo Santo so we'll see how good their support is.
I had the same problem all the time, no matter what i was trying.
But I read on the internet, that you have to install "libsdl2-2.0-0" and this solved the blackscreen problem for me, too.
avatar
Thezips: I had the same problem all the time, no matter what i was trying.
But I read on the internet, that you have to install "libsdl2-2.0-0" and this solved the blackscreen problem for me, too.
This worked - thanks!
avatar
Thezips: I had the same problem all the time, no matter what i was trying.
But I read on the internet, that you have to install "libsdl2-2.0-0" and this solved the blackscreen problem for me, too.
It worked for me as well. You just put Campo Santo to shame. I have been trying to get some kind of fix for this out of them for over 2 months and you fix my issue in seconds. They hadn't even responded to me in over a month. Well done.