Posted May 06, 2018
*SOLVED* Reinstalling the most current drivers for NVIDIA seemed to fix the issue. I guess I jumped the gun on blaming the game for driver issues. This topic is now irrelevant. Thank you! *SOLVED*
Hello everyone here on GoG.com. I recently completed the base game of the first F.E.A.R game with little issues (had to disable HID devices with a simple .dll file.) After completing the campaign however, I ran into some more issues with the expansions:
- Both of the expansions refuse to launch.
- When launched, both of the .exe files go to a back screen briefly - before returning to the desktop with the error message:
"Unable to initialize the renderer to a valid video mode".
What I've tried so far:
- Modifying the settings.cfg files on both of their respective document folders to match the settings I used for the base game.
- Copying over the settings.cfg from the base game and replacing the expansion settings. There is not much there, since not much has been changed due to being unable to launch the games in the first place.
- Overriding the game's settings with NVIDIA Control Panel to force the game to use my current GPU, to no avail.
- Using compatibility modes for windows XP SP2 & 3
- I even picked up a hint from one user on the Steam forums to disable any image mounting tools from my PC (such as Daemon Tools), which I did. No bueno.
These are the settings I've tried:
- All of the config.exe resolutions in the Expansions' own configuration launcher.
And these, overridden in the settings.cfg file located in C:\Users\Public\Documents\TimeGate Studios\FEARXP :
"GammaB" "1.069204"
"GammaG" "1.069204"
"Renderer" "NVIDIA GeForce GTX 1060 6GB"
"GammaR" "1.069204"
"BitDepth" "32"
"HardwareCursor" "1.000000"
"ScreenWidth" "1920"
"VSyncOnFlip" "0.000000"
"DeviceName" "\\.\DISPLAY1"
"ScreenHeight" "1080"
"RestartRenderBetweenMaps" "1.000000"
Aaand to give you guys more specifications about the rig that I'm running (even though it should make little difference, due to the base game working wonderfully).
Operating System: Windows 10 Pro 64-bit (10.0, Build 16299) (16299.rs3_release.170928-1534)
BIOS: BIOS Date: 06/07/17 10:10:53 Ver: 04.06.05
Processor: AMD FX(tm)-8350 Eight-Core Processor (8 CPUs), ~4.5GHz
Memory: 16384MB RAM
Available OS Memory: 16296MB RAM
Page File: 8148MB used, 10580MB available
DirectX Version: DirectX 12
Card name: NVIDIA GeForce GTX 1060 6GB
DAC type: Integrated RAMDAC
Device Type: Full Device
Display Memory: 14200 MB
Dedicated Memory: 6052 MB
Shared Memory: 8148 MB
Nvidia driver version: 397.31
If you need the full dxdiag for further analysis, I will be more than happy to provide it for you. For the sake of this forum post however, I will leave you with these essentials.
Does anyone have a clue how to make these expansions work? I'd really like to try them out, since they are pretty much the only content I haven't played from the original game of the series.
*SOLVED* Reinstalling the most current drivers for NVIDIA seemed to fix the issue. I guess I jumped the gun on blaming the game for driver issues. This topic is now irrelevant. Thank you! *SOLVED*
Hello everyone here on GoG.com. I recently completed the base game of the first F.E.A.R game with little issues (had to disable HID devices with a simple .dll file.) After completing the campaign however, I ran into some more issues with the expansions:
- Both of the expansions refuse to launch.
- When launched, both of the .exe files go to a back screen briefly - before returning to the desktop with the error message:
"Unable to initialize the renderer to a valid video mode".
What I've tried so far:
- Modifying the settings.cfg files on both of their respective document folders to match the settings I used for the base game.
- Copying over the settings.cfg from the base game and replacing the expansion settings. There is not much there, since not much has been changed due to being unable to launch the games in the first place.
- Overriding the game's settings with NVIDIA Control Panel to force the game to use my current GPU, to no avail.
- Using compatibility modes for windows XP SP2 & 3
- I even picked up a hint from one user on the Steam forums to disable any image mounting tools from my PC (such as Daemon Tools), which I did. No bueno.
These are the settings I've tried:
- All of the config.exe resolutions in the Expansions' own configuration launcher.
And these, overridden in the settings.cfg file located in C:\Users\Public\Documents\TimeGate Studios\FEARXP :
"GammaB" "1.069204"
"GammaG" "1.069204"
"Renderer" "NVIDIA GeForce GTX 1060 6GB"
"GammaR" "1.069204"
"BitDepth" "32"
"HardwareCursor" "1.000000"
"ScreenWidth" "1920"
"VSyncOnFlip" "0.000000"
"DeviceName" "\\.\DISPLAY1"
"ScreenHeight" "1080"
"RestartRenderBetweenMaps" "1.000000"
Aaand to give you guys more specifications about the rig that I'm running (even though it should make little difference, due to the base game working wonderfully).
Operating System: Windows 10 Pro 64-bit (10.0, Build 16299) (16299.rs3_release.170928-1534)
BIOS: BIOS Date: 06/07/17 10:10:53 Ver: 04.06.05
Processor: AMD FX(tm)-8350 Eight-Core Processor (8 CPUs), ~4.5GHz
Memory: 16384MB RAM
Available OS Memory: 16296MB RAM
Page File: 8148MB used, 10580MB available
DirectX Version: DirectX 12
Card name: NVIDIA GeForce GTX 1060 6GB
DAC type: Integrated RAMDAC
Device Type: Full Device
Display Memory: 14200 MB
Dedicated Memory: 6052 MB
Shared Memory: 8148 MB
Nvidia driver version: 397.31
If you need the full dxdiag for further analysis, I will be more than happy to provide it for you. For the sake of this forum post however, I will leave you with these essentials.
Does anyone have a clue how to make these expansions work? I'd really like to try them out, since they are pretty much the only content I haven't played from the original game of the series.
*SOLVED* Reinstalling the most current drivers for NVIDIA seemed to fix the issue. I guess I jumped the gun on blaming the game for driver issues. This topic is now irrelevant. Thank you! *SOLVED*
Post edited May 06, 2018 by Mutka
No posts in this topic were marked as the solution yet. If you can help, add your reply