Game Crash


(BomBaKlaK) #1

Happen 3 times in 2h … Freeze then crash and now it’s happen in few minutes everytime with the nexon repport issue.
Unplayable more than sometimes 1 min sometimes 5


(Violator) #2

Just had this happen as well (was on VIP server with Bomba)


(Ceres) #3

Happened to me last night a few times as well. I think everyone is randomly crashing now.


(BomBaKlaK) #4

Yep happen again …


(Rex) #5

Same for me. Game froze and crashed randomly. Happened already twice since the new patch.


(Killgar) #6

Last build I’d crash 3-4 times in a day of playing, today it was closer to 30-40 times. lots of different types of crashes/lockups at all different times and situations.


(psycozz) #7

Same bomba I’m gonna cry because we are not gonna play the cup because of this crashes


(Raviolay) #8

Can’t even play CTD as soon as enter the server.


(BomBaKlaK) #9

Meh … I think you miss nothing look like there is only few teams …


(Anti) #10

Folks, please can you let us know what you were doing at the time of the crash and attach any logs you might have. That information will make it much easier for us to track this down and fix it.

Thanks


(PixelTwitch) #11

[QUOTE=Anti;503581]Folks, please can you let us know what you were doing at the time of the crash and attach any logs you might have. That information will make it much easier for us to track this down and fix it.

Thanks[/QUOTE]

Could it be the fact that some of our “logs” are over 2gb in size?


Ignore last attached -.- both files where named the same -.-


(Mustang) #12

I’ve had this 3 times, I don’t think it’s happened during gameplay, but during map end/lobby load, could also be related to alt-tabbing out of the game because I’d usually do it at this time.


(Toomic) #13

[QUOTE=PixelTwitch;503584]Could it be the fact that some of our “logs” are over 2gb in size?


Ignore last attached -.- both files where named the same -.-[/QUOTE]

Holy Moly! Is there a specific error that’s spamming in there?


(rookie1) #14

Tbh I would like to see all the new Pre Play Launcher windows Scrapped and Back to Pre patch setup .
Its just look like Before it was polish and now we Have a version of Pre Alpha


(RasteRayzeR) #15

I found a log file of 394 MO lol. The game crash happened to me as well. Found this line spamming all over the place (thousands of times):

[1241.46] ScriptWarning: Accessed None ‘SGPRI’
SGUIScoreboardWidget Transient.SGUIGameMenuManager_1:SGUIScoreboardWidget_1
Function ShooterGame.SGUIScoreboardWidget:UpdateDeadTimer:0067

The values change but this is constant : “ScriptWarning: Accessed None ‘SGPRI’”


(PixelTwitch) #16

[0110.87] ScriptWarning: Accessed None ‘m_SGTeam’
SGUIGameOverviewScene Transient.SGUIGameMenuManager_0:SGUIGameOverviewScene_0
Function ShooterGame.SGUIGameOverviewScene:UpdateStopwatchTimeBar:037C
[0110.87] ScriptWarning: Accessed None ‘m_SGTeam’
SGUIGameOverviewScene Transient.SGUIGameMenuManager_0:SGUIGameOverviewScene_0
Function ShooterGame.SGUIGameOverviewScene:UpdateStopwatchTimeBar:037C
[0110.87] ScriptWarning: Accessed None ‘m_SGTeam’
SGUIGameOverviewScene Transient.SGUIGameMenuManager_0:SGUIGameOverviewScene_0
Function ShooterGame.SGUIGameOverviewScene:UpdateStopwatchTimeBar:037C
[0110.87] ScriptWarning: Accessed None ‘m_SGTeam’
SGUIGameOverviewScene Transient.SGUIGameMenuManager_0:SGUIGameOverviewScene_0
Function ShooterGame.SGUIGameOverviewScene:UpdateStopwatchTimeBar:037C
[0110.87] ScriptWarning: Accessed None ‘m_SGTeam’
SGUIGameOverviewScene Transient.SGUIGameMenuManager_0:SGUIGameOverviewScene_0
Function ShooterGame.SGUIGameOverviewScene:UpdateStopwatchTimeBar:037C
[0110.87] ScriptWarning: Accessed None ‘m_SGTeam’
SGUIGameOverviewScene Transient.SGUIGameMenuManager_0:SGUIGameOverviewScene_0
Function ShooterGame.SGUIGameOverviewScene:UpdateStopwatchTimeBar:037C
[0110.87] ScriptWarning: Accessed None ‘m_SGTeam’
SGUIGameOverviewScene Transient.SGUIGameMenuManager_0:SGUIGameOverviewScene_0
Function ShooterGame.SGUIGameOverviewScene:UpdateStopwatchTimeBar:10F2

