Some issues I'd like patched...

Post » Fri Nov 16, 2012 12:34 am

I'm really looking forward to playing this game when my Oculus Rift arrives. It will be awesome. I haven't actually played the game itself yet, except for a bit of poking around and testing.

But poking around with it, I noticed some issues that you should fix:

1. The installer complained about insufficient privileges when it tried to launch the DirectX setup and the Visual C++ runtime installer. I had to run them manually.
2. Alt+Tab doesn't work. That's completely unacceptable in a modern game. We need to be able to access our desktop sometimes.
3. In the Full SBS 3D mode, the status bar text describing the menu items in the main menu is unreadable because it's positioned in the wrong place (too far to the left).
4. There's no obvious Oculus Rift, or other HMD, support, except by manually setting many console commands individually. That isn't too surprising since the Oculus Rift design hadn't been finalised when Doom 3 BFG was released. But it needs to be patched for proper Oculus Rift support, including the new tracker and new FOV, before December when the dev kits come out.
5. When I tried activating the Rift's screen warping with a console command, it seemed to also letterbox the top and bottom of the screen with straight black bars. I don't like that, unless those pixels really can't ever be seen while wearing a Rift. Hopefully that's my fault and just an issue with the way I messed with the commands and settings, and not a design decision.
6. Doom 1 and Doom 2 don't support widescreen (needed for most TVs) or tallscreen (needed for the Oculus Rift).
7. Doom 1 and Doom 2 don't support 3D.
8. Doom 1 and Doom 2 don't have the humorous messages when you try to quit.
9. Doom 1 and Doom 2 medikits don't look right. You need to tell the Red Cross that you can't tamper with a historic work of art like Doom, any more than you could paint over parts of the Mona Lisa that offended someone. Tell them you tried to do what they wanted, but players just wouldn't accept that kind of mutilation of the classics. And change them back.
10. Doom 2 has almost completely removed the secret level. That's completely unacceptable for people outside Germany. Don't forget that other countries have laws about what you can sell too... and one of those laws is that you can't falsely claim to include the original Doom 1 and Doom 2 games when you aren't doing that. You are legally obligated to provide us outside Germany, with the Doom 1 and Doom 2 that you promised. So there needs to be a special patch just for the non-Germany region.
User avatar
Misty lt
 
Posts: 3400
Joined: Mon Dec 25, 2006 10:06 am

Post » Fri Nov 16, 2012 10:48 am

1. Not sure on this one.
2. Fully agree, this is completely unacceptable.
3. No comment.
4. Don't care for 3D support.
5. That should be fixed.
6. Source ports fix this.
7. No no no no no. A 19 year old game does NOT need 3D!
8. Another blow by gamesas(?) thinking those messages are too cheesy?
9. Strongly agree. Red Cross can go get bent, the iconic artwork of the game should NOT be altered in any way!
10. Also a strong agree, but http://www.doomworld.com/vb/wads-mods/61818-doom-3-bfg-edition-iwad-patches/
User avatar
Melanie Steinberg
 
Posts: 3365
Joined: Fri Apr 20, 2007 11:25 pm

Post » Thu Nov 15, 2012 9:23 pm

1. This is normal for installers that update system files, and is enforced by Windows. There's nothing id can do about that.

2. Alt-Tab actually does work but the BFG edition window remains topmost. An easy enough fix.

3. No idea.

4. I expect this to be patched when the Rift spec is finalized. It's one of the major selling points.

5. See 4.

6. Widescreen should be supported. It's nice to remain faithful to the original, but when the original was clearly crap it's a sign that it's faithfulness gone too far. For tallscreen see 7.

7. I don't expect this to be patched. id might surprise us though.

8. These should be restored.

9. I don't expect this to be patched. It's a decision for the legal team rather than the developers anyway.

10. This would first need an investigation into whether or not id actually did claim to be selling the original games, or is that more a case of people reading more things into public announcements that weren't even there to begin with? Either way it's a tricky one; I'll refrain from further comment.
User avatar
мistrєss
 
Posts: 3168
Joined: Thu Dec 14, 2006 3:13 am

Post » Fri Nov 16, 2012 12:04 pm

2. Alt+Tab doesn't work. That's completely unacceptable in a modern game. We need to be able to access our desktop sometimes.

USe Alt-Enter to switch from full screen to windowed mode to get to the desktop - then escape button to get the mouse pointer to the desktop ( so Alt-Enter-esc to get to desktop ) then left click back in window of game and alt enter again to get back to full screen game play !
User avatar
Gisela Amaya
 
