Skip to content

Commit c2538df

Browse files
UngeziefiUngeziefi
committed
Performance info
1 parent cbcc059 commit c2538df

File tree

2 files changed

+71
-20
lines changed

2 files changed

+71
-20
lines changed

‎sitemap.xml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,7 @@
6868
<url>
6969
<loc>https://themidnightride.moddinglinked.com/utilities.html</loc>
7070
<priority>0.64</priority>
71-
<lastmod>2025-10-17</lastmod>
71+
<lastmod>2025-10-18</lastmod>
7272
</url>
7373
<url>
7474
<loc>https://themidnightride.moddinglinked.com/mo2.html</loc>

‎utilities.html‎

Lines changed: 70 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -320,20 +320,87 @@ <h3 class="install">Installation instructions</h3>
320320

321321
<div class="card" id="PhysicsFix">
322322
<p>
323+
<h2>Performance Preamble</h2>
324+
Limiting framerate is very important for overall stability, as it <strong>smooths out framepacing</strong>, which is the most important thing for the overall feel of fluidity.
325+
<br>
326+
<br>
327+
More advanced limiters can also <strong>reduce latency</strong> or CPU power consumption (it's difficult to have both at the same time).
328+
<br>
329+
<br>
330+
For a limiter to do anything, you want to set it to <u>a framerate you can actually achieve regularly</u> enough. This will prevent the GPU load from maxing out and further reduce latency, while reducing power usage, often considerably.
331+
332+
<h3>Setup</h3>
333+
<ol>
334+
<li>Make sure <strong>V-Sync</strong><sup><a title="V-Sync" href="#annotation1">[1]</a></sup> is enabled, you can do this through <a href="mo2#GameSettings">BethINI Pie</a>. Your driver settings shouldn't override this<sup><a title="V-Sync" href="#annotation2">[2]</a></sup>.</li>
335+
<li>If your monitor supports it, enable <strong>Variable Refresh Rate</strong><sup><a title="Enabling VRR" href="#annotation3">[3]</a></sup>.</li>
336+
<div class="card-yellow">
337+
<p>
338+
<u>Do not disable V-Sync when using VRR</u>! The latter expects the former<sup><a title="V-Sync + VRR" href="#annotation4">[4]</a></sup>.
339+
</p>
340+
</div>
341+
<li>In Fallout 4, specifically, <u>do not use any external limiter</u>. The steps below will use High FPS Physics Fix to configure one. This exception is born from Fallout 4's loading speed being tied to framerate, meaning that an external limiter cannot dynamically switch value, missing out on the speed-up.</li>
342+
</ol>
343+
344+
<div class="expander-top">
345+
<p>
346+
<h3>Details</h3>
347+
<img class="chevron" style="transform: rotateX(0deg);" src="img/UI/Chevron Down.svg" alt="UI element - Chevron">
348+
</p>
349+
</div>
350+
<div class="expander-bottom">
351+
<p>
352+
<ol>
353+
<li id="annotation1">
354+
V-Sync will <strong>prevent tearing</strong> as result of syncing the monitor's VBLANK to the GPU output. This will limit your framerate from going over the refresh rate.
355+
356+
<div class="card-red">
357+
<p>
358+
Even though it acts as one, V-Sync on its own is <i><u>NOT</u></i> a limiter. Using it without a dedicated limiter will result in a <b>massive</b> latency penalty.
359+
</p>
360+
</div>
361+
</li>
362+
<li id="annotation2">
363+
Generally, <strong>default settings</strong> for both the <b>Nvidia Control Panel</b> and AMD's <b>Adrenalin</b> will work. Reset them if you're unsure and <u>don't change settings unless you are sure of what they do</u>.
364+
</li>
365+
<li id="annotation3">
366+
You can enable VRR by going to the <b>Nvidia Control Panel</b> if you're on Nvidia or <b>Adrenalin's Display Settings</b> if you're on AMD. If the setting isn't there, your display doesn't support the feature or it's not enabled in its OSD.
367+
368+
<div class="card-yellow">
369+
<p>
370+
Nvidia users need to make sure that G-Sync is set to <b>Fullscreen</b> and that <b>Display Specific settings</b> are enabled, the <b>Windowed</b> option is problematic due to it being a hacky method.
371+
<br><br>
372+
Both of the settings are wrongly named! They do not actually directly refer to the display method.
373+
</p>
374+
</div>
375+
</li>
376+
<li>
377+
Despite popular misinformation, <u>VRR alone doesn't get rid of tearing</u>. It can minimize the rolling tear however, but that varies between displays. Additionally, the latency reduction applies only at framerates below the display's refresh rate.
378+
<br>
379+
<br>
380+
Once the framerate reaches refresh rate, VRR will engage V-Sync emulation. To account for this, VRR users should configure their limiter with a <strong>slight bias below refresh rate</strong> (to cover spikes).
381+
</li>
382+
</ol>
383+
This section is purely informative, the calculator below will take all of this information into consideration.
384+
</p>
385+
</div>
386+
387+
<br>
388+
<hr>
389+
323390
<h3 class="link-download"><a href="https://www.nexusmods.com/fallout4/mods/44798" target="_blank">High FPS Physics Fix</a></h3>
324-
All-in-one solution for smooth FPS-unlocked gameplay, mitigates stutter and reduces loading times massively.
391+
All-in-one solution for smooth FPS-unlocked gameplay, mitigates stutter and <a href="https://moddinglinked.com/benchmarks.html#expander-3" target="_blank">reduces loading times massively</a>.
325392
<h3 class="install">Installation instructions</h3>
326393
<ul>
327394
<li><b>Main Files</b> - High FPS Physics Fix (1st file)</li>
328395
<ol>
329396
<li>Once the mod has been installed, double-click it in the left pane of MO2.</li>
330397
<li>In the <strong>INI Files</strong> tab, open <span class="card-basic">F4SE/Plugins/HighFPSPhysicsFix.ini</span></li>
331-
<li>Change only the following options<sup><a title="Warning" href="#annotation1">[1]</a></sup>:</li>
398+
<li>Change only the following options:</li>
332399
<ul>
333400
<li>Set <b>DisableBlackLoadingScreens</b> to <strong>true</strong> (line 37).</li>
334401
<li>Set <b>PostloadingMenuSpeed</b> to <strong>3.0</strong> (line 51).</li>
335402
<li>Set <b>OneThreadWhileLoading</b> to <strong>false</strong> (line 84).</li>
336-
<li>Use the calculator below to determine your optimal FPS limit<sup><a title="Warning" href="#annotation2">[2]</a></sup> setting. You can find your exact refresh rate <b><a href="https://www.testufo.com/refreshrate" target="_blank">here</a></b>.</li>
403+
<li>Use the calculator below to determine your <strong>optimal FPS limit</strong> setting. You can find your exact refresh rate <b><a href="https://www.testufo.com/refreshrate" target="_blank">here</a></b>.</li>
337404

338405
<div class="card-basic">
339406
<div class="center" style="margin: 10px;">
@@ -361,22 +428,6 @@ <h3 class="install">Installation instructions</h3>
361428
<li>Save your changes.</li>
362429
</ol>
363430
</ul>
364-
365-
<hr>
366-
367-
<span class="annotations">
368-
<ol>
369-
<li id="annotation1">
370-
You can <strong>check if you are using VRR</strong> by going to the <b>Nvidia Control Panel</b> if you're on Nvidia or <b>Adrenalin's Display Settings</b> if you're on AMD. If the G-Sync tab is missing from NVCP, your display doesn't support it or doesn't have the feature enabled in the OSD.
371-
<br>
372-
<br>
373-
Nvidia users need to make sure that G-Sync is set to <b>Fullscreen</b> and that <b>Display Specific settings</b> are enabled, the <b>Windowed</b> option is problematic due to it being a hacky method. Both of the settings are wrongly named so they do not actually directly refer to the display method.
374-
</li>
375-
<li id="annotation2">
376-
You always want your FPS capped by a <strong>limiter instead of being hardware bound</strong>, this will reduce lag and increase power efficiency. It is also less jarring for the player when visual smoothness is the same across all scenes.
377-
</li>
378-
</ol>
379-
</span>
380431
</p>
381432
</div>
382433

0 commit comments

Comments
 (0)