doh, didn't answer your question about which node to use. I'm just using the standard node, the above screen shot shows what my infinimap extended node looks like, for some reason mine has no outputs. So I've never been able to use the extended node.

You can once you add an image. Since it allows you to access multiple channels within an OpenEXR image, the number and types of the outputs is dynamic and depends on the image being loaded.
How close is your deadline? I could pull the implementation of normal maps forward and send you a beta.

Having said that, a sample normal map and mesh would help me a lot in developing.

Cheers,
Mike

I would like to participate in this beta if possible. I too am up against a deadline on a HD project using multiple terrains all mapped with infinimap. All of my normal maps were generated as 8K TIFFs, but I'm forced to use 2048 or 4096 JPEGS as my normal maps due to the DP kit crashes. I'd love to be able to refine my project using the 8K normals to give it that needed punch.

Sweet, found it, for some reason g-mail labeled your email as spam.

Jon, have you noticed or found any advantage to using exr floating point normal maps vs jpeg2000 8-bit normals? I've been doing some tests and with my particular models and maps it doesn't seem to make any visible difference.

Just wanted to post some additional info I found with the object tangent node problem. I think I've just about found a reliable way to duplicate and avoid the problem. I'll pass my findings on to Denis Pontonnier (author of DP kit) as soon as I have it fully figured out. But in the meantime the information might be useful.

So far it seems its a guaranteed corrupted object if you: 
Load an object, apply object tangent node to its surface / UV. Load another object and apply object tangent node to its surface / UV and save.

This also applies to the "Normal Cast" node as well. The object corrupting is definitely tied to how those two nodes select a UV. I've noticed UV's of previously loaded objects tend to hang out in those two plugins drop downs even if the previous object and its accompanying UV has been removed from the scene.

The workaround is to open a new scene, load one object and apply normal cast or object tangent nodes to the surface, save the object. Clear scene. Then load the next and repeat. In other words you must surface the objects one at a time in a separate scene in order to avoid your objects being corrupted if your using those two nodes.

Obviously the workaround is major pain but using that workflow I was able to apply object tangent node to 30 different objects and load a scene with all 30 of those objects in it.

Next up there seems to be some major memory leak going on when rendering an animation that uses infinimap to object tangent node. Its like for every frame object tangent loads the data infinimap sends it but never releases it. So the next frame it loads more data and so on.

(Keep in mind so far all testing has been on done w/ Lightwave 9.6 x64. Haven't tried 32-bit or previous versions of lightwave)