mmerelles

thanks for your great work and continuos support EDIT: haven't seen the hemisphere gps pos issue for southern latitudes on the list, but tested and seems to be fixed as well.

watch your IAS target .84, the aircraft is pointing the nose way down to increase its speed to .84. this is a known bug. When you clic FLCH the aircraft should keep its speed and because throttles are retarded to idle it should put the nose down a bit to mantain its present speed. BUT when you press FLCH the speed re-sets to .84 MAC (due to the bug) and the aircraft dives down like crazy trying to reach target speed. edit: forgot to say, workaround is press FLCH and immediately reconfigure IAS target as per your present speed to have a nice FLCH descend rate

it is my understanding JAR released an update to fix this already. check!

@3rdwatch Just to be sure i edited the script for you and put 127 & 128. If it doesn't work i give up with jetmax note: editing the lua scripts with improper editors like notepad may lead to the script not loaded properly. Here is the script if you want to test it just to be sure. joystick.lua

I think we are quite accustomed to poor simulations, when ixeg simulates not only basic systems but complex systems that runs beyond the pilot on the real thing we see issues everywhere you better watch this

this bird has no callouts on real life, nor here.

ok @3rdwatch here you go... put the attached script into your /xplane 10/Resources/plugins/FlyWithLua/scripts/ folder. Launch xplane and test. Comments: The script will run single time everytime you load a new aircraft, if it senses you are loading the 737-300 it will set the handlers accordingly. As per your screen capture 128 is the ID for handler engine 2 so i would assume 127 for handler engine 1. Lua is -1 so i put 126 & 127 on the script Lua is very powerfull if the script works for you and you are happy, you can use lua to sense what aircraft you are loading and based on that set on a per aircraft basis your axis, nullzones, sensivities, buttons, keys, custom mappings, anything. So you do not have to reasign manually every time you load a different bird. Let me know how it works joystick.lua

Interesting situation... I have seen this scenario dozen of routes in PE over the SoCal area, because all flights departing KLAS and arriving to the WEST (KSNA, KSAN, KLAX etc) share the same transition point for the SID and the STAR such us TNP, HEC among others, also flying back to KLAS you share DAG for SID/STAR quite often. Being a PE member, i also see there are 733's online at all times, so this scenario comes into play quite often. I also seen none of the SIDs has restrictions for shared transitions while some STARs have restrictions for entering the transition. If this helps... this is the way i look at it when SID/STAR share transition over a short route: -If only one has restriction, that one should take precedence -If none has restriction and the user didn't entered anything, then you go to cruise from your last sid restriction, then you descend to comply first star restriction. -If none has restriction but the user entered something i think its safe to asume this is part of the descend profile and t/d should be recalculated, because the SID transition occurs at the end of the departure procedure and rarely will require restriction? while ATC quite often ask you for an altitude entering the procedure

You should understand a bit the difference between datarefs and custom commands first. Datarefs -trying to say it simple- is INFORMATION, a memory position where you read/store something. Datarefs are used mainly for programmes to perform actions based on what the dataref value is or to change the dataref value to be used for something. You can not map a key or button on xplane joystick & assignment to a dataref/information. Because doing a clic on the button what is supposed the memory position do or happen? Custom commands are actions, you map custom commands to keys/buttons. The costom command has a predefined action when you clic it put FD ON, when you clic it disengage the A/P you can read a bit more here http://developer.x-plane.com/2009/04/datarefs-vs-commands-i-whats-the-difference/ The PDF you are referring contains a list of custom commands, things you can map directly to button/keys and a list of datarefs, memory positions/information of the aircraft status to interact with it via programming. Very useful for cockpit builders.

i can provide you a simple lua script to handle fuel levers. But i have to be sure i am understanding how your jetmax handlers are recognized. Under jjoystick & assignment, button adv - tab Recognized as switch When you toggle the handler up to idle, a button press displays and it stays. I mean it keeps displaying like something went to ON When you toggle the handler down to cutoff button representation on the display turns off. Recognized as a button When you toggle the handler up to idle, a button press displays and goes away (a blink) When you toggle the handler down to idle, a button press displays and goes away (another blink) during those blinks the button identifier for IDLE and CUTOFF is the same or different?

@ROBBAN you are having rendering alarms coming from Polish Airports V3 that contains EPWR. I would suggest move "Polish Airports V3" out of "xplane/custom scenery/" and reload xplane to use the default airport. Test your flight again to confirm the problem was solved. If the problem was solved you should check if there ir a newer version available for donwload? or contact the developer for the rendering issue

you can tune the packs volume on the aircraft menu

As i explained above, no MCP will work properly unless your MCP provider -or a third party developer- provides you an INTERFACE for you to customize your hardware. Even if your provider makes some internal changes to map the ixeg bird, it will not work for any other aircraft addon and surely it will also stop working with the ixeg during updates. Start pushing your MCP provider for the interface and/or researching if someone else created such interface for your hardware.

as per your statistics when the fps drops your cpu goes crazy it means something on the simulator is triggering to load and kills your fps momentarily. This has nothing to to with ixeg but your xplane plugins/settings. -It could be the airport itself. try removing this photo scenery based and use default to compare -it could be a plugin like x-life that triggers ground traffic (cpu) -it could be your xplane AI traffic if enabled (cpu) -it could be airport ground traffic plugin (cpu) attaching the log.txt would be a good starting point to see what you have running.

I do understand your point for a random waypoint enroute. But TNP (twenty nine palms) is part of the LYNDY4 arrival, i think the FMC should at least recognize whether the pilot is entering/changing/removing a restriction that belongs to the STAR procedure -or the SID- is safe to asume is part of the DESCEND -or the CLIMB- and the FMC should make the necessary computations to comply. https://skyvector.com/files/tpp/1605/pdf/00373LYNDI.PDF