Posts: 3424
Joined: Tue Oct 23, 2007 4:29 pm

Post » Fri Nov 16, 2012 2:19 am

Well, I for one would like to be able to play the game for a start. I get some OpenGL error everytime I try to start it.
User avatar
Felix Walde
 
Posts: 3333
Joined: Sat Jun 02, 2007 4:50 pm

Post » Thu Nov 15, 2012 11:52 pm

Well, I for one would like to be able to play the game for a start. I get some OpenGL error everytime I try to start it.

That is usually due to a problem with either outdated or improperly installed video drivers (ssems to be common on Intel chipset graphics if using the newest drivers try reverting to v2761 they seem to work fine but newer ones ( 2828 / 2857beta / 2867) are having problems with the new opengl driver included in them !) - if not on Intel then make sure you have the latest video card drivers for your card and that you have installed them properly.
User avatar
James Hate
 
Posts: 3531
Joined: Sun Jun 24, 2007 5:55 am

Post » Fri Nov 16, 2012 2:51 am

It would also help diagnosis if you said what the error was.
User avatar
Michelle davies
 
Posts: 3509
Joined: Wed Sep 27, 2006 3:59 am

Post » Fri Nov 16, 2012 12:06 pm

It would also help diagnosis if you said what the error was.

Ha. Suppose so. Tried updating my drivers. Not sure how to roll them back to v.2761. Will copy exactly what the window that pops up says, and you can make sense of it if you like.

QA Timing INIT: 000088ms
D3BFG 1.1400 win-x86 Oct 5 2012 11:38:38
2094 MHz Intel CPU with MMX & SSE & SSE2 & SSE3 & HTT
3008 MB System Memory
1308 MB Video Memory
Winsock Initialized
Found interface: {03CE49E4-F02D-4136-AE97-97AF52A07FF0} Atheros AR9287 Wireless Network Adapter - 192.168.1.66/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:
C:\Program Files (x86)\Steam\steamapps\common\DOOM 3 BFG Edition/base
C:\Users\Mead\Saved 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: Mobile Intel® 4 Series Express Chipset Family
StateFlags : 0x5
DeviceID : PCI\VEN_8086&DEV_2A42&SUBSYS_048A1025&REV_09
DeviceKey : \Registry\Machine\System\CurrentControlSet\Control\Video\{2BDF8524-DD06-409A-96C5-4D3DDCA18CD4}\0000
DeviceName : \\.\DISPLAY1\Monitor0
DeviceString: Generic PnP Monitor
StateFlags : 0x3
DeviceID : MONITOR\SEC3046\{4d36e96e-e325-11ce-bfc1-08002be10318}\0000
DeviceKey : \Registry\Machine\System\CurrentControlSet\Control\Class\{4d36e96e-e325-11ce-bfc1-08002be10318}\0000
dmPosition.x : 0
dmPosition.y : 0
dmBitsPerPel : 32
dmPelsWidth : 1366
dmPelsHeight : 768
dmDisplayFlags : 0x0
dmDisplayFrequency: 60
...calling CDS: ok
display device: 0
DeviceName : \\.\DISPLAY1
DeviceString: Mobile Intel® 4 Series Express Chipset Family
StateFlags : 0x5
DeviceID : PCI\VEN_8086&DEV_2A42&SUBSYS_048A1025&REV_09
DeviceKey : \Registry\Machine\System\CurrentControlSet\Control\Video\{2BDF8524-DD06-409A-96C5-4D3DDCA18CD4}\0000
DeviceName : \\.\DISPLAY1\Monitor0
DeviceString: Generic PnP Monitor
StateFlags : 0x3
DeviceID : MONITOR\SEC3046\{4d36e96e-e325-11ce-bfc1-08002be10318}\0000
DeviceKey : \Registry\Machine\System\CurrentControlSet\Control\Class\{4d36e96e-e325-11ce-bfc1-08002be10318}\0000
dmPosition.x : 0
dmPosition.y : 0
dmBitsPerPel : 32
dmPelsWidth : 1280
dmPelsHeight : 720
dmDisplayFlags : 0x0
dmDisplayFrequency: 60
...created window @ 0,0 (1280x720)
Initializing OpenGL driver
...SetPixelFormat failed
Shutting down OpenGL subsystem
...wglMakeCurrent( NULL, NULL ): failed
...releasing DC: failed
...resetting display
...shutting down QGL
...unloading OpenGL DLL
Initializing OpenGL subsystem with multisamples:0 stereo:0 fullscreen:1
...initializing QGL
...calling LoadLibrary( 'opengl32' ): succeeded
X..WGL_EXT_swap_control_tear not found
display device: 0
DeviceName : \\.\DISPLAY1
DeviceString: Mobile Intel® 4 Series Express Chipset Family
StateFlags : 0x5
DeviceID : PCI\VEN_8086&DEV_2A42&SUBSYS_048A1025&REV_09
DeviceKey : \Registry\Machine\System\CurrentControlSet\Control\Video\{2BDF8524-DD06-409A-96C5-4D3DDCA18CD4}\0000
DeviceName : \\.\DISPLAY1\Monitor0
DeviceString: Generic PnP Monitor
StateFlags : 0x3
DeviceID : MONITOR\SEC3046\{4d36e96e-e325-11ce-bfc1-08002be10318}\0000
DeviceKey : \Registry\Machine\System\CurrentControlSet\Control\Class\{4d36e96e-e325-11ce-bfc1-08002be10318}\0000
dmPosition.x : 0
dmPosition.y : 0
dmBitsPerPel : 32
dmPelsWidth : 1366
dmPelsHeight : 768
dmDisplayFlags : 0x0
dmDisplayFrequency: 60
...calling CDS: ok
display device: 0
DeviceName : \\.\DISPLAY1
DeviceString: Mobile Intel® 4 Series Express Chipset Family
StateFlags : 0x5
DeviceID : PCI\VEN_8086&DEV_2A42&SUBSYS_048A1025&REV_09
DeviceKey : \Registry\Machine\System\CurrentControlSet\Control\Video\{2BDF8524-DD06-409A-96C5-4D3DDCA18CD4}\0000
DeviceName : \\.\DISPLAY1\Monitor0
DeviceString: Generic PnP Monitor
StateFlags : 0x3
DeviceID : MONITOR\SEC3046\{4d36e96e-e325-11ce-bfc1-08002be10318}\0000
DeviceKey : \Registry\Machine\System\CurrentControlSet\Control\Class\{4d36e96e-e325-11ce-bfc1-08002be10318}\0000
dmPosition.x : 0
dmPosition.y : 0
dmBitsPerPel : 32
dmPelsWidth : 1280
dmPelsHeight : 720
dmDisplayFlags : 0x0
dmDisplayFrequency: 60
...created window @ 0,0 (1280x720)
Initializing OpenGL driver
...SetPixelFormat failed
Shutting down OpenGL subsystem
...wglMakeCurrent( NULL, NULL ): failed
...releasing DC: failed
...resetting display
...shutting down QGL
...unloading OpenGL DLL
Unknown command 'vid_restart'
Unable to initialize OpenGL
Shutting down OpenGL subsystem
...shutting down QGL
User avatar
Alexandra Ryan
 
