FCO TTW - Sideways eyes despite fixes

[Mintyfreshtea]

SOLVED: Rolling back to the previous version of FCO worked. Please flag for locking the thread.

Hello!

My name is Minty, and I've been modding games for a little over a year now. I'm still fairly new to this all, so please; bear with me.

Recently, I decided it would be appropriate to play Fallout 3 again, and decided the most effective way to do that would be to play it with Tales of Two Wastelands (or TTW). Installing that was of no issue, in fact, it was surprisingly easy.
What has proven to be a big issue, however, is FCO. For some reason, certain characters are perpetually gazing to their right. I have read, through multiple forums, that this issue is due to the head meshes changing, and that the best way to fix this is to run an eye texture mod. Unfortunately for me, this does not work. I have installed several various fixes for FCO (which I shall link below, as well as my load order (fret not - it is fairly short)) to no avail.
All I want to do is run FCO with TTW - but alas, this eludes me.

FCO: https://www.nexusmods.com/newvegas/mods/54460
Fixes 1: https://www.nexusmods.com/newvegas/mods/61357
Fixes 2: Secondary file in FCO (apparently fixes issues with base FCO 3.0)
Hi-Res eyes: https://www.nexusmods.com/newvegas/mods/37537

 

My load order is as such:

 

 

FalloutNV.esm

DeadMoney.esm

HonestHearts.esm

OldWorldBlues.esm

LonesomeRoad.esm

GunRunnersArsenal.esm

ClassicPack.esm

CaravanPack.esm

Fallout3.esm

Anchorage.esm

ThePitt.esm

BrokenSteel.esm

PointLookout.esm

Zeta.esm

taleoftwowastelands.esm

MoreChems.esp

FCOMaster.esm

TTW_AnchorageCustomization.esp

TTW_StartupMenu.esp

ttw_wildwasteland.esp

TTWOptions.esp

MoriartysTestFix.esp

The Mod Configuration Menu.esp

TTW - Deadly But Fair Combat Damage.esp

S420EssentialCompanions.esp

pyDoF.esp

SenterPats Weapon Pack.esp

FCO - GlowingOne.esp

FCO - OHSB NPC Edits.esp

FCO - NPC Changes.esp

Total active plugins: 30

Total plugins: 34

Truth be told, the only mods I am using are:
TTW
FCO
Senterpats weapons/armor
Senterpats Drugs (or CAM)
Deadly but Fair combat
DoF Holotape

9mm Retex

Thank you very much for your time and patience (assuming you have bothered to read this cry for help thus far in its entirety) and I wish you a lovely afternoon.
-Minty

PS: It is worth noting that my framerate has dropped well into 56-57fps at 4k this eve, despite previously having a stable 60fps prior to tonight? I know not the issue, but I figured it might be worth mentioning in case that is an indicator of conflicting mods.

Edited November 8, 2018 by Mintyfreshtea

[dubiousintent]

You've done your homework, so I doubt this is going to make any difference. But please see the 'Issue: Body Replacer - FCO or FNV Redesigned3 Eyes rolled to the side' entry under the 'Solutions to Graphics problems' section of the wiki "Fallout NV Mod Conflict Troubleshooting" article.

 

I would suggest that combining multiple patches intended to resolve the same problem are more likely to conflict than combine into a better solution. This is general application of the 'Third Rule: The Rule of One' from the wiki "FNV General Mod Use Advice" article.

 

See also the 'Merge Patch File' section of that article. Any time you are using a "replacer" mod like FCO you need a "Bash/Merge" patch file to resolve record level conflicts with the vanilla game characters.

 

As for your FPs drop, this game never envisioned 4K textures. The size of your image files also has an impact. Larger/higher resolution is not always "better". Please see the wiki "Display resolution versus Image Size" article.

Re: Stuttering or "micro-stutters". All visual stuttering problems are caused by the video stream having to wait for the "art assets" required to render the display OR the game writing something to disk (such as a save game file or logging). Mostly these are due to the hard disk drive being orders of magnitude slower than VRAM, with System RAM (e.g. "ENBoost") and "solid state drives" (SSDs) being in between. Keep in mind that this game was designed for older PC and XBox console systems, and it is now possible for your new "latest and greatest" gaming machine to be faster than it can handle. There are internal design choices that cannot be overcome. The "video pipeline" has always been prone to problems. The following are "mitigations" that have been found to help some people.

