Extend the duration of idle instance to 30 mins ~ 1 hour temporily.
|
Hi all,
Has anyone of you facing the problem that when you got disconnected during questing, go back the nearest way point and to your horror, the instance where the waypoint has already been reset, end up you have to clean up the whole instance again and when you come back to the level where you were, it got reset as well? Best example would be the Ancient Pyramid where it spans over 5 instances, due to disconnection, I have to go thru it for more than 5 times for get to act 3. It really hurts the first play thru experience. As a result, I'm suggesting to increase the duration for idle instance to 30 minutes ~ 1 hour before it will be reset, at least until the stability issue has been resolved. Pants are for nephalem, we are exiles, we do not need pants.
~~~~~ This thread has been automatically archived. Replies are disabled.
|
|
|
Part of what is making the severs stable is the short idle instance duration - since having them go away after 15 minutes makes the strain on the server a lot less.
Imagine everyone rushing the beginning of the game - each of, say, 10,000 people could have 5 or 6 (or more) instances up if they increased the duration of idle ones staying open. That's 50,000-60,000+ instances the servers have to remember instead of maybe 20,000-25,000. "I see now that the circumstances of one's birth are irrelevant; it's what you do with the gift of life that determines who you are." - Mewtwo
|
|
" Don't get me wrong, I totally understand and support the idea of trashing out instance that have been idle for X amount of time to conserve server memory. I am just saying extend it temporarily until the stability issue has been addressed. Currently it is giving the feeling of quickly rush to the next waypoint before one got disconnected. Pants are for nephalem, we are exiles, we do not need pants.
~~~~~ |
|
|
In order to do that they'd either have to permanantly enable the log in queue system or request significantly greater server capacity, neither of which I think the community nor the developers would desire. The former being disliked by the community and the latter being disliked by the developers due to the significant costs involved.
Computer specifications:
Windows 10 Pro x64 | AMD Ryzen 5800X3D | ASUS Crosshair VIII Hero (WiFi) Motherboard | 32GB 3600MHz RAM | MSI Geforce 1070Ti Gamer | Corsair AX 760watt PSU | Samsung 860 Pro 512GB SSD & Crucial MX 500 4TB SSD's |
|
|
How about an alternate solution whereby if the last town portal is still active, it will remain until the idle instance has been trashed, as oppose to immediate removal of active town portal upon disconnection. The instance is still there anyway, at least now one can jump right back in.
Pants are for nephalem, we are exiles, we do not need pants.
~~~~~ |
|
" That's a nice idea. Computer specifications:
Windows 10 Pro x64 | AMD Ryzen 5800X3D | ASUS Crosshair VIII Hero (WiFi) Motherboard | 32GB 3600MHz RAM | MSI Geforce 1070Ti Gamer | Corsair AX 760watt PSU | Samsung 860 Pro 512GB SSD & Crucial MX 500 4TB SSD's |
|
|
Total instance data isn't (or shouldn't) even be that great in the first place although when you account for total number of instances across all players per gateway/server it can pile up.
Total info for a single instance: - list of tile data (tileId + orientation + position) - list of interactive statics (doors, chest/vases/rocks/quest triggers/...) - list of mobs (mobId, status, location, mobMods, ...) - list of loot-able items (itemId, location) All this might get up to maybe a few kilobytes at most (I am only assuming how their map info might be constructed) but yes multiply that with whatever number of players are placed per server along with instance number and you reach you final server load/limit (not accounting for data needed per loaded player character and other stuff). However instance data could be serialized to a drive when they are idled and kept per player session (need to account for disconnects as well) or server could simply keep only the instance checksum/hash and instance data is persisted on client side and uploaded back before zoning in. Some sort of data validation is needed to prevent local tampering and you get the benefit of keeping instance data alive per player session (resetting an instance is already implemented). |
|
" Your point? Pants are for nephalem, we are exiles, we do not need pants.
~~~~~ |
|
" I made a thread yesterday suggestion exactly that: http://www.pathofexile.com/forum/view-thread/83544 |
|
|
I noticed that the Slums in Act 3 is nothing but instances that don't expire for 30 minutes. Not sure if that's exclusive to Act 3 or not but they may have changed the time out period.
Computer specifications: Windows 10 Pro x64 | AMD Ryzen 5800X3D | ASUS Crosshair VIII Hero (WiFi) Motherboard | 32GB 3600MHz RAM | MSI Geforce 1070Ti Gamer | Corsair AX 760watt PSU | Samsung 860 Pro 512GB SSD & Crucial MX 500 4TB SSD's Last edited by Nicholas_Steel#0509 on Jan 30, 2013, 10:16:43 PM
|
|
