I thought this was done away with and fixed in the last version but seems that it’s back after the anniversary update. The only mods I’m using are FSTL and Concorde. Retried multiple times, rebooted etc but still it seems to discard my flight plan after take off.
It always feels like 2 steps forward but 3 steps back with MSFS recently. After £120 and 300GB of storage, I’m beginning to wonder whether it’s all worth it? I’m prepared for the trolling and passive-aggressive comments but I don’t feel the enjoyment in a 5-10 min starting process, then what feels like reporting an never ending list of re-occuring bugs for Asobo at my expense everytime I boot up. My patience and mental health is at breaking point now and I feel it may be best to cut my financial losses, uninstall and learn my lesson. All that freed up space could be used to install games I’ve not had the chance to play yet.
I’m exausted.
I’m not sure what your issue is?
What was done away with and is back?
2 Likes
If the concern is that the player can’t request a pop-up IFR clearance from either cold & dark or while enroute - at any time - well, I personally would not have expected this to get fixed before Working Title fixes the Flight Planning logic in the sim, and even then, they’d still have to revamp the ATC logic after that. The best solution is to load the plan at the World Planner for now.
1 Like
That’s exactly what I did and keep doing. But as soon as you take off, the ATC window shows this command as an option indicating your flightplan has in fact been scrubbed. It’s been working fine for the last 6-8 weeks.
Are you creating it in some utility then importing into the sim?
I didn’t create it but someone sent it to me. Accurate Concorde flightplans that used the same waypoints etc. I think they downloaded them from somewhere.
I’d load that first into something like Little Nav Map and check the characteristics, make sure nothing’s funky. Then re export as a PLN file.
I genuinley appreciate your help, I really do but I’m not familiar with that app and cba downloading even more software to spend even more time checking out files that were working fine for a month or so prior to the update the other day. Im not enjoying the game anymore as i spend that much time doing this type of thing already.
I’m just exausted and needed to vent. Sorry.
No problem. If you feel like it, upload one of them to this thread. No guarantees I can do anything but I’m curious to see this plan now.
Here you go.
EGLL KJFK Concorde.pln (6.9 KB)
So - I took it apart in Little Nav Map. Other than it’s missing a Start Position, the route calculated okay
What I did is I tried to define a Start Position inside Little Nav Map - picking one of the locations at EGLL. Nothing doing - it insisted on starting at RWY09, which is definitely not a good test case. It also specified a SID and a STAR - not really a concern to what we’re troubleshooting.
So I zoomed into the Map after loading the plan and picked an existing ramp location. That cleared the SID and made it a Direct. Again, not a big deal. Plan accepted - hit Fly.
I just used the Default Longitude since I wanted to see what would happen after I took down ATIS and contacted Clearance Delivery. It seemed to accept the plan okay - note the radio prompts. There’s no Retry IFR or Request Clearance for IFR. Had the jet been ready to go, I’m at the point where I could request pushback and taxi.
Is this your experience or something different? Note the sequence of steps above which may differ from yours - and that might be the answer to why you’re still getting the prompts?
1 Like
Thank you for taking the time to examine that further on my behalf. Yes, I do find it puts you on Rwy 09 automatically. My proceedure is, I have to load the plight plan into the world map. Then I zoom into Heathrow and change the start point to Gate 40 which was Concorde’s gate (I think). I then select a departure pattern which gives me the smoothest route out of the area without any sharp turns.
As for the destination at New York, I choose a direct approach only to ILS RWY 31R which I was told on here was accurate again, due to Concorde not coping with sharp turns at low speeds.
Other than the massive frame drops at touchdown and therefore the inputs for the reversers not registering (which I suspect is an FSTL issue), it’s always worked fine and guides me to the same arrivals gate. I can’t remember the number.
Since the update however, I’ve tried both my normal method as mentioned here and just simply starting from RWY 09 and in both cases I get the same result. I tried both methods multiple times too. The worst thing is, in the months past when I first came across this, when I’ve selected the IFR clearence option, I discover it messes up your altitude callout iinstructions from ATC both on the ascent and decent.
So whenever that message pops up, that’s when I know there’s a problem.
Might be worth mentioning it to Dean and see if he knows of any workarounds. I don’t have the Concorde, so I can’t identically try what you’re doing. I wonder if picking a Direct Departure instead of a SID might work, since that seems to be the only thing you and I are doing differently.
I’ve done direct departures also today with the same result I’m sure but I’ll double check in the morning and get back to you.
1 Like
I have reproduced this issue on the A310 and A320neo, so I do think it’s a more general bug. This is just using the world planner for IFR navigation. I am on Xbox Series X.
I’ll have to take screenshots and investigate more to help narrow it down, but it does look like ATC will sometimes drop the IFR plan and require to resubmit it en route. This started in SU11 beta for me and carried over into the final SU11 release.
1 Like
Yes, it still happens with a direct departure. And in the past it has happened with other planes at other airports.
