Grumbling about file formats .NK and .IES

Come here for help & support.
Post Reply
1 post • Page 1 of 1
forgeflow
Posts: 63
Joined: Thu Oct 29, 2009 5:26 pm
Location: Canada
Contact:

Grumbling about file formats .NK and .IES

Post by forgeflow » Wed Jul 07, 2010 12:25 am

Question: Why doesn't Indigo handle certain file formats properly? Indigo will only work correctly with a subset of the .nk data it is supplied with, and will not work with a lot of .nk data files obtained elsewhere. For example, there is a TiN.nk (titanium nitride) file that I've used in LuxRender as a substitute for Brass. This will not work in Indigo - locks up the renderer at the "build" time. Is the .nk file format not a published standard? If LuxRender can read these files properly, why can't Indigo?

Also, there are a number of .IES files that Indigo will not work with as well, because they are a full 360 degree definition, and Indigo will not work with .IES files that have more than 180 degrees of data in them. Again, is this not a published standard? If an open source project can handle these things properly, why can't Indigo?

From some reading on the subject, I gather that there are two different "types" of .nk data, and that it is possible to convert from one to the other with a script of some sort. A really old forum posting on the topic here mentions it, but no script was ever posted. Does anyone know the method of converting type2 .nk files to type1?

Post Reply
1 post • Page 1 of 1

Who is online

Users browsing this forum: No registered users and 5 guests