Author Topic: Blender can no longer import/export nifs?  (Read 509 times)

Offline 086gf

  • Location: United Socialist States of America!
  • Posts: 1357
  • Cookies: 32
Blender can no longer import/export nifs?
« on: December 21, 2011, 01:57:20 PM »
I have the most current version of Blender and the nif plugin for it but it wont show up as an option in the import/export lists. I also have the minimum required(for the nif plugin) versions of Python and PYFFI but maybe I need to have more current versions? I know atleast two others here(Unknown aaannnddd...???) use Blender too so im curious what I need to do.

Thanks.
All hail the messiah!

Offline eclipse74569

  • Roger Smith of the U.S.S. Lollypop, a good ship
  • Webmaster
  • Posts: 2240
  • Cookies: 65535
Re: Blender can no longer import/export nifs?
« Reply #1 on: December 22, 2011, 12:34:01 PM »
I think they got rid of most of the importer information...you might want to contact the developers.
Humankind cannot gain anything without first giving something in return, to obtain, something of equal value must be lost.  That is alchemy's first law of equivalent exchange.  In those days we really believed that to be the world's one and only truth~Alphonse Elric

Offline X_TheUnknown_X

  • Posts: 325
  • Cookies: 328
  • (Semi) Retired
Re: Blender can no longer import/export nifs?
« Reply #2 on: December 23, 2011, 12:58:41 PM »
The developers of Blender NIF Scripts (who created the .nif exporter for Blender 2.4x) have said somewhere that they are holding off making an exporter for 2.5/2.6 until Blender Foundation release 'stable' version. To my knowledge, we've had a stable, yet incomplete, version of Blender for some time now. So either the NIF Scripts people are waiting for the final realease (2.6x probably), or a plugin in currently in development now.
Currently, there are two ways of getting Blender models into NIFs: 1) Just open up the file in Blender 2.4x, and export using the original pugin, or 2) Download NIFSkope, and use whatever version of Blender to export to an OBJ file which NIFSkope can read. In my experience, method 2 is better, because NIFSkope sets up the 'blocks' in the .nif file properly for BC (the NIF Scripts plugin didn't).
Hope this helps  ;)