In the worst case all changes can be undone by deleting the Fallout.ini from its directory, so the game will create a new, default one with the next start.Ī file of this type can be edited with any text editor, though it is recommended to use a simple one – such as Windows' Notepad – to avoid unallowed symbols or unwished formatting. In addition it is wise to do changes step-by-step, so that unwanted effects can easily be reverted.Įditing the file can lead to game crashes, strange visual behavior, more errors or even a blue screen. It is strongly recommended to, before doing any changes to game files at all, make a backup copy of them. There are many guides and utilities spread across the web, regarding optimization, cleaning, and tweaking for an audio-visual appearance exceeding the game's ultra settings. Some possible variables aren't listed at all, but default values for them are hard-coded. For some variables it is unknown if the game really uses them. Some variables appear twice in the same section, in which case it's unclear which value is taken into account by the game, though it can be assumed, that this would be the first one. The sections and variables are in no specific order. Also some variables are contained in both configuration files, the Fallout.ini and the FalloutPrefs.ini, where the former determine the default values and the latter the values used by the game when playing it (with one definite and one possible exception: iPresentInterval and iRadialBlurLevel). The variables are organized in sections, with some appearing in more than one section.
Some comments are contained, lines starting with. Variables starting with u: Unsigned integers.Often used for file references or to display text. Values are plain text without quotation marks. Variables starting with s/ S: Strings.They are composed of the three RGB values (ranging from 0 to 255), divided by commas and without blanks. is also often reduced to 4 or 2 decimal places. The console command SaveIniFiles creates a configuration file, where all these are cut down to 4 decimal places, while the command GetINISetting puts them out with only 2. Variables starting with f: Floating-point numbers, using up to 6 decimal places.They can only have the valid values of 0 and 1, where 0 means "false" or "disabled", and 1 means "true" or "enabled". Variables starting with b: Boolean variables.There are several types of variables, determining the possible values one can have.
It normally remains unchanged, though the Fallout: New Vegas version is overwritten with default values each time the game is started via Steam. It is then saved in the user's My Game directory.
#Gamebryo engine startup video mod
Some say Bethesda did this on purpose in an attempt to encourage people to wait until it releases its own official mod workshop, while others say it’s simply a bug.įor those who don’t use/care about mods, here is the full list of changes the 1.The Fallout.ini, together with the FalloutPrefs.ini, is created when for the first time the launcher of the game is started.
#Gamebryo engine startup video Patch
There are several other workarounds that involve altering the game’s filenames or making the plugins.txt file read-only, and these still require the use of the Nexus Mod Manager.īethesda has a history of supporting mods and the modding community, and people are debating whether the patch intentionally made it more difficult to modify the game. There’s also a version of the Fallout 4 script extender that works with the latest patch, but that also requires jumping through several hoops to get it working, and it needs the Nexus Mod Manager to function. First of all, you’ll need to have the Nexus Mod Manager (NMM) installed you'll need to launch NMM, then launch Fallout 4, then switch back to NMM and re-enable the mods. It’s still not clear whether Bethesda intentionally removed mod support or if it was just a mistake.Ī user on the Nexus Mods forum has published a way to bypass the problem, but it’s not the simplest of processes. INI edit that previously got round this issue no longer works.
The patch adds a new launcher that disables mods on startup, and using the. But it’s not such good news for those who have been modding the game, as the 1.2 patch breaks support for mods. Good news for Fallout 4 fans: the latest official patch for the game has arrived on Steam, bringing with it a couple of new features and several fixes.