9 réponses à ce sujet

[ColorsFade]

I created a new test module and when I try and run the module from the Toolkit it goes into an infinite loop and keeps saying "Unloading Module..." I have to CTRL-ALT-DELETE to get out and kill the process. 

I thought maybe one of the scripts I was testing was causing the issue, so I created another new module from scratch and did abo****ely nothing to it other than create a single external area and bake it. I then save the module (as a directory) and when I try and load that module from the toolkit I get the same problem. 

The modules will load from the game if I start the game up, but not from the Toolkit. 

My campaign still loads fine from the Toolkit. 

Is there a module property or something I need to set in order for it to run from the Toolkit? 

Anyone ever run into this before? It's making testing a PITA. 

[kevL]

hey CF

Load from toolset works fine for many persons, it did for me for a while. Then it refused to work right and eventually crashed so bad i had to re-install SoZ

( consider that a warning! )


So i just keep the toolset open while loading/reloading the game...

[MasterChanger]

Load from TS is useful when it works but that's pretty limited. For one thing, I'm pretty sure it loads the module with the first character it finds, so it's usually Ole Drow Whose Name Starts With 'A'. If there's any amount of custom content in your module that would make him illegal, BOOM infinite load loop.

[Darin]

Also, if you downloaded and hacks/mods that effected the core game (like any that edited the OC) and open a campaign made before, it will give you a multitude of error messages on loading in the toolset, and loop your mod load. Making a character named Aaron or Aarya is advisable, because the drow is annoying.... make sure your Aa- character has no hak-based stuff assosiated with him/her...

[rjshae]

There have been a couple of times in the past where things got so messed up that I just had to reload the game and the patches. What a nuisance that was. Hopefully that's not the case here.

Do you have anything in your override folders? Perhaps try temporarily removing those and see if a new module will then load from the toolset.

[andysks]

Had the same problem as OP then it somehow got fixed.I don't even know how.These warnings like KevL said...might save lives someday though.

[Morbane]

never used the toolset game test method - leaving the game idling on the main menu is the best way to go imho

[kevL]

Morbane wrote...

never used the toolset game test method - leaving the game idling on the main menu is the best way to go imho

that's usually good as far as recompiling scripts and changes to areas go

but when making changes to core files ( like .2das ) or adding files to Override, might hafta reload completely.

[andysks]

I don't know if this is going to be helpful but I think I noticed something.Toolset had a problem when running a module saved as a directory.After I saved it as a module it run it without the loop.This changed after I installed the Power Bar...now it runs the directories as well.

[Morbane]

kevL wrote...

Morbane wrote...

never used the toolset game test method - leaving the game idling on the main menu is the best way to go imho

that's usually good as far as recompiling scripts and changes to areas go

but when making changes to core files ( like .2das ) or adding files to Override, might hafta reload completely.

Ya - I always restarted just to be sure in that case.