All Activity

This stream auto-updates   

  1. Today
  2. iPhone or Samsung

    My 4 year old iPhone 4S is not too slow and lasts about 6 hours so I am in the market for a new phone. I have had iphones for the past 6 or 7 years but I am now tempted to jump ship to android. I am comparing the iPhone 6S and Samsung S7 and they seem pretty similar in all respects. However one key element for me is how useful they are for aviation. So does one phone offer an aviator more than the other? Does one work better with SD than the other, does one have a better selection of flying apps etc?Reviews and thoughts welcome as ever.
  3. Window heat test

    Hi admroz, you are right, there should be a small "OVHT" label above the window heat test switch, I will take a look, thanks for pointing that out! Tom is right, to reset the window overheat condition you need to turn each switch OFF then ON. The effect of the switch is kind off the same in both directions. Pushing it UP (ovht) will trigger the overheat condition, illuminating all lights. Pushing it down will apply "full power", which will usually also result in an overheat condition (a real one) with the above effect, at least on the ground. Note that we do not simulate the cooling effect of airflow (yet)... Hmm, gives me an idea... The manual says, however: NOTE: Do not PWR TEST when all amber OFF lights are extinguished. Whatever that means...I have never used that on the real plane, I would think that it is mainly for maintenance use. Cheers, Jan
  4. KDEN PANC crash

    Hmm, especially troubling after such a long flight! You do know how to recover from a gizmo-soft-crash, right? So you can finish your flight? Procedure to keep on flying after gizmo-soft-crash: Click "reboot" in gizmo toolbar (little "flash" symbol) raise landing gear engage autopilot, autothrottle engage ALT HOLD and SPD, set a sane speed turn off parking brake finish flight with basic modes or enter information into FMS as needed (just enter destination airport, no need for an origin) Jan
  5. AT Disconnect

    Your guess is as good as mine...
  6. Yesterday
  7. AT Disconnect

    Your hack seems to work Ok! The question is why the soft button works ok but the script needs 2 commands to return the value to 0.
  8. AT Disconnect

    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 )
  9. AT Disconnect

    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...
  10. AT Disconnect

    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...
  11. AT Disconnect

    The lua script allows you to configure each joystick button to do the same function on each plane using the dataref each plane has for that function. For example, the fuel start/cutoff levers on IXEG are switched with "create_switch( 3, "ixeg/733/fuel/fuel_start_lever1_act", 0, 0, 1 )" while on the FF763 is "create_switch( 3, "1-sim/fuel/fuelCutOffLeft", 0, 0, 2 )" This enables you to load each plane and have the joystick configured for that plane without having to touch anything on XP11.
  12. AT Disconnect

    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.
  13. AT Disconnect

    Because I am just a masochist! I use to ¨fly¨ a few different jet planes and assigning that button to the IXEG does not work with the others. So I make a LUA script to solve that.
  14. AT Disconnect

    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.
  15. AT Disconnect

    Sure, disconnect the Autothrottles.
  16. AT Disconnect

    May I ask what you're trying to achieve with your LUA script?
  17. Window heat test

    I think the only way to reset the overheat protection is to turn the switches off and on again. I don't have the same "Window Heat" panel in my FCOM, so im not sure excatly how it should work. Looks like the PWR TEST actual is doing a overheat test. So maybe its combined power and overheat test.
  18. KDEN PANC crash

    After almost 5 hours! Aghhh The route: KDEN LAR V118 MBW J136 BIL J13 GTF J569 NAAPP V324 YYD V301 XT R4 PR B28 SIT J133 ALJ JOH PANC Log.txt IXEG_FMS_debug.txt
  19. Window heat test

    This is problably the least important issue you can imagine, but I'm just curious if this is intended behavior of 733, as it differs from NGs When performing window heat PWR TEST, the only way to turn off 'overtheat' lights is to recycle each window heat switch or to be precise going from ON to OFF state. Furthermore, the up position of this switch has no label, shouldn't it be "OVHT"?
  20. AT Disconnect

    Hi, I am having trouble in returning to 0 the value of "ixeg/733/MCP/mcp_at_disengage_act". Using the software button on the side of the throttles it works as it should: when pressed, the value goues to 1 thus disconnecting the AT (releasing returns to 0), the second time puts the A/T annunciator off. create_switch( 9, "ixeg/733/MCP/mcp_at_disengage_act", 0, 0, 1) Using a LUA script, the command above conflicts with somethnig, because it is constantly rattling as if it is forcing the switch to "0" Then using this one the trick is done, but the value remains in 1, never returning to 0. Hitting the soft button again it cycles and returns to 0. create_positive_edge_trigger( 9, "ixeg/733/MCP/mcp_at_disengage_act", 0, 1 ) Any ideas? Regards, Max
  21. [FAQ] Stutter/Performance Hit

    I believe the plane is flyable with the microstutters, just during on ground taxiing this is a little bit more noticeable. Devs are working on the issue and I'm sure they will find the way to sort it out.
  22. [FAQ] Stutter/Performance Hit

    I believe I have isolated where the stutters are coming from, I went through the whole process starting from cold and dark and got the IRS's aligned, route entered and checked, everything except starting the engines. At this point no pauses, as soon as I started the first engine the pauses began. This behavior is isolated to this addon specifically, and quite frankly I have to shelf it until the issue is addressed, which is a shame because this has been my favorite addon since the release.
  23. After some thinking about logging the cycle between flights its giving no sense. Since each cycle have the equal chance to fail
  24. You are confusing MTBF and lifetime expectancy. The former is about random failures of a device while the latter is about how long a device is expected to last. Those two can be very different. For example given the 2003 "life table" for the US - a 30-year old has a ~0.1% chance to die in that year - this translates to a MTBF of roughly 1000 years, however even the best wear out long before that - their lifetime expectancy is a mere 49 years. So MTBF expresses really just a random chance to fail and thus does not require any life time tracking. If you were to implement some form of that (e.g tires lasting only X landings), then you'd need indeed some form of air frame state save. In reality, you'd also hope that maintenance is aware of the lifetime expectancy of the various devices and replaces them before that. So I don't think you would gain much by tracking stuff across flights, unless you want to implement some sort of maintenance simulation, i.e. replace engines after X hours (depending on usage), etc. along with the financial impact to enable some kind of "running an airline" experience. In this simulation MTBF is really just there to give you a better idea of what to expect, i.e. a MTBF of 20h would mean you should expect one failure in 20h of flight (or 5% per hour, or adhering to how it's programmed: 0.0139% per 10s ) regardless of how those 20h are composed. Since it IS random however, you might experience 20 faults in 10 hours or none in 100h. In reality the MTBFs are much higher of course and vary from system to system as well, while here it's all combined into one.
  25. There is no history/logging between flights.. So the MTBF is "resetted" everytime you load the aircraft. So the MTBF just say something how often the failure can occur. But maybe some logging between the flights would be something for the next version. Thanks for the idea
  26. Studying your script I was wondering if the MTBF actually makes sense there. As far as I can tell you never save the time on the airframe (If I understand it correctly Cycles will always be set to 0 on each new script startup). So if I only do let's say short haul 1h flights, it would be highly unlikely that a failure occurs. That's not what I would expect. Could you clarify this for me? I may just have got it completely wrong, I'm by no means a LUA expert Regards, Bene
  27. Xplane 11?

    Your team does great work. I have the IXEG 737-300 classic and the BAe Jetstream 32 and they are both great aircraft, awesome modelling and Oh so realistic. Can't wait for the V2 of the SAAB 340A as I am fully into XP11 now and just can't bring myself to go back to XP10. Realise you will bring an update out for it to work in XP11 but will wait for version 2 so I can enjoy it in XP11 and in all it's glory. Thanks for all your hard work and commitment to releasing awesome products.
  1. Load more activity