NWN Explorer Issues

[Legacy_henesua]

               Lately I have been having trouble with NWN Explorer.
(FYI - I upgraded to NWN Explorer reborn and still have these problems)

Problem 1:
Not all resources were showing up in the HAK folder.

Solution:
I had been using the HAK directory as my PATCH directory (in nwn.ini under aliases). I changed the PATCH alias in nwn.ini back to the PATCH directory, and this problem went away.

Problem 2:
In default view (see all NWN resources on left) opening a resource in a HAK gives me "Error Opening the Resource"

Solution:
Use the "open" command on a specific HAK. -- All resources can be read normally in this manner. BUT I still can't open HAKs in the default view (does the program get overwhelemed with too many resources?)
               
               

               
            

[Legacy_Khuzadrepa]

               Try emptying your 'hak' folder (backing it up first, of course) and then putting just a few haks back into it.
               
               

               
            

[Legacy_henesua]

               Khuzadrepa, I haven't done that to test, but I think you are right. The program behaves as if it was hit with TMI when browsing HAKs that way. BUT if I only browse the resources of a single HAK using the open command, it has no problem.
               
               

               
            

[Legacy_Lightfoot8]

               You may have created an infinite loop with the two folders being the same.  when you changed the PATCH directory back Did you have a Folder there for the directory.   Perhaps it is not getting reset(over written) if there is no folder.
               
               

               
            

[Legacy_henesua]

               Lightfoot8, i don't know about the infinite loop, but I've never had the patch directory show up in NW Explorer. Nevertheless issue 1 was solved as soon as I changed the alias back to the Patch directory - both NW Explorer and the toolset have none of the issues I noticed when I tried this experiment.

Problem 2 exists independently of how I set the alias for the patch. I have however recently gone HAK crazy in my HAK folder. Previously I had limited the partition dedicated to NWN to 32 GB and been very careful about which HAKs I keep there. Now I am using a 100 GB partition for NWN and being much less selective. I've got almost ten times the number of HAK resources I had before. Thats the only thing that has changed.
               
               

               
            

[Legacy_Khuzadrepa]

               

henesua wrote...

Lightfoot8, i don't know about the infinite loop, but I've never had the patch directory show up in NW Explorer. Nevertheless issue 1 was solved as soon as I changed the alias back to the Patch directory - both NW Explorer and the toolset have none of the issues I noticed when I tried this experiment.

Problem 2 exists independently of how I set the alias for the patch. I have however recently gone HAK crazy in my HAK folder. Previously I had limited the partition dedicated to NWN to 32 GB and been very careful about which HAKs I keep there. Now I am using a 100 GB partition for NWN and being much less selective. I've got almost ten times the number of HAK resources I had before. Thats the only thing that has changed.

The reason I suggest that is that I also had a boatload of haks that built up over years of custom content testing, and I had a similar sounding error such that I couldn't see individual hak resources by browsing thru the tree. Hopefully, that is also your issue, as it's an easy fix. '>
               
               

               
            

[Legacy_Tiberius_Morguhn]

               NWNExplorer (even the newer, updated revisions) have a hard set limit of 512 files for the HAK folder in the tree view.  Putting more than that in the hak folder, and NWNExplorer gives the error you encountered.  I have the same issue with keeping too many haks to look at all the goodies '>
               
               

               
            

[Legacy_henesua]

               thats good to know the actual limit, Tiberius. Thank you.