M48A5

You ported meshes from New Vegas to FO3. The texture path shown in NifSkope does not show the complete path of the disc drive, game name, data, textures, file folder, texture name. It has been truncated to show only textures\file folder\texture name. So the meshes you ported from FNV will be looking for FNV texures, not FO3 textures. You will have to manually change the path the textures using Nifskope even if FO3 has the same named textures.

Did you change the path to the textures when you ported the meshes? Are the textures installed in the correct location? Are the shader flags set correctly for FO3? Did you toggle Archive Invalidation after installing the textures?

I'm surprised no=one has mentioned Zion Trail https://www.nexusmods.com/newvegas/mods/61939\ Zion Trail Redux https://www.nexusmods.com/newvegas/mods/61939. Make sure you get both and install them properly.

This is not the way to ask for assistance. I suggest you read "How to ask for help" at the following link: https://wiki.nexusmods.com/index.php/How_to_ask_for_help

Since this is the Fallout: New Vegas forums, it is a given that you have Fallout: New Vegas and the DLCs installed, even though you failed to list them in the load order. However, there is no listing for any Fallout 3 files. These are needed for TTW to work. If you don't supply all the information, the members here can only make guesses about a solution to your problem.

Let's see, too many files installed, the game not patched to use 4GB or more of RAM, TTW installed, but no listing of FO3.

Did you make the changes to the Fallout3.ini, located in the My Documents folder, that would limit you CPU to using only two cores? bUseThreadedAI=1 iNumHWThreads=2

Not a problem, it's a feature. You need to look down the sights in order to aim properly. You can't do this in third person.

Game assets cannot be uploaded and shared. If you bought your game from Steam or GOG, just verify the game files.

Project is listed in the load order you posted. If it is not currently installed, you will need to post your new load order. When asking for help, it is extremely important that your current load order be posted. Otherwise you will get responses like the one from JimboUK. We can only go by the information you have provided before we can begin to offer a solution to your problem.

You have two .esp files mixed in with the .esm files. This should not be. It would lead me to believe that Project Nevada was not installed properly. After you install a mod, you do use File Explorer to check that the mod was installed correctly, don't you?

I looked at the .nif file that you have and none of the ShaderFlags are set properly. You have to set the flags on each individual body and armor parts listed in the .nif. While looking at the file, there was a point when I rotated the image, part of the right leg became transparent. However, I was not able to duplicate it. I have never had this happen to me. If the shader flags were not correct in a .nif that I had used in blender, the armor was completely invisible.

Open your model in NifSkope and check to make sure that the correct shaders are active. For anything other than skin, the shader type should be sader default. For skin, it should be shader skin. For each item, except for any caps or meat, shader flags that should be active are Specular, Skinned, Windows Environment Mapping, Remapple Textures, Shadow Map, ZBuffer Test. Along with FaceGen if it is any skin part. Also check to ensure that the path to the texture is correct.

Did you disable Archive Invalidation and then enable it after you activated our .esm? Archive Invalidation needs to be toggled, not left on, for changes to become active.

After you made the changes but before you started the game, did you toggle Archive Invalidation? If you are using VORTEX, the built-in Archive Invalidation does not always work. You might have to toggle it a few more times or use the stand alone version that is here on Nexus Mods.