OnCourse Software

Hello Dave and everyone. I filed this flightplan, using AIRAC 2402:

KIAH BNDTO CRGER EWM J4 WLVRN ESTWD HLYWD KLAX

KIAH scenery is FSDT, KLAX is default MSFS. It's the first time in MSFS I fly to anywhere in California. However, after starting the flight and connecting PF3, it takes up to 5 minutes until it's finally connected. Also, after requesting clearance, it's another 5 minutes until I hear my F/O requesting it, and 5 more minutes until I receive it.

I restarted my computer, regenerated PF3 database (I dread doing so, because it takes up to 30 minutes), but PF3 is still sluggish. I pushed on, after switching to Ground (from Clearance), everything went back to normal.

This didn't happen to me last flight (LIMC-KIAH, which went uneventfully), and I don't remember having this problem since I got PF3 (back in 2017). How can I fix this?

I'm attaching the whole Logs folder, just in case. Before my second attempt, I wiped it out, so it's all fresh. I couldn't finish my flight because of real world issues; that's why it may appear incomplete.

So is the included log from a flight where you actually had this problem?

Yes, it's from this flight. I didn't finish it, although.

Edit: I deleted and redownloaded the flight plan from Simbrief, and didn't get the clearance delay this time. Strange... Can a corrupted flightplan have these effects?

It looks like the problem was with PF3 trying to connect to the online weather station and it was failing... hence the wait time... but the wait time wasn't 5 minutes it was 1.5 minutes.

However, if you now say it's working okay it must be due to the connectivity issue has now been cleared.

Thanks for your reply! That makes sense, and redownloading the flightplan was just a coincidence.

So, in case that happens again, restarting PF3 and starting a flightplan without online weather in PF3 could be a workaround?

No you really don't want to be flying with no live weather because PF3 can't detect any weather/winds except that directly around you. I would say check you internet connection and see if that's okay and if so restart PF3. I'm only guessing though as I've never come across this issue before