Jump to content

FalloutNewVegas TTW mesh error


Hmmm1232

Recommended Posts

Please forgive me for coming here again.

For some reason I could not ask questions on the TTW forum, so I had to ask questions here.

 

https://imgur.com/zs0gIY0

https://imgur.com/qOFwSQx

https://imgur.com/2j9CCTI

https://imgur.com/OMh0oyO

 

I tried to rebuild FalloutNewVegas as I installed before.

There was no crash. And also CTD too.

However, there were a lot of red exclamation points that had not existed before.

When trying to find out the cause, it turned out to come out when installing TTW.

I tried invalidating the archive, but it was ineffective.

I kept clean installation many times but I did not solve anything

Please help me

 

[X] FalloutNV.esm
[X] DeadMoney.esm
[X] HonestHearts.esm
[X] OldWorldBlues.esm
[X] LonesomeRoad.esm
[X] GunRunnersArsenal.esm
[X] Fallout3.esm
[X] Anchorage.esm
[X] ThePitt.esm
[X] BrokenSteel.esm
[X] PointLookout.esm
[X] Zeta.esm
[X] CaravanPack.esm
[X] ClassicPack.esm
[X] MercenaryPack.esm
[X] TribalPack.esm
[X] TaleOfTwoWastelands.esm
[X] YUPTTW.esm
[X] SolidProject.esm
[X] IWR.esm
[X] AWorldOfPain(Preview).esm
[X] MojaveTerror.esm
[X] TTWInteriors_Core.esm
[X] TTWInteriorsProject_Combo.esm
[X] oHUD.esm
[X] NVStripOpen.esm
[X] NSkies URWLified.esm
[X] AmmoChecking.esp
[X] LootMenu.esp
[X] Reload Sounds.esp
[X] DK_BulletTime_NV.esp
[X] The Weapon Mod Menu.esp
[X] Roberts_NewVegas.esp
[X] B42 RWMS.esp
[X] ItemBrowser.esp
[X] Diagonal movement.esp
[X] AWOP-PERFORMANCE_PATCH.esp
[X] AK_AR15WP.esp
[X] IWR - Rebuilt.esp
[X] StripOpenMain.esp
[X] Mountain Fort.esp
[X] Remy.esp
[X] MojaveTerror - Level list.esp
[X] Mossberg590.esp
[X] FalloutNVCheatTerminal.esp
[X] BM4A1.esp
[X] M16A2.esp
[X] QS_Blackwolf_NV_Backpackmod.esp
[X] BLEED.esp
[X] CRHDV3O2.esp
[X] CRHDV3O3.esp
[X] TheLozza's_Gasmasks_V2.esp
[X] Dead Money - No Collar Explosion and No Poison Cloud.esp
[X] No Weapon Remove Dead Money.esp
[X] SOGFusionTomahawk.esp
[X] theHeroNV_1.1.esp
[X] LFox Invisible Armored Vests.esp
[X] Hood.esp
[X] Remove That Glove - NV.esp
[X] LVL99PEL.esp
[X] Lighter Gold Bars.esp
[X] LiveDismember.esp
[X] DragsModernGunslinger.esp
[X] MojaveTerror - Level list - TTW.esp
[X] Clanf_NoWeaponsRemove.esp
[X] Reload Reloaded.esp
[X] Reload Reloaded - Perks.esp
[X] Sit Anywhere.esp
[X] sledgehammer.esp
[X] TTW CRTLF.esp
[X] GUN Reload Sounds.esp
[X] Clean Industrial Machines.esp
[X] AK_AR15WP_Tasha_shop.esp
[X] Clean Utility Tileset.esp
[X] IMPACT.esp
[X] Tracer nv.esp
[X] dD - Enhanced Blood Main NV.esp
[X] Holster Gear.esp
[X] NaturalWaters.esp
[X] The Mod Configuration Menu.esp
[X] 1911.esp
[X] BHPM1935.esp
[X] ZoomingScope.esp
[X] Bashed Patch, 0.esp
[X] CF_FastStart.esp
[X] NSkies URWLifiedDM.esp
[X] NSkies URWLifiedHH.esp
[X] NSkies URWLifiedOWB.esp

 

 

Link to comment
Share on other sites

* You really need to use a "Merge Patch File" with that collection of mods. Please see the 'Third Rule: The Rule of One' and 'Merge Patch File' sections of the wiki "FNV General Mod Use Advice" article.

Because "Texture/Mesh" replacement mods replace vanilla versions of those files, you absolutely have to toggle "ArchiveInvalidation (AI)" off-and-then-on again after installing or removing one of them so it recognizes that there are loose files (added by the mod) which have to be used in place of the vanilla files in the BSA files or are no longer there and the BSA files should be used instead. That failure to toggle is the most common reason behind most "texture problems". This is usually evidenced by red "!" icon for missing meshes, and solid colors for missing textures, or "messed up" textures. This "ArchiveInvalidation" mechanism is incorporated in all the currently used mod managers, so there is no need to (and problems arise if you do) install older mods to provide that capability. ONLY USE ONE METHOD of AI, especially if you have multiple mod managers installed. Otherwise they will conflict, as they use their own "arbitrarily chosen" names for the AI BSA files. (There is not a standardized name used among them all.) Please see the 'ArchiveInvalidation (by Manager)' section and also see the 'Checklist Item #15 & 16' entries in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

