I just discovered that I cannot open an area that I have the Bugbear Hero model in…you know the vanilla Bugbear model from the standard pallette.
How the heck do I fix this!!!..I can’t even go in there to delete the model…anyone else having this issue?
OMG…this can seriously screw up my whole module wherever spawns call for this. I tried to open the model in the standard pallette and my module just crashes.
What the Hades???..how can a standard creature become corrupted?
I searched and searched and tested why I kept crashing in certain areas. Then I discovered that in all those areas I had bugbears. Then I went to look at all the bugbears on my palette (I opened one by one in both the custom then the standard palettes). I realized that when I went to click on the first bugbear hero on the standard palette the toolset would crash (the spiral of death)…only on that model…it won’t let me open it nor place one in the model. So I suspect it has an issue. Anyone else have this issue? How can I fix this?
Ok, the best assumption I can offer is, that the standard-model of bio is overwritten by a corrupt model in any hak.
So get your appearance.2da and search for duplicate entries in column “Race”.
Relevant names are:
c_bugchiefA
c_bugchiefB
c_bugwizA
c_bugwizB
c_bugbearA
c_bugbearB
These names are given in lines 25-30 of the appearance.2da. They must not appear again with higher line-numbers. The first two are the most suspicious.
If you find another entry with one of these, deactivate it by setting the first five columns after the line number to “****” Never delete an entire line from a 2da.
The next step is to search through all your custom … hey don’t rush me … haks for these names and remove the .mdl files.
Exactly on the lines you said above on the 2da…lines 25-30. No other duplicates of these on my 2da. I have bugbear versions of c to h on the lower part of my 2das. No conflicts. I can place all of my bugbears from the palettes on the ground except the one that crashes the toolset. I removed the bugbear hero mdl from my hak…still crashes. This was never an issue…until recently…wonder if an update screwed it up. You get the same issue?
Hero loads for me as a base game model. You could share the MDL file, but it sounds like it’s still loading the old version, restart your computer and remove it from the hakpack before loading the toolset.
You can also use nwnexplorer to triple check the file isn’t somewhere else erroneously like override, development or anything.
The Heroes may be any of those, I forget which matches up.
I looked in my hak where my bugbear mdls are. See below image. Can you tell if anything is wrong here? I do note there seems to be two bugbear hero types very similarly named. I put a yellow dot highlight by the similar names:
If you remove all the c_bug models, well, copy them out. I suspect it is c_bugchiefa or c_bugchiefb - wonder where they are from. If you know the source you might be able to find some fixed versions.
Is it possible that the mdl has both a .dds and tga for the same mdl causing this conflict? But if so I have my dds hak above my tga hak so it would read the dds first and ignore the tga right?
I restarted my computer…I opened the toolset and placed all of the bugbears from both the standard and custom with no problems in my module toolset…when I go to place that dam bugbear model in the toolset now…I get this new error:
I narrowed it down…it definitely is the c_bugchiefA
Don’t know why it is an issue, but as soon as I commented out the line 25 of my appearances.2da (first 5 columns with **** I can now access those areas. I removed all references to this bugbear model from my model. This is crazy…even without the model in my hak it still gave me issues.
So you got an advanced bug from the bear. Commenting the 2da-line out will only prevent loading the model by the toolset. It does not resolve the conflict in your haks.
Say, do you have somewhere an a_ba.mdl somewhere in your haks?
These are supermodels of the bugbear, and are most commonly responsible for animation. a_ba and it’s decendants are used by many many other creatures. Importing them from a third party source is always a bit dangerous. I think there might be an incompatibility between the bio-bug and the imported file (and other problems you havn’t detected so far.).