One of the Devs wants a proper debug report. What do I do/post?
The more (relevant) information you give us the more chance we have of solving the problem. So here's what I need.
1) Your computers CPU, graphics card and RAM. Sound card can help too.
2) Run the debug build (either directly or by selecting it from the launcher) If it gives you an error message. Post it. On Windows all you need to do is paste (Possibly on Linux and Mac too).
3) After it crashes, runs or whatever you'll find a file called FS2_Open.log in your Data folder. That file give me a whole bunch of useful info. Here's what I want from it.
DEBUG SPEW: No debug_filter.cfg found, so only general, error, and warning
categories can be shown and no debug_filter.cfg info will be saved.
Passed cmdline options:
Building file index...
Searching root 'I:\games\btrl\demo\'
Searching root pack 'I:\games\btrl\demo\z_missions_BtRLDemo.vp'
Searching root pack 'I:\games\btrl\demo\z_root_BtRLDemo.vp'
Found 3 roots and 3246 files.
Setting language to English
Using 'Generic Software' as OpenAL sound device...
OpenAL Vendor : Creative Labs Inc.
OpenAL Renderer : Software
OpenAL Version : 1.1
... OpenAL successfully initialized!
GR_CPU: Family 6, MMX=Yes
Initializing OpenGL graphics device at 1024x768 with 32-bit color...
Requested WGL Video values = R: 8, G: 8, B: 8, depth: 24, double-buffer: 1
Actual WGL Video values = R: 8, G: 8, B: 8, depth: 24, double-buffer: 1
OpenGL Vendor : ATI Technologies Inc.
OpenGL Renderer : RADEON 9800 x86/MMX/3DNow!/SSE
OpenGL Version : 2.0.5885 WinXP Release
And the last 5 lines.
I don't need the rest unless I ask.
4) If the game crashes I don't need your entire errorlog.txt file. All I need is this bit
fs2_open_3_6_9_debug caused an Access Violation in module fs2_open_3_6_9_debug.exe at 001b:007b3ec6.
Exception handler called in FreeSpace 2 Main Thread.
Error occurred at 3/6/2007 20:05:00.
F:\Games\Freespace2\fs2_open_3_6_9_debug.exe, run by NamelessOne.
1 processor(s), type 586.
1024 MBytes physical memory.
Read from location 00000000 caused an access violation.