The only other reasons for mods to have these "missing element" error indications are that you failed to install all the necessary files (such as an ESM or BSA file), or they aren't in the correct location.

In the case of (for example) "Weapon Retexture Project" (WRP) v1.95, the package has a "non-standard" folder structure. (Not an uncommon mistake by mod authors, so learn from this.) The game (to include most mod managers like NMM, MO, and FOMM) is expecting the top level folder of an archive package to be standardized, folder names such as "Textures" or "Meshes", or ESM/ESP/BSA files. It assumes they are being placed under the game "Data" folder. This example package starts with a "RLS" folder, which the game does not recognize, and so it places that as the "top level" under "Data". (Sometimes this is the author's name or initials, other times it's the mod name and version, but anything unexpected is treated the same way: as a new folder or file.) Most likely when the files are "installed" but aren't found correctly, something similar to this is your problem. Unpack the mod archive (WRP in this instance) to some other location and then either rebuild the archive so the top level folders are "Textures" and "Meshes" (in other words, without the "RLS" folder from WRP at all), and then install with your mod manager, or manually drag those two folders into the game "Data" folder.

The text file under the WRP "RLS" folder is a documentation file. If you want to keep similar in the package, just place it in the top level along with the "Meshes" and "Textures" folders. Personally, I rename such to "<mod_name>_ReadMe.txt" so I know which package they came from. (Many authors act as if their mod's text file is the only one that might possibly exist in the same location or use the same common name (i.e. "Readme.txt").)

The various "NSkies URWLified" plugins (assuming they are compatible) should be placed before the Bashed Patch. The "Rule of One" still applies. My guess would be that the last one (NSkies URWLifiedOWB.esp) is causing the previous ones (DM & HH versions) to have record conflicts. But I hadn't even heard of that mod before, so I could be wrong.

 

Make sure you have checked the TTW FAQ Forum links to both the "Recommended" and "Incompatible" mods pages.

 

-Dubious-

Link to comment
Share on other sites

  • 2 weeks later...

I really don't know why you need to have TTW Installed it seems more of a headache and the guy who runs the website is not very helpful. (The audio for the F3 side sucks also) Plus none of the MODS work.

 

The YOUTUBE install video is TERRIBLE in my opinion.

 

Plan and simple in order to read the game files it needs to be placed in the DATA folder in Fallout New Vegas.

 

It needs to read the textures, if it is not reading them in the linked position or the textures are missing you get the red exclamation points.

Link to comment
Share on other sites

I really don't know why you need to have TTW Installed it seems more of a headache and the guy who runs the website is not very helpful. (The audio for the F3 side sucks also) Plus none of the MODS work.

 

The YOUTUBE install video is TERRIBLE in my opinion.

 

Plan and simple in order to read the game files it needs to be placed in the DATA folder in Fallout New Vegas.

 

It needs to read the textures, if it is not reading them in the linked position or the textures are missing you get the red exclamation points.

The "!" in the red shape is the error symbol for a missing mesh, not texture.

Link to comment
Share on other sites

@Hmmm Let me know your account name if you are having trouble posting on the forum and I'll look into it. You'll get help faster/better by joining our discord.

 

You have missing meshes, usually an indication that FalloutCustom.ini is not working correctly. Some setups have a problem with the sArchiveList entry not working, and it needs to be put in Fallout.ini

 

@Deter32 TTW is a total conversion, it is easy to install, and works fine on it's own or with mods which are for it or compatible with it. Any problems you are having are likely on your end. Your opinion is not helpful to the user asking for help.

Link to comment
Share on other sites

Clone Master Gary aka RoyBatterian,

 

You banned me from your website and your forums so I am having trouble posting. So I can't get any help and I am rejected from joining.

 

Why are you trying to be nice here?

 

What did you call me, an Insane mentally disturbed nut case madman troll or whatever. I don't know I am banned for asking how to port over custom F3 mods.

 

 

Like I told you, had to re purchase the game from Steam just to test out the TTW. It was not easy to install.

 

 

Anyway i have no hard feeling nor any ill to your project, it is a neat idea.

 

Since our encounter figured out how to port things back and forth from F3 and New Vegas so for me, I will leave it as two separate games.

Edited by HynoDesigns
Link to comment
Share on other sites

Thank you everyone.

Reinstalling TTW resolved this issue

 

As RoyBatterian says, this may have happened because there was no FalloutCustom.ini

But it is strange

FalloutCustom.ini can only be obtained when installing the TTW as an EXE file

I need to take a backup, but why is it not generated in the TTW installation folder

Sorry for the complicated question

Link to comment
Share on other sites

"FalloutCustom.IN" is part of the "JIP LN NVSE Plugin" mod. (Perhaps it is included as part of TTW v3.2; I don't know.) It goes into the "Users\<AccountName>Documents\My Games\FalloutMV" folder where it is used to override the settings of the other Fallout INI files because that is how it is designed to function.

 

-Dubious-

Link to comment
Share on other sites

Our installer is an exe, it's meant to either convert your game to TTW, or create files for use with MO2/Vortex. It's very complex and not a typical mod as it's a total conversion (like Enderal etc). It creates the ini files in the ini folder in the same place the base game does, MO2 is able to manage these INI files (FalloutCustom.ini) along side the games INI files, that is it's intended purpose.

 

@dubiousintent You may want to familiarize yourself with TTW, it is one of the oldest and largest mods not available on nexus (we wish it were, but that's the staff's call) with many hundreds of thousands of users and a large community centered around it.

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...