Thanks for stepping in and confirming that function issue … I thought I was beginning to have some sort of corrupted toolset/game. It was one of about five issues that hit me in a single testing of my campaign.
Here is what happened … Started when I went to test mega-area after being broken into three parts …
- Could not place waypoints in area. (Baked once. Sorted.)
- Deleted old trigger, but could not pace new ones. (Had to bake again. Sorted.)
- Could not place creatures. (Baked again. Sorted.)
- Placed creatures not responding correctly or crashed game in testing. (Maybe due to low CR PCs.)
- Placed creatures not returning combat and summoning creatures even though function should not.
- Boost XP on PCs. (Function failed to work as expected. You just confirmed.)
- Work with boosted PCs, but 1st level rogue failed to level when recommend pressed. (Crashed.)(*)
- Panic set in, made the forum post.
(*) I guess we would not normally notice this issue as you would not normally press “recommend” if you just created a rogue (at first level). It was only because I used that button to quickly level all the PCs (after gaining XP) that I noticed it. It was not a problem for any of the other classes I was testing with. The game crashes when I was using “Barran” (who had just had his levels reset to zero and I was leveling again with new XP) and with the default XML scripts. i.e. My XML was not the issue.
After posting …
- Reloaded, rebaked all new areas, and the area object placements appeared to settle down/work.
- Boosted PCs XP appeared to start some AI in creatures correctly, but still not one.
- Edited an XML to bypass the “recommend” button at first level PCs (although it is just the rogue class at first level that sometimes crashes it), so I did not click it by accident and crash the game.
I am still working on … RWS Living Portal issues …
- It simply stops fighting.
- It somehow summons a creature even though it does not meet the criteria in its setup.
I am not sure how the Living Portal works as it appears to have some properties that I have not set, and also ignore some properties I am setting instead. I don’t know enough about new creature models to understand how they work or are expected to work to deal with this. For instance, I am trying to give it the ability to cast a magic missile, and it does not do so. I cannot understand why.
And then there were the normal issues, which I managed to overcome once I came out of panic mode …
EDIT: Or maybe not … (I shut down and restarted the toolset and it did not crash the second time around.)
I have contacted the makers of my SSD as I think there are some problems outside of the toolset going on here now … Programs not thinking they have been updated … copy and paste not working as expected … just general weirdness all round. E.g. I updated the SSD test program two days ago, and went to run the test again today, and it asked to be updated again. Same update! As if the update had never taken place! This appears to be similar to issues with my toolset. i.e. I do something, and then have to repeat what I just did for it to work again. (NB: I did NOT do any system restores.)
I may have to put any toolset work on hold until I sort this out, which may mean a new SSD … new system install … new NWN 2 install … I grow pale at the thought …
New SSD ordered … as I believe my SSD (being four years old) was outside its warranty and likely reached its natural end of write life! As an aside, their test software reported 2% on its “life usage”, but this means it only has 2% left, and will switch to “read only” soon.
Apparently that has a better TBW value of 600 (compared to 120 of Crucial - my current one), so should last a lot longer before write fails in future. (The price is actually £129 at the moment.)
EDIT: I am editing this post to help highlight my SSD issue that may be relevant to other owners of SSD drives out there, and modding with the toolset. I have had my SSD for around four years now, and have not had any issues until the last week or so. My point is, (and also as a reminder to myself), these hard drives have a limited number of writes in their lifetime. If your SSD is three years old or more and has a low TBW rate, then beware that when using the toolset, you may also eventually have write problems that can cause some bizarre errors.