Stuck at a loading screen when I try joining any server

I am stuck loading any server I try to join. I also have to keep changing the build it says when I try loading into servers everytime and I dont know how to fix that either.

I do have the full game also not the stand alone.

That is for FiveM anyway, don’t know if it will be the same for RedM but it might help in locating the problem

I am also having the same problem, have you tried locating your logs? All my logs say this;

[ 612891] [ GTAProcess] MainThrd/ Warning: LoadObjectsNow took 118328 msec (invoked from 00007ffb96949c18)!
[ 612891] [ GTAProcess] MainThrd/ ---------------- DO FIX THE ABOVE ^
[ 612891] [ GTAProcess] MainThrd/ ---------------- IF YOU CAN NOT FIX IT AND THIS OCCURS DURING GAMEPLAY
[ 612891] [ GTAProcess] MainThrd/ ---------------- PLEASE CONTACT THE FIVEM DEVELOPERS ON https://forum.fivem.net/
[ 612891] [ GTAProcess] MainThrd/ ---------------- WITH THIS CITIZENFX.LOG FILE
[ 612906] [ GTAProcess] MainThrd/ ----------------
[ 612906] [ GTAProcess] MainThrd/ ---------------- THIS BLOCKING LOAD WILL CAUSE CLIENT GAME CRASHES
[ 494563] [ GTAProcess] MainThrd/ Warning: LoadObjectsNow took 46594 msec (invoked from 00007ffb96949c18)!
[ 494563] [ GTAProcess] MainThrd/ ---------------- DO FIX THE ABOVE ^
[ 494563] [ GTAProcess] MainThrd/ ---------------- IF YOU CAN NOT FIX IT AND THIS OCCURS DURING GAMEPLAY
[ 494563] [ GTAProcess] MainThrd/ ---------------- PLEASE CONTACT THE FIVEM DEVELOPERS ON https://forum.fivem.net/
[ 494563] [ GTAProcess] MainThrd/ ---------------- WITH THIS CITIZENFX.LOG FILE
[ 494563] [ GTAProcess] MainThrd/ ----------------
[ 494563] [ GTAProcess] MainThrd/ ---------------- THIS BLOCKING LOAD WILL CAUSE CLIENT GAME CRASHES
[ 715719] [ GTAProcess] ResourcePlacementThr/ This asset is INVALID, but we’ve fixed it for this load. Please fix the exporter used to export it.
[ 715719] [ GTAProcess] ResourcePlacementThr/ Details: Poly 28 edge reference is invalid. It leads to vertex 58301, when there are only 19630 vertices.

Have a quick look at your log files and see if there is anything you can do, I am not sure myself what to do