Frame Lag

[StOneDOes]

Has anybody else experienced frame lag when you have a framerate that is well above the refresh rate of your screen, with VSync disabled. I have old screens that have a 60hz refresh rate so I don't know what it would look like with VSync on, on a high refresh rate but for me it is way too slow on 60 VSync. 

I can get some video of this if needed but want to see if people have ideas first. Whats interesting is that this does not occur on every run, only sometimes. This is in release mode.

Windows 10

AMD Ryzen 9 3900X

AMD Radeon RX 6600 XT

 

[Josh]

What is frame lag?

[StOneDOes]

Essentially the experience that you have when your current framerate is lower than the screen refresh rate. It makes the game feel jittery when moving the mouse for mouselook; such that its not smooth or seamless. 

[Josh]

Okay, so you are saying the main game loop feels like it is slowing down. You can check this like this:

auto tm = Millisecs();

while (true)
{
	auto newtime = Millisecs();
	auto elapsed = newtime - tm;
	tm = newtime;
	window->SetText(elapsed);
  	
	world->Update();
	world->Render(framebuffer);
}

The number in the window titlebar should be 16-17 at all times.

You can also check world->physicsstats.physicstime to see how long the physics thread is taking. Call world->RecordStats(true) to enable stats recording.

[StOneDOes]

So using that same test in my game loop gives me 16 or 17 as expected. The physics thread is giving me 0-1ms. 

The interesting thing about this issue that I just found, is that goes away after calling world->pause() and world->resume()

[StOneDOes]

Right now I'm just checking to see if it has anything to do with this AMD adrenaline software garbage that pops up. I would much rather that be the problem than anything else.

[Josh]

Also close your web browser. I have noticed just having a web browser open, even if it is minimized, gives me slightly inconsistent timing.

[StOneDOes]

Ok, so of course as usual after spending days investigating something myself, I post and then figure it out not long later ...

Fow now Josh, I think we can put this down to AMD Adrenaline software. I'm unable to reproduce this after disabling the software. I'll mark this as solved but please give me a few days before locking this thread if you don't mind incase I can reproduce it again. Thanks for your help.