Jump to content

Vleeswolf

Members
  • Posts

    7
  • Joined

  • Last visited

  1. As was said several times: this issue occurs because TrackIR 5 has a fixed update rate of 120Hz. You can either limit frames rate of your games to eg. 40, 60, or 120, or you can alleviate the issue somewhat by increasing the smoothing parameter in the TrackIR software, at the expense of increasing input lag. This has nothing to do with OpenGL or DirectX, it is a fundamental property of input devices. You just don’t notice it as much with mouse and keyboard because their update rate is typically as high as 1000Hz.
  2. Agreed on having easily configured frame rate limiter that works for everyone! Some of my settings, fwiw: Game settings: full-screen, vsync off. Only in graphics.lua I changed maxfps to 60. Not using any autoexec.cfg in user documents. Windows 10 full screen optimizations enabled. NVIDIA cp settings: fast sync, max. prerendered frames 1.
  3. It’s not a game engine thing, it’s because of the relatively low update frequency of TrackIR (120hz), and being out of tune with that frequency leads to stutter. If you cannot limit FPS with the ingame limiter better use Rivatuner Statistics Server instead of NVIDIA Profile Inspector, which can cause input lag.
  4. I only edit graphics.lua, changing maxfps=180 to maxfps=60. I do not use the options.graphics.maxfps thing as it does not seem to do anything (used to work previously in autoexec.cfg). Disable vsync in the in-game menu.
  5. I limit frame rate using the game’s own limiter (by editing graphics.lua, indeed) and it works perfectly fine. You also need to disable the game’s vsync though, which often is a good idea with most games and gsync. If you do get tearing, which you shouldn’t at 60 FPS with a 144 hz gsync monitor, you could try forcing vsync or fast sync with the NVIDIA control panel.
  6. No, with gsync you keep your monitor refresh rate at highest, 144 in your case. But you lock game FPS to 60.
  7. TrackIR 5 has a 120 Hz update frequency. If you run your games at any other frame rates than integer multiples or divisors of 120 (eg 40, 60, 120, 240), they will have a stuttery motion, especially with panning the camera. The proper way to fix this is to limit the frame rate to 60. 120 you can probably not reach consistently. An inferior solution is to increase the smoothing level in the TrackIR software. That will help smooth things, but also increase response times.
×
×
  • Create New...