Analyzing Game Data

FiveM Discussion Bug reports
29

Hey,

just to get me into this discussion. I also experience very long loading times.

Hardware:

  • i7 11700k
  • RTX 2070 OC
  • 64 GB RAM

What i tried and did not help (not even the .cfg “workaround”)

  • reinstalled GTA 5 (i hade re-shade and stuff, so i wanted to test this on a clean install)
  • reinstalled FiveM
  • upgraded to Windows 11
  • switched back and forth from stable to canary and vice verca
  • running as Admin
  • running in secure windows mode with enabled network

If required, i can also supply some of those dumps, just mention me.

30

Does this get fixed if you downgrade your NVIDIA drivers to a version from July?

31

I can give this a try tomorrow.

32

Actually, I see what might have changed here: some code path got moved to run earlier around tweak(nui/core): send BeginFrame events even before game runs · citizenfx/fivem@a21d297 · GitHub and if unlucky (high refresh rate? load order?) this leads to a global per-process lock in the NVIDIA driver getting stuck for a very long time.

33

There’s another canary build that hopefully fixes this too, but I’m not very hopeful about that (no evidence it will and it doesn’t happen here no matter the GPU driver version :confused: ).

34

Downgrading to 471.96 seems have solved the issue for now (tried 472.12, game crashed in 5 mins)

35

are you on canary too or is that production build?

36

seems both works

37

trying this now

38

Yup. Fixed my issue lol. Hopefully it’s a temp fix tho, I think have out of date drivers causes lag no?

39

… great, so now we can’t confirm or deny whether or not this is any better/worse with changes we do, and you ignored my message asking to check current canary. :roll_eyes:

You’re going to have to take it up with NVIDIA however if it’s also a regression on their end, we haven’t been able to reach them at all at any point now or in the past.

40

Hi.

I was on the latest build of canary and I also faced issues with “analysing game data”. Took roughly 3-5 minutes to opens fivem. My apologies on not clarifying.

41

Yeah, this is indeed an NVIDIA driver bug then where as long as anything calls ID3D11DeviceContext::Flush, a call to D3D11CreateDevice on another thread will hang for a very long time on some driver-internal lock… but somehow only for whatever settings/GPU generation/… you folks are using. What makes is worse is that the default stage of doing this out-of-process works fine, but that leads to this ‘UI lag’ thing due to Microsoft being unwilling to fix a bug on their end.

We can’t do much here without either Microsoft’s or NVIDIA’s cooperation, sadly.

42

I appreciate the time you have taken and efforts made to help. Thank you for your time

43

This seems to be solved with the new Nvidia 496.49 driver, thankfully!

2 Likes
44

I can also confirm that this is solved upgrading to the newest NVIDIA driver 496.49 :slight_smile:

45

I am still having the issue with 496.49, even after a fresh DDU

46

Manage to resolve it by downloading an earlier version of the driver from Nvidia (471.68). The new version didn’t work for me, but the August one did.

47

Yeah, the issue is back on the latest driver (496.49).
It worked 100% 21 days ago.

48

Yeah, at this point it’s down to NVIDIA. There’s nothing the FiveM devs can do. Latest driver is 496.76 btw, that once was released on 18th and works fine afaik