Litjan

Yep, I will try to test this tomorrow as well! Cheers, Jan

I am sure (if you are into cockpit building) that you have looked for some datarefs already... I know very little about this, but from what I can tell the datarefs: ixeg/733/engine/eng1_thro_angle ixeg/733/engine/eng2_thro_angle output the throttle angle at all times? Jan

I still have to try - but there is one thing to consider: If the thrust levers are advanced into forward thrust, they will disarm the autobrake. So even a little bit of thrust still set at touchdown will disarm them. Now normally the reversers will not deploy while the thrust levers are not at idle - but I don´t know how X-Plane handles that. I could see a scenario where the pilot lands with the thrust levers not completely at idle, or maybe advancing them again before the plane registers that the reverse thrust is active (the dataref needs a second to switch). The real plane will not allow the reverse levers to be pulled back before the reverse sleeves are in the fully deployed position, while X-Plane may allow that. So a good test would be to touch down with idle thrust, keep the nose up, deploy reversers, keeping the nose up, then adding reverse thrust when the reversers are definitely deployed (it takes 2 seconds or so). You could actually start deploying the reversers when radar altitude is below 10 feet, but that is really bad piloting technique, so I don´t even want to encourage that ;-) Cheers, Jan

Hmm, do you have a physical throttle that can move by itself? If you do, then I can see the purpose of this request. If you don´t, then "aligning" the physical throttles with the virtual ones is the only way to sensibly achieve what you describe, because nothing would be worse than switching back to a hardware throttle that is not at the correct powersetting - ask any A320 pilot that inadvertantly disconnected the autothrust before aligning the thrust levers with the "donuts" on the engine display (it is like falling off the horse, every rider needs to have done that at least once , and so did I!) Cheers, Jan PS: If this is related to XPUIPC interface - we do have a dataref that may help: Try to set the ixeg/733/hardware/xpuipc_overrides to 1 and see if that helps?

There is no dataref for that. We move the thrust levers within our code, without a dedicated dataref - we write directly to the throttle position of X-Plane, iirc. Cheers, Jan

Ha, good find - yet I am confused that this happens only on our aircraft - we are using the default X-Plane system for both reverse thrust and the autobrake, so I would assume similiar behaviour on the default 737, for example... I will see if I can find out what is happening. Thanks for the hint, Jan

Here is the next version of LOWI that Laminar will include soon: LOWI Demo Area V1.1.zip

Hi Daniel, I hope you are succesfull! There are many possibilities for plugins not to work together, the first step is always finding out which ones clash. Please let us know when you find out! Cheers, Jan

Well, you are running librain, that is not compatible with X-Plane 11.50 I think... plus many other plugins that could cause all sorts of problems, too. Add on top of that any scenery that one can possibly download, all crammed into a beta version of X-Plane. Your log is full of reports of stuff going wrong and not working... Something is gotta give at some point. I suggest a thorough housecleaning of your X-Plane installation (imagine two big containers in front of the house and a crew in full-body white suits and breathing gear)... and then we can start guessing what the cause might be Cheers, Jan

Wow, you are right! Good catch! Cheers, Jan

Well, knobs can´t move up or down, they are fixed on the rotational axis and can only rotate counterclockwise and clockwise. The consensus so far is that "mouse up" increases the value and "mouse down" decreases the value represented by the knob. I know that in the case of the EHSI mode there is no real "increase or decrease", but we are going with "increase = clockwise" for commonality. I think I understand what you are trying to say - if you see the "marker" on the side of a knob in the 3 o´clock position you would expect to push it "up" towards the 12 o´clock position. And if it is in the 9 o´clock position you would also expect to push it "up" to the 12 o´clock position... Now what do you do when the marker is pointing straight up at the 12 o`clock position - and you want to move it to the 9 o´clock position? Do you "pull it down"? But what happens if it slides down "the wrong side" and now ends up at the 3 o`clock position? Do you hold your mouse sideways? This isn´t going to work in any way that makes sense - I think that Apple does it that way - but there you go (I said "makes sense" ). And no, we aren´t even going to consider changing it or making an option, either . Cheers, Jan

The idea here is to "increase" the value, you push your mousewheel up. And just like turning up the volume in your car, turning the knob to the right (towards PLAN) means "increasing" it. Just like on the range button. Turn left is decreasing, turn right is increasing. It works that way on all the knobs in the whole cockpit - or did you mean something else? Cheers, Jan

