Aller au contenu

Photo

Need Help with Toolset Crash...


  • Veuillez vous connecter pour répondre
19 réponses à ce sujet

#1
jackkel dragon

jackkel dragon
  • Members
  • 2 047 messages
I tried to start up the NWN2 toolset to test a few things, but I've run into a pretty major snag. Whenever I try to open a properties window, I get an error. Areas, modules, and blueprints all give me this error. Since I can't figure out what file(s) might be corrupted, I was hoping someone else could decipher this error message for me. I'm hoping to avoid needing to reinstall after having done so only a month or two ago, but without help I might be on that road...

Here's the error message as it appears when trying to create a new area, since that seemed to have the most info: here

Modifié par jackkel dragon, 25 novembre 2012 - 12:39 .


#2
MarshallV

MarshallV
  • Members
  • 43 messages
Try installing .NET 2.0

#3
jackkel dragon

jackkel dragon
  • Members
  • 2 047 messages
Is there a specific version I should try installing? I tried to install .NET 2.0 SP1, but it says that my Windows 7 computer isn't compatible saying something to the effect of "this doen't run on Windows Vista".

#4
MarshallV

MarshallV
  • Members
  • 43 messages
You can also check and see if you have .NET 3.5 as well

http://www.microsoft...ails.aspx?id=21

#5
jackkel dragon

jackkel dragon
  • Members
  • 2 047 messages
I tried the linked download, but it didn't work for me. The error message didn't give me much info either. I tried using the .NET 4 installer to repair that framework's installation on my computer, but I still have no luck on getting the toolset to work properly.

#6
Morbane

Morbane
  • Members
  • 1 883 messages
try making a test module - see if it loads...

#7
Morbane

Morbane
  • Members
  • 1 883 messages
windows 7 is backward compatible with all of the previous .net versions...

#8
jackkel dragon

jackkel dragon
  • Members
  • 2 047 messages
I can load modules, I just can't open the properties window for anything. If I select an object blueprint, an area, or the module I get the error. I'm really not sure how to proceed... there must be something missing or corrupt somewhere but I don't know what it is.

#9
Morbane

Morbane
  • Members
  • 1 883 messages
somewhere in the player directory (mydocuments/neverwinternights2/....) is a file that controls user settings - hopefully someone will remember what it is called - if you delete that file your toolset settings will go back to default - maybe that will help.

PJ156 wrote...

This one has come up once or twice.

Q: Help! My toolbars are gone!
Q: Help! My other windows are gone!
A: Click on the View menu and choose Options.... On the left side, choose Windows. Click the Reset button, then click OK. Close the toolset, and reopen it.

If this doesn't correct the issue, or if your menu bar is gone, close the toolset. Open up Windows Explorer, and paste this text into the Address bar:

Windows XP: %USERPROFILE%\\Local Settings\\Application Data
Windows Vista: %USERPROFILE%\\AppData\\Local

Hit Enter. From there, delete the folder named NWN2 Toolset. That will reset everything for when you next launch the toolset



#10
jackkel dragon

jackkel dragon
  • Members
  • 2 047 messages
I tried deleting the toolset folder in the AppData/Local directory. It reset all my windows to the default, but the error persists. I think something might be wrong with my .NET framework installation. Which is upsetting since I already used the .NET 4.0 installer to repair it twice in the past few days.

#11
KurumiMorishita

KurumiMorishita
  • Members
  • 29 messages
Have you also tried to completely uninstall/reinstall NWN2? some days ago my toolset always crashed (already during launch), too and nothing else than a complete reinstall of NWN2 worked for me.

#12
jackkel dragon

jackkel dragon
  • Members
  • 2 047 messages
I think re-installing NWN2 might be the only sensible option left. I'll have to get on that once I figure out where my disks got to...

#13
Morbane

Morbane
  • Members
  • 1 883 messages
make sure you back up your user directory - uninstall will delete that folder and all of your player-created modules.

#14
jackkel dragon

jackkel dragon
  • Members
  • 2 047 messages
Ugh. I reinstalled everything, and now the toolset doesn't even start up anymore. I don't know where I can possibly go from here.

#15
Kaldor Silverwand

Kaldor Silverwand
  • Members
  • 1 592 messages
Did you install DirectX 9.0c? Windows 7 comes with DIrectX 10 I think. I found a note online that says that if you are running Windows 7 x64 the DirectX files need to go into the folder c:\\windows\\syswow64 rather than c:\\windows\\system32

Hope this helps.

Regards

#16
jackkel dragon

jackkel dragon
  • Members
  • 2 047 messages
I'll look into that, thanks.

#17
Morbane

Morbane
  • Members
  • 1 883 messages
I preventitively planned and installed Win7 as 32 bit

I can play even the newest games and NWN2 runs flawlessly

food for thought

#18
jackkel dragon

jackkel dragon
  • Members
  • 2 047 messages
The good news: After reinstalling a second time and running the DirectX installer manually from the disk (it's corrupted and won't run during normal install) NWN2's toolset is working properly for me again. Properties window and all.

The bad news: I still have no idea what the initial problem was. Also, the days of my main NWN2 disk are apparently numbered.

Hopefully the toolset with still work after reinstalling the expansions...

#19
jackkel dragon

jackkel dragon
  • Members
  • 2 047 messages
Ugh, the properties window problem returns after I install the expansions and patch to 1.23. This is infuriating.

#20
jackkel dragon

jackkel dragon
  • Members
  • 2 047 messages
Not sure if I'll be able to get the toolset working again even if I can fix it, but I noticed my old friend "System.Design" (a windows OS file and root of my toolset window problem) is one of several corrupted files while checking for problems with something else. Still trying to figure out how to replace the corrupt file with one that works, but I believe I have the cause of the problem tracked down now.