What the hell happened there!?

Post » Fri Nov 16, 2012 6:39 pm

Dear id/Bethesda,

I've been a massive fan of DOOM and other groundbreaking id titles since the age of 4, I preordered the BFG edition back in July on Amazon and I've been anxiously awaiting its arrival, in particular I've been getting very giddy this past week. Unfortunately, upon installing the game about an hour ago and launching it, a little message said this.

QA Timing INIT: 000075ms
D3BFG 1.1400 win-x86 Oct 5 2012 11:38:38
3415 MHz AMD CPU with MMX & 3DNow! & SSE & SSE2 & SSE3 & HTT
3328 MB System Memory
1024 MB Video Memory
Winsock Initialized
Found interface: {63B5E4AF-EF1E-4C92-9E51-3EB519979050} 802.11g USB 2.0 adapter #4 - Packet Scheduler Miniport - 10.0.0.2/255.255.255.0
Sys_InitNetworking: adding loopback interface
doom using MMX & SSE for SIMD processing
enabled Flush-To-Zero mode
enabled Denormals-Are-Zero mode
------ Initializing File System ------
Loaded resource file _common.resources
Loaded resource file _ordered.resources
Loaded resource file _sound_pc.resources
Loaded resource file _sound_pc_en.resources
Current search path:
D:\Program Files\Steam\steamapps\common\DOOM 3 BFG Edition/base
C:\Documents and Settings\Ciaran\My Documents\My Games\id Software\DOOM 3 BFG/base
file system initialized.
--------------------------------------
WARNING: Unable to open resource file maps/_startup.resources
----- Initializing Decls -----
------------------------------
Couldn't open journal files
execing default.cfg
couldn't exec D3BFGConfig.cfg
couldn't exec autoexec.cfg
----- R_InitOpenGL -----
Initializing OpenGL subsystem with multisamples:0 stereo:0 fullscreen:1
...registered window class
...registered fake window class
...initializing QGL
...calling LoadLibrary( 'opengl32' ): succeeded
X..WGL_EXT_swap_control_tear not found
display device: 0
DeviceName : \\.\DISPLAY1
DeviceString: AMD Radeon HD 6800 Series
StateFlags : 0x8000005
DeviceID : PCI\VEN_1002&DEV_6739&SUBSYS_23041787&REV_00
DeviceKey : \Registry\Machine\System\CurrentControlSet\Control\Video\{D5C81310-1CE8-4719-B143-553712C1E4F5}\0000
DeviceName : \\.\DISPLAY1\Monitor0
DeviceString: Plug and Play Monitor
StateFlags : 0x3
DeviceID : Monitor\SAM02AD\{4D36E96E-E325-11CE-BFC1-08002BE10318}\0007
DeviceKey : \Registry\Machine\System\CurrentControlSet\Control\Class\{4D36E96E-E325-11CE-BFC1-08002BE10318}\0007
dmPosition.x : 0
dmPosition.y : 0
dmBitsPerPel : 32
dmPelsWidth : 1440
dmPelsHeight : 900
dmDisplayFlags : 0x0
dmDisplayFrequency: 60
...calling CDS: ok
display device: 0
DeviceName : \\.\DISPLAY1
DeviceString: AMD Radeon HD 6800 Series
StateFlags : 0x8000005
DeviceID : PCI\VEN_1002&DEV_6739&SUBSYS_23041787&REV_00
DeviceKey : \Registry\Machine\System\CurrentControlSet\Control\Video\{D5C81310-1CE8-4719-B143-553712C1E4F5}\0000
DeviceName : \\.\DISPLAY1\Monitor0
DeviceString: Plug and Play Monitor
StateFlags : 0x3
DeviceID : Monitor\SAM02AD\{4D36E96E-E325-11CE-BFC1-08002BE10318}\0007
DeviceKey : \Registry\Machine\System\CurrentControlSet\Control\Class\{4D36E96E-E325-11CE-BFC1-08002BE10318}\0007
dmPosition.x : 0
dmPosition.y : 0
dmBitsPerPel : 32
dmPelsWidth : 1280
dmPelsHeight : 720
dmDisplayFlags : 0x0
dmDisplayFrequency: 60
...created window @ 0,0 (1280x720)
Initializing OpenGL driver
...creating GL context: created OpenGL 3.2 context
succeeded
...making context current: succeeded
X..WGL_EXT_swap_control_tear not found

