Resolved Fatal exception copying landing lights effects resource file

[pgde 571]

Simbol -- after running the update to 1.27, I am getting the following error: Fatal exception copying landing lights effects resource file: Object reference not set to an instance of an object and error 4567C, please contact support.

My Windows is full USA English. BTW, 1.25 worked perfectly!

 

 

Edited January 21, 2021 by pgde

[simbol 5,832]

11 hours ago, pgde said:

Simbol -- after running the update to 1.27, I am getting the following error: Fatal exception copying landing lights effects resource file: Object reference not set to an instance of an object and error 4567C, please contact support.

My Windows is full USA English. BTW, 1.25 worked perfectly!

 

 

Hi There,

I had reports with 1.25 and previous versions that the landing lights effect file was missing, so with 1.27 I added an extra check during copy operations with a custom error to tract this down.. so most likely with 1.25 you were having issues with landing lights but never saw the error. Now If you are getting this error it means AILRP is unable to copy an internal resource file to create the landing lights effects. 

Error 4567C is related to invalid license files, invalid product key or invalid activation code, so it is very posible your antivirus is blocking AILRP from copying the resource file and communicating with the license activation servers causing you these issues, please add all the executable's inside AILRP to your antivirus exclusion list and see if the error clears up.

If this fails send me a PM with your email so we can troubleshoot.

Regards,

S.

[simbol 5,832]

*Update*

Another user on FB reporting the same issue, I am working with him to debug what can be causing this.

S.

[simbol 5,832]

*Update*

Ok found the cause, Prepard3D.cfg file encoding is expected to be UCS-2-LE BOM and it appears when people are editing theirs manually using text files editors they are saving them back as ASCII or UTF-8. This caused an issue on my side.

I am now forced to detect the encoding of this file prior opening it since people are saving it using multiple tools and the original encoding format is getting lost..

This issue will be fixed shortly with version 1.28.

Regards,

Simbol

Edited January 22, 2021 by simbol

[kevinfirth 1,406]

1 hour ago, simbol said:

*Update*

Ok found the cause, Prepard3D.cfg file encoding is expected to be UCS-2-LE BOM and it appears when people are editing theirs manually using text files editors they are saving them back as ASCII or UTF-8. This caused an issue on my side.

I am now forced to detect the encoding of this file prior opening it since people are saving it using multiple tools and the original encoding format is getting lost..

This issue will be fixed shortly with version 1.28.

Regards,

Simbol

Amazing support from @simbol as usual 👍😄

[pgde 571]

Thanks Simbol -- just FYI I changed the encoding with Notepad++ and that was the problem. 1.27 loads fine now. Will update to 1.28 soon.

P.