Atlichna!

None of that modern gadgetry...we follow the floatsam and the direction of the seagulls! Use the Aviat you got in flightschool to correct for drift and coriolis force and you don´t even need to tune the ILS when landing in foggy JFK 8 hour later!

Hi jojo, thanks for the report...I thought we had fixed this, maybe it crept back in with exporting the cockpit object. Funny enough the yellow bug starts out at the first line, but then you can never push it back all the way up. I also want the checklist to be "flush" against the yoke - we only flipped it up to read it, then would pop it back in. It bothers me that it is out all the time :-) Cheers, Jan

Hallo Jürgen, the only way to fix this would be changing the "increments" for the mousewheel - but then you would have to turn it a lot to achieve the desired dimming/brightening. I think it is a good compromise... Bis dann, Jan

b. look at my video - I think the problem is you using the mousewheel, it will "jump" the knob by certain amounts, so it looks like it moves backwards (strobe effect). EHSI brightness.mp4

Hallo Jürgen, this is a known problem with beta 15. You can update your avitab to fix it or wait for beta 16 which should be out fairly soon. Viele Grüße, Jan

Hallo Jürgen, I know about the DME ID´s - this seems to be an X-Plane issue - as there is no special procedure to tune and listen to them, compared to the VORs. The direction of the brightness knob for the Captain´s ND seems to be working fine on my end - make sure you are not misled by the "stroboscopic" effect when turning things really quick at low framerate (like a car´s wheels seem to turn backwards in old movies). The brakes don´t work exactly "opposite" - in real life you can depress the brakes to release it, just like in our plane. It is true, however, that in real life you have to depress the brakes to engage the parking brake, this is not modeled in our aircraft (we use the default X-Plane parking brake system). Changing the way the brakes work is not very easy in X-Plane, you can "fail" them (we do that to simulate them running out of hydraulic pressure) but to override them is a different thing (you can´t overwrite the brake dataref). Viele Grüße, Jan

Yes, I had the same synopsis. I could use the internet just fine, including playing online games etc. But when I tried to download (I think it was TerraMaxx) it would download most of it ok - but choke on some files. The daisy-chain may in your case be (beyond your control) in the way the data network is laid out in your building or so... I don´t think there is any other way to get you the installation files but as an online download. Some alternatives may be a connection through your cellphone or possibly a WLAN in a restaurant or at a friends place? I must admit I do not know if you can download the installation files on a laptop (while at McDonalds or Starbucks) and then later at home transfer them to your desktop and install them there? Hope any of this helps, Jan

Hi Iain, this explained it. The PLAN line "overwrites" the measure fuel quantity for planning purpose. Imagine you sit at the gate and wonder if you can make an altitude restriction on the SID or how much fuel you would have when you arrive at the destination... you put in your ZFW, but the fuel truck did not refuel the aircraft, so the GW calculated by the FMS (ZFW + measured fuel quantity) is not what you will actually have when you take off (too light). Another use for this field is entering the actual fuel value when the fuel summation unit messes up and the measured fuel quantity in the FMS is wrong. It would lead to all sorts of wrong calculations, so you can overwrite (hardlock) the value here. So you can enter this PLAN FUEL and this will effectively overwrite your "measured fuel". Until you eraze it. Cheers, Jan

While I am not an expert, often the "unable to download" errors point to a problem with the internet connection. I had this when having my computer behind multiple routers - plugging it directly into the DSL modem worked. Cheers, Jan

Hmm - I will try to recreate that problem by setting up your situation, 150NM northwest of YVO then to BEMOG,... I will let you know if I can reproduce that. Edit: Tried to set up your flight as close as possible but the LNAV was humming along very well and went after that magenta like the devil after the poor soul... so I am not sure what is interfering on your end. I doubt that the long range of the flight had anything to do with it. I recently took it from SFO to Honolulu and that went flawlessly... Also variation and latitude is not special for this flight. Cheers, Jan

Thanks for letting us know, teelo! I will try if I also get this with my Rift - and maybe it is also possible with the mouse? Normally the guard being closed will also close (connect) the battery, but maybe it is not checking the "state" of that guard but rather the "movement"... Cheers, Jan

Thanks for letting us know! Happy landings!