One Hour One Life Forums

a multiplayer game of parenting and civilization building

You are not logged in.

#1 2018-04-10 10:55:23

gondor2222
Member
Registered: 2018-04-10
Posts: 4

Game detects 900+ max fps

I just downloaded the game again on my windows 10 laptop with both Intel Graphics 530 and NVIDIA GTX 970M. When I start the game or manually start the fps detection, it detects something in the range of 899.9 - 900.1 FPS for some reason, and according to the log files the game ends up setting the FPS to 144. This only happens in the max fps detection - the settings consistently report my fps at ~60.
Setting target FPS to 60 seems to fix the game to the right 60 fps, but I can't enable VSYNC because the 60 target fps doesn't match my "actual" 900+ fps.

I also crash frequently when being born but I'm not sure if this is related. The game runs fine on my desktop computer.

Last edited by gondor2222 (2018-04-10 10:58:11)

Offline

#2 2018-04-12 22:05:44

Gederian
Member
Registered: 2018-03-28
Posts: 164

Re: Game detects 900+ max fps

I have a surfacebook and the dGpu is off by default for most applications. I had to specifically enable it for OneLife.exe file. Here is how to do it:

1. Make sure your nvidia drivers are up to date by opening your control panel then selecting Device Manager. Expand Display adapters, right click your Nvidia device and select update driver.

2. Go back to control panel and click "NVIDIA Control Panel" (be patient, it opens but there is no indicator). Click the Program Settings tab, then click Add, then click Browse, then locate your OneLife.exe file. Select the Nvidia processor for step two then click Apply on the bottom right.

That's it. You should now get to 60FPS and vsync will be enabled.

Offline

#3 2018-04-14 16:35:07

jasonrohrer
Administrator
Registered: 2017-02-13
Posts: 4,805

Re: Game detects 900+ max fps

Yeah, the logging about picking 144 is a little misleading.  It says that 144 is the closest match, but then it determines that 900 is too far from 144, and it uses the default of 60.

This is actually correct behavior.  It is sleeping at 60fps when it cannot count on vsync.

There's nothing I can do here in terms of code.  It's up to you to get vsync enabled on your GPU, or settle for sleep-based frame rate control, which will have some visual tearing.

Crashes are another issue.  Can you try running the debugger on your laptop?

Offline

Board footer

Powered by FluxBB