blocks_off

Really silly question - sorry! Are you running the IXEG from the same folder?

Having not flown her for a while, I took the IXEG out for a flight - I was not caught out by having to momentarily pause whilst both engines spooled up independently to 50 - 55% N1 That, and watching the engine temps cool down exponentially are just some of the many details that still give me a smile when flying her. -Carl

I will try this out when I next fly - looks interesting. Thanks!

Interesting thread guys - thanks to all and esp. the OP for giving my brain another task to think about I'd had some ideas which need script to read CDU so I'll look when i next fly the IXEG. - Carl

Version 26/08/18 is released. During start routine, set ignition to L if the cruise altitude (as read from pressurisation panel) is odd. R if even. -Carl

Version 19/08/18 is released. Whilst cycling many miles in the country I had an idea - why not get the first officer to help setting the pressurisation panel standby altitude.... and so they do now - Carl

Thanks for taking the time to review my script As you say we have a different taste on what we wanted to achieve - it's fantastic that we were able to do so in the IXEG. Yes I have seen you were releasing for the A320 - well done. I have another planned in the future, but not for the A320 Thanks again. - Carl

Hi All, Please find a link to the manual & script of my first officer.... (s)he is a LUA script. Drop the LUA script into your LUA scripts folder https://forums.x-plane.org/index.php?/files/file/46628-blocks_off-ixeg-first-officer/ The script will help you during high workload phases of flight. Preview Video (to supplement the manual) -Carl

Good idea

Thankyou - I should have said when I did not see the variables I require in the documentation I'd tried this tool. I'll have another look with a fresh pair of eyes - Carl

Hi, Is there a variable for Panel Bright (left and right side), Background Bright please ? I assume it is not these (as they do not have _act at the end) ? "ixeg/733/lighting/light_main_pilot_side" "ixeg/733/lighting/light_main_copilot_side" - Carl

Thanks - Carl

Thanks - so this is of course why when in the air and switching off the centres the remaining few kilos are used ?

Hi Before start, if there is less than 1000kgs in the centre tanks, I leave off the centre pumps until after take off (assuming of course there is fuel in centre!) I noticed for the first time, when I loaded the fuel I had 830kgs in the center and so the centre pumps were off. Taxiing out I did see a very small reduction - down to 800kgs just after take off. Assume some fuel still gets drawn from the centre in that case ? Thanks - Carl

What I do is look at the MCP - the N1 button will be green (2 little green dots : ) Also on the PFD you will see ARM | | change to N1 | TOGA Once you get used to that, there is no need to look 'down' at the button. -Carl

Hi @jfjoubert You are correct with what you say and it is great fun testing when you move a switch to a different position, then it moves it back but i digress..... I do not hear repeated clicks, there are a few steps where I check for the state and then only set if it is not in the correct position for that routine such as gear handle, start switches. I've had a quick look at your code, and as much as I like the randomness idea, I will park it for now Well done though with that achievement... did you drink a lot of your favorite drink whilst writing it ? Thanks for your reply and interest -Carl

Yes that is true of the code I posted earlier, but not if taking this into account i.e. it's part of a function as described here. As above

Thanks - and with all the thinking my brain can do, I do not know why i've done it as per my original note. Just putting some more lines together in my lunch (for my shutdown routine) looks much neater per your suggestion :- (I've intentionally put the same time on some actions - I want my first officer using all fingers when he can! if r_includeIRS then if os.clock() > r_trigger_start_time + 1 then w_acft_irsL = 0 end if os.clock() > r_trigger_start_time + 2 then w_acft_irsR = 0 end end if os.clock() > r_trigger_start_time + 4 then w_acft_fuelLfwd = 0 end if os.clock() > r_trigger_start_time + 4 then w_acft_fuelLaft = 1 end -- leave on for apu if os.clock() > r_trigger_start_time + 5 then w_acft_fuelRfwd = 0 end if os.clock() > r_trigger_start_time + 5 then w_acft_fuelRaft = 0 end if os.clock() > r_trigger_start_time + 6 then w_acft_winheat_l_side = 0 end if os.clock() > r_trigger_start_time + 6 then w_acft_winheat_l_fwd = 0 end if os.clock() > r_trigger_start_time + 7 then w_acft_winheat_r_side = 0 end if os.clock() > r_trigger_start_time + 7 then w_acft_winheat_r_fwd = 0 end if os.clock() > r_trigger_start_time + 8 then w_acft_pitot_a = 0 end if os.clock() > r_trigger_start_time + 9 then w_acft_pitot_b = 0 end if os.clock() > r_trigger_start_time + 10 then w_acft_hydELEC2 = 0 end if os.clock() > r_trigger_start_time + 11 then w_acft_hydELEC1 = 0 end if os.clock() > r_trigger_start_time + 14 then w_acft_seatbelt = 0 if os.clock() > r_trigger_start_time + 15 then w_acft_beaconLIGHT = 1

