Anyone have any workarounds for the WT FMS power up issues where you just get a ‘/’ appearing. I’m finding that 50% of the time I load in a flight (when I’m in a hurry) starting on the runway & ‘ready for takeoff’, the WT FMS starts up in this state and I haven’t found a way around it other than quitting the flight and starting the whole process from scratch. ie a 'restart on same flight still leaves it in the ‘/’ state. Cycling the preset ‘states’ in the EFB does not bring it back to life and I don’t know of any power or reboot switch to restart the FMS with. It’s a real pain. Interestingly the flightplan is still usable by the AP, but it is unviewable / uneditable when you can’t see it in the FMS. Anyone found a way around this?
In this mode, you can also click on the DIR key in the FMS and get the message “Untitled”. A clue?
Side note but similar: There is definitely some inconsistency with starting the 146 in this "ready for take off’ & on the runway mode as sometimes the 146 spawns on the runway with its engines turned off too and then subsequently goes through a lengthy engine spool up. Other times it spawns as expected with all engines ready to take off with. Why the inconsistency?
It’s a bit frustrating for me as I don’t always have the extra time to start cold at gate and just want to do a quick flight. I’ve done this a lot recently while checking out the new release and FMS for example.
EDIT: I’m about to test out the same but with the GNS530 the GTN750 and the WT C4J mods removed from community to see if it makes a difference.
UPDATE: Seems like this is related to those mods. Removed them from community and FMS boots up fine on 10 successive loads. Not sure which one is causing the issue, but worth removing each of if you have them.
I’ll check but I suspect that’s outside of our control. For the co-pilots, all we do is specify the location for them to spawn and the simulator handles the rest. I’m not sure why there’d be a difference in behaviour between VR and non-VR mode.
Martyn - Just Flight
1 Like
What I have notice is Toggle Afterburner nor Set ELT button assignment are no longer holding sync mode with target altitude set. Plane just levels off in both configuration (afterburner used to work on my Bravo), anyone else?
And that’s with the replacement WASM gauge that l linked to above?
Martyn - Just Flight
Hi, sorry I didn’t associate that with my issue, yes it’s fixed it. Many thanks 
1 Like
It’s interesting seeing who uses the FMS and who uses vor, ive used the fms a handful of times, brilliant for flights when you are busy but for me, almost 97% of the time I use vor…
How about you guys
1 Like
I’m trying to go the other way but I’m new to SID’s & STAR’s, I seem to get discontinuity or miss the turn etc. happens with MS FP and Simbrief, thing is I’m not sure if it me or inherent in the transfer of FP
You do have to check for and remove discontinuities in the flightplan in the FMS. Of course I forgot to check for them this morning on one flight and when it encountered one the aircraft seems (for me at least) end up just circling around, with AP light off and unresposive to manual HDG mode. I actually had to toggle AP off (even though AP light was already ‘off’) then re-engage it for it to start responding again to manual AP/HDG inputs again.
I do use VOR’s with the 146, but mainly for DME measurements, but use FMC most of the time for NAV. I tend to reserve VOR navigation manly for the JF Arrows/Warrior. The 146 is a great aircraft for doing VOR navigation in though. Just not what I spend most of my time doing with airliners.
Just noticed speed brake doesn’t do anything. Looked outside and it isn’t open even though the lever is to the max. Anyone else?
Try it again. I thought I saw this a couple of times but wasn’t sure. It won’t come on at max throttle/overspeed situation, so reduce throttle to 3/4 and then engage speedbrake. It works for me after that.
Are there some requirements for the Copilot Callouts? Callouts in the EFB are activated, but no callouts for V1, Rotate, Localiser captured … 
You have a mod installed I will bet 100% that is causing this. Also update the to the latest WT CJ4
Ahh. I’m using a FedEx livery. Think that’s a mod. Thanks for info
Feel bad for the gamer I just pulled along side of at EGLC, went to turn around and if you didn’t know any aircraft of your type that are within a given distance enter the same state! Asobo need to fix this.
ARe you on the ground? Do you have hydraulic power? What state is the AC in when you looked?
Not sure they are gating items, but TMS to T/O config and flaps at 18 for takeoff usually prompts speed callouts for me. I’m usually using the FMS for a flightplan, but not sure that that impacts callouts.
I usually keep climbing at flaps 18 until the initial climb tops out and I get a speed call to retract flaps.
The next call is usually only after enabling localiser(V/L) ahead of capture and enabling g/s ahead of glideslope capture. The calls about flaps on approach/final are usually made if you slow down enough for the call to be made. If you engage flaps ahead of time the call won’t happen.
1 Like
No mods whatsoever. As mentioned all other planes are fine. No worries, and no need for more guesses, I will figure it out myself. Thanks everyone. 
They happen in most FMS’s that I’ve encountered. CRJ, A320NX, 737, WT FMS. You just have to watch out for them when you first load in, go check your fligthplan in the FMS, deal wth them (either copy & paste next waypoints over them or delete them. They are just boundary points say between the start or end of the main flight plan and the SID and STAR. all you are effectively doign is joining the broken flight path up so the FMS knows to go from SID to start of main flightplan to start of STAR/approach in one cntinuous path/route.
Sometimes they are present and other times not. They are very easy to deal with though, and should be removed prior to takeoff. or if not then prior to encoutering them while flying the flightplan. Always page through your flightplan to review it for these and make sure it all makes sense.
Have you monitored your resources? ie RAM/VRAM/CPU to see what’s maxing out when using it.
