First, I don't recommend it. But if you have a cheap PC (or Mac on bootcamp) with integrated graphics like my Intel HD 4000 graphics chi...

Modding on integrated intel graphics

First, I don't recommend it. But if you have a cheap PC (or Mac on bootcamp) with integrated graphics like my Intel HD 4000 graphics chip, you can run fallout though it isn't pretty.

Using dxcpl to configure direct x compatability

This article was very helpful in getting past startup crashes. Basically you can set your direct x compatibility using a program called dxcpl:

https://www.reddit.com/r/lowendgaming/comments/3sf7ea/i_did_it_how_to_run_fallout_4_on_intel_hd/

"Force WARP" will cause the game to always load but run at very low FPS (1-5). If I leave this setting off it will crash during startup most of the time but eventually work (After 5-10 tries). I find that using Task Manager to set the priority of the fallout4.exe process to "above normal" or "high" and clicking on the window helps (I run it on lowest res in windowed borderless mode).

After tweaking graphics settings to low it will actually run quite well though there are still some crazy artifacts that appear. With vsync off the frame rates are 15-30.

Speed up dev/test cycle

To get around having to re-start the entire game to test a single small change, I figured out you can actually keep the game running and reload the mod. This is especially important if you game crashes a lot during startup like it does for me (see above).

Basically, remove the mod from the load order and let the game reload (not restart the app itself). Then you can save your mod using the Creation Kit since the mod files will no longer be locked. Once saved, re-add the mod to the load order and then test your changes.

Summary

I play Fallout 4 primarily on my xbox and only bought a PC copy of the game for modding. The above allows me to do basic testing on my PC which speeds up dev time. 

0 comments: