For everyone having trouble with archive invalidation and the new patch here's how to get things working.
Short and sweet:
Before doing the following make sure you save a copy of your save game files and copies of the files that you are editing for that JUST IN CASE situation.
Retrieved from 'https://wiki.nexusmods.com/index.php?title=Archive_invalidation&oldid=40071'
Fallout.ini is the configuration file in which the basic and default settings are deposited, the Gamebryo engine needs to run Fallout 3 and Fallout: New Vegas properly on any personal computer. It contains values about audio and graphical options, background processes, implementation of the Havok Physics engine, and many more.
Overview[edit | edit source]
The Fallout.ini, together with the FalloutPrefs.ini, is created when for the first time the launcher of the game is started. It is then saved in the user's My Game directory. It normally remains unchanged, though the Fallout: New Vegas version is overwritten with default values each time the game is started via Steam.
There are several types of variables, determining the possible values one can have.
Some comments are contained, lines starting with
; .
The variables are organized in sections, with some appearing in more than one section. 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 sections and variables are in no specific order. 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. Even faulty entries exist. For some variables it is unknown if the game really uses them. Some possible variables aren't listed at all, but default values for them are hard-coded.
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.
Editing[edit | edit source]
It is strongly recommended to, before doing any changes to game files at all, make a backup copy of them. In addition it is wise to do changes step-by-step, so that unwanted effects can easily be reverted.
Editing the file can lead to game crashes, strange visual behavior, more errors or even a blue screen. 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.
A 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.
Sections are defined by square brackets around the name, e.g.
[ Audio] . Only the first section with a specific label is taken into account, a second section with the same name would be completely ignored.Variables have to be put into the according section, to be taken into account by the game, with their value following a = in the same line.Removing the value of a variable or the variable at all will not disable the according setting, instead the default value will be used by the game. This doesn't count for string variables, which use nothing if their value is set to empty. Though floating-point variables may have up to 4 decimal places, it is recommended to cut them down to the last digit that is not 0. In rare cases values with high numbers, e.g. 1800.0000, might be read incorrect by the game engine and cause bugs, if not altered to e.g. 1800.
Text after a
; isn't regarded by the game and can serve for annotations. It doesn't matter, if this is done in an extra line, or directly after a valid value, though the latter isn't recommended. This way it is possible to disable variables or placing comments. A good way to make reverts easier would be to copy the entry, the change shall be applied to, and inserting it below with the altered value, then commenting the original value out.
Fallout: New Vegas
The Fallout: New Vegas version of the file is read-only, and changing it will result in nothing, because Steam overwrites it with the default version each time the game is started.
A workaround would be to change the template itself, in which case the backup is even more recommended. A better way to apply changes to this file, would be a 'custom' configuration file. It is possible to make a copy of the original Fallout.ini, and rename it to FalloutCustom.ini. The game then uses this file over the default one, and it is not overwritten by Steam. Though this method has a small restriction: No variables, that are not already part of the default file, can be added, at least not with any effect. A word about 'tweaking'[edit | edit source]
This guide isn't intended as a tweaking guide. There are better ones – more focused, less blown up, more fun to read. (See the credits for some examples.) Instead it's more of a documentation and shall serve as a reference.
Though it's possible to use it for such a purpose…
The Vault doesn't take any responsibility for consequences to your game, your saves, or your PC, if you edit game files by using comments and instructions, listed on this page.
On modern hardware Fallout 3 and Fallout: New Vegas with all their add-ons should be automatically put to ultra settings by the launcher, when the default option is used. And run well on your computer. However there are possibilities to change some things, both, the audio-visual game appearance, as well as game mechanics. Be warned again, that such changes might have unwanted consequences, such as low performance, crashes, even corrupted save games, and worse. In addition many of these promising variables, listed below, are exactly this: promising – and nothing more. Some have a huge impact on the appearance of the game, some do simply nothing, or at least nothing remarkable. This documentation tries to cover these things, but doesn't claim to be absolutely accurate and complete.
File locations[edit | edit source]Fallout.ini[edit | edit source]
The Fallout.ini can by default be found in the user's My Games directory, together with the Saves. The exact path differs by operating system.
On Windows Vista and later, assuming C: as the user profile drive, it is located under
On Windows XP, assuming C: as the user profile drive, it is located under
Fallout_default.ini[edit | edit source]
The template for this file can be found in the installation directory of the game. It is named Fallout_default.ini. This is also the file to be edited – if wished! – when applying changes for the Fallout: New Vegas Steam version. Locating it is dependent on some more conditions; the default installation path is assumed, using C: as the installation drive.
On a 32-bit Windows, game installed via Steam:
On a 64-bit Windows, game installed via Steam:
On a 32-bit Windows, game installed off Steam:
On a 64-bit Windows, game installed off Steam:
Clean and default version[edit | edit source]
With the use of the console a configuration file can be created that contains only the hard-coded default values. This can serve as a reference, but shouldn't be used for playing the game because it lacks many variables existing in the default file.
Whenever in the following tables a comment exists, 'Not part of the default file', then that specific variable is taken from this file.
To get this file the game has to be started (preferrably with default settings), then the existing file has to be deleted. Back in the game open the console by using the key directly left of the
1 and below Esc . On a US keyboard this is ~ , the label of the key varies by country specific keyboard layouts. Type SaveIniFiles and Enter , and a new file will be created. You can copy this to a safe location, but should – as mentioned – replace it with it's original version after quitting the game.
Technical background[edit | edit source]
Distances are measured in game units, where 64.0000 units equal 1 yard, or around 70 units 1 meter.
Some terms will appear frequently:
Sections and variables[edit | edit source]
In the following tables all possible sections and variables are listed – those initially created by the game, those that can be added, faulty ones, also those which don't seem to have any purpose. Just a few variables appear in only one of the games, a few more have different values for each game.
Those that are not part of the default file, as it is created by the game, are taken from that one, that can be created via the SaveIniFilesconsole command – see above.
Many variables appear in the G.E.C.K. configuration file, GECKCustom.ini, too, though sometimes with different values. Also that file contains additional variables and even whole sections.
Unfortunately no official and publicly accessible documentation exists, so the effects and actual use of many variables remain unclear.
[Absorb][edit | edit source]
[AnimationWarning][edit | edit source]
[Archive][edit | edit source]
[Audio][edit | edit source]
[BackgroundLoad][edit | edit source]
[bLightAttenuation][edit | edit source]
[BlurShader][edit | edit source]
[BlurShaderHDR][edit | edit source]
[BlurShaderHDRInterior][edit | edit source]
[BudgetCaps][edit | edit source]
[CameraPath][edit | edit source]
[Combat][edit | edit source]
[Controls][edit | edit source]
[CopyProtectionStrings][edit | edit source]
[Debug][edit | edit source]
[Decals][edit | edit source]
[Display][edit | edit source]
[DistantLOD][edit | edit source]
[Fonts][edit | edit source]
[FootIK][edit | edit source]
[GamePlay][edit | edit source]
[General][edit | edit source]
[GeneralWarnings][edit | edit source]
[GethitShader][edit | edit source]
[GrabIK][edit | edit source]
[Grass][edit | edit source]
[Hacking][edit | edit source]
[HAVOK][edit | edit source]
[HeadTracking][edit | edit source]
[Imagespace][edit | edit source]
[Interface][edit | edit source]
[InterfaceFX][edit | edit source]
[Landscape][edit | edit source]
[LANGUAGE][edit | edit source]
[Loading][edit | edit source]
[LOD][edit | edit source]
[LookIK][edit | edit source]
[MAIN][edit | edit source]
[Menu][edit | edit source]
[MESSAGES][edit | edit source]
[NavMeshGeneration][edit | edit source]
[Online][edit | edit source]
[Pathfinding][edit | edit source]
[Pathing][edit | edit source]
[Pipboy][edit | edit source]
[RagdollAnim][edit | edit source]
[RagdollFeedback][edit | edit source]
[RenderedMenus][edit | edit source]
![]()
[RenderedTerminal][edit | edit source]
[SaveGame][edit | edit source]
[ScreenSplatter][edit | edit source]
[SpeedTree][edit | edit source]
[Surgery3D][edit | edit source]
[TerrainManager][edit | edit source]
[TestAllCells][edit | edit source]
[VATS][edit | edit source]
[Voice][edit | edit source]
[Water][edit | edit source]
[Weather][edit | edit source]
Enabling v3.0 shaders[edit | edit source]
The game is able to do some graphic processes using shader model 3 if the graphics adapter is compatible. Though 'being able' doesn't mean it will always do so – but it can be forced.
Prerequisites[edit | edit source]
In the same directory where the Fallout.ini file is located (see above for instructions), another text document can be found, called RendererInfo. It is also created when starting the launcher for the first time, and contains basic informations about the abilities of the graphics adapter.
It contains a line 'Shader Package' with a number behind. This number will be needed in the next step. It is not advised to change anything here in this text file!
Changing the shader package[edit | edit source]
In the game's installation directory (see above for instructions) there's a subfolder Data, containing another subfolder Shaders. Here shaderpackages#….sdp can be found, one of them ending with the previously found number.
Note: The file index '.sdp' may not be shown, depending on the system configuration. In this case the files will only be named shaderpackage0##. This doesn't have affect on the renaming instructions.
Credits and external references[edit | edit source]
Retrieved from 'https://fallout.gamepedia.com/index.php?title=Fallout.ini_(Gamebryo)&oldid=1909340'
Posted by2 years ago
Archived
In the past I had played Fallout: New Vegas on my Windows 10 laptop, which worked fine. But now that I have a new PC with Windows 7 it first told me via Steam 'Failed to run (missing executable)', and now the launcher opens up but for that it says 'Unable to find ini file. Please re-install Fallout.' This may be because I tried to patch the game with the English version, uncensoring and translating it from German.
I've tried several methods such as:
-Verifying the integrety
-Deleting all local Fallout files manually, restarting and reinstalling
-Patching the game like I did back then (I can't find the translation patch though) and starting it that way
I'm at a loss here. What do I do?
4 comments
Overview
This a collection of specific common problems and solutions, along with a general checklist of things known to contribute to problems, collected from around the web. The 'Fallout NV Mod Conflict Troubleshooting' thread in the 'Fallout New Vegas Mod Troubleshooting' forum is for questions, suggestions, and discussion of this article's contents.
The article is organized around various generic topics, with specific mod conflicts or issues that don't fit into the other categories under 'Solutions to Miscellaneous problems'.
If you haven't already, it is suggested to read the wiki article FNV General Mod Use Advice first to understand basic terminology as used here and differences in FNV from other games you may be used to modding.
Troubleshooting is a logical process of elimination. If all logic fails, you have to revert back to a vanilla game and slowly re-install mods, testing each one thoroughly before adding the next. It is a trade-off of 'time' versus 'effort'. Where that tipping point lies is up to you. This is why you are always advised to follow a slow 'install and test each mod one at a time' procedure when first setting up your game. Then you know specifically which mod is causing your problem, which saves time.
The How to ask for help wiki article applies to any game. Read it before posting your next problem in the forums to speed up getting to the correct solution. The time you are wasting otherwise is not just your own.
Checklist
Standard list of things to ask yourself about your current FNV problem:
00. Did you install Steam under the default location of the 'C:Program Files' tree? This causes many 'strange' problems not otherwise explainable. As painful as it may sound, read the wiki article Installing Games on Windows Vista+ and move at least FNV. That article has a link to the official Steam Procedure (a good indication that they now recognize the need to correct this). This should be the first solution you try. Otherwise you will spend a lot of time and effort trying other solutions, and still have to move the game files in the end anyway.
01. Are you getting an error message? What is that pointing to as the source of the problem: the game, Steam, or Windows?
02. What most recently changed (as far as what you have deliberately done to your game is concerned: New, updated, or removed mods or plugins)?
02b. Did any of the following which interact with the game get updated or changed recently. They are prime suspects if nothing in the game itself changed:
03. If you have recently 'verified local files' or 're-installed' the game, try renaming both the INI files in the 'C:Users<YourAccountName>DocumentsMy GamesFalloutNV' folder, and let the game rebuild them. (There might have been some unexpected changes.) Rename to anything you choose. I usually just add to the extension: from '<filename>.ini' to '<filename>.ini.old'. The purpose is to be able to examine the old files for things you want to be able to replicate in the new versions of the same file.
04. Does the most recent mod change use New Vegas Script Extender (NVSE) or supplemental plugins like JIP NVSE Plugin or 'Lutana NVSE Plugin'? Check that log (in the game's root folder: i.e. '<Steam install path>steamappscommonFallout New Vegas').
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |