Game Crashes since V36382 - Help us kill them with fire!

(Silvanoshi) #1

Howdy folks!

As you’re more than likely aware if you’re reading this thread, the frequency of game crashes seems to have increased with V36382. We’ve been quietly working away on the problem, but more information from you guys may help us to track down and crush the bug that’s causing all of this misery.

As such, we’re looking to pull all specific info on the matter into one thread, and direct all new bug reports here. As DB testers, it would be absolutely fanatastic if you could submit a bug report whenever affected by the crashes in this thread.

I’m going to quote a slightly modified versionToomic’s general bug reporting guide here:

[QUOTE=Toomic;409014]Before reporting an issue please make sure you have done the following:

  1. Ensure you meet our Minimum System Requirements
  2. Ensure your Graphics Drivers are up to date

If you can’t find the issue reported on the forums already, please report it with the following information:

Description
• A detailed description of the issue that you encountered
• Try to be as detailed as possible with your description, the more information the better!
• Please state which server you were playing on and the approximate time the issue occurred

Steps to Reproduce
• A list of steps you took leading to the issue
• If the issue occurs 100% of the time when following the given steps
• Include every step you took leading up to the issue, any step could be a clue for us

DxDiag
• Detailed information about your PC specifications
• Essential for compatibility and performance issues, please attach one to every bug
• To obtain your DxDiag, type ‘dxdiag’ into your search bar and then click ‘Save all information’

Screenshot + Bug Location
• Essential for any visual issues, especially issues with certain areas of a map
• Press F12 to take a screenshot or type “Bugit” into the console
• Screenshots are saved to “C:\Users\USERNAME\Documents\My Games\UnrealEngine3\ShooterGame\ScreenShots”
• A .txt document is also produced when F12 is pressed which contains information on the location of the issue, please include this information.
• Screenshots are saved as .bmp files by default, please convert them to Jpeg to upload them

Crash dumps & Log files
• A crash dump provides more detailed information on a crash - these are not always generated
• A log file provides detailed information on the lead up to the crash - essential for every crash
• Client Log files and Crash dumps can be found here for the game “C:\Users\USERNAME\Documents\My Games\UnrealEngine3\ShooterGame\Logs”

Please ensure that no information about the game is posted outside of the VIP Closed Alpha forum[/QUOTE]

We’re aware that the log files are particualrly large at this moment in time, we’ll be working to address that in future builds. In the meantime, rather than uploading the crashlog, please copy and paste its content into your report post, remembering to use the [ PHP]PHP Tags (remove the space after each bracket in each tag)[ /PHP]

Please include the time and date of the crash (remembering to include your timezone) as well.

Here’s to getting this bug tracked down and destroyed!

(Mustang) #2

Okay I tried cutting out a load of the spam to post my report, but after 1.5 hours of editing it’s still 5000 lines long and I can’t remove anything else without knowing that it won’t hinder your ability to track down the bug, yet still it tells me “413 Request Entity Too Large” whenever I try to make my post.

Can you come up with another way to report these crashes please?

(BomBaKlaK) #3

Yep ready to help but same problem.

(n4ts) #4

My whole firefox crashes when I paste my log into the quick reply. LOL

(BomBaKlaK) #5

FTP access is the best solution

(Nail) #6

funny-fox-jumping-snow.jpg450×933 63.6 KB

here’s a pic

(Mustang) #7

Still lots of crashing, any update on how we can report these?

(BomBaKlaK) #8

Look like they don’t care anymore, maybe they find the bug

(Mustang) #9

So for anyone interested the word on the street is that we should wait until the next build to give our reports, if it’s still crashing then, because the plan is to have log files fixed by this time, that is they should be smaller and pasteable again.

(spookify) #10

Well I broke my game somehow…

The nexon launcher works fine and I thought I would close it while the game was loading.

I signs in and refreshing account an insta freezes every-time… I can not get on…

EDIT:

I repaired the game = Nothing

I uninstalled twice and even deleted the folder = Nothing

It almost loads me into the main menu after the auth and the little spinning flash type thing starts right before the NDA OK window and it crashes and the Nexon error report pops up.

Looks like I am done playing for a while! I was rocking the hours too! Crap!

Edit: I was also messing with SLI before I opened the game the first time…

Open Crash Open Crash over and over and the oops report error pops up.

(spookify) #11

Bump^ Help :frowning:

(Silvanoshi) #12

Your issue is slightly different to the one that this topic is addressing. Let’s continue discussing yours in the thread that you started.

(fzl) #13

Here is a little Tip for the Crash Issues…:mad:

this one helps me…

nexon launcher .exe set it to win7 mode in properties :cool:

extraction exe set in process mode (task manager) to “high priority” :cool:

now i have max. 1 crash in 2-3 hours of playing …before i had 4-6 crashes per hour…

hope this helps a few players a little bit

greetz fzl aka Pilgr!m:stroggflag:

note. Special Thanks to HardyRah for his suggestions…

(spookify) #14

SD do you still want us to report crashes? Or wait until next patch now? I crash about 3 times a night now and it seems to be new or possible due to the new Nvidia graphics driver that just came out… Thats the only thing I can think of that I got new. I think I did try to tweak my cfg also… I will go back to default and wait until next patch.

(Silvanoshi) #15

It certainly would be interesting to hear how how going back to the default config affects your crash rate.