EVERY SECOND! lol

Think its MAINLY an issue with spectating


(Violator) #17

I’ve got 3/4 GB of logfiles in there now (Launch.log is around 200MB) which seems to have grown massively since the last patch:


27/06/2014  22:53         1,050,151 Launch-backup-2014.06.27-22.53.42.log
28/06/2014  00:16       149,281,671 Launch-backup-2014.06.28-13.20.32.log
28/06/2014  14:36        96,093,194 Launch-backup-2014.06.28-14.37.13.log
28/06/2014  14:44           524,299 Launch-backup-2014.06.29-15.32.22.log
29/06/2014  16:57       112,660,720 Launch-backup-2014.06.30-00.33.03.log
30/06/2014  00:37           897,024 Launch-backup-2014.06.30-00.37.22.log
30/06/2014  02:20       196,215,863 Launch.log
25/05/2014  23:04         9,646,465 Launch_2.log
20/10/2013  17:30           279,889 unreal-v8710-2013.10.20-17.29.55.dmp
20/10/2013  17:30               563 unreal-v8710-2013.10.20-17.29.55.event
20/10/2013  17:30           609,605 unreal-v8710-2013.10.20-17.29.55.inidump
20/10/2013  17:30               877 unreal-v8710-2013.10.20-17.29.55.json
20/10/2013  17:29             7,740 unreal-v8710-2013.10.20-17.29.55.log
26/10/2013  22:58           400,513 unreal-v8710-2013.10.26-21.35.30.dmp
26/10/2013  22:58               563 unreal-v8710-2013.10.26-21.35.30.event
26/10/2013  22:58           632,198 unreal-v8710-2013.10.26-21.35.30.inidump
26/10/2013  22:58               894 unreal-v8710-2013.10.26-21.35.30.json
26/10/2013  21:35         7,726,623 unreal-v8710-2013.10.26-21.35.30.log
01/11/2013  18:38           281,264 unreal-v8710-2013.11.01-17.38.29.dmp
01/11/2013  18:38               563 unreal-v8710-2013.11.01-17.38.29.event
01/11/2013  18:38           610,523 unreal-v8710-2013.11.01-17.38.29.inidump
01/11/2013  18:38               877 unreal-v8710-2013.11.01-17.38.29.json
01/11/2013  18:38             7,360 unreal-v8710-2013.11.01-17.38.29.log
09/11/2013  17:13           390,153 unreal-v8710-2013.11.09-14.08.26.dmp
09/11/2013  17:13               563 unreal-v8710-2013.11.09-14.08.26.event
09/11/2013  17:13           632,982 unreal-v8710-2013.11.09-14.08.26.inidump
09/11/2013  17:13               894 unreal-v8710-2013.11.09-14.08.26.json
09/11/2013  15:08        19,749,875 unreal-v8710-2013.11.09-14.08.26.log
14/11/2013  22:56           678,237 unreal-v8710-2013.11.14-20.46.33.dmp
14/11/2013  22:56               563 unreal-v8710-2013.11.14-20.46.33.event
14/11/2013  22:56           632,982 unreal-v8710-2013.11.14-20.46.33.inidump
14/11/2013  22:56             1,051 unreal-v8710-2013.11.14-20.46.33.json
14/11/2013  21:46        14,935,229 unreal-v8710-2013.11.14-20.46.33.log
22/11/2013  00:20           378,759 unreal-v8710-2013.11.21-21.45.04.dmp
22/11/2013  00:20               563 unreal-v8710-2013.11.21-21.45.04.event
22/11/2013  00:20           633,030 unreal-v8710-2013.11.21-21.45.04.inidump
22/11/2013  00:20               894 unreal-v8710-2013.11.21-21.45.04.json
21/11/2013  22:45        15,099,971 unreal-v8710-2013.11.21-21.45.04.log
02/12/2013  21:15           359,768 unreal-v8710-2013.12.02-19.19.06.dmp
02/12/2013  21:15               563 unreal-v8710-2013.12.02-19.19.06.event
02/12/2013  21:15           633,060 unreal-v8710-2013.12.02-19.19.06.inidump
02/12/2013  21:15               894 unreal-v8710-2013.12.02-19.19.06.json
02/12/2013  20:19        11,025,946 unreal-v8710-2013.12.02-19.19.06.log
11/03/2014  22:45           821,416 unreal-v8710-2014.03.11-19.09.40.dmp
11/03/2014  22:45               563 unreal-v8710-2014.03.11-19.09.40.event
11/03/2014  22:45           672,020 unreal-v8710-2014.03.11-19.09.40.inidump
11/03/2014  22:45               787 unreal-v8710-2014.03.11-19.09.40.json
11/03/2014  20:09       187,023,774 unreal-v8710-2014.03.11-19.09.40.log
18/03/2014  20:51           952,785 unreal-v8710-2014.03.18-19.49.31.dmp
18/03/2014  20:51               563 unreal-v8710-2014.03.18-19.49.31.event
18/03/2014  20:51           603,649 unreal-v8710-2014.03.18-19.49.31.inidump
18/03/2014  20:51               958 unreal-v8710-2014.03.18-19.49.31.json
18/03/2014  20:49           906,761 unreal-v8710-2014.03.18-19.49.31.log
18/03/2014  20:52           579,876 unreal-v8710-2014.03.18-19.52.04.dmp
18/03/2014  20:52               563 unreal-v8710-2014.03.18-19.52.04.event
18/03/2014  20:52           603,326 unreal-v8710-2014.03.18-19.52.04.inidump
18/03/2014  20:52             1,512 unreal-v8710-2014.03.18-19.52.04.json
18/03/2014  20:52             8,109 unreal-v8710-2014.03.18-19.52.04.log
28/06/2014  14:36           953,131 unreal-v8710-2014.06.28-13.20.32.dmp
28/06/2014  14:36               563 unreal-v8710-2014.06.28-13.20.32.event
28/06/2014  14:36           743,029 unreal-v8710-2014.06.28-13.20.32.inidump
28/06/2014  14:36               801 unreal-v8710-2014.06.28-13.20.32.json
28/06/2014  14:36               801 unreal-v8710-2014.06.28-13.20.32.log

Also mainly filled with this:

[5245.84] ScriptWarning: Accessed None ‘SGPRI’
SGUIScoreboardWidget Transient.SGUIGameMenuManager_4:SGUIScoreboardWidget_4
Function ShooterGame.SGUIScoreboardWidget:UpdateDeadTimer:021C

and

[2647.47] ScriptWarning: Accessed None ‘m_SGTeam’
SGUIGameOverviewScene Transient.SGUIGameMenuManager_2:SGUIGameOverviewScene_2
Function ShooterGame.SGUIGameOverviewScene:UpdateStopwatchTimeBar:037C

(the hex number after ‘UpdateDeadTimer’ / 'UpdateStopwatchTimeBar/ goes up).


(Violator) #18

Just had another CTD (had to end task). Logfile grew from blank to 35MB and was chopped off mid-sentence -

SGPawn OBJ_Victoria.TheWorld:PersistentLevel.SGPawn_607
Function ShooterGame.SGPawn:OnHealthChanged:01BA

[3601.79] ScriptLog: SGPRI RepicatedEvent: Score
[3601.79] Log: ASDPlayerController::SDClientHearSound() SGProjectileItemC4_19 has uninitialised SoundExciter, assu

Possibly related my internet died just after for a minute or so (and trying to post this).


(n4ts) #19

I have the same issue - game crashed 4 times in the last 2 hours.
Also crashed 2 times yesterday.

Programs I had running were:

Teamspeak 3
Steam
Mozilla Firefox
Bitdefender
And some standard Windows stuff.

My connection is stable - no high pings and no packet loss.


(Killgar) #20

The largest log is 800MB, it just crashes notepad and notepad++ says it’s too large to be opened. The smallest log is too large to attach (120 KB).