You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fixes the engine bug that causes workshop navmesh cuts to persist throughout all interior cells.
276
+
<h3class="install">Installation instructions</h3>
277
+
<ul>
278
+
<li><b>Main Files</b> - Interior NavCut Fix</li>
279
+
</ul>
269
280
270
281
<divclass="card-red">
271
282
<p>
272
283
<b>IMPORTANT:</b>
273
284
<br>
274
-
Mac and Linux users will need to disable the Interior NavCut Fix in Buffout and use the No Multithreading version of the original mod by following these steps:
275
-
<ul>
276
-
<li>Once the mod has been installed, double-click it in the left pane of MO2</li>
277
-
<li>In the <strong>Text Files</strong> tab, select <spanclass="card-basic">F4SE/Plugins/Buffout4.toml</span></li>
278
-
<li>Change the following options:</li>
279
-
<ul>
280
-
<li>Set <strong>InteriorNavCut</strong> to <b>false</b> (line 9)</li>
281
-
</ul>
282
-
<li>Download and install <ahref="https://www.nexusmods.com/fallout4/mods/72904" target="_blank">Interior NavCut Fix</a> (No Multithreading)</li>
283
-
</ul>
285
+
Mac and Linux users will need to use the <b>No Multithreading</b> version instead!
These last 2 mods <strong>should be installed only by users of Nvidia graphics cards</strong>. If you are unsure of what graphics card you are using, you can find that information in Task Manager's performance tab.
This fix is recommended only to Nvidia users because its visual changes do not translate well to AMD hardware, leading to visual problems and a different performance gain.
<li>Disabled NumOfThreadsWhileLoadingNewGame in the High FPS Physics Fix instructions to speed up loading, the bug mentioned in the INI doesn't seem to exist.</li>
178
+
<li>Added instructions on how to disable the Threads setting in X-Cell to avoid a conflict with High FPS Physics Fix that would cause New Game loading to get stuck.</li>
179
+
</ul>
180
+
<h2><strong>Bug Fixes</strong></h2>
181
+
<ul>
182
+
<li>Added the following mods:
183
+
<ul>
184
+
<li>Facial Expression and Eyetracking Engine Fixes - F4SE.</li>
185
+
<li>Interior NavCut Fix, it turned out that Buffout 4 NG doesn't replace this fix for the OG executable.</li>
186
+
</ul>
187
+
</li>
188
+
<li>Removed Godrays Performance Fix Redux - ESPless. Vanilla god rays settings are already good performance wise, so the mod doesn't have a big enough impact to be included. Removed the NVidia Fixes section as a result since only Weapon Debris Crash Fix remains.</li>
189
+
</ul>
190
+
<h2><strong>User Interface</strong></h2>
191
+
<ul>
192
+
<li>Removed Extended Dialogue Interface due to its many issues (you're obviously free to keep the mod if these problems don't matter to you):
193
+
<ul>
194
+
<li>No service costs</li>
195
+
<li>No PA-specific coloring</li>
196
+
<li>mismatched text on randomized dialogue options</li>
197
+
<li>Partial coverage of companion dialogue</li>
198
+
<li>Swapped sarcastic/maybe and affirmative options</li>
199
+
</ul>
200
+
</li>
201
+
<li>Removed MCM Settings Manager and its TMR Configuration - there's only 3 or 4 settings players should objectively change now that DLC Timing is gone and that's not enough to warrant a whole manager for it. The MCM configuration is now up to the user.</li>
202
+
</ul>
203
+
<h2><strong>Gameplay</strong></h2>
204
+
<ul>
205
+
<li>Removed DLC Timing because its settings are too arbitrary for the guide, its replacement starts with the addition of Integrated Automatron.</li>
206
+
</ul>
207
+
<h2><strong>LOD Guide</strong></h2>
208
+
<ul>
209
+
<li>Updated the pre-generated LOD for FOLIP 6.0.1.</li>
210
+
</ul>
211
+
<h2><strong>Wabbajack</strong></h2>
212
+
<ul>
213
+
<li>Updated to reflect changes above.</li>
214
+
<li>With the removal of the NVidia Fixes section, Weapon Debris Crash Fix is now also enabled by default.</li>
215
+
<li>Updated the following mods:
216
+
<ul>
217
+
<li>X-Cell (1.5-b84)</li>
218
+
<li>Lighthouse Papyrus Extender (1.13.0)</li>
219
+
<li>Garden of Eden Papyrus Script Extender (19.3)</li>
220
+
<li>Papyrus Common Library (1.4.3)</li>
221
+
<li>Ownership Fixes (1.5)</li>
222
+
<li>Community Fixes Merged (3.5.9)</li>
223
+
<li>Community Fixes Merged - Weapon Mod Fixes Patch (2.0.5)</li>
Alters how Automatron is handled to have it behave more like base game content rather than announcing its presence to the world as soon as you hit level fifteen.
<li>At least 52GB of free drive space, game included (45GB if you delete all the downloads).</li>
240
240
<li>Windows 10 or higher (64-bit).</li>
241
+
242
+
<divclass="card-red">
243
+
<p>
244
+
Do not use any sort of debloating tool or alternative version of Windows (including LTSC)! Removing core components will break random features - there's no performance benefit to be found from these practices.
245
+
<br>
246
+
<br>
247
+
Doing so will be unsupported.
248
+
</p>
249
+
</div>
250
+
241
251
<ul>
242
252
<li>
243
253
Mod Organizer 2 does <b>NOT</b> support <strong>ARM64</strong> Windows.
Generating/installing new LOD is <b>NOT</b> a requirement, but it will add detail in the distance by increasing the amount of objects that appear in the distance while also making all LOD match your modded textures. Naturally, this also means a minor performance hit.
171
+
Generating/installing new LOD is not a requirement, but it will add detail in the distance by increasing the amount of objects that appear in the distance while also making all LOD match your modded textures. Naturally, this also means a minor performance hit.
172
172
<br>
173
173
<br>
174
174
You can also generate terrain LOD, which will allow mods that edit the game's landscape to have LOD that reflects their changes. Terrain LOD creates a much larger file size and will take longer to generate.
@@ -190,7 +190,7 @@ <h3>What is LOD?</h3>
190
190
In the context of Bethesda games, LOD mainly refers to <strong>Cell LOD</strong>, not geometry LOD. It's used to represent whole cells (the game's "chunks" of land) in the distance.
191
191
192
192
<p>
193
-
Cell LOD is <b>not</b> based on distance - it's a binary state of whether cell is either loaded or not. The LOD Block distance settings control the max draw distance of LOD itself, not the point where it begins.
193
+
Cell LOD is not based on distance - it's a binary state of whether cell is either loaded or not. The LOD Block distance settings control the max draw distance of LOD itself, not the point where it begins.
194
194
<br>
195
195
This means that you will see LOD pop-in at the same distance regardless of the settings.
Copy file name to clipboardExpand all lines: mo2.html
+1Lines changed: 1 addition & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -371,6 +371,7 @@ <h3>Game Settings</h3>
371
371
<li>Press <strong>Apply</strong> in the lower right, then <b>OK</b>.</li>
372
372
<li>Select <b>BethINI</b> from the drop-down and <strong>run</strong> it.</li>
373
373
<li>Click <b>Fallout 4</b> then press <strong>Select Game</strong>.</li>
374
+
<li>If you get a <b>Setup</b> prompt press <strong>OK</strong>. You don't need to redirect the INI path to MO2's profile folder because MO2's VFS already handles the redirection.</li>
374
375
<li>Apply the following settings:</li>
375
376
<ol>
376
377
<li>Select a BethINI <strong>preset</strong> depending on your hardware.</li>
0 commit comments