OMG this.Hypertionb14_ESO wrote: »Want to go to the undaunted Kiosk IN grahtwood by teleporting to the Elder tree? 1minute loading screen followed by another 1minute loading screen the moment you try to run to the kiosk
Most heard sentence when doing trials with a group.I'm stuck in a loading screen.
ers101284b14_ESO wrote: »Mine only take 5-10 seconds
ers101284b14_ESO wrote: »Mine only take 5-10 seconds
That it does - most of the time.
But then there are times when I have to wait a minute or two; does not always happen, is not reliable reproducible, nothing.
But it happens.
Too frequently to ignore it or solely blame it on lag (or addons for that matter)... and apparently my client is long done "loading" (no more disk activities) anything and is just sitting there waiting on something from the server - which is not triggered or includes a *** huge delay for some unknown reason.
ers101284b14_ESO wrote: »
After a patch it takes a bit longer to load in but that's the only time.
ers101284b14_ESO wrote: »
After a patch it takes a bit longer to load in but that's the only time.
Yeah, I know about that one - that delay is even before char selection and that's not what I meant.
Just today we were running AA three times in a row; the first time when we went outside to reset AA it took me only about 10s to load Craglorn.
After the second run, I stared at a loading screen for over a minute; then after the 3rd time I teleported out (and out of Craglorn) into Reaper's March - again with the usual 10s loading screen.
Sometimes the server is either lagging out really badly (doubtful because not everyone is affected) or is simply forgetting to sent some packets until the client finally request a resend.
Other example... last week at HelRa; there is a (usually very brief) loading screen after the last big trash mob group with the horn before you enter the chamber with the statues which can trigger hard mode.
On the first run I (as usual) barely noticed it; on the second run I was stuck there "loading" for nearly a minute.
I dont know what it is... but there *is* something. Not always and never reproducible,
Lord_Kreegan wrote: »Generally the loading screens occur for two reasons (fairly standard game design):It doesn't matter if you have the latest-greatest-fancy-schmanzy graphics card and terabytes of RAM. This is a 32-bit application using DirectX. A 32-bit application doesn't address even 4Gb and the MSWindows OS insists on using virtual memory (disk) no matter how much memory you have. DirectX insists on buffering communications with your graphics card; object creation starts in RAM before it is handed off to the card.
- Graphics - unless the graphics data for the zone you're switching to has been cached, your client has to unload the current zone data (deallocate the memory) and load the new zone data (allocate new memory), manipulating that data DirectX-style for display. This has nothing whatsoever to do with LAG. If the graphics data has been cached, the loading screen lasts only a short time. If the data has not been cached, it can last a significant amount of time depending on the complexity of objects in the zone you're going to. This can all take longer if:
- Memory - As you allocate/deallocate memory, you have to wait for the OS garbage collection routines to coalesce the fragments into blocks of the size you need. If you've exhausted free memory through several zone changes, the garbage collection process can take some time...
It's the economy architecture, stupid players... [decided to borrow a phrase from the politicians]
If you played SW-TOR, you noticed that loading screens tended to pop up at inopportune times, not just when crossing zones (ESO will do this, too). EA-BioWare is a bit more honest with their players; they explain that the loading screen allows the client to "catch up". Actually it's letting the OS do the garbage collection drill to provide RAM to the client, but that's TMI for most players.
If you played SW-TOR, you might have also noticed that there is a 1Gb cache file in the game directory on your harddrive. The game actually runs better if you delete it before every playing session (SW-TOR doesn't flush the cache at the end of a session, so a new game session starts with whatever was in the cache at the end of the last session).
I haven't seen such a caching operation with ESO... that may be part of the problem.
Hypertionb14_ESO wrote: »Want to enter a building? 20second loading screen.
Lord_Kreegan wrote: »Generally the loading screens occur for two reasons (fairly standard game design):It doesn't matter if you have the latest-greatest-fancy-schmanzy graphics card and terabytes of RAM. This is a 32-bit application using DirectX. A 32-bit application doesn't address even 4Gb and the MSWindows OS insists on using virtual memory (disk) no matter how much memory you have. DirectX insists on buffering communications with your graphics card; object creation starts in RAM before it is handed off to the card.
- Graphics - unless the graphics data for the zone you're switching to has been cached, your client has to unload the current zone data (deallocate the memory) and load the new zone data (allocate new memory), manipulating that data DirectX-style for display. This has nothing whatsoever to do with LAG. If the graphics data has been cached, the loading screen lasts only a short time. If the data has not been cached, it can last a significant amount of time depending on the complexity of objects in the zone you're going to. This can all take longer if:
- Memory - As you allocate/deallocate memory, you have to wait for the OS garbage collection routines to coalesce the fragments into blocks of the size you need. If you've exhausted free memory through several zone changes, the garbage collection process can take some time...
It's the economy architecture, stupid players... [decided to borrow a phrase from the politicians]
If you played SW-TOR, you noticed that loading screens tended to pop up at inopportune times, not just when crossing zones (ESO will do this, too). EA-BioWare is a bit more honest with their players; they explain that the loading screen allows the client to "catch up". Actually it's letting the OS do the garbage collection drill to provide RAM to the client, but that's TMI for most players.
If you played SW-TOR, you might have also noticed that there is a 1Gb cache file in the game directory on your harddrive. The game actually runs better if you delete it before every playing session (SW-TOR doesn't flush the cache at the end of a session, so a new game session starts with whatever was in the cache at the end of the last session).
I haven't seen such a caching operation with ESO... that may be part of the problem.
My gaming rig most certainly exceeds minimum requirements. I generally have no difficulty otherwise playing with settings maxed out, it is only in high population areas (eg. Elden Root and Rawl'Kha in AD) that it seems to drag like this. Even once the loading screen is done, it doesn't really finish rendering things in the area, so I must wait for everything to render before moving through the area or suffer another load screen immediately.My loading screens usually take 5-10 seconds.
I don't mean to insult anyone, but are you guys with minute-long loading screens playing on minimum requirement machines? Do you have addons installed? Have you checked if there's a difference to the loading duration if you disable them?
coplannb16_ESO wrote: »#1 reason for loading screen: addons
seriously, look at your saved variable folder. If it contains more than say 2 MB in files you will notice a huge increase in loadtime.
Especially EsoHead and its derivates are creating large XML-files (storing map-data) which takes a long time to parse on loading.
Upon disabling EsoHead my load time went from 1-2 minutes to 10 seconds (Iam also no longer getting the "your UI memory is running low"-message ingame).
Also if your load time is too long you will timeout and get the infinite loading screen...
coplannb16_ESO wrote: »#1 reason for loading screen: addons
seriously, look at your saved variable folder. If it contains more than say 2 MB in files you will notice a huge increase in loadtime.
Especially EsoHead and its derivates are creating large XML-files (storing map-data) which takes a long time to parse on loading.
Upon disabling EsoHead my load time went from 1-2 minutes to 10 seconds (Iam also no longer getting the "your UI memory is running low"-message ingame).
Also if your load time is too long you will timeout and get the infinite loading screen...
Pretty much hopped in to say this. We know it's an age old ZOS mod classic, but addons can extend your load time if you're using quite a few (or one really, REALLY big one). We recommend renaming your SavedVariables folder to SavedVariables.old and disabling your addons to see if the load times improve.
coplannb16_ESO wrote: »#1 reason for loading screen: addons
seriously, look at your saved variable folder. If it contains more than say 2 MB in files you will notice a huge increase in loadtime.
Especially EsoHead and its derivates are creating large XML-files (storing map-data) which takes a long time to parse on loading.
Upon disabling EsoHead my load time went from 1-2 minutes to 10 seconds (Iam also no longer getting the "your UI memory is running low"-message ingame).
Also if your load time is too long you will timeout and get the infinite loading screen...
Pretty much hopped in to say this. We know it's an age old ZOS mod classic, but addons can extend your load time if you're using quite a few (or one really, REALLY big one). We recommend renaming your SavedVariables folder to SavedVariables.old and disabling your addons to see if the load times improve.
grimsfield wrote: »coplannb16_ESO wrote: »#1 reason for loading screen: addons
seriously, look at your saved variable folder. If it contains more than say 2 MB in files you will notice a huge increase in loadtime.
Especially EsoHead and its derivates are creating large XML-files (storing map-data) which takes a long time to parse on loading.
Upon disabling EsoHead my load time went from 1-2 minutes to 10 seconds (Iam also no longer getting the "your UI memory is running low"-message ingame).
Also if your load time is too long you will timeout and get the infinite loading screen...
Pretty much hopped in to say this. We know it's an age old ZOS mod classic, but addons can extend your load time if you're using quite a few (or one really, REALLY big one). We recommend renaming your SavedVariables folder to SavedVariables.old and disabling your addons to see if the load times improve.
This is BS and until mods and devs like you accept that there is a problem with loading in this game, we will continue to have problems with loading screens. Getting you guys to accept that there is a problem is the biggest issue in the game right now.
The fact that I didnt have any problems with this game until about patch 1.4 tells me that some change in 1.4 is causing this. NOT ADDONS. Not anything the player is doing. This is a problem with the game that was introduced with that large patch.
grimsfield wrote: »coplannb16_ESO wrote: »#1 reason for loading screen: addons
seriously, look at your saved variable folder. If it contains more than say 2 MB in files you will notice a huge increase in loadtime.
Especially EsoHead and its derivates are creating large XML-files (storing map-data) which takes a long time to parse on loading.
Upon disabling EsoHead my load time went from 1-2 minutes to 10 seconds (Iam also no longer getting the "your UI memory is running low"-message ingame).
Also if your load time is too long you will timeout and get the infinite loading screen...
Pretty much hopped in to say this. We know it's an age old ZOS mod classic, but addons can extend your load time if you're using quite a few (or one really, REALLY big one). We recommend renaming your SavedVariables folder to SavedVariables.old and disabling your addons to see if the load times improve.
This is BS and until mods and devs like you accept that there is a problem with loading in this game, we will continue to have problems with loading screens. Getting you guys to accept that there is a problem is the biggest issue in the game right now.
The fact that I didnt have any problems with this game until about patch 1.4 tells me that some change in 1.4 is causing this. NOT ADDONS. Not anything the player is doing. This is a problem with the game that was introduced with that large patch.