Cosmopilot

Members
  • Content count

    84
  • Joined

  • Last visited

Community Reputation

40 Excellent

About Cosmopilot

  • Rank
    Advanced Member

Profile Information

  • Gender
  • Location : Germany
  1. [Landing Light Combo] description=All Landing Lights ON new_command=IXEG_737/LL dataref=ixeg/733/lighting/land_light_all_act on_value = 1 off_value = 0 [Nav switch] description=Switch NAV-Lights new_command=IXEG_737/Nav_Switch dataref=ixeg/733/lighting/position_lt_act on_value = 1 off_value = 0 [Beacon switch] description=Switch BCN-Lights new_command=IXEG_737/Beacon_Switch dataref=ixeg/733/lighting/anti_col_lt_act on_value = 1 off_value = 0 [FD1 switch] description=Switch FD1 new_command=IXEG_737/FD1_Switch dataref=ixeg/733/MCP/mcp_plt_fd_act on_value = 1 off_value = 0 [FD2 switch] description=Switch FD1 new_command=IXEG_737/FD2_Switch dataref=ixeg/733/MCP/mcp_cplt_fd_act on_value = 1 off_value = 0 [Taxi switch] description=Switch TAXI-Light new_command=IXEG_737/TAXI_Switch dataref=ixeg/733/lighting/taxi_lt_act on_value = 1 off_value = 0 [Transponder switch] description=Switch Transponder new_command=IXEG_737/Transponder_Switch dataref=ixeg/733/xpdr/xpdr_stby_act on_value = 2 off_value = 1 [LLLeft switch] description=Switch LandingLightLeft new_command=IXEG_737/LLL_Switch dataref=ixeg/733/lighting/l_inboard_ll_act on_value = 0 off_value = 1 [LLRight switch] description=Switch LandingLightRight new_command=IXEG_737/LLR_Switch dataref=ixeg/733/lighting/r_inboard_ll_act on_value = 0 off_value = 1 [LLLeftOut switch] description=Switch LandingLightLeftOutboard new_command=IXEG_737/LLLO_Switch dataref=ixeg/733/lighting/l_outboard_ll_act on_value = 2 off_value = 0 [LLRightOut switch] description=Switch LandingLightRightOutboard new_command=IXEG_737/LLRO_Switch dataref=ixeg/733/lighting/r_outboard_ll_act on_value = 2 off_value = 0 [Strobe switch] description=Switch Strobe new_command=IXEG_737/Strobe_Switch dataref=ixeg/733/lighting/strobe_lt_act on_value = 1 off_value = 0 [EHSI Mode Flick] new_command=IXEG_737/EHSI_Mode dataref=ixeg/733/ehsi/ehsi_mode_pt_act description=EHSI Mode values = 0, 1, 2, 3, 4 [EHSI Range] new_command=IXEG_737/EHSI_Range dataref=ixeg/733/ehsi/ehsi_range_pt_act description=EHSI Range values = 0, 1, 2, 3, 4, 5 Quick & Dirty xJoyMap file that adds the light commands and a command to change the map range.
  2. Green Cockpit Shimmer in XP11

    Make sure that you're not flying near to a nuclear power plant. (Serious: I can confirm the shimmer when the shades are removed)
  3. [Temporary]IXEG 737 in X-Plane 11 How to get it work

    You nailed it
  4. To IXEG - a roadmap?

    Rly? I suggest just to be patient. How many "hurry up" topics do we all need
  5. Hm, after thinking a little bit about it, the classification into 2 categories would make more sense. Just "Flight can be continued if the failure occures" and "Divert to neares suitable".
  6. You could also implement some kind of failure level. Maybe 1,2,3 where 3 triggers the badass failures. 1 triggers the "light" ones and 2 the "medium" ones. This ensures that the user can finish his flight when chosing the lower levels. Sometimes you want to reach your scheduled location :-)
  7. am I reading this right?

    Recently got this one. Unsure if it's correct
  8. am I reading this right?

    Mayday.
  9. TCAS freezes with IXEG-v1.1 (Xplane10)

    That's an option and you would make many users happy. But you should publish that script @ the IVAO or XSB forums.. they should implement it natively without forcing users to fiddle around with scripts to make their products work "somehow". (Sadly the IVAO SoftDev is "dead" and does not accept any suggestion or improvement by 3rd parties - so, I don't think there will be an update within the next 1,2,5,10 years).
  10. TCAS freezes with IXEG-v1.1 (Xplane10)

    One thing to mention is how X-Plane or better X-IvAp or XSB handles the AI-Traffic: So, if a pilot enters your 20nm range, X-IvAp will "hijack" one of X-Plane's internal AI-Aircrafts and position it where the Online-Player is flying. After the guy is out of range (lateral or vertical), or turns off the Transponder, or whatever, X-IvAp stops "hijacking" this AI-Plane and the TCAS Target remains on it's last position. This is why so many other Payware-Aircrafts /Tools show those false TCAS-Targets that seem to be stuck and that don't move. X-IvAp only ensures that those aircrafts are out of your visibility range, but sometimes....yeah.. I'm the softdev of EFASS and I spent hours on getting rid of this bad TCAS bahviour by always checking if a target is really moving or not. So complicated for such an easy task. Another interesting find is, that each time X-IvAp repositions the AI-Aircrafts (to keep them out of your visual range), you will experience a short stutter in your Sim.
  11. Well, I was lucky (or maxbe not), IXEG Failure triggered: -------------------------- IXEG Failure triggered: Time: 14:55:23 - 31 May 2017 IXEG Failure triggered: Failure happend after: 12 minutes IXEG Failure triggered: Failed System: EDP B FAST LEAK IXEG Failure triggered: Failures left: 1 IXEG Failure triggered: -------------------------- IXEG Failure triggered: -------------------------- IXEG Failure triggered: -------------------------- IXEG Failure triggered: Time: 15:46:27 - 31 May 2017 IXEG Failure triggered: Failure happend after: 63 minutes IXEG Failure triggered: Failed System: ELECTRIC HYD PUMP B IXEG Failure triggered: Failures left: 0 IXEG Failure triggered: -------------------------- IXEG Failure triggered: --------------------------
  12. Just downloaded - will give it a try today and report back
  13. It's a mechanism to prevent PAX from seeing pilots operating the chemtrail pumps. It's a feature.
  14. @Tom Stian Nice script - You're the guy who brings us Online-Pilots into big trouble with the ATC And that's what I really like :-) So, from the software engineer's point of view, I have some small suggestions for your script. You're declaring a bunch of global variables in your script (Max_Failures, FailFactor, Cycles,... etc). That may cause problems with other LUA scripts. So it's either a good way to declare these vars locally in a function or prefix them with something like IXEG_Failuers_Cycles [...] to make sure that no other script will accidently produce sideeffects. Especially "Cycles" is a var that'll be used quiet often. 2nd: By adding these 2 lines behind line 16, you can Enable/Disable the script via the Macros-Menu. add_macro( "IXEG Failures DISABLE", "Max_Failures = 0" ) add_macro( "IXEG Failures ENABLE", "Max_Failures = 2" ) Cheers and happy checklist running
  15. [UNCONFIRMED] XP v11 issues, report here

    @ the two guys before this post, did you try to disable "Draw Vortices" in the IXEG menu? I remember there was a similar issue with powerlines some time ago.