Jump to content
Search In
  • More options...
Find results that contain...
Find results in...


  • Content Count

  • Joined

  • Last visited


This user doesn't have any awards

About Glazarus

  • Title

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. In-game - (this case Rainbow Six Siege) you have to chose a refresh rate. Here I have it chosen according to my display refresh rate. 120 hz in Rainbow Six Siege settings and 120 hz on my monitor and Nvidia settings. GPU Tweak II - FPS target is set to 120 fps. I've also tried as Battle(non)sense describe, putting this to lower at 117 fps, which doesn't help at all. In Nvidias control panel - Max 120 fps setting. I have tried these three in all possible combinations; all set to 120 fps, one each, different values towards each other, higher values on GPU tw
  2. As mentioned, it will always be one to two frames below the cap, regardless of lowering graphics settings. I can put Rainbow Six Siege to its lowest settings, lowest resolution or render resolution, making my system able to pull hundreds of frames over my monitor display and it will still be one or two frames under the monitor chosen framerate. Lowering the framerate will just set a new framerate for which it renders one or two frames below. Graphics settings are irrelevant to the issue. And Rainbow Six Siege always has a framerate target in its options so I need to set that. There
  3. If you cap the fps you lower the load for your GPU so that it can maintain a more consistent FPS target. However, it doesn't matter, if I don't cap the one-two frames lower problem is still there. So it does not change anything about the issue. As mentioned, I've tried all possible optimization tips that I could find about G-Sync, nothing helps. Not ignoring the tips, not using the tips. I recommend Battle(non)sense if you need more specific info. The key issue here though is that it doesn't matter which target fps value I play at, the monitor can handle 120 fp
  4. Yes, I even got the monitor's own FPS overlay showing the framerate and the lower than target framerate. As mentioned, it doesn't matter which target I aim for, I can put the FPS target to anything and the actual framerate is always one or two frames below that target. I could render the resolution at 480p, all settings on low, aim for a 30 fps target and the G-Sync would end up at 28-29 fps. GPU or CPU load does not affect this issue. Yes, I've tried the native mode for this display, no change as it doesn't matter which target I aim for. If I turn of overclock f
  5. I'm trying to hit the framerate target of my G-Sync ultrawide screen at 120 fps with my RTX 2080ti. However, it always stays at an average 117-118 FPS. When G-Sync is enabled and I'm doing "normal stuff" in Windows 10, it is stuck at 120 fps as it should. Moving windows and programs around has no tearing and it works as it should. However, when I start a game, primarily Rainbow Six Siege, the framerate hits one or two frames under the intended target. Processor and GPU never hit maximum so there's no throttling as I can see. I've tried both having all settings unlimited for fr
  6. Unfortunately I have and it's not that.
  7. Yeah, which is my point. The card is one of the best cards and the processor isn't the worst for gaming and within a very simple rendered environment, like the grid/mountain loading screen for SteamVR, which gets the timing of the GPU down to 0,4, you still get these hiccups from "WaitGetPoses". Since everyone supposedly are on the same drivers for SteamVR and Nvidia, it would be interesting to hear the frame timing others have. This is an issue that can be hard to spot when just casually playing, but it's glaring in slower things and if you notice a large purple spike in the in-he
  8. I bought a Valve Index headset and installed everything properly. Using a RTX 2080ti and a water cooled and slightly overclocked i9-7960x I have more than enough for simple VR games on low settings. The rendering is smooth in every game, even Half Life Alyx at Ultra settings. However, there are these very distinct frame skippings occurring randomly with around 8-10 seconds intervals. They doesn't seem to be related to any CPU bottlenecks or GPU problems, both being at 12% and 40% in Steam Home. I've tried seeing any correlation between software jumping up in use in the
  9. I've got a setup were my PC is a few meters away from my screen in order to have a clean work area. The problem I've encountered is that my displayport cable's length seem to be affected by interference. The included cable seem to work fine, but the longer randomly lose connection, blanking the screen out and then directly returning with a "DP" logo in the upper right corner. Sometimes the screen totally lose connection. Interferences can even be done with a candle lighter, clicking on the flame close to the screen (!). The cable I'm using is a 5m DP-4050 Deltaco cable that is shi
  10. I have the same issue on my Acer X34P. I've searched all over internet for a solution but I don't get answers on this forum or anywhere. Shutting off G-Sync does not help, nothing helps, overclocked to 120 Hz is the same as non-overclocked at 100 Hz. Having other monitors plugged in is the same as the X34P only. Flickering and black screens with the DP-sign popping up, occurs more frequently when the GPU is at heavy load. Using the computer normally, browsing etc. usually won't affect the screen. HDMI at 60 Hz is fine, this only occurs on Display Port. I've re-installed Windows, d
  11. I've tried searching around for an answer and I can't get any answers anywhere, not from Acer, not from users, even though lots of people are experiencing this. Sigh, anyone?
  12. These: Corsair 64GB (4x16GB) DDR4 3600MHz CL18 Vengeance LPX And my CPU is an Intel Core i9 7960X 2.8 GHz 22mb And my motherboard is an ASUS WS X299 SAGE Enabled the XMP profile, but disabled Asus multi-core handling since I only have a 750w power so I don't want the board to overclock past Intels specs.
  13. I saw the LTT video about RAM speeds and XMP overclocks and I have this overclock (think I got the same RAM as they used) boosting my RAM from 2330 MHz to 3600 MHz. Now, Linus mentions that even if the system seems stable now (I've stress tested the memory without problems at this time), it can start failing down the line. This leads me to think that I'm risking damage to my system having this overclock. Is it better to just turn off XMP or maybe lower the overclock to a bit under 3600 MHz? I don't want to risk damaging my system, but I don't want to miss out on th
  14. UPDATE: I enabled XMP but disabled Asus multicore handling. Did a stress test at my 4.0 GHz core and 2.8 Cache frequency in Intel Extreme Tuning and the system seems to be stable. However, this is without the 2080 ti overclocked (only Strix default overclock at 1650 MHz. So where to go from here? Not sure how stable I can overclock my GPU without overloading the whole system on my 750w. Is it possible to do the JayzTwoCents-overclock safely, or would I need a 1000w power for that?