Forum:DLG Editor Issue (Solved)

Pecoes,

I have been recently having trouble with the DLG Editor application - the one adapted for Jade Empire. For some reason I cannot see (a bug? a glitch?) there are times when I simply cannot edit *any* new PC reply / dialog line. After I succesfully add a dialog.tlk entry with the tlk editor, the DLG application refuses to identify it, and leaves the dialog box empty, in spite of the added .tlk number. Just the PC's replies though, the standard/"red" entries identify their dialog.tlk counterparts correctly and edit as they should.

Strangely enough, this affects only the newly created entries. If I edit a pre-existing PC line, the glitch does not happen. I can only do this once per entry however, as the second time the application treats it just as it does with the rest of the "new" ones.

I have tried installing, running as administrator, etc, to no avail.

Ideas? Suggestions? It's frustrating to have to open and close the Editor a hundred times until you hit a session without this... glitch, or whatever it is.

Thank you.

Qvaestor 23:10, December 30, 2011 (UTC)Qvaestor

Have you tried manually loading the new version of the TLK? I haven't tested that excessively, but it seems to work...

While we're at it, a few other tips:
 * 1) Always turn "Automatically apply changes" off! That tends to create bloat and logical errors.
 * 2) Work only additively! Neither cutting nor deleting work.
 * 3) Last not least: Make very frequent backups and save them under different names!
 * 4) Sometimes it's easier to use K-GFF instead of the DLG Editor. Yes, editing DLGs with K-GFF is tedious, but it usually beats starting all over.

--Pecoes 01:21, December 31, 2011 (UTC)

Ah, apparently the problem originated from a combination between not having the "Automatically apply changes" settings turned off and that the program does not recognize the default "(none)" value in the speaker/receiver drop-down menus, despite what it says. One has to manually drop-down and (re)select that value for the changes to apply succesfully.

That was the reason why the problem only occured on PC replies in the first place. Because that was the time when I thought that the default "(none)" was enough.

Thank you for your help.

Qvaestor 02:07, January 1, 2012 (UTC)Qvaestor