Can anyone comment on how fast it is to test out changes in-game with this toolset? Specifically I'm talking about things like changes to the terrain, objects, conversations, scripts, etc. I guess the main concern I have is having to slog through a bunch of loading screens and ads just to test out some changes. Probably an unfounded concern, but I thought I'd throw it out there anyway.
Testing and Iteration?
Débuté par
Minejumper
, nov. 02 2009 05:04
#1
Posté 02 novembre 2009 - 05:04
#2
Posté 02 novembre 2009 - 06:39
Being able to turn off the obligatory dozen start-up videos is a valid concern.
#3
Posté 02 novembre 2009 - 06:44
As I recall it, for NWN and NWN 2 you could use the Test Module function to open up NWN and go straight to the game with a one of the premade characters. I'd imagine it'll work similarly here.
#4
Posté 02 novembre 2009 - 12:16
You don't need to restart the game each time you make changes, just reload your module after you have updated it in the toolset. You even can select a (temporary) spawn position and area for that export to quickly spawn at the desired location in game. (I hope I'm allowed to say this, but this information should be somewhere in the wiki anyway)
#5
Posté 02 novembre 2009 - 02:02
Depends on the changes - you can see the effect of changes to some things without actually running the game at all. Cutscenes can be previewed in the toolset for instance.
#6
Posté 02 novembre 2009 - 06:15
Yep. Other things might not be so practical to test each time you make a change because they are very intensive to generate (e.g. lightmaps depending on the layout).





Retour en haut