Please see the following entries under the 'Solutions to Performance problems' section in the wiki Fallout NV Mod Conflict Troubleshooting" guide if you haven't already.
* 'Issue: "Full screen mode" exhibits CTDs and stutters or micro-stutters'
* 'Issue: Lag or "micro stutters" even with "New Vegas Stutter Remover" installed'
* 'Issue: Win10 Screen tearing in "Borderless Windowed Mode"'
* 'Issue: CTD without warning, "Out of Memory error", or stops responding after the Main Menu' for other settings that can indirectly affect micro-stutter.
* There are also some NVSR configuration suggestions under the 'Issue: Game in slow motion' and entries.
* The 'Issue: What's with these Solid Green billboard signs in the distance (LOD)?' entry under the 'Solutions to Mesh (Red "!" icon) or Texture (solid color) problems' section can also help if your problems started after you installed VWD/LOD texture packages.
* If you are using CASM or some similar "auto-save" mod to manage your save game files (recommended), try increasing the "time between saves" set in the "save frequency"; and reducing the number of occasions it saves to the minimum (e.g. disable most "Autosave Events" in CASM) and see how that impacts the game seeming to freeze temporarily.
* If you have "NVSE logging" enabled (see the 'Checklist Item #4' entry in the wiki "Fallout NV Mod Conflict Troubleshooting" guide), disable it until actually needed.

Reading from or writing to disk for any reason is the slowest thing the game does.

The 'Issue: What INI edits seem to be most beneficial to performance' entry of the wiki "Fallout NV Mod Conflict Troubleshooting" guide) may also be some help. However, the above mitigations are more likely to have a fundamental beneficial effect with or without any INI adjustments, so consider them as the last resort.

-Dubious-

 

[Mintyfreshtea]

Thank you! Unfortunately, the suggested article (specifically concerning FCO eye issues) was not a success. Neither was removing the various patches, though I would like to specify that these patches were not for this one particular error, rather for various errors concerning FCO.

I had hoped one might contain the fix for the eyes.

 

Concerning the merge patch, I did attempt to find WHERE the hi-res eyes might be, as it would be beneficial to try re-ordering them in the load order, but for some accursed reason (despite their very functional in-game presence) not LOOT nor any load order mentions their existence. Perhaps, and this is referring back to my time modding Witcher 3, the solution is to place a '0' before the file name to load it before all others? Or maybe a way to force LOOT to display all plugins?

 

 

Also, RE the sudden lag? I'm only running the game at large textures at 4k, with a modern operating system capable of forcing 60fps 4k out of most games. I have no issue turning it down to 2160 x 1440, I just found it extremely worrying that in a closed off environment (Vault 101) framerates would begin dropping even without a texture mod. Microstuttering is, as of yet, not an issue. It's just hovering below 60fps.

 

I will continue to re-attempt the FCO eye article's fixes, and even redownload an older version of FCO, in case I may have done something (anything) wrong.

 

Thank you for your assistance, Dubious Intent.

PS: I love the name!

Edited November 7, 2018 by Mintyfreshtea

[Mintyfreshtea]

UPDATE: Rolling back FCO to 2.6 worked! The game now has a perfect Dad, HOWEVER, I have discovered the game runs at 56-57fps no matter the resolution. Even at 1080p. I will attempt to install the stutter remover, though I already have the 4gb LAA installed (which I assumed would fix memory usage issues).

[dubiousintent]

That is a perfectly acceptable and more than playable framerate. Turn off your FPS display and see if you can really tell the difference? Which would you rather do: play, or try to achieve some "perfect" FPS this 8 year old game was never expecting to achieve?

 

Please see 'Solutions to Performance problems' section of the wiki "Fallout NV Mod Conflict Troubleshooting" article.

 

If you are using ENB or SweetFX or some similar "post processor", see the 'Solutions to Post-Processor (ENB/SweetFX et. al.) problems' section as well. And in that case, you should also look at this post about Configuring ENB Fallout New Vegas (and ENBoost) from MajinCry on the TTW site.

-Dubious-