Pixelhate

It's named parallax in NV. I thought I answered those questions already.

Apart from not being real PBR, I know next to nothing about FO4 texture system, you'll probably find tutorials on Yt about how to adapt them for FNV. If I have to use PBR textures in FO3-FNV, I usually: - take the AO and overlay it on the Albedo. - use the Opacity to make the diffuse Alpha. - use the Specular or the Roughness or a combination of both for the Normal Alpha. - use the Emissive for the Glow Mask. - use the Height for Parallax. - use the Specular or the Roughness or a combination of both for EnvCube Mask. Not every Textures are used every time. Filters and adjustments are often done in Photoshop - Gimp - Paint.net to make it work in the old rendering engine.

Short answer: yes. Optimization is less about the weight of the nif than the way it is proceeded trough a 2006 game engine (Oblivion) patched for FO3 and later once again for FNV. A poorly made nif will not make a big difference if only added to the Vanilla mistakes already existing. But the accumulation of bad material will only lead to poor performance and/or issues difficult to troubleshoot. And yes, many modders don't have the knowledge or the will to learn and bring clean mods but that doesn't mean they have to be imitated.

Correct, my mistake. You should Stripify your nif.

NiTriStrips are optimized, NiTriShapes aren't. Armors, characters and creatures are in TriShapes. The rest in TriStrips, as you can see if you open and inspect Vanilla nifs. You should Triangulate (NifSkope Spell) your nif. There's a lot of unwelded vertices too, which increase the computer strain and can eat FPS like nothing, I can't say much more about it, Weapons are not my forte. As a general advice, I would recommend not to build upon structurally bad nif. Working directly with .obj in NifSkope is also opening ways to unsolvable issues. If, somehow, your NifSkope is now corrupt reinstall fresh.

Install & version seems OK. In more than 10 years of use I can count NifSkope crashes on one hand, mostly due to my mistakes. There are several ways to delete or remove a Node or an Array in a nif. (I guess that's what you mean with "assets") The correct (and long one) is: 1. Unlink the Node from its parent. 2. Select the Root Node -> Rclick -> Crop to Branch 3. In menu select Spells, -> Sanitize A.-> Collapse link Arrays B.-> Reorder link Arrays C.-> Reorder Blocks 4. Save This should ensure a safe result (if the nif is originally healthy). The nifs you linked are indeed bad with NiTriStrips and NiTriShapes mixed. I can't pinpoint other error at first sight but the fact that it can't be proceeded in Sniff with "not a valid nif" message says it all. Troubleshooting deeper might be uncertain. I could remove parts without crashing, with NifSkope giving an error message one time on closing. I would stay away from such meshes unless you are able to import/export from a 3D app with the correct settings. If the issue you've described persist with other know clean nif then you might need to reinstall NifSkope.

Yes, that's how you proceed with the pseudo-pbr of FO4. You take a separate spec map and you integrate it in the Alpha of the Normal map. But linking a spec map only in a slot of the texture Shader in a FO3-FNV nif won't do anything. There is 6 slots available, There's a naming convention. Diffuse/Alpha Texture/Transparency Name.dds Normal/Alpha Relief/Specularity Name_n.dds Glow Mask Mask for Emissive Color Name_g.dds Parallax Depth effect Name_p.dds EnvCube Reflection on the object Name_e.dds EnvCube Mask Mask for reflection Name_m or Name_em.dds Diffuse & Normal can be in DXT1 or DXT5 depending the need. EnvCube has its own setting, the other are in DXT1. Glow Mask & EnvCube mask are telling which part to reveal of a setting that applies on the whole NiTriStrips/Shapes. If you set an Environment Cube flag in your nif but don't assign an EnvCube map, the game will assign (an ugly) one by default. If you don't assign a Envcube mask while having flag and EnvCube map set, the game will use the Specular (Alpha) of the normal. These two situations might lead to an increased Draw Calls and GPU strain. You can use the Specular map to generate a *_m.dds or draw one in graphic app. The dark part will mask the EnvCube map reflection, White part will fully reveal and nuance of grey to attenuate.

This is not normal behaviour for NifSkope. - Where and how did you install it? - Describe exactly each step you are performing till crash. - If it happens with one nif in particular, please share it so I can have a look.

Separate spec map don't work in FO3-FNV, they are useless.

The Normal Maps in FO3 -FNV use an Alpha channel for Specularity. Add an alpha channel to your Normal map where white = bright/shiny, black = dull and grey for nuances. Save in DXT5.

Here's a couple of links to should help: https://www.nexusmods.com/skyrim/mods/5622?tab=files For 2012 version you want Figments 3.7.3 plugins when using 3ds max 2013 you should use this exact version, the newer one is broken https://github.com/figment/max_nif_plugin/releases/tag/3.8.0-a3 https://www.nexusmods.com/newvegas/mods/69752

In FO3Edit, find the deleted cell and un-delete it.

Many improvements to the NV engine of these last years (mainly dll) are related to The Frontier trying to push it to its limits.

The closest is: https://www.nexusmods.com/fallout3/mods/24347

https://wiki.nexusmods.com/index.php/FNV_General_Mod_Use_Advice https://wiki.nexusmods.com/index.php/Fallout_NV_Mod_Conflict_Troubleshooting

Actually, it's not a port but an original work recreating the mesh from scratch. Since the mod is mesh & textures only, you can install in NV and it should work right away.

Thank you, Dubiousintent, for providing a solution but I didn't had to resort to it. After trying unsuccessfully to re-date with Wrye Bash (unfamiliar to me) I have been advised to update my xEdit version. That solves the issue which was GOG version missing a last modified date on the game master.

I can't check my work in xEdit because a master tries to load before FalloutNV.esm. To correct that I need to change the timestamp and re-date the plugin. Could someone, please, explain the procedure to do so. Thank you.

I believe ground mesh (*_go.nif) is more for armors and such. The problem here is likely a missing or misplaced collision in nif structure.

I wonder what part of "Speaking in non-accusatory, very general terms:" is unclear.

https://wiki.nexusmods.com/index.php/How_to_fix_hard-coded_texture_paths_in_NIF_files

You don't want to mess with actor collisions, part of it is hardcoded. Some highly talented modder manage to have the collision shrinking when actor is crouching, which is a great achievement but only for NV and thanks to to NVSE and its plugins.

The .obj export in NIfSkope is broken, not reliable. Most people using 3D Max to work on nif use an older version. So does Blender users.

SpecialIdle is the name of .kf, the animation of the creature. Sound is referenced in the .kf.

BSA are in the Data folder and should look like this