Ekis Zak Posted May 9, 2015 I just installed the Doomsday Engine and whenever I up a game doesn't load up and I get a error message along the lines of "Doomsday has crashed". I'm running 32-Bit Windows 7. 0 Quote Share this post Link to post
Doomkid Posted May 9, 2015 Could you provide a screenshot of the crash? 0 Quote Share this post Link to post
Ekis Zak Posted May 9, 2015 I click play, the window disappears and this shows up http://imgur.com/r035NiI 0 Quote Share this post Link to post
snapshot Posted May 9, 2015 Ekis Zak said:I click play, the window disappears and this shows up http://imgur.com/r035NiI You need to Update your graphics card driver, you can install "Ma-config" and let scan your PC to detect your drivers : http://www.ma-config.com/fr/configuration/ 0 Quote Share this post Link to post
Graf Zahl Posted May 9, 2015 DMGUYDZ64 said:You need to Update your graphics card driver Are you a clairvoyant or what? That error doesn't even remotely give enough information about what is at fault here. 0 Quote Share this post Link to post
snapshot Posted May 9, 2015 Graf Zahl said:Are you a clairvoyant or what? That error doesn't even remotely give enough information about what is at fault here. Yes i am >:) That happened to me before when i reinstalled the Os, i Still didn't install anything and i had this crash till i Decided to install the drivers and it worked . 0 Quote Share this post Link to post
Doomkid Posted May 9, 2015 Obligatory "are your IWADs in the folder, have you tried right clicking and running as Administrator" post. Aside from that, this is just flat out weird. 0 Quote Share this post Link to post
DaniJ Posted May 9, 2015 Looks like the classic Windows missing OpenGL driver issue to me. Doomsday does not require you to copy your IWADs, nor does it need admin access to any of the folders used by default. 0 Quote Share this post Link to post
Ekis Zak Posted May 9, 2015 Doomkid said:Obligatory "are your IWADs in the folder, have you tried right clicking and running as Administrator" post. Aside from that, this is just flat out weird. Tried that, I'll try what DMGUYDZ64 said. 0 Quote Share this post Link to post
Ekis Zak Posted May 10, 2015 I've also had another problem, but this time it's with GZDoom. Ultimate Doom, Doom 2, Plutonia and TNT work fine but games like Hexen, Strife or even Chex Quest refuse to start up and I get this error message http://imgur.com/UiR0qbT. 0 Quote Share this post Link to post
Graf Zahl Posted May 10, 2015 First, get a newer GZDoom version from http://forum.drdteam.org . 1.8.2 is very old and obsolete. 0 Quote Share this post Link to post
Ekis Zak Posted May 10, 2015 Graf Zahl said:First, get a newer GZDoom version from http://forum.drdteam.org . 1.8.2 is very old and obsolete. I just downloaded the new GZDoom version (2.0.05) but it still gives me the error. EDIT: I also get this error when trying to start any Doom game now that I've updated http://imgur.com/ELaVwdr. 0 Quote Share this post Link to post
Graf Zahl Posted May 10, 2015 Can you post the entire startup log? Normally this error means that the engine tries to load some corrupt data and tries to allocate an incorrect amount of memory which fails. I'd need to see what was printed to the log before. For that you have to start the engine from the command line with 'gzdoom +logfile log.txt'. 0 Quote Share this post Link to post
Ekis Zak Posted May 10, 2015 OS: Windows 7 (NT 6.1) Build 7601 Service Pack 1 M_LoadDefaults: Load system defaults. Using program directory for storage Gameinfo scan took 0 ms W_Init: Init WADfiles. adding C:/Users/```/Desktop/Doom/gzdoom.pk3, 587 lumps adding ./doom2.wad, 2919 lumps I_Init: Setting up machine state. CPU Speed: 2328 MHz CPU Vendor ID: GenuineIntel Name: Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz Family 6, Model 15, Stepping 11 Features: MMX SSE SSE2 SSE3 SSSE3 I_InitSound: Initializing FMOD FMOD Sound System, copyright © Firelight Technologies Pty, Ltd., 1994-2009. Loaded FMOD version 4.26.27 V_Init: allocate screen. S_Init: Setting up sound. ST_Init: Init startup screen. Checking cmd-line parameters... S_InitData: Load sound definitions. G_ParseMapInfo: Load map definitions. Texman.Init: Init texture manager. ParseTeamInfo: Load team definitions. LoadActors: Load actor definitions. R_Init: Init Doom refresh subsystem. DecalLibrary: Load decals. M_Init: Init menus. P_Init: Init Playloop state. ParseSBarInfo: Loading default status bar definition. ParseSBarInfo: Loading custom status bar definition. D_CheckNetGame: Checking network game status. player 1 of 1 (1 nodes) I_InitInput I_StartupMouse I_StartupKeyboard I_StartupXInput I_StartupRawPS2 I_StartupDirectInputJoystick Warning: 'Object' is freed outside the GC process. Execution could not continue. R_OPENGL: Unable to create an OpenGL 3.x render context. 0 Quote Share this post Link to post
Graf Zahl Posted May 10, 2015 Your hardware does not support OpenGL 3.x. In that case you have to use 1.8.10, the 2.x builds won't work. 0 Quote Share this post Link to post
Ekis Zak Posted May 10, 2015 Graf Zahl said:Your hardware does not support OpenGL 3.x. In that case you have to use 1.8.10, the 2.x builds won't work. I'm getting an error message saying "Unsupported OpenGL version. At least GL 2.0 is required to run GZDoom." I'm on GZDoom 1.8.10 0 Quote Share this post Link to post
Graf Zahl Posted May 10, 2015 What kind of graphics hardware do you use? 0 Quote Share this post Link to post
Ekis Zak Posted May 12, 2015 Graf Zahl said:What kind of graphics hardware do you use? Sorry for the late reply. i believe it's a ATI Radeon HD2400. I'm running a Dell Optiplex 755 with no new parts. 0 Quote Share this post Link to post
DaniJ Posted May 12, 2015 Evidently OpenGL 3.0 support for the HD2400 was added in Catalyst 9.1 for XP and Vista (no mention of 7, though). Try going here and see if automatic detection suggests a better driver for you. 0 Quote Share this post Link to post
Ekis Zak Posted May 16, 2015 DaniJ said:Evidently OpenGL 3.0 support for the HD2400 was added in Catalyst 9.1 for XP and Vista (no mention of 7, though). Try going here and see if automatic detection suggests a better driver for you. Nope they gave me nothing but Vista software. 0 Quote Share this post Link to post
DaniJ Posted May 16, 2015 As far as I know, it is generally possible to use Vista drivers on Windows 7 because the OS is backward compatible. You could try making a system restore point and then install the Vista driver to see if it works. If not, you can simply roll back. Worth a try at least. 0 Quote Share this post Link to post
Ekis Zak Posted May 16, 2015 DaniJ said:As far as I know, it is generally possible to use Vista drivers on Windows 7 because the OS is backward compatible. You could try making a system restore point and then install the Vista driver to see if it works. If not, you can simply roll back. Worth a try at least. I've use the installers I've been given but I they say they've been installed but nothing has changed. 0 Quote Share this post Link to post
DaniJ Posted May 16, 2015 Its probably a long shot but have you tried running the installer in Windows Vista compatibility mode? (Right click -> Properties, check "Run this program in compatibility mode for:", select Windows Vista) 0 Quote Share this post Link to post
Ekis Zak Posted May 16, 2015 DaniJ said:Its probably a long shot but have you tried running the installer in Windows Vista compatibility mode? (Right click -> Properties, check "Run this program in compatibility mode for:", select Windows Vista) I'll try that. 0 Quote Share this post Link to post
DaniJ Posted May 16, 2015 There is one other method that I am aware of and that depends on having a "plain" *.inf file for your driver and using the PnPUtil command to install it manually... However! Do proceed with caution because I've never done that myself and I can't advise you whether its going to work or guarantee anything. If you do decide to try this method then do take the time to understand what you are actually doing before messing about with admin privileges in the guts of your system. 0 Quote Share this post Link to post
Ekis Zak Posted May 16, 2015 DaniJ said:There is one other method that I am aware of and that depends on having a "plain" *.inf file for your driver and using the PnPUtil command to install it manually... However! Do proceed with caution because I've never done that myself and I can't advise you whether its going to work or guarantee anything. If you do decide to try this method then do take the time to understand what you are actually doing before messing about with admin privileges in the guts of your system. Would this screw up the parts in my PC or just screw up my files. 0 Quote Share this post Link to post
DaniJ Posted May 16, 2015 I don't *think* it would lead to catastrophe (do create a restore point first!) but honestly I can't say for sure. Documentation for PnpUtil 0 Quote Share this post Link to post
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.