n4gix
Resource contributor
- Messages
- 11,674
- Country

Let me extend my thanks to Lockheed-Martin for the huge improvement with the ContentErrorLog reporting!
Because of that, I finally managed to track down that elusive error ") " because the expansion to include the following x number of characters pin-pointed the precise location of the error!
Previously, all I had was just
Now I got this instead:
That made the error quickly 'searchable' since I had more to go on. 
Oh, and the cloud shadows and fantastic improvements with Autogen are simply indescribable!
Because of that, I finally managed to track down that elusive error ") " because the expansion to include the following x number of characters pin-pointed the precise location of the error!

Previously, all I had was just
Code:
") "
Code:
")
els{ (L:B737_Com1Stby_FRAC_TUNE,enum) }"

Oh, and the cloud shadows and fantastic improvements with Autogen are simply indescribable!

