Strange Error Messages in ContentErrorLog.txt

[n4gix]

I managed to clear up all of the non-gauge errors in P3D v2.1 that had to do with duplicate entries in various aircraft.cfg files, et cetera...

...except for these that are reported in two custom .fx files:

[error.0]
error=Key values exist outside of a section: 
 File:C:\Lockheed Martin\Prepar3D v2\EFFECTS\milvizc310_taxibloom_01.FX
 Key:[Library Effect]
[error.1]
error=Key values exist outside of a section: 
 File:C:\Lockheed Martin\Prepar3D v2\EFFECTS\milvizc310_taxibloom_01.FX
 Key:Lifetime
[error.2]
error=Key values exist outside of a section: 
 File:C:\Lockheed Martin\Prepar3D v2\EFFECTS\milvizc310_taxibloom_01.FX
 Key:Version
[error.3]
error=Key values exist outside of a section: 
 File:C:\Lockheed Martin\Prepar3D v2\EFFECTS\milvizc310_taxibloom_01.FX
 Key:Radius
[error.4]
error=Key values exist outside of a section: 
 File:C:\Lockheed Martin\Prepar3D v2\EFFECTS\milvizc310_taxibloom_01.FX
 Key:Priority
[error.5]
error=Key values exist outside of a section: 
 File:C:\Lockheed Martin\Prepar3D v2\EFFECTS\milviz_taxibloom_01.FX
 Key:[Library Effect]
[error.6]
error=Key values exist outside of a section: 
 File:C:\Lockheed Martin\Prepar3D v2\EFFECTS\milviz_taxibloom_01.FX
 Key:Lifetime
[error.7]
error=Key values exist outside of a section: 
 File:C:\Lockheed Martin\Prepar3D v2\EFFECTS\milviz_taxibloom_01.FX
 Key:Version
[error.8]
error=Key values exist outside of a section: 
 File:C:\Lockheed Martin\Prepar3D v2\EFFECTS\milviz_taxibloom_01.FX
 Key:Radius
[error.9]
error=Key values exist outside of a section: 
 File:C:\Lockheed Martin\Prepar3D v2\EFFECTS\milviz_taxibloom_01.FX
 Key:Priority

I've looked at these two custom .fx files until my eyes were crossed, but I'll be darned if I can fine any errors at all!

What is even stranger, when I substituted contents of the _02.FX versions in the _01.FX versions, it made not one whit of difference! The 'so-called errors' are still listed...

...even though the _02.FX versions are now identical to the _01.FX versions, but they are not shown as "errors!" How strange is that?

I just thought it would be prudent to get all the non-gauge errors cleared up before beginning to find the XML gauge errors, one gauge at a time!

 

[mariomotta]

Hi,
i have also a non-gauge errors like this:

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

and this:

[error.37]
error=Gauge: cronograph
Error: Invalid unit specified: "number)".

The first one seems coming from a non-gauge that however uses xml, what could be ?
May be a module using embedded xml code ?
Or may be a .mdl file ?
The second one more mysterious since the XML code triggering the error works correctly and seems to be
syntax-corrected as well:

0 (>L:CLOCK_LAP,number)

Any cue ?

 

[n4gix]

For the first, search your modeldef.xml file for " els " (with a blank space before and after!). If you find one, it is probably caused by an extraneous blank space such as "els {"...

For the second, try substituting "enum" for "number". If that doesn't work, change the > symbol to & gt; (without the space of course)...

 

[mariomotta]

Tanks Bill,
the first one was an error of mine: (L:CLOCK_LAP, number))
for the second, now I've lost my eyes but I can not find a misspelled els{ or {
in the modeldef.
Futhermore the error count stops to 999 meaning (as in compiler language) they are far more, but all the same:
Error: Invalid script (command not found - perhaps a space is missing or there's an extra space?): "els"
Error: Invalid script (command not found - perhaps a space is missing or there's an extra space?): "{"
Does the error log does not recognize multiple errors and logs each time the code is run ? (i guess yes)
/Mario
BTW:
have you tried P3D v. 2.1, did you experienced slow texture loading and huge blurries ?
2.0 was really sharp, while 2.1 takes several seconds to load internal VC textures even with medium/low settings.
My rig:
I7 3770 K at 4.6 Ghz
16 GB
Nvidia 660 Ti
SSD Samsung