Pils

I know it sounds silly, but X-Plane can also be silly... Look down, are the brake pedals depressed? Have you removed the chocks?

To match the existing First Officer.

Not that I know of. The script works fine, and even has audio to match.

That's the navigation source, that's unrelated to the processing configuration of the FMSes. Check the rear right of the pedestal.

Within the PERF function.

Check the reversionary panel, you probably have FMS3 active.

Thanks for the reply. Just trying to reconcile this with what Jan said. So, for example, the individual pax load stations will have different values from flight to flight, but the overall total will always be very close if not exactly equal to the number of pax multiplied by the average and the weight factor, with a balanced C of G? Thanks.

Yes, it's not built for an on-screen keyboard use, as that's a tiny tiny minority of users (you're the first I've ever seen). However, once you're in the gear bay then standing up is not a problem, there is room for that. Yes.

That's not how it works. You probably didn't do the right thing. Sorry for not providing more detailed instructions.

It's been stated that the XP 11 version would be made available upon request, however you should contact X-Aviation Support via e-mail before making a purchase to get confirmation.

Please provide details of attempted input along with screenshots of the CDU at the time. Thanks.

Oh, I had one question I forgot to ask; it seems like the "base" average weight is ~100 kg (multiplied by the "weight factor" when above 1.0), and there's no randomness when adding passengers to the actual payload, is that correct? Would you consider making the actual payload that's added in the background (to the load stations) be more variable as would be in real life? There's presumably several bell curves upon which airliners based their averages (summer, winter, adult, child, etc.). Excuse me if this is already the case, it wasn't clear from the post. Thanks!

Firstly, less CAPS LOCK, please. It's hard to read. Secondly, the way the airframe and state management system works this would not be practical. Thirdly, we don't want to dictate what exactly "Ready For X" means to every pilot. Fourthly, we want all pilots to take the time to become familiar with the aircraft enough to get oneself to these states. In the airframe manager window create a new airframe, voila back to the beginning.

I don't think these datarefs are for what you think they are. The transponder state will be reflected in the default X-Plane dataref(s) as this is needed by programs such as xPilot.

My advice is also this: if you or another person has signed into another account from the PC in question (which is what the error message indicates), even if it was for innocent reasons, then be 100% transparent with Support about how and why. Do not try to hoodwink them.

It's always advisable to wait, they don't like duplicate tickets. Double check your e-mail spam folder, etc. Maybe they'll see this post and check the history.

The sim's Log.txt probably shows the go-around actions being triggered, but it won't say by what key, etc.

I think you're accidently pressing a bind for TO/GA, or clicking the wrong button in the 3D cockpit (the ones on the side of the throttle levers aren't AT disconnect).

Unfortunately Gizmo does bundle a very old copy of OpenAL, so who knows if there's now some incompatibility. A weird one for sure. Not really fair of LR to just shrug their shoulders when there's nothing in the log--which they're responsible for--that gives any debugging information. Oh well. Fingers crossed for FMOD.

That’s cursed!

I understand, but the log gives no indication that any of the plugins run by the IXEG 733 are at fault, which is usually an indication of a deeper simulator or PC issue, and that's not something anyone but LR can solve. I hope @Litjan will be able to come up with a workaround in the mean time, because I am out of ideas.

You've been busy. Looks good. One suggestion that comes to mind immediately; I know some people are going to prefer direct text input for any slider, as in the default interface. Cheers.

You are correct. This feature will have to be considered INOP for the time being.

Have you got in touch with Laminar Research's X-Plane Support?

You are flying uncoordinated, likely due to inadvertent rudder input or trim. If you have pedals you should recalibrate them in the X-Plane joystick controls settings. You may also need to add a response curve to include a "dead zone".