Posts: 3438
Joined: Mon Jul 31, 2006 9:01 am

Post » Fri Nov 16, 2012 5:50 am

Here's your problem:

DeviceString: Mobile Intel? 4 Series Express Chipset Family

The 4 Series is, unfortunately, not a great gfx chip and almost certainly can't run BFG Edition. I have run the original Doom 3 on one, and it needed 640x480 mode with most everything disabled to peak at 20fps.

It is Direct3D 10 capable but Intel's OpenGL driver hasn't tracked the capability of their D3D driver, so it's stuck at GL 2.1 - which is nowhere near sufficient for BFG Edition (as an aside, while BFG Edition can run up to 5 times faster it uses modern GPU capabilities to achieve that, and the 4 Series doesn't expose those in it's GL driver - you're also highly unlikely to make 5x on a 4 Series as it's going to bottleneck on fillrate anyway).

You may be still in luck. If you have e.g. an AMD switchable graphics or NVIDIA Optimus laptop (I'm assuming a laptop owing to the mobile gfx chip) it may be the case that BFG Edition is just detecting the wrong gfx chip on startup, in which case there should be a control panel option (in your gfx chip's control panel) for telling it which chip to use, or - worst case - you should be able to disable the switchable/etc graphics in your BIOS. It's unfortunate that this technology isn't standardised between vendors and between APIs otherwise none of that would be a problem, but until such a time as that does happen it is the customer who ends up suffering.
User avatar
Yvonne
 
Posts: 3577
Joined: Sat Sep 23, 2006 3:05 am

Post » Fri Nov 16, 2012 3:25 am

Ah. Okay. Bad news is I don't have the switchable graphics at all, so yeah. Thanks for the help. Really appreciate it.
User avatar
Angelina Mayo
 
Posts: 3427
Joined: Wed Jan 24, 2007 4:58 am


Return to Othor Games