NWN Toolset Extender + Compiler plugin

[virusman]

NWN Toolset Extender 1.0.0 + Compiler plugin
Required CRT: http://www.microsoft.com/download/en/details.aspx?id=5555
Download: http://data.virusman.ru/nwn/nwntx-compiler-1.0.0.rar
Install: Just unpack the files to your NWN folder and use NWNTX Loader.exe to launch the Toolset. The compiler will be switched seamlessly.
Thanks a lot to Skywing for the help and for his compiler library.
Details: http://social.bioware.com/forum/1/topic/188/index/7645830
The sources will be on SVN in a few days.
_________________
In Soviet Russia, NWN plays you!

[Lokey]

On 1.21ish WINE here. Winetricks for the msxml version to install the runtime resulted in a dead link.

Launcher works, provides feedback that makes sense.
_________________
Neversummer PW NWNx powered mayhem

[virusman]

New version with bugfixes and updated compiler dll:
http://data.virusman.ru/nwn/nwntx-compiler-1.0.1.rar
_________________
In Soviet Russia, NWN plays you!

[virusman]

[virusman]

New release!
NWNTX Compiler 1.0.2
http://data.virusman.ru/nwn/nwntx-compiler-1.0.2.rar
Added an ini file to enable/disable compiler optimizations and extensions.
Also, the compiler now generates debug data if it's enabled in nwtoolset.ini.
New compiler dll and msvcr100.dll are bundled with the package.
_________________
In Soviet Russia, NWN plays you!

[Lokey]

Loaded previously, now

[DM_Vecna]

Hello

I have been experiencing an issue with this compiler. When I compile my scripts I can see that it is finding any errors but when I launch the game none of the changes are effected. Even a simple debug line will fail to show up. It is looking at the old version before I adjusted anything in the toolset. Can any users see if they are getting a different result. Or if SkywingL or Virusman are available maybe they could look into this?

I am on Windows 7

Thanks

[virusman]

Try recompiling all scripts with Build Module.
_________________
In Soviet Russia, NWN plays you!

[DM_Vecna]

Thanks for the response Virusman. But maybe I'm missing something. That is how I always try to compile them.

After I lunch nwntx loader, I make changes then build the module with the compile scripts box checked. The. I save the module and close the toolset. Am I missing anything? I see the scripts being checked as I would with the default toolset but then no changes happen in game.

[virusman]

Are you using the latest version?
http://data.virusman.ru/nwn/nwntx-full-1.0.5.rar
_________________
In Soviet Russia, NWN plays you!

[DM_Vecna]

Thanks for the support. I am continuing to debug this issue. I am on the current build and I discovered I can get some other modules to build just not my player world. I will try to establish what is going on with that module.

There are some scripts that are not compiling due to errors. I will remove those first and see if it makes a difference. Other than that I am at a loss. I dont want to try and cut up my module to see what is causing the issue. But I will poke around.

[Sherincall]

Sorry for thread necromancy, not sure if there is a more active place to post this..

Anyway, small feature request - specify the module to be loaded through the command line. This way we could associate .mod files with the toolset loader. The original toolset has this feature already, so you could probably just forward the argument.

And thanks again, this is a handy little tool.
_________________
Shadows and Silver

[MercurioGenesis]

I have a functions script that just stores a group of functions. I accidentally included it in itself (#include "script_name"), thus creating a circular reference. An error was displayed, I clicked 'Ok', and then corrected the issue.

Now any script that points to that functions script will not compile and debug properly. I can type nonsense in and it will still compile successfully.

I have compiled the scripts individually, used the Build option, exported and re-imported the scripts, deleted and remade the script - the error persists.

Anyone know of a fix?

Edit : A bit of investigation later, and it appears that the NCS file is not being generated, for a spell script that references the 'broken' library, in //modules/temp0 after a build. This suggests there is a compilation error (somewhere!) but it is not being reported.

Edit 2 : Fix found. One of my structs had some comments at the end that were not closed with a */. Of all the things to go wrong...