DXCPL - DIRECTX PROPERTIES
Ensure your drivers are up to date.
Open dxcpl
Click "Edit list".
Find the Fallout 4 .exe file (NOT THE LAUNCHER). If you need to, you can go to your Steam library, right-click on Fallout 4, click "Properties", click "Local Files", then click "Browse Local Files" to find the correct path
Add the .exe to the list.
Click OK. At the bottom of the window, set "Feature level limit" to "10_0".
Hit "Apply", then OK.
Open Fallout 4.exe
Just generate a default "Low" Windowed via launcher. Then possibly navigate to Fallout4Prefs.ini and edit the resolution and what not... no need to check read only on Launcher generated config...
Enjoy!
EDIT: You can try WARP on/off : WARP off worked. The game will run, but only in windowed mode at the slowest framerate you may of ever seen. haha
*Update* Tested Intel HD on Windows 10 on 1st gen i3. It's not really happening for Intel HD as the vga frame buffer is the same ram that processor needs to start the game. What this means is, It's going to take a good 20 minutes to start the game and even then it will run horribly.
I probably squeezed every last bit of performance out of this little netbook, though Windows 10 is holding it back by a lot.
I would only suggest running Windows Vista/ 7 minimum. Since it runs a lot better when putting the system under load on an old 1st gen i3 netbook like my Gigabyte T1125.
Even using the Nvidia GT 310M overclocked, it wasn't really happening either. It ran maybe 4 fps faster (5fps total)in the menu and was unable to start the game it was so lagged out.
Not only that, but maybe it was a Windows 10 issue. If you start the game and close, you pretty much need to hold down the power and shut down the system since it continued to lag out badly on the desktop.
I'll try Windows 7 and see if I can get it working better.
Update : Doesn't seem to work at all on Windows 7 like it did on Windows 10. Windows 7 runs a lot better on this old laptop.
Notifications
0 comments