P3D 4.1 Errors after Upgrade

[bobuffs 0]

Hi, 

having just upgraded from v4 to v4.1, using the 'client only' approach, I am getting a 'content errors' log reported on sim closedown, irrespective of aircraft flown (addin or otherwise). The number of errors reported are circa 250, an extract is below, which is a selection of the type of errors.  This would have been greater but I have deinstalled both the Carenado Phenom 300 and DA24 which were reporting a great many duplicates in the aircraft config file.  I deinstalled these to see what the effect was.

Before I resort to a complete reinstall of P3D, which I am loath to do, has anyone experienced this, and if so, was there a simple fix?

Assistance greatly appreciated.....

[error.0]
error=Texture icon_airplane_blue.bmp failed to load (FE_REQUEST_STATUS==13)

[error.1]
error=Texture icon_airplane_green.bmp failed to load (FE_REQUEST_STATUS==13)

[error.2]
error=Texture icon_airplane_red.bmp failed to load (FE_REQUEST_STATUS==13)

[error.37]
error=Texture icon_scenery_green.bmp failed to load (FE_REQUEST_STATUS==13)

[error.38]
error=Texture icon_scenery_red.bmp failed to load (FE_REQUEST_STATUS==13)

[error.39]
error=Texture icon_scenery_yellow.bmp failed to load (FE_REQUEST_STATUS==13)

[error.60]
error=Error loading ".\RAASPRO\RAASPRO.dll." in "C:\ProgramData\Lockheed Martin\Prepar3D v4\DLL.xml."

[error.61]
error=Error loading ".\CMeteoXml.dll." in "C:\Users\Chris2\AppData\Roaming\Lockheed Martin\Prepar3D v4\DLL.xml."

[error.62]
error=Error loading ".\Carenavigraph.dll." in "C:\Users\Chris2\AppData\Roaming\Lockheed Martin\Prepar3D v4\DLL.xml."

[error.63]
error=Failed to load visual effect "fx_Aerosoft_Twot_engfire "

[error.64]
error=Failed to load visual effect "fx_Aerosoft_Twot_engsmoke "

[error.65]
error=Failed to load visual effect "fx_Aerosoft_Twot_engfire "

[error.223]
error=Gauge/Script Error
Type: Gauge
Name: GPS_530view2D
Error: Invalid script (command not found - perhaps a space is missing or there's an extra space?): "True" in: True

[error.224]
error=Gauge/Script Error
Type: Gauge
Name: TW_Sys2
Error: Invalid variable (missing : - did you forget a macro?): PROP BETA:1

[error.225]
error=Gauge/Script Error
Type: Gauge
Name: TW_Sys2
Error: Invalid variable (missing : - did you forget a macro?): PROP BETA:1

[error.229]
error=Key values exist outside of a section:
 File:C:\Program Files\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\Aerosoft_DHC6_300_WHEEL\sound\sound.cfg
 Key:This soundpack is produced by Turbine Sound Studios. Licenced to Aerosoft 2008.

[error.230]
error=Key values exist outside of a section:
 File:C:\Program Files\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\Aerosoft_DHC6_300_WHEEL\sound\sound.cfg
 Key:All files are copyrighted 2008.

[error.231]
error=Key values exist outside of a section:
 File:C:\Program Files\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\Aerosoft_DHC6_300_WHEEL\sound\sound.cfg
 Key:more info at www.turbinesoundstudios.com

[error.232]
error=Duplicate Section Name
File: C:\Program Files\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\Aerosoft_DHC6_300_WHEEL\sound\sound.cfg
Section: CENTER_TOUCHDOWN

[error.235]
error=Taxiway path with 0 width

[error.236]
error=Taxiway path with 0 width

[error.237]
error=Taxiway path with 0 width

[Bob Scott 7,714]

Did you go back to the new post-update Prepar3d.exe and set it to run as administrator?  Looks like there are a lot of file system permissions issues.

Regards

 

[vgbaron 3,486]

Disable content error reporting in the settings.

 

Vic

[bobuffs 0]

Hi, thanks!  I am in fact already running P3D as administrator....

With regard to disabling error reporting, reasonable suggestion....if you want to ignore errors:-)  But my concern is that there are a great many error reports and really these should not exist, or at least be understood and resolved where possible.

I would be guessing that most people do not have error reporting switched on(?), but anyone who does it would be appreciated if you could advise if you see similar.....

Thanks again....

Chris

[Nighthwk 566]

2 minutes ago, bobuffs said:

With regard to disabling error reporting, reasonable suggestion....if you want to ignore errors:-)  But my concern is that there are a great many error reports and really these should not exist, or at least be understood and resolved where possible.

They’re relatively normal, nearly everyone has them. Unless something reported has a negative impact on your experience, I wouldn’t worry about it.

[vgbaron 3,486]

The majority of the content errors are syntax errors - you could manually correct SOME of them but most need to be fixed by the developer. Since they cause no problems OTHER than generating a content error in P3D - many dev's won't take the time to correct.

Unless you have a system crash that you can attribute to a content error (a rarity) - turn off content error reporting or live with it.

Just as a FYI, last time I checked my error log had over 1200 errors - most of them relating to titles in gauge or xml files that didn't have a delimiter. They were ignored in prior versions but flagged in this.

Vic

[bobuffs 0]

Thanks both, that really answers my question - I shall fly happy again!