The Light Keeps Us Safe

The Light Keeps Us Safe

iwanPlays Oct 14, 2018 @ 12:57pm
Performance
I love the game! Did not expect I would enjoy YABH2 so much!

One huge issue is the performance. There are no options we can change to get a decent (60) FPS. I'm using a GTX970 which I mainly upgraded to (from GTX750Ti) for playing Tölva. :)

https://steamcommunity.com/sharedfiles/filedetails/?id=1539333779
Originally posted by Phunk:
Hi, thanks for posting! We'll be dropping in more quality options in one of the EA patches, once we've finalised what settings we can mess with without losing the atmosphere.

In the meantime, can you let us know the rest of your spec, please, and the FPS you're seeing?
< >
Showing 1-8 of 8 comments
The author of this thread has indicated that this post answers the original topic.
Phunk  [developer] Oct 14, 2018 @ 3:33pm 
Hi, thanks for posting! We'll be dropping in more quality options in one of the EA patches, once we've finalised what settings we can mess with without losing the atmosphere.

In the meantime, can you let us know the rest of your spec, please, and the FPS you're seeing?
ianriches Oct 15, 2018 @ 3:00am 
I'm having no frame rate issues with my GTX 970 (partnered with an I7-4790k, 16GB RAM) - but I'm only playing at 1680x1050, so not pushing it on the resolution front...

I don't think I've seen FPS below 60, and it's often above 100.
MissLaKitti Oct 15, 2018 @ 7:07am 
I acutlly play this game too, i know it is a early access game, the performance can be in the developing time checket, why was it here not possible? or was it know that it have a lot of performance problems. the game runs over 6.788mb of RAM and trust me it doesnt matter which grafikcard is in use.

(GTX 1060 / 1080)
iwanPlays Oct 18, 2018 @ 10:22am 
@phunk I just published the second video. At 1080p you can actually see the steam FPS at the bottom left. (video #1 also has fps indicator)

https://steamcommunity.com/sharedfiles/filedetails/?id=1542001895

The most fps problems (36fps most of the time) is in the third video (publishing in 1 week, it's the level that I enter at the end of the video in this post.

The rest of my specs: i5-6600, 32GB RAM (DDR4-2132 (1066MHz))

Mainboard B150M PRO-VDH (MS-7982) 1.0
Chipset Skylake rev07
Southbridge B150 rev31

This is while recording with OBS using NVENC (so as far as I understand, the GPU encodes the video).

PS: AA and shadow quality will be the most important options I think. Could it be that you don't have LOD models?
Last edited by iwanPlays; Oct 18, 2018 @ 10:30am
Phunk  [developer] Oct 18, 2018 @ 1:06pm 
We do have LOD models.

On that spec you should see much higher framerate (I get higher than that on my test machine at half the spec). Could you share a log file please, from a session where you've seen the low FPS? By default you'll find that here:

C:\Users\<you>\AppData\LocalLow\Big Robot Ltd\The Light Keeps Us Safe

Thanks in advance!
Last edited by Phunk; Oct 18, 2018 @ 1:06pm
iwanPlays Jan 1, 2019 @ 6:39am 
@Phunk sent DM on Twitter with a link to the log
Phunk  [developer] Jan 1, 2019 @ 1:07pm 
Thanks for the log! What it's showing is an error that's happening every frame and spamming your log file - which is almost certainly the biggest contributor to your low framerate.

We'll have a look into that for a future patch - it looks like one of the component containers is wired up wrong and causing the issue. Unfortunately that means there's not a huge amount you can do to work around it until the patch is available - though if you start a new game or travel to a different level it might not be an issue there.
iwanPlays Jan 2, 2019 @ 12:25am 
I was in the level with the annoying flying castle where the log was created. I left into the bunker and the log didn't contain this error any more. Frame rate was nearly always 60 or more. When going back into said level, the log was full of it again and frame rate dropped again. I didn't try other levels and I didn't restart the game (would start in bunker anyways and take long to reach outside and would have to backup saves).

Here's the problematic seeming bit in the log in case anybody else wants to check:

NullReferenceException: Object reference not set to an instance of an object
at C_ComponentHolder.SetToOff () [0x00000] in <filename unknown>:0
at C_ComponentHolder.Update () [0x00000] in <filename unknown>:0

(Filename: Line: -1)

(200000 lines of this)
< >
Showing 1-8 of 8 comments
Per page: 15 30 50

Date Posted: Oct 14, 2018 @ 12:57pm
Posts: 8