XXX.pdt files

[skir4d]

This has probably been brought up before, but as I was creating a chart of which parameter in the supplied editor was in each line of the XXX.pdt file when opened with a simple text editor (Context) I noticed the following.

If I opened a provided XXX.pdt (in this case Cape George) the fourth line in the text editor was the Secondary Fire Values, specifically range, fire, and reload in that order. Three values only (no sign of the hit modifier). The line above the fourth line in the text editor was 0.01 0.01 which, by the end of my charting, had no corollary in the supplied parameter editor.

While searching for the hit modifier in the text editor, I changed it in the supplied parameter editor and searched for that value in the text editor. Well, the third line disappeared (no more 0.01 0.01 in that location) and the hit modifier was now at the end of the original 4th line (which was now the third line in the text editor)

Also, the first line in the test editor incremented from 14 to 16 when this was done. This behavior was duplicated in a test file made from the early.pdt.

I did find all of the values in the supplied parameter editor in the text version, however the first line in the text editor does not seem to appear in the parameter editor. Once I neaten it up if anyone is interested I'll be glad to share it. Next up is to create a chart for the xxx.scn file unless someone has already done that.

[GMcClellan]

I have to step out so can't get into all the guts at the moment, but the *first* line is the pdt version. As we've developed the NC engine, the format and included information has been updated, and so some pdt reflect that. Thus, the change from 14 to 16.

[skir4d]

Okay, that makes sense. The other changes are most likely due to the changes in the NC engine, and I only bring it up to inform. Thanks for the response.

Jack W