BluesmanEP

Well, maybe version 1.3.1 fixed this, because I'm no longer having the issue also. In previous version it happened at every airport, every time I started the sim. Glad to see it's been fixed, even if accidentally! Thanks.

I managed to get a bad resolution video of the issue - unfortunately you can't see the mouse which would be helpful. The first video shows a (very bad, sorry!) landing with ATS engaged. It goes to FAIL after landing, and you can see the red boxes start to flash. After this point I have no hardware control of the throttle levers, although the mouse works perfectly well. If I disable ATS before landing and use manual throttles there are no issues. After turning off the runway, I park and move throttle 1 with my mouse. Then I shut the engine down and you can see the lever moving on it's own. All this was done with the mouse, hardware throttles are still unresponsive. The second video is parked with both engines off. Using the mouse I move the levers from cutoff to idle and you can see them move by themselves. I also noticed that the levers move by themselves when the plane is completely powered down - all screens dark, no APU or GPU and no Main Battery. I don't have a video, but it's the same behavior. The levers move by themselves when the throttle is moved out of cutoff. Note, this only happens after a landing. When I first load the plane, prep, taxi, takeoff etc. there are no issues at all. Thanks!

I'll see what I can do tonight - thanks!

Some more info: On the ground with the engines off (after finishing a flight) I can manually move the throttles to the cutoff position. Using the mouse if I move them to the idle position, the levers slowly creep up to full, regardless of what my hardware throttle is doing. This happens even if my bravo is unplugged. The move is slow, about the same rate at the takeoff throttle up when ATS is engaged. Is it possible the ATS system isn't getting disengaged, even when it appears to be? Not sure what else could be going on, since it happens even with my hardware unplugged, I don't think that's it.

I am having a similar issue after landing. If I land with ATS engaged, I can't get manual control of the throttle levers. The graphic shows in the bottom right side, with the blinking position box at the top and the ATS box at the bottom. I know my hardware is working, and the levers show correctly in the joystick setup page. The ATS system is disabled. If I turn it on, the throttles move up, but they stay stuck wherever they are when ATS is turned off. But the 'position' of my throttle levers seems to be stuck at 100%. I can move them with the mouse, but it's doesn't change anything regarding the out-of-sync ATS and manual positions. I'm using a honeycomb bravo if this helps.

I've been leaving the front gear bay door open after putting the pin in when leaving the aircraft. When I next load the sim and walk to the plane the door is always closed. As soon as I power on the main battery (doing nothing else) the door opens. It seems like the position of the door isn't restored until the plane has power. Bug or expected? Thanks!

Woah, ok great. I'll try that tonight. I've been using xCamera since it was released and never had this issue before in any plane. Hopefully this will work. Thanks!

Hi All, Firstly, yes I'm using xCamera and TrackIR, but I'm very careful to disable xCamera before using any of the walk-around features. Once I'm sitting in the seat I turn xCamera on. However, maybe 1 out of 3 times I disable xCamera I lose all 2D elements on the screen - all popup panels, checklist hints, the phone screen, any of the study windows, and even the clipboard in the FBO. I'm also unable to access the Challenger settings window. Popup windows still pop up, but they're entirely blank. Also, any popup windows generated by another plugin unrelated to the Challenger are also blank. Finally any elements drawn to the screen using FlyWithLua are also gone. All the cockpit manipulators are still there, and clicking on the MFD screen (for example) still works. But nothing shows up on the screen. It's like all screen drawing thats not in the actual 3D model isn't happening. Any ideas? I'd really hate to have to give up trackIR for this plane, and I've never had this happen with any other XP addons. Thanks! Log.txt

This livery was just posted today on the .org forum. Not sure if I can post a link there, but a quick search will find it.

Haha that makes sense I'm comfortable flying manually calculating ToD and managing my own crossing restrictions, I just didn't think that's what you were 'supposed to do'. So from cruise, I should just set a new altitude on the dash, and use FLC / VS to descend - not worrying about re-programming the FMS at all? I assume as I get closer to the airport the FMS and my manual descent will 'sync' up again, once I pass the FMS calculated (but wrong) ToD point. Thanks for your help!

so it seems that you can only edit the descent parameters while the descent mode is active. Once I reached the calculated ToD, I was able to change speeds etc. That makes it all the more confusing to me. I guess my general questions is, how do I setup an 'ad-hoc STAR'? When flying a real STAR the FMS knows that the ToD point is actually quite far from the airport, and there may or may not be various level-off points along the way. Once in descent mode, you're able to edit the descent parameters, and add / delete crossing restrictions etc. However, if my first required altitude is at the IAF of an ILS approach (say 3500') and I'm cruising at FL200, I may be given by ATC several "descend and maintain", or "cross XXX at 8000" commands. The calculated ToD point is such that I fly a straight descent to 3500'. It seems the FMS isn't happy when flying below cruise altitude before the ToD point. So my question is, how to I fly these step-down legs? Do I just keep setting a new, lower cruise altitude in the FMS? If I do that I always get a 1000 fpm descent rate, but no guidance on when to start that descent to cross a fix at a specified altitude. Is there any way to set a crossing altitude restriction, and have the FMS calculate the ToD to reach that point, even if the FMS isn't yet in 'descent mode'? Does this make any sense? haha... I'm very solid on flying a route with a SID and a STAR, but I seem to be having trouble understanding how the FMS wants to fly a route in a more manually managed descent mode. Thanks!

That worked great, thanks! It did bring up a few more questions though I think the problem I was having with the ToD point is that I was flying a route without a STAR, so the calculated ToD was actually pretty close to the airport. By getting the "cross XXX at 15000" I basically wanted to start the descent at a point to capture that as a crossing restriction, not a new cruise altitude. Is there a way to have the FMS go into 'descent' mode on command? Rather than waiting for the calculated point? Also, on the CRZ and DES page, I think I should be able to specify a cruise speed (the TGT SPD box), but I can only enter mach numbers, I can't enter a value in knots. Additionally on the DES page, if I want to enter a new descent speed I enter /270 and click TGT SPD. I get an EXEC prompt, but the entered value doesn't show up. It's still the value it was previously. The top of the DES page shows "280kt PATH DES 1", even though I entered a restriction of 270 knots. I assume I'm doing something wrong... but can't figure out what. Thanks!!!!

Don't disable Windows Defender!! Probably not a good idea to run without it... All you need to do is make an exception for your X-plane folder. Open windows defender, click settings. Scroll down to 'Add an Exclusion', and click 'Exclude a folder'. Navigate to your entire X-plane folder and click ok. You should be good to go! I had the same problem with the EXEC button until excluding the XP folder. I'm happily running windows defender on the rest of my system.

Perfect! I'll give it a try tomorrow. Thanks! Sent from my iPhone using Tapatalk

Hello! I recently ran into an issue while flying online. I was at cruise FL200 and got a cross XXX waypoint and maintain 15,000, well before the FMS ToD point. I tried to enter an altitude restriction for that point, thinking the FMS would re-calculate the descent point to meet the new altitude. The FMS accepted the restriction, but the next waypoint went back up to the cruise altitude setting. It seems the FMS was never in the 'descend' mode. At that point I lost all use of the FMS altitude restrictions, and had to fly the rest of the route and approach using only manually set altitudes and VS or FLC commands. What's the procedure for small altitude changes (descents) well before the calculated ToD point? Should I have entered the altitude as a new cruise altitude? Thanks!