Certain Objects Appearing as Red Triangles

[AgentGrady]

All domestic binoculars and brahmin are appearing as red triangles. All lobotomites and also Christine appear encased in triangles. I know this means that an object is missing but I don’t know how this could be.

 

 

 

 

[M48A5]

Neither will anyone else without more information. Please see "How to ask for help" and provide all the information noted there.

 

https://wiki.nexusmods.com/index.php/How_to_ask_for_help

[dubiousintent]

Those are "missing mesh" indicators. Please see the 'Solutions to Mesh (Red "!" icon) or Texture (solid color) problems' section of the wiki "Fallout NV Mod Conflict Troubleshooting" article.

 

-Dubious-

[AgentGrady]

Thank you, Dubious

 

However, it says there that one of the ways to fix this is with archiveinvalidation, I am using Mod Organiser 2 with New Vegas and I cannot find archiveinvalidation on there. Does anyone know where on Mod Organiser 2 it is?

Edited April 8, 2019 by AgentGrady

[dubiousintent]

Please see the 'ArchiveInvalidation (by Manager)' section of the wiki "Fallout NV Mod Conflict Troubleshooting" article. If nothing else, it links to the support forums for each.

 

-Dubious-

[AgentGrady]

Ok, Ok Ok, I have tried both archiveinvalidation and LOOT but nothing seems to fix this. Nif Scope is out of the question because I don't know exactly what models are causing all this problems. So, I am posting my mod list, which I realise I really should have done in the first place. I hope that this might help to show where my problem may lay.

 

 

00

FalloutNV.esm

01

DeadMoney.esm

02

HonestHearts.esm

03

OldWorldBlues.esm

04

LonesomeRoad.esm

05

GunRunnersArsenal.esm

06

ClassicPack.esm

07

MercenaryPack.esm

08

TribalPack.esm

09

CaravanPack.esm

0A

Active Wasteland.esm

0B

agcStarTrek.esm

0C

AWorldOfPain(Preview).esm

0D

Momod.esm

0E

EZ_CompanionNVSE.esm

0F

Companion Core.esm

10

RobCo Certified.esm

11

Project Nevada - Core.esm

12

Project Nevada - Equipment.esm

13

Project Nevada - Rebalance.esp

14

Companion Share & Recruit.esm

15

CFWNV.esm

16

Project Nevada - Cyberware.esp

17

MikotoBeauty.esm

18

Mission Mojave - Ultimate Edition.esp

19

MoMod-Terminators.esp

1A

MoMod-Aliens.esp

1B

MoMod-MCMMenu.esp

1C

MoMod-NightSpawn.esp

1D

AWOP-MoMod.esp

1E

EZ_Force_Killable_NormalMode.esp

1F

RobCo Certified Friendly Hit Fixer.esp

20

Mission Mojave - Ultimate Edition Plus.esp

21

Mission Mojave - Ultimate Edition Plus Standalone.esp

22

BTB - Beyond the Borders.esp

23

Active Wasteland - Vanilla Replacements.esp

24

Fellout.esp

25

Active Wasteland - Dead Money Replacements.esp

26

Active Wasteland - Coffee Maker.esp

27

Color Me Evil - Cass.esp

28

EZ_VanillaFollowers.esp

29

Color Me Evil.esp

2A

MikotoBeauty.esp

2B

Caesars_Legion_Overhaul.esp

2C

IncreasedLegion1_1.esp

2D

hunter.esp

2E

Mercy Killing Karma v2.0.esp

2F

Companion Share & Recruit Companions.esp

30

EZ_GLUE.esp

31

ArenaAnySex.esp

Caesars Freeside Shop.esp

32

Existence 2.0.esp

33

agcStarTrek.esp

34

Active Wasteland - Dead Money Coffee Maker.esp

35

Active Wasteland - Dead Money Goggle Tints.esp

36

Active Wasteland - Goggle Tints.esp

37

PerkEveryLevel.esp

38

MoraelinsGladius.esp

Edited April 12, 2019 by AgentGrady

[dubiousintent]

* If you have more than one mod that makes any change to the same record or set of records in the vanilla game, then 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.

To identify which mod is failing to find a particular mesh, please see the 'Issue - Find the source mod-index of an object in-game' entry under the 'Solutions to Mesh (Red "!" icon) or Texture (solid color) problems' section of the wiki "Fallout NV Mod Conflict Troubleshooting" article.

The only other reasons for mods to have these "missing element" error indications that are not resolved by toggling "ArchiveInvalidation" 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").)

-Dubious-