paperspace
Member
Can you turn off the crosshair yet?
-
Hey Guest. Check out your NeoGAF Wrapped 2025 results here!
Firewatch PC performance thread
- Thread starter viveks86
- Start date
Inspectah_Deck
Member
http://steamcommunity.com/games/383870/announcements/detail/990053830261398188
Awesome!
Can´t wait to try out the performance improvements.
The shadow map LOD distance on High is still very low.
I assume this is the end of the line and there's nothing Campo Santo can do.Inspectah_Deck
Member
I finally played through this yesterday.
Very touching and great game.
I loved the story, please more of that!
Performance on the other hand was all over the place.
Up-to-date GOG version.
FX-8350 @4.5Ghz
Fury Nitro
16GB RAM
Game on SSD
3440x1440 @75Hz
Limited to 74fps for Freesync.
On Day 1 I had locked 74fps in every area.
Then on the following days until the end I got framedrops all the way down to the mid 30s without any noticable reason (area around the lookout).
Also the microstutter is very strong in this game.
Got mostly 60-74fps during my playtime, but felt more like 30-40fps.
I hope one day this game will be ported to a better engine.
This masterpiece must be conservated with a flawless PC version.
(Or I hope we can at least bruteforce through all the problems with future GPU generations.)
Very touching and great game.
I loved the story, please more of that!
Performance on the other hand was all over the place.
Up-to-date GOG version.
FX-8350 @4.5Ghz
Fury Nitro
16GB RAM
Game on SSD
3440x1440 @75Hz
Limited to 74fps for Freesync.
On Day 1 I had locked 74fps in every area.
Then on the following days until the end I got framedrops all the way down to the mid 30s without any noticable reason (area around the lookout).
Also the microstutter is very strong in this game.
Got mostly 60-74fps during my playtime, but felt more like 30-40fps.
I hope one day this game will be ported to a better engine.
This masterpiece must be conservated with a flawless PC version.
(Or I hope we can at least bruteforce through all the problems with future GPU generations.)
Is there really a fix for my gpu usage? With everything maxed out, sometimes the fps drops down to ~45 while both the gpu and cpu are not being completely used (~50%/60%). Ram is not the problem either, since it uses about 4gb. Even though it stays most of the time at 60, for example around my tower and on the inside of it, it always drops to the ~50s.
I noticed that if I set 'World Details' to high instead of ultra, the game runs much smoother, with no fps drops at all (only the engine caused fps drops to ~56 when changing area that everyone reports).
Is there really a solution to this fps cap while not even running out of power both cpu and gpu-wise?
If there's no solution, is there any notable difference between the 'world details' option high and ultra?
I've got a gtx 1060 6b/i5 3550 with 8gb RAM ddr3.
I noticed that if I set 'World Details' to high instead of ultra, the game runs much smoother, with no fps drops at all (only the engine caused fps drops to ~56 when changing area that everyone reports).
Is there really a solution to this fps cap while not even running out of power both cpu and gpu-wise?
If there's no solution, is there any notable difference between the 'world details' option high and ultra?
I've got a gtx 1060 6b/i5 3550 with 8gb RAM ddr3.
Frequent stutter and I always crash on the examine communication wire dialogue.
Stutter happens in nearly every indie game I've played over the last year which is completely crazy since they all use sprites or low poly. Technically the devs' faults but I ascribe all of the blame on Unity being the standard engine.
Stutter happens in nearly every indie game I've played over the last year which is completely crazy since they all use sprites or low poly. Technically the devs' faults but I ascribe all of the blame on Unity being the standard engine.
Would you mind sharing your config? You can DM if you don't want to post here.
Yeah, I'll send them in 8 hours when I get home. Really cool that you do personal support this far from launch.
We were never able to chase it down. It seems related to our audio middleware partially flushing it's cache or some other memory management thing we weren't able to find and kill, in a notable way, on some configs if you don't use the radio for a while. Sorry I don't have a better answer.
Oh ok, thx for answering. I was gonna start messing around with settings but it sounds like there's a less obvious problem happening here so I'll just try and ignore it.