Hello there,
We have been developing our PW for some time and are preparing to start it. We have many scripts, some xmls etc. When testing (using server configuration, nwnx ) everythings works fine. But when we uploaded our module on dedicated server, all gui callback stoped working. Not just the ones from XMLs but even messagebox callbacks doesn't work. Doesn't anyone have some idea that could help?
Thanks in advance.
P.S.
We have disabled override folder and custom GUI (our xml files are contained within the haks, and are loading ok (tested) )
GUI Script callbacks stopped working
Débuté par
DFDark
, févr. 16 2011 11:13
Retour en haut
#2
Posté 17 février 2011 - 12:11
painofdungeoneternal
-
- Members
- 1 799 messages
You have a "on the fly" compile error where the game is trying to verify your parameters you are using.
This not working means either the scriptname.nss is not available, one of the includes is not available, or the game tries to compile the script and it returns an error. It is not actually compiling it, just doing a security check on the parameters, but it still needs everything just like it was compiling right where its sitting.
Steps to troubleshoot, make sure you have all the nss and ncs files available, and your complete library of nss is there which is used by the given script.
Without moving any files - preferably on your server, open toolset, and then compile the scripts right where they are - is there an error. If so, fix it. The toolset has open / convo script which can open scripts in override folder for example, or it might be in module.
If the above does not work, you have a very difficult include issue, where it works one way in toolset, and another in game. ( ie it works fine in toolset, but it loads the various includes different in game and thus has a problem ). To fix this you need to really simplify your includes which are deeper than one level deep. To do this i figure out everything being #include'd, even things deep and hidden and include them all from the main script so as to flatten it. Usually its a needle in a haystack at that point though, hopefully it's not the issue as it's very hard for even a great scripter to identify the core issue going on.
This not working means either the scriptname.nss is not available, one of the includes is not available, or the game tries to compile the script and it returns an error. It is not actually compiling it, just doing a security check on the parameters, but it still needs everything just like it was compiling right where its sitting.
Steps to troubleshoot, make sure you have all the nss and ncs files available, and your complete library of nss is there which is used by the given script.
Without moving any files - preferably on your server, open toolset, and then compile the scripts right where they are - is there an error. If so, fix it. The toolset has open / convo script which can open scripts in override folder for example, or it might be in module.
If the above does not work, you have a very difficult include issue, where it works one way in toolset, and another in game. ( ie it works fine in toolset, but it loads the various includes different in game and thus has a problem ). To fix this you need to really simplify your includes which are deeper than one level deep. To do this i figure out everything being #include'd, even things deep and hidden and include them all from the main script so as to flatten it. Usually its a needle in a haystack at that point though, hopefully it's not the issue as it's very hard for even a great scripter to identify the core issue going on.
#3
Posté 17 février 2011 - 12:40
DFDark
-
- Members
- 9 messages
putting *.nss files to the server solved the issue. I was under assumtion that it was just another file which is used only by toolset like in nwn1 and so I deleted it. Guess I was wrong.
Thanks for the solution
Thanks for the solution
Modifié par DFDark, 17 février 2011 - 12:40 .
