Sign in to follow this  
Phil Chimbolo

Alpha v0.1.579 - Airport Scanning Stops at 80.08%

Recommended Posts

Just got the latest experimental version 0.1.579 and tried running the airport scan.    It scans speedily until it gets to EDDP or 80.08% where it just stops.   This doesn't freeze the application, nor does it impair my ability to use Chase Plane's camera presets or my camera movement axes.  However, once it stops there is no way to start the scan again because the progress is displayed and the clickable label to start the scan is no longer visible.

 

I've waited for 30-minutes to see if it would continue, but i never does.   I've run the scan  about 10-times and it ALWAYS stops at "80.08% - EDDP"

 

Anyway, let me know how else I can help to debug this.

 

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Hi Phil,


 


Many users are reporting this issue right now and we are looking into it.


Can you tell me the file described in the tooltip if you hover your mouse on the percentage and airport code?


 


Regards,


Keven


Share this post


Link to post
Share on other sites

Can you tell me the file described in the tooltip if you hover your mouse on the percentage and airport code?

 

Yes, sorry for the delay Keven.

 

The file is in the Aerosoft scenery folder, specifically:

 

Aerosoft\Afd\Scenery\EDDP_APP.bgl

 

You probably also knew that although ChasePlane doesn't crash, the CPU utilization continues to be between 20%-30% while stuck on this file... until I shut down the UI and restart it.

 

Cheers, and many thanks for this incredible product!

Share this post


Link to post
Share on other sites

Hi,

 

I got the same issue on some freeware airports. Is there any way to bypass them to complete the rest of airports, and generate the error list for debugging?

Share this post


Link to post
Share on other sites

Yeah i had same issue. if you hover the mouse over the running % it will tell you where the file is located. I deleted said file and then everything ran fine.

 

Offending file was an old FS9 MAIW scenery file.

Share this post


Link to post
Share on other sites

Offending file was an old FS9 MAIW scenery file.

 

Thanks for the clue, I will head my research in that direction!

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this