I just tried your scenarios and it all worked for me, with a slight exception. If I choose to start on the runway, or if I chose cold and dark AND use auto start (CTRL+E default key binding), the flight plan would load itself into the FMS with no EXEC option needed.
During my testing, I accidentally started a flight with the default GPS direct routing selected in the world map planning screen. I decided to try this since I was loaded in anyway, and this did not appear to load a flight plan in and both the MFD and VFR map were absent any routing. If I pressed the FPLN button on the FMS, it did show the departing and arrival airports at the top already filled in, but I had to add the arrival airport as a DIRECT TO destination and execute to get the routing to show up.
So just to make sure weāre on the same page, you are selecting the IFR (either low or high altitude airways) option in the world map planning, and not leaving it at the default GPS direct or other setting?
Thanks. Yes, Iām selecting high-altitude IFR in the world map planning screen. If it helps, I can work on putting together a short video demonstrating the recurrence of the problem.
Ok, here is a demonstration of the problem for me (the problem being the flight plan not loading into the FMS). Attempt 1 was a success. Attempt 2 was a failure. Attempt 3 was a follow-up on the failure (experimenting with FMS in programming a route manually - had success in loading an approach into the FMS).
Attempt 1:
Attempt 2:
Attempt 3 (FMS experimentation):
Noting as a possible variable that I did not use real time - I adjusted the time to have daylight in the cockpit. Wonder if that (i.e. times) has something to do with it? Or the remoteness of the airport in Attempt 2?
For #1, initialize your position in the FMS before executing the flight plan. I think itās in the IDX menu. Set your FMS position to GNSS is I think the option. That way the plane will know where you are, then execute the flight plan. See what happens.
I donāt have time to get back into the sim to investigate, but I noticed something you may want to look into.
In the first example, I noticed when you selected IFR, it inserted all the waypoints into the flight plan while in the world map. In the second example, selecting IFR did not populate any waypoints, and treated it the same as a GPS direct route and the FMS functioned the same as it did for me when I used GPS direct.
I suspect a couple of things may be at play. I noticed you used two different departing and arrival airports in your two examples. Iām wondering if the second set of airports have a bug that doesnāt link them to the airways, or they are so remote that an acceptable airway doesnāt exist between them. It may be worth checking the navlog when re-trying your second example to see what your altitude profile looks like. Itās a somewhat short route and it would be interesting to see if your maximum altitude is set so high that you canāt reach it before itās time to descend.
Iām about to hop offline for the night, but my suggestion to you is to see if this problem only happens at specific airports or with specific routes. Try using the same departing airport as your second example, but a longer route to a different arrival and see if that changes anything. Also try the same airports as your second example, but manually add a waypoint in the world map so itās not a direct route. Basically we need to narrow this down to what specific situation(s) cause this issue, and then find out if itās a bug or functioning as intended for whatever reason.
If you want to try mine that worked, I was experimenting with KDTW (Detroit) to KATL (Atlanta).
Just to note this again, in none of your examples did you address the yellow message on the FMS to initialize your position. Thatās step one once you get the FMS on. Iām not a Collins Proline expert, but I have a suspicion thatās the common denominator.
Edit: Hereās my home-made, simple, āworks for meā checklist I use for the CJ4.
I donāt think this matters in the sim. I normally initialize as the first thing, then recall my plan from Simbrief, but in my testing above I just executed right away.
I think I have some insight now, if not fully figured it out. TL;DR I think this is expected behavior when there are no waypoints regardless of flight rules being used.
I tried re-creating your second example, CDK2 to CYJP and I got the same result as you. I did notice that in both our cases, when pressing EXEC, the flight plan is actually loading (You can see the āNo flight planā notice go away at 3:10 in your video). When loading a flight plan, itās common to not know the arrival runway and approach ahead of time in the sim. Real world may be different, but the way the sim works is you are assigned your arrival info when nearing the destination when flying IFR. When you enter a flight plan, the routing will show all known legs, but the CJ4 will now show discontinuities in many instances. These are times when you would get vectored by ATC either for departure or getting onto the arrival. When this happens, the discontinuity will show up as a missing path in the route on your MFD and VFR map.
So normally youāll see something like your flight path run from your departing runway, through all of your waypoints, then have a blank section, then a final small segment for the final approach. What is happening in your case (and I realize now when flying direct GPS) is that there are no waypoints to follow and the entire path is acting like a giant discontinuity. The aircraft knows where the two airports are, but not the runways youāll be using or the departure/arrival routes youāll take. If you look at your videos, youāll notice in the world map, the Canadian airports of the second example are listed as direct departure and arrival (essentially a GPS direct route), and the approach is listed as automatic. If you look at your first example with the larger airports, you are given specific departures and arrivals so the flight plan is able to plot a route most of the way. But even that example has a discontinuity that you can see as a gap between departure and the CFDCT waypoint. With a more developed plan, you can often simply delete the discontinuities and connect the two waypoints directly for autopilot to follow, but there are no waypoints to connect in your example #2.
When this happens and there is no flight path shown at all, what you can do is go to the FMS and press the FPLN button to bring up the active flight plan. Press the top right button next to DEST to copy that airport code into the scratch pad, then press the 4th button down on the right side next to the space below the TO entry on the screen. This will paste the destination airport as a VIA DIRECT route. Youāll still need to get final approach info from ATC when you get near, and then manually enter that into the arrival info of the FMS. Or you can manually enter the runways and departure/approach info in the world map if you donāt want to leave it up to ATC, but then you may have undesirable wind or other issues.
Only having the Origin and Destination is not a valid āmission statementā for this avionics set.
So indeed what you would do is, to copy the destination and put it in as a enroute fix.
Or in case you set an approach/arrival (attempt 3) you have to manage it in LEGS to get a fully connected flight plan.
I know I speculated on this, but I can now confirm from the tests I was doing last night that initializing position does not matter for purposes of loading the flight plan in the sim. It still may be a good idea to do this first for the sake of realism if thatās how the real aircraft functions, but itās not necessary.
While Iām here, does anyone know if thereās a bug preventing the ground power unit truck from connecting? I can call it (via ATC and Pushback Toolbar) and itāll get into position, but it wonāt connect. I also have the Woolemod mod, which I thought could be the problem, but it was recently updated to fix this. I updated my version, but still no ground power.
Iām having an issue with the throttles not working on first launch. Essentially I go into a new flight and no matter if itās a cold and dark start at the gate or fully operational on the runway, the throttles wonāt work when the engines are running.
I then quit back to the main menu and tried again and the throttle controls worked fine. Is anyone else having this issue where they need to reload in order to get the throttles to work?
So Iām on XBox and was just using my controller when I tested it instead of my throttle/joystick. I tried it again today with the same controller setup and it worked fine first try. Weird because it was the only plane I had an issue with. So for now I guess itās fixed.
So I read all 490 posts, but didnāt see this issue:
Several times ive tried to popout the FMC > window WT21_FMC1 ( Pilot or left side fmc)) the magnify glass with the x shows up but no popup ever happens. However, I can pop out the co-pilot (right) side FMC without issue. - WT21_FMC2
The problem is Air Manager overlay only powers the Left side #1 FMC. Am i missing something.
This is a brand new computer and has never had the older WT CJ4 ran on it, no mods, vanilla all the way.
All other popouts work as designed. NOTES: Not using DEV mode, the PC was built about a two weeks ago, so its all up to date. On my old PC I wasnt able to try the AUU1 CJ4 yet, so all I remember is from the old WT ver, witch the popout worked
BTW, really enjoying the new avionics! Thank you to all.
The avionics donāt have any knowledge of the pop out systemās existence and canāt control or affect it. That all happens within the sim.
Some folks get pop outs that come up off the screen, but Iām not sure what the solution to that is. Either way it wouldnāt be something that anything in the avionics code could fix.
Thanks! , i didnāt know that. so then Microsoft determines which panels popout? I can post that as a bug then.
However, to rule out user error i still would love to know if anyone else out here can recreate the issue before i post: see if you can popout the left pilot FMC data window in the CJ4.
Iāve read in multiple places that simbrief support was gone a few months ago. I just tried it for the first time today and the import worked fine, much to my surprise. Is this new functionality added back in? Or is it still going to be taken away?
