I have a few questions on toolset i was hoping someone can answer:
1) anyone know how to uncorrupt modules?
my machines had issues on end with toolset lately and suddenly now my one module wont open in toolset because it says the headers screwed up and i tried to load into a game and no it wont even light up play.
2) anyone know why a npc with a conversation set wouldnt launch the conversation when spoke to? i mean i have no conditional just point blank npc wont launch conversation in game.
3) anyone know why half of the time i have more then 1 responce for the player to pick from in a conversation file the game only displays the first option of what should be 4. once again i have no conditionals for the nodes set.
i mean i already repatched my game 3 times now with 1.69 and 2 & 3 are still occuring
Toolset Issues>
Débuté par
Ryuhi2000
, juin 28 2011 03:32
Retour en haut
#2
Posté 28 juin 2011 - 03:49
Omega27
-
- Members
- 198 messages
Are you using windows 7 for your toolset?
ive ran into this issue my self. Ive tried system restore, that work. Im not sure if this is just a Windows 7 function but:
I went to my modules folder in NWN directory, right click on the file, then click the option to "Restore to a Previous Version". that fixed the (1) problem for toolset.
the other two i cant really think on exactly why they are happening but i can look in to it for you.
ive ran into this issue my self. Ive tried system restore, that work. Im not sure if this is just a Windows 7 function but:
I went to my modules folder in NWN directory, right click on the file, then click the option to "Restore to a Previous Version". that fixed the (1) problem for toolset.
the other two i cant really think on exactly why they are happening but i can look in to it for you.
#3
Posté 28 juin 2011 - 03:58
Ryuhi2000
-
- Members
- 97 messages
technicaly its happening on 2 machines. one with win 7 home premium 64bit and on a machine with vista home premium 32bit.
i wouldnt mind it so much if it was just happening on the vista machine but its happening on both machines which is a bit of an issue.
ill try that restore to a previous version thing i totaly forgot about the shadow copies windows keeps
Edit: That was a fail there were no previous versions that it would find
i wouldnt mind it so much if it was just happening on the vista machine but its happening on both machines which is a bit of an issue.
ill try that restore to a previous version thing i totaly forgot about the shadow copies windows keeps
Edit: That was a fail there were no previous versions that it would find
Modifié par Ryuhi2000, 28 juin 2011 - 03:59 .
#4
Posté 28 juin 2011 - 01:55
Fester Pot
-
- Members
- 1 394 messages
1) Always, ALWAYS back your own work up and copy it to a directory outside of NWN. Unless you have a copy of the module from a previous time, you might be out of luck here. The only way I know to get around a corrupted module is to load it into the toolset and export each area, followed by creating a new module and importing all those areas. Since you can't even do that, your next method is to use one of your own backups.
2) This will happen when the NPC is doing something else, where the conversation will not fire or it is and being canceled before it can even begin. I suggest making an NPC COPY from one of the BioWare NPCs - one that is not in the hostile faction - place it in an area and change its conversation to yours. Then test it.
I'm guessing you have a script on the NPC that is causing the NPC to be doing something or cancel the conversation.
3) I suggest forcing the conversation node with the four selections and make sure it is always at the top of your conversation - so you know it's the one always firing - and then see if the selections are there.
As well, writing your own conversations will have no bearing on whether you've updated to 1.69 or not. New conversations are written and created by us, so any results that are unexpected are usually our doing.
FP!
2) This will happen when the NPC is doing something else, where the conversation will not fire or it is and being canceled before it can even begin. I suggest making an NPC COPY from one of the BioWare NPCs - one that is not in the hostile faction - place it in an area and change its conversation to yours. Then test it.
I'm guessing you have a script on the NPC that is causing the NPC to be doing something or cancel the conversation.
3) I suggest forcing the conversation node with the four selections and make sure it is always at the top of your conversation - so you know it's the one always firing - and then see if the selections are there.
As well, writing your own conversations will have no bearing on whether you've updated to 1.69 or not. New conversations are written and created by us, so any results that are unexpected are usually our doing.
FP!
Modifié par Fester Pot, 28 juin 2011 - 01:58 .
#5
Posté 28 juin 2011 - 06:12
Ryuhi2000
-
- Members
- 97 messages
1) yeah i did thank god find a older copy but i lost around 5 hours of work tho
2) ill have to dbl check into that since i think thats what i did but i changed the apperence of the npc nothingelse
3) ill have to try that
i just thought it was worth mentioning which patch i was on in case in was relevent. because it was number 4 but i was able to resolve number 4 with some help.
number 4 was randomly half of both the standard and custom pallete wouldnt paint in toolset. to fix i had to wipe my hak folder redownload cep 2.0 and then rerun the 1.69 patch and now my pallete works right again. what im guessing it was a conflict between cep 2 & cep 2.1. since the module i had that error was cep 2.0 and i had cep 2.1 installed as well as cep 2.0
2) ill have to dbl check into that since i think thats what i did but i changed the apperence of the npc nothingelse
3) ill have to try that
i just thought it was worth mentioning which patch i was on in case in was relevent. because it was number 4 but i was able to resolve number 4 with some help.
number 4 was randomly half of both the standard and custom pallete wouldnt paint in toolset. to fix i had to wipe my hak folder redownload cep 2.0 and then rerun the 1.69 patch and now my pallete works right again. what im guessing it was a conflict between cep 2 & cep 2.1. since the module i had that error was cep 2.0 and i had cep 2.1 installed as well as cep 2.0
Modifié par Ryuhi2000, 28 juin 2011 - 06:13 .
#6
Posté 30 juin 2011 - 06:02
CID-78
-
- Members
- 1 124 messages
5 hours is nothing if you get a corruption, trying to repair the file would take longer. you can allways run SVN or GIT as a backup system. aslong as you remember to check in your work you can allways go back and just pull individual files.
#7
Posté 30 juin 2011 - 11:59
Ryuhi2000
-
- Members
- 97 messages
yea i just lost like 5 areas and a ton of scripting but what are SVN and GIT?
#8
Posté 01 juillet 2011 - 06:25
CID-78
-
- Members
- 1 124 messages
they are subversion control systems, and they are both free. basically you check in your files into the system and it keep track of every change you do on each individual file and when you do them, it allow you to recover old files at any state during development. ie before you applied system X that wrecked the module. or because of a corruption.
#9
Posté 01 juillet 2011 - 09:50
Ryuhi2000
-
- Members
- 97 messages
intresting ill have to give those a try then
#10
Posté 01 juillet 2011 - 10:15
CID-78
-
- Members
- 1 124 messages
I would recommed Tourtoise Windows SVN Client, it give you a good GUI and is plugged straight into your explorer. easy for those that don't want to deal with console lines. but there is several other that do the same thing. This is the one i have used during many years of development both proffesional and for my hobby projects.
