Jump to content

Problem with importing armor into 3ds max 2014


mitchell.badger

Recommended Posts

Hi there,

I have just started to try learning how to edit armor mesh in 3ds max recently and so far I have had a tiny bit of a problem regarding the armor texture. I've been following Nightasy's tutorials on youtube and have successfully installed the nif plugin for 3ds max. The armor I tried to edit is successfully imported. However, the texture did not show on the mesh. I tried to enable material on the mesh but it still did not make any difference. The mesh showed up in grey-ish color which made it really difficult to visualize the armor. Does anyone know which steps should I take in order to force 3ds max to properly show the mesh texture? I am using 3ds max 2014 by the way.

Link to comment

I checked at the "Realistic materials with maps". Is it the right one because It still display the mesh with grey-ish color?

 

Ok.

 

I rarely work with 2014.
It seems to be a problem with file path (texture).
 
 
Customize -> Configure User Paths -> External Files: Add your Skyrim Texture folder.
 
If it does not work, try this (quickly as a material editor)
 
1. Open Asset Tracking (Shift + T)
2. Click on File -> Refresh
3. Now all your maps should be displayed
4. If the status is not ok, right-click (on Map) -> Set Path
Now select the correct path
Link to comment

 

I checked at the "Realistic materials with maps". Is it the right one because It still display the mesh with grey-ish color?

 

Ok.

 

I rarely work with 2014.
It seems to be a problem with file path (texture).
 
 
Customize -> Configure User Paths -> External Files: Add your Skyrim Texture folder.
 
If it does not work, try this (quickly as a material editor)
 
1. Open Asset Tracking (Shift + T)
2. Click on File -> Refresh
3. Now all your maps should be displayed
4. If the status is not ok, right-click (on Map) -> Set Path
Now select the correct path

 

Worked like a charm! Thank you so much! It seemed that asset tracking is disabled for my 3ds max 2014. Configuring the asset path manually did solve the issue.

Link to comment

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

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

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. For more information, see our Privacy Policy & Terms of Use