------- Input Initialization -------
Initializing DirectInput...
mouse: DirectInput initialized.
keyboard: DirectInput initialized.
freespace_version: 0.6
0 freespace devices
------------------------------------
OpenGL Version: 3.2
OpenGL Vendor : ATI Technologies Inc.
OpenGL GLSL : 4.2
...using GL_ARB_multitexture
...using GL_EXT_direct_state_access
...using GL_ARB_texture_compression
...using GL_EXT_texture_compression_s3tc
...using GL_EXT_texture_filter_anisotropic
maxTextureAnisotropy: 16.000000
...using GL_EXT_texture_lod_bias
...using GL_ARB_seamless_cube_map
...using GL_ARB_framebuffer_sRGB
...using GL_ARB_vertex_buffer_object
...using GL_ARB_map_buffer_range
...using GL_ARB_vertex_array_object
...using GL_ARB_draw_elements_base_vertex
...using GL_ARB_fragment_program
...using GL_ARB_uniform_buffer_object
X..GL_EXT_depth_bounds_test not found
...using GL_ARB_sync
...using GL_ARB_occlusion_query
...using GL_ARB_timer_query
Couldn't find proc address for: glGetQueryObjectui64vARB
X..GL_ARB_debug_output not found
----- Initializing Render Shaders -----
While linking GLSL program 32 with vertexShader shadow.vp and fragmentShader
Vertex shader(s) linked.

While linking GLSL program 33 with vertexShader shadow_skinned.vp and fragmentShader
Vertex shader(s) linked.

Unknown command 'vid_restart'
idJointBuffer::MapBuffer: failed
Shutting down OpenGL subsystem
...wglMakeCurrent( NULL, NULL ): success
...deleting GL context: success
...releasing DC: success
...destroying window
...resetting display
...shutting down QGL
...unloading OpenGL DLL


Now as I understand it, a few other people have had similar problems. RAGE was forgivable, we all get hiccups afterall, but TWO consecutive releases that don't work is rather upsetting and disturbing. I sincerely hope DOOM 4 doesn't suffer from this kind of out of the box 'support' or I fear many customers and loyal fans on the PC will give subsequent releases a miss.

I hope this problem can be fixed, so myself and others can blast the demons we wanted to today :smile:

Regards
SPAYYSE!
User avatar
Heather Kush
 
Posts: 3456
Joined: Tue Jun 05, 2007 10:05 pm

Post » Fri Nov 16, 2012 3:15 pm

Hmmm, buddy of mine had that same issue from installing from STEAM. Try deleting all local data via STEAM properties for the game, and reinstalling, it may have been delivered corrupted. Also, are you installing the game with a STEAM setting for non-standard Local install locations?
User avatar
Flesh Tunnel
 
Posts: 3409
Joined: Mon Sep 18, 2006 7:43 pm

Post » Fri Nov 16, 2012 6:45 pm

Hmmm, buddy of mine had that same issue from installing from STEAM. Try deleting all local data via STEAM properties for the game, and reinstalling, it may have been delivered corrupted. Also, are you installing the game with a STEAM setting for non-standard Local install locations?

I'll give it a shot. By that do you mean do I install outside the STEAM folder in Program Files? If so no, I let Steam decide where do put it. :)
User avatar
Robert DeLarosa
 
Posts: 3415
Joined: Tue Sep 04, 2007 3:43 pm

Post » Sat Nov 17, 2012 1:04 am

yep, that's what I mean. So if your letting steam use it's default directories and install, then you should be good. On a side note, ATI drivers are having some issues with Doom 3 BFG edition as of current... I see your display adapter is ATI... have you tried installing latest drivers? if you are using them, there's been a lot of people updating forums with ATI-related bugs for this release, so search through some of the ATI bug posts to see if there may be similar issues from other ATI owners reported and if any resolutions
User avatar
Laura Wilson
 
Posts: 3445
Joined: Thu Oct 05, 2006 3:57 pm

Post » Fri Nov 16, 2012 6:18 pm

I've realized something. It ain't XP compatible is it? Luckily I'm dual booting with Windows 7 and it works just fine on that, its pretty awesome! However I'm still quite shocked that RAGE, which is technically superior to DOOM 3, is XP compatible and this isn't. Funny old world but hey ho. Thanks for your responses beavermatic :)
User avatar
Connor Wing
 
Posts: 3465
Joined: Wed Jun 20, 2007 1:22 am


Return to Othor Games