LBW More Options

LBW More Options 0.0.2

Added the following options:
  1. DoubleClickTime
  2. EnableTuner
  3. FrontEndTickIntervalInHZ
  4. InactiveTickIntervalInHZ
  5. TickIntervalInHZ
DoubleClickTime is how fast you have to complete the single click to register a double click. It defaults to 200ms which is a bit marginal for an old fart like me. The game doesn't really use double click and that may well be why. It's sort of a balancing act between long enough to be able to double click but not so long as to cause to single clicks to register at a double click. You can change it in 50ms increments. 300ms should be good for most, but I let it go up to 1s since a hanicapped individual might need longer. I didn't go over 1s because it seems that isn't long enough you need a better solution.

EnableTuner let's the FireTuner from Civ VI connect to the game until they release the SDK for Civ VII which will presumably have a new tuner. The Civ VI one does work, but you have to coerce it a bit. You'll have to read about that in other threads.

FrontEndTickIntervalInHZ, InactiveTickIntervalInHZ and TickIntervalInHZ is suppose to frame limit the game which was mentioned in the release notes. I play on a laptop with a 4070. Without frame limiting it pegs the GPU at 100% doing 200+ FPS and generating a lot of heat and needless stress on the GPU. Only TickIntervalInHZ is actually implemented by the game. That will limit the FPS (HZ) while playing the game. FrontEndTickIntervalInHZ was, presumably, suppose to limit the FPS when on the Main Menu displayed when you first start the game, but it doesn't. InactiveTickIntervalInHZ was, presumably, supposed to limit the FPS when the game loses focus because you switched to another application. It doesn't. If you're in game it will continue at whatever rate you set for TickIntervalInHZ. If you're on the Main Menu there's no frame limiting when inactive.

Personally, I use RivaTuner to limit frame rates and will continue to do so. Programming I spend a lot of time with the game idling. My view is there's really no point going over 60 FPS in general and certainly not in this game. I've heard the arguments but I just really don't think most can tell the difference over 60 FPS without instrumentation. I only allowed setting the limit up to 120 FPS. If you want a number higher than that then you might as well set it to 0 and have no frame limit.
Back
Top Bottom