Jump to content

Help needed with custom NIF (private mod)


21crescendo

Recommended Posts

So, this is a private mod, in which I'm using assets from 2 different mod authors. The original NIF is of a CAR 15 rifle reflex sight which I've converted into a Trijicon ACOG

sight using the RU556.

It's not the copying and/or pasting of blocks that I need help with, nor is it placing the right materials path. The sights, the mildot and the red dot et al are aligned properly and work well in game.

The problem arises when I place the backup iron sights from the RU556 on top of the rear stock of the rifle (they don't serve a purpose with the ACOG, just aesthetics). The save game in which I'm using the modded rifle with the custom attachment crashes.

I've troubleshooted it down to the fact that the problem most definitely has to do with the backup iron sights and sights holder blocks. The materials path in both(1

, 2

) blocks is correct (I've double checked); what seems to vary though from the original RU556 is the BSTriShape 'name value'.

I've tried using blank fields, I've tried using name values from the original RU556 nif, I've tried setting some custom names, but they don't work.

I've also loaded up the custom NIF on BodySlide just to check if it works but quite rightly, the application crashes as does the game itself.

What am I doing wrong? Can anyone help me out?

Link to comment

Is this just for asthetics reasons or do you mean to have the iron sight blocks be editable in the game's weapons crafting workshop?  I've seen crazy stuff happen when copying entire blocks, because when you do that - you're also copying the underlying references along with.  So when you attempt to use that in-game, the engine bombs out when more than 1 reference returned when it expects a single value.

 

If it's just asthetics, that would make life easier as you can edit the actual mesh in blender or 3dsmax.  I've had similar issues with clothing mods I was working on, when block copying and editing in NIFSkope.  Doing the edit to the mesh itself in other software, then importing the whole thing to NIFSkope to finish it off did the trick.

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