P3D v2 Using the ContentErrorLog.txt to Debug XML Syntax Errors

[n4gix]

Using the new "ContentErrorLogging" feature of P3Dv2.1 has been an adventure. Using it, I've finally managed to clear up all of the modeldef.xml errors (there were only two, and both trivial: 50* instead of 50 *), as well as some missing textures (fresnel_ramp.bmp & another custom .dds Fresnel bitmap).

I've also cleared up the most critical errors in my custom FBS_GNS530_1.xml "gauge", to the point that it now works 99.9%. There is one "error" I simply cannot fathom though.

Understand one thing though, the ContentErrorLog.txt contains snippets of "unraveled script," meaning that all @Macros have been expanded. This makes searching for the specific script being bitched about "more challenging..."

I have two remaining "errors" which have got me stumped:

[error.10]
error=Gauge: FBS_GNS530_1 
Error: Invalid script (command not found - perhaps a space is missing or there's an extra space?): "True"

[error.11]
error=Gauge: FBS_GNS530_1 
Error: Invalid script (no command is more than 4 characters): "@kNavPageGroup (>C:fs9gps:1:currentGroup) 
  (C:fs9gps:currentGroup) 4 == (C:fs9gps:group4currentPage) 0 == && if{  3 (>C:fs9

The only place where this bit of script is to be found is identical to that used in the gps_500.xml gauge!

Oh, and here was a charming one to find:

[error.10]
error=Gauge: FBS_GTX330
Error: Invalid script (command not found - perhaps a space is missing or there's an extra space?): "if"

Not too much to go on there! But, searching for "if " (with a blank space after) found this silly mistake...
if { 1 (>L:bt0,bool) }