jfjoubert

If I sell my car I can also buy a Brunner Yoke here in South Africa...

Just read the included pdf... you have to click on the Oxygen test button to start the preflight procedure.

No, I don't drink and code...

@blocks_off Correct me if I'm wrong but won't your code execute the same steps multiple times until the 22 seconds have passed and r_trigger_shooting_approaches is set to false? It should work if you conditionally check each item and only set it once like this: if os.clock() > r_trigger_start_time +1 then if w_acft_flap ~= 0.5 then w_acft_flap = 0.5 end end Otherwise you might end up hearing all the click sounds in the cockpit when switches are set to a specific position, even though they might already be in that position from a previous loop through the function. Anyway, it could work. I just felt like typing a lot of code...

You're welcome @XPJavelin

As promised... IMPORTANT NOTE TO ALL: This file is not a complete replacement for the original code from @XPJavelin. It simply shows a way of applying some randomness in the procedure steps. Please also note: The code was only modified for the PREFLIGHT Procedure (start with OXYGEN test switch) You can easily change the min and max time (in seconds) for the random delay in the code I re-enabled some of the datarefs and made some "readonly" to be able to do some conditional checks If you don't know FlyWithLUA or LUA or you don't care about the underlying code then wait for an official update from @XPJavelin This will only happen if @XPJavelin wants to incorporate this into his code @XPJavelin I did add comments as far as possible to the code so hopefully it will make sense. Shout if anything is unclear. IXEG_proc.lua

Soon it will be released... I'm just busy testing to avoid a red face.

The problem with the above code is that you cannot have it in a function which is only executed once... you will never get to most of the steps. The current code has a conditional check for PREFLIGHT to see that preflightproc_trigger == 0 and beforestartproc_trigger == 0 and OXYTEST == 1 Now this means that the actual code inside the function will only execute once. On the second pass all the above variables will not meet the condition again. So you will never get to os.clock() > r_trigger_start_time + 4 and further. So one possible solution is to change the conditional check to make sure that the code inside the function is repeated until all steps have been completed. This is what is adding to the clutter because now you have to make sure that you don't repeat a previously executed step and and that all steps are still done in the right order. Anyhow, I will upload my lua file (once done) with my modified code for the PREFLIGHT procedure and you guys can then have a look to see if it's not too much clutter in the code.

I am still trying to see if I can optimise my code (clutter wise and not speed wise). I have absolutely no lags or stutters whatsoever. I will upload as soon as I feel it is worthy of sharing.

Hi @XPJavelin Thanks for this nice script. I see that you mention that all steps are performed "speedily" as you couldn't get delays between steps to work without pausing everything. So I took your code from version 2 and added this "delay" logic and it's working pretty well. It does however clutter the code a bit due to the fact that I'm using os.clock() and checking for how much time passed since the previous step was done. Currently I'm using a random delay of between 0.5 and 1.5 seconds between steps. It gives you the feeling that the copilot is sometimes thinking of what he must do next. I'm pretty sure that someone with more LUA knowledge could probably write better (more elegant) code than what I have done. If you are interested let me know and I will share. PS: I think you should also rename your script to "Not so speedy Copilot" once the random delays have been added.

Hi, I tried this SID with the IXEG and the FFA320 and it seems to be correct. On both aircraft the last point on the SID is TEMAM. I'm using Navigraph cycle 1806.

Hi, apologies for the delay... So here's the good news. Try the attached FlyWithLUA script and let me know if it's working for you. Once again, please read the section at the top of the file which will describe what you need to do to map your joystick button to toggle the reversers. The "debug" mode is on by default so you can see what is happening... just change the debug_on = true to false to disable the on screen display. Enjoy. ixeg_single_throttle_control.lua

I'll have a look at adapting the script to work on a single lever... Will let you know once done.

Glad it's working... I have a Lua script which will activate the thrust reversers independently for each throttle when you pull the lever into the bottom switch position (assuming you use 2 levers to control both engines independently). This will simply "toggle" the reverser on/off and then you simply push the lever forward again to control the amount of reverse thrust you need. Pulling it back into the bottom switch position will deactivate the reverser and normal throttle control will return. This gives you full control on the amount of reverse thrust... not just all or nothing. I also have a Lua script which adds the fuel cutoff commands to X-Plane and I have the 4 buttons beneath the 2 levers mapped to control the fuel cutoff levers. So for the 2 right most levers button T3 is fuel engine 1 on and T4 is fuel engine 1 off and T5 is fuel engine 2 on and T6 is fuel engine 2 off.

Ah, ok... As far as I know you cannot assign an axis to the fuel levers through the default X-Plane joystick configuration. Attached find a basic FlyWithLua script which you can use to map your joystick axis to the IXEG fuel cutoff levers. Please read the text at the top of the script file which will explain some basic info about what to do... and let me know if you need help. I tested it on my rig and it's working. Just as a thought... the way I have my throttle quadrant set up for the IXEG is as follows: The 2 right most levers (mixture and prop) are configured as throttle 1 and throttle 2 for the IXEG. Then I use a Lua script which will activate the thrust reversers independently for each throttle when you pull the lever into the bottom switch position. This will simply "toggle" the reverser on/off and then you simply push the lever forward again to control the amount of reverse thrust you need. Pulling it back into the bottom switch position will deactivate the reverser and normal throttle control will return. Works a charm. I also have a Lua script which adds the fuel cutoff commands to X-Plane and I have the 4 buttons beneath the 2 levers mapped to control the fuel cutoff levers. Not as nice as having an axis, but then again the fuel is either on or off in my books. Let me know should you be interested in the other scripts. Jean ixeg_fuel_lever_axis.lua

Hi, I'm not sure what you mean by "put the blue in number 1 and red in number 2". Please explain in a bit more detail what you're trying to accomplish and I'll see if I can maybe assist.

It would be nice if LR could somehow "disable" dataref checks against hardware whenever replay mode is active... just a thought.

Your guess is as good as mine...

I tried with the create_positive_edge_trigger( 21, "ixeg/733/MCP/mcp_at_disengage_act", 0, 1 ) and it's working as expected. Is there any particular reason that you need the value to reset back to 0? I did find a way around it though... but it might just be a hack. Simply create both a positive_edge_flip and negative_edge_flip on the same button. This will work exactly like pressing the virtual AT disconnect button on the throttle. create_positive_edge_flip( 21, "ixeg/733/MCP/mcp_at_disengage_act", 0, 1, 0 ) create_negative_edge_flip( 21, "ixeg/733/MCP/mcp_at_disengage_act", 0, 1, 0 )

Yes, it's weird. I also get the "rattling" with both the AT and AP disconnect manipulators. If I use the "ixeg/733/MCP/mcp_toga_act" for example then it's working fine. I'll play around and see if I can find anything...

Makes sense, I never really looked into the create_switch commands. I will see if I can get the AT disengage to work like this...

Ok, but you'll still need to map a button to a command irrespective of whether the command is already available or coded via LUA. So in effect what you need is to be able to map the button to different commands depending on the plane you're flying... if I understand it correctly. Not sure this is possible, but maybe someone has a solution.

Why not just use the Disengage AT command already supplied by IXEG to map to your buttons? You will find it under ixeg - 733 - autopilot in the X-plane Joystick mapping screen. No need for a LUA script.

May I ask what you're trying to achieve with your LUA script?