Error 316704, double game creation becouse of high server latency

[krzys]

Hey, since few days i have a problem with db,
My latency is fine, i was using db for months without problems,
When creating the game i have a few seconds delay before loading screen pops out.(start/resume game is gray for a few seconds, than loading screen pops out)
Becouse of this Demonbuddy creates a game, and then it gets impatient because the game is slow to load and sends a second create game command which causes the error.

goes like this:
db creating the game in xx seconds
start/resume game clicked, gray for a few seconds
(too long gray)
db creating the game in xx seconds (second time)
loading screen pops out
character ingame
Error 316704 pops out, closing
character doasnt move/crash

It does close the dialogue for you, but after this character stands in town not moving,
If start/resume isnt gray so long, db start game normally, no error, works fine
Im looking for a fix which will add few seconds more, and will let db wait little bit longer before trying to create an other game.
Thx in Advance

 

[buian01]

Hey, since few days i have a problem with db,
My latency is fine, i was using db for months without problems,
When creating the game i have a few seconds delay before loading screen pops out.(start/resume game is gray for a few seconds, than loading screen pops out)
Becouse of this Demonbuddy creates a game, and then it gets impatient because the game is slow to load and sends a second create game command which causes the error.

goes like this:
db creating the game in xx seconds
start/resume game clicked, gray for a few seconds
(too long gray)
db creating the game in xx seconds (second time)
loading screen pops out
character ingame
Error 316704 pops out, closing
character doasnt move/crash

It does close the dialogue for you, but after this character stands in town not moving,
If start/resume isnt gray so long, db start game normally, no error, works fine
Im looking for a fix which will add few seconds more, and will let db wait little bit longer before trying to create an other game.
Thx in Advance

I am having the same issue. Please help

 

[Tony]

well,we cant do something about high server latency

 

[vixor]

Hey, since few days i have a problem with db,
My latency is fine, i was using db for months without problems,
When creating the game i have a few seconds delay before loading screen pops out.(start/resume game is gray for a few seconds, than loading screen pops out)
Becouse of this Demonbuddy creates a game, and then it gets impatient because the game is slow to load and sends a second create game command which causes the error.

goes like this:
db creating the game in xx seconds
start/resume game clicked, gray for a few seconds
(too long gray)
db creating the game in xx seconds (second time)
loading screen pops out
character ingame
Error 316704 pops out, closing
character doasnt move/crash

It does close the dialogue for you, but after this character stands in town not moving,
If start/resume isnt gray so long, db start game normally, no error, works fine
Im looking for a fix which will add few seconds more, and will let db wait little bit longer before trying to create an other game.
Thx in Advance

Try this: Open Settings->Bot and in the boxed with the "Game Wait time" add 10 seconds to booth of them.

I had that issued and it was a bad mix of thingth timmings (got something like 1-3 lol) and bad latency. My guess was that the DB was trying to create a new game and, if the amx time passed, it would try again, wich would fuck up if my shit latency wasnt able to let me create a game in a propper way. I added 15 seconds to booth of them and voil? i worked.

Good luck.

 

[bunnykill]

well,we cant do something about high server latency

Tony, it's not caused by server latency. I see from posting history from the past year that that's been the default response, and it's incorrect.

The error is caused by DB trying to create a game while already in a game. There should be a check for this.

[02:13:42.604 N] Waiting 52.8 seconds before next game...
[02:13:49.540 N] Loaded profile In a Rush - Dahglur Oasis
[02:13:49.766 N] [Trinity] New Game - resetting everything
[02:13:49.785 N] GameChanged. Clearing actors
[02:13:49.808 D] Joined a game!
[02:13:49.810 D] [QuestTools] LastJoinedGame is 11/28/2013 19:13:49
[02:13:49.810 N] [Trinity] New Game - resetting everything
[02:13:49.829 N] ProfileOrderManager.OnGameJoined, Reloading profile.
[02:13:50.043 N] Loaded profile In a Rush - Dahglur Oasis
[02:13:50.043 N] Game joined, Resetting profile caches.
[02:13:50.043 D] Resetting current behavior.
[02:13:50.044 N] ========== Grid segmentation resetting!!! ============
[02:14:35.415 N] Creating new game. Params: [Act:A2 Difficulty:Inferno Quest:57337 QuestStep:41 ResumeFromSave:False IsPrivate:True Handicap:5]