If you are willing to buy a MCP hardware... get one that is fully supported for xplane, otherwise you will end up having a hardware partially useful and they are not cheap. Most aircraft no matter its complexity uses default xplane commands/datarefs for IAS, COURSE, ALTITUDE, HDG. But all payware aircraft that mimics real life birds uses extensive proprietary custom commands/datarefs for VNAV, LNAV, CMD A-B, CWS A-B , FD switches, AT switch, VS display & wheel, N1, AP disengage, light status, etc. thus they will not work unless your can program your MCP on a per aircraft basis. That being said, the most important thing you have to look at for your decision is: per aircraft support vs platform programable support I mean, if you get a MCP that the developers made internal support for specific aircrafts, then be sure you will not run your precious and expensive MCP to any other cool addon that releases until they decide to support it, and you even risk some features stop working on your existing aircrafts during aircraft's developers updates until they update their code as well. What you need is a MCP having a xplane interface tool for you creating on a per aircraft profiles to map your mcp hardware to differemt aircraft specific commands/datarefs. Unfortunately i learnt that the hard way. Bought my Goflight MCP PRO without much research/knowledge a year ago, sooner i realized it had no interface for xplane, some free developers managed to create plugins that supported specific aircrafts of their interest. Those developers moved on some time ago, and once those payware birds got a few updates they stopped working, crashes and many issues that forced me to retire my MCP PRO. Fortunately god shined us a few weeks ago and Pollypot released their Goflight intergace tool for xplane (payware), but dam, this app is so cool. It has a graphical interface were you create profiles on a per aircraft basis, and you assign any button, light, switch, rotary, display, etc. of the MCP PRO to any aircraft custom command / dataref. So it supports ANY aircraft and you can keep tuning it by yourself when new aircraft releases or existing ones updates. You can also import/export profiles to share the community not requiring everyone creating their own profiles. I am not telling you go and grab goflight + pollypot, that is your call, could be other alternatives to compare. But be sure you get what you need, otherwise you will get a course/hdg/ias selector instead of a full working MCP to any aircraft as you expect. hope this helps someone.

impressive

I am using Brunners CLS Yoke, amazing stuff. Couple of things i like to highlight. -Hydraulics. You can simulate hydraulics on a per aircraft basis. You loose the hydraulics inflight/turnoff intentionally and you better got some training on the GYM, it goes really heavy -Stick stall. You can enable stick vibrations for the engine, runway, turbulence, etc. and customize them, but the yoke shaking under stall in the ixeg like the real thing is crazy, really nice. -Forces based on IAS are extremely good. Feeling how the pitch washes out under low speeds at final is amazing. Specially on the Cessnas. Inflight surfaces are all about pressure on the yoke but during takeoff and landing you have to actually pull it, deflect it. -Centering. it simulates standard centering as a desktop yoke, centered via wind pressure over the surfaces (you deflect it left while parked and stays there, as soon as you gain speed it centers itself pitch & roll) or via hydraulics. So you can customize how it behaves. It has so many options and parameters, still experimenting for fine tuning it to the ixeg an all of my addons.

Sr. you have to take it easy and be a bit more open mind here. 1. The link the developer provided you, is a constructive guide for users having issues what to do. This avoids frustration. 2. Your problem about not hearing some audio may not be the aircraft itself. There seems to be an issue on specific users with specific configurations. I would asume you are smart enough to understand no developer has the capability to test their aircraft against any potential user hardware/software/settings configuration mix prior to release. There are simply infinite potential configurations at home. So be collaborative when your free time permits, as said, this may not be ixeg fault but any of the other piece of software you put on xplane. The developers are interested to understand incompatibilities issues to get the resolved by them -or by third party developers- as already happened with other plugins. The link the developer provided you points out to remove the plugins to better point out the issue. if you attach your xplane log.txt file found in the xplane's root folder we can have a look at it an tell you potential issues based on other users similar scenarios.

On another thread discussing the same some people found JAR ground handling was the culprit, removing it solved the problem. I would suggest you remove ALL your plugins except GIZMO and try again. if problem gets solved add plugins one by one to identify the ofender.

This is interesting guys. I am runing imac el capitan 10.11.4 no sound issues at all. xplane 10.45 skymaxxpro + real weather connector flywithlua + terra haze seatraffic note: i also installed botcamp + windows 10 to compare performance and no sound issues either. can you attach your log.txt files to have a look at it? weird

Ok great if being a button we are spot on. Go to xplane joystick & assignments - button adv tab and: Assign left cutoff button to "engines/mixture up a bit for engine #1" Assign right cutoff button to "engines/mixture up a bit for engine #2" You are done. Go back to the cockpit and flip the levers up&down to confirm.

can you try cold & dark just to confirm? if you share me your airport, route, procedures i can try to help you out if anyway to get it re-aligned and working starting ready to fly.

ohhh i got your post via your profile posting. Not much description here as well, but i presume you are using the GPS position resulting from entering the airport ICAO as gps reference. The FMC always assumes to be in the northern hemisphere, this is a known bug. To align your IRS, press POS then press NEXT PAGE and clic the LSK of the current aircraft GPS position for copying it to the scratchpad, then press PREV PAGE and paste on the GPS RSK for alignment. You will be good to go. If you have any other issue please share us more details

this is a bug on the fmc not navdata. it is known already. as you already realized use "next page" current gps aircraft position instead of airport position and you are good to go