@XPJavelin Thank you too and for your solution to the engine start switches which uses the set command. I've also applied the set command to set my gear lever to off after take off. Here is an excerpt below from one of my features showing how i pause between actions. This particular function is started by choosing it from the menu (I wrote this particular function just to set the status of lights, gear etc. when i do some approach practice from 10 miles out. There are probably much better ways and far more efficient ways than my coding that I learnt as i went along Aircraft_shooting_approaches () is active every second as i use do_often. The code only runs in the function when r_trigger_shooting_approaches is true. The last item in my function always sets the trigger to false, r_trigger_shooting_approaches = false function Aircraft_trigger_shooting_approaches () if r_debug > 1 then logMsg( "[blocks_off 7373 First Officer] Aircraft_trigger_shooting_approaches - is now active") end r_trigger_start_time = os.clock () r_trigger_shooting_approaches = true end function Aircraft_shooting_approaches () if r_trigger_shooting_approaches then if r_debug > 0 then logMsg( "[blocks_off 7373] First Officer] Aircraft_shooting_approaches - is now active") end function message() draw_string( 50, 20, "Shooting Approaches...", "black" ) end if os.clock() > r_trigger_start_time +1 then w_acft_flap = 0.5 end if os.clock() > r_trigger_start_time +2 then w_acft_l_outboard = 2 w_acft_r_outboard = 2 end ...other code if os.clock() > r_trigger_start_time + 22 then r_trigger_shooting_approaches = false if r_debug > 0 then logMsg( "[blocks_off 7373 First Officer] Aircraft_shooting_approaches - has now ended") end function message() draw_string( 50, 20, "", "black" ) end end end end --end of function Aircraft_shooting_approaches () add_macro( "7373 Shooting Approaches", "Aircraft_trigger_shooting_approaches () " ) do_often ("Aircraft_shooting_approaches ()")

Hi, I like the randomness idea - I was thinking the same in what I have written here (I've added alot since this preview) >>> https://drive.google.com/open?id=1k-90ng-W0l09Zuw986TV7v5TR8FFUfhu And yes, my code is very lengthy based on the pause of typically around one second that i do between each step. Of course this is the 757 and was built to fill my own needs so is not as sophisticated as speedy copilot i.e. I do other actions from other triggers but I am currently porting this into the IXEG and will make it available when it is ready. -Carl

Hi, In your script - do you still get the same behaviour if you just leave in the 2 lines that declare the variables ? I ask as this was my experience with my LUA script - i.e. my switches got stuck and just for interest i removed the actions, leaving the assignments and still experienced the switches sticking. DataRef("w_733_1_start", "ixeg/733/engine/eng1_start_act","writable") DataRef("w_733_2_start", "ixeg/733/engine/eng2_start_act","writable") - Carl

Hi, I have a second copy of x-plane on my main x-plane computer - I of course copied from my main folder. I do not wish to fly the IXEG in my second copy and as I get the activation prompts when I start x-plane, can I simply delete the folder ? I ask as of course there is an uninstaller but I don't dare run that! - Carl

I found the same too (it's probably my set up!) but what i do is ignore the spoiler axis for the IXEG. In lieu of this, if I want to deploy some spoiler I use the mouse and drag the handle. I am not a real pilot but I use the spoilers like the other controls, don't just hit detent but i move them there over a second - maybe two (approx). Same when moving them back down a gradual movement and I watch the v/s react too (when in FLCH or VNAV) I also understand it is good practice to keep your hand on the s/b lever - this so that you do not forget you have deployed the spoiler. Hope this helps - Carl

This is the idea that I had in mind https://youtu.be/wGvXjGG4Mx0

Hi All, Appreciate this may not be correct place but what i am hoping for is some help to get started with hopefully what will be a small Lua script for an idea that I have. Does anyone have a link they can share please so that I can get a feel for how a Lua script is coded to work with the IXEG ? Of course as I think there is a dedicated forum, but hopefully i can started by taking something and learning in that way. Thanks - Carl