Trinity starts the game loads the profiles, verifies the game has been joined.
Then DB waits out the delay and tries to create the game again.

I actually fixed this error on my end by LOWERING the delay time, I had it set way too high.
Had to lower it to under 30 seconds.

 

[kaze3d]

This problem has been fixed many beta's ago.

- No longer creates more than one game when creating a new game.

 

[NHK]

This problem has been fixed many beta's ago.

Are you suggesting that all the people with this issue are using outdated versions of DB?

 

[Tony]

Tony, it's not caused by server latency. I see from posting history from the past year that that's been the default response, and it's incorrect.

The error is caused by DB trying to create a game while already in a game. There should be a check for this.

[02:13:42.604 N] Waiting 52.8 seconds before next game...
[02:13:49.540 N] Loaded profile In a Rush - Dahglur Oasis
[02:13:49.766 N] [Trinity] New Game - resetting everything
[02:13:49.785 N] GameChanged. Clearing actors
[02:13:49.808 D] Joined a game!
[02:13:49.810 D] [QuestTools] LastJoinedGame is 11/28/2013 19:13:49
[02:13:49.810 N] [Trinity] New Game - resetting everything
[02:13:49.829 N] ProfileOrderManager.OnGameJoined, Reloading profile.
[02:13:50.043 N] Loaded profile In a Rush - Dahglur Oasis
[02:13:50.043 N] Game joined, Resetting profile caches.
[02:13:50.043 D] Resetting current behavior.
[02:13:50.044 N] ========== Grid segmentation resetting!!! ============
[02:14:35.415 N] Creating new game. Params: [Act:A2 Difficulty:Inferno Quest:57337 QuestStep:41 ResumeFromSave:False IsPrivate:True Handicap:5]

Trinity starts the game loads the profiles, verifies the game has been joined.
Then DB waits out the delay and tries to create the game again.

I actually fixed this error on my end by LOWERING the delay time, I had it set way too high.
Had to lower it to under 30 seconds.

in that case open your own thread providing a full log file as attachment and we will check it

 

[kaze3d]

Are you suggesting that all the people with this issue are using outdated versions of DB?

Actually, yes. I personally would call the release branch a bit dated seeing there has been a tremendous amount of work put into the beta's, especially this past week. Being part of the DB Test group, I test alot of builds on 10+ sessions and have yet to see this bug return since it was fixed in beta .264 I believe. I can only really think of 3 reasons why people still use 317... they dont know about the beta builds, scared of the beta builds, using a *****ed DB that is always linked to the 317 release.

Even since last maintenance when the so called "latency" problem started while creating games (which is Blizzs fault and has to do with the release of RoS beta/new queue system) I still havent seen the double creation bug on a beta build.

 

[WackJagon]

Actually, yes. I personally would call the release branch a bit dated seeing there has been a tremendous amount of work put into the beta's, especially this past week. Being part of the DB Test group, I test alot of builds on 10+ sessions and have yet to see this bug return since it was fixed in beta .264 I believe. I can only really think of 3 reasons why people still use 317... they dont know about the beta builds, scared of the beta builds, using a *****ed DB that is always linked to the 317 release.

Even since last maintenance when the so called "latency" problem started while creating games (which is Blizzs fault and has to do with the release of RoS beta/new queue system) I still havent seen the double creation bug on a beta build.

The latest BETA was requiring vcredist_x86 2012.exe (assuming it still is) and there were significant performance issues with the switch to the new kit. I had to go back to non-beta however it has been over a month. At any rate, a new version of DB was just released a couple days ago. Not clear how much it differs from BETA but the latest release from a couple days ago works ok for me performance wise, but BOT SETTINGS don't work

 

[Tony]

The latest BETA was requiring vcredist_x86 2012.exe (assuming it still is) and there were significant performance issues with the switch to the new kit. I had to go back to non-beta however it has been over a month. At any rate, a new version of DB was just released a couple days ago. Not clear how much it differs from BETA but the latest release from a couple days ago works ok for me performance wise, but BOT SETTINGS don't work

open your own thread


closed