Jump to content

AngelOfAttack

Members
  • Posts

    59
  • Joined

  • Last visited

  • Days Won

    1

AngelOfAttack last won the day on January 31

AngelOfAttack had the most liked content!

1 Follower

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

AngelOfAttack's Achievements

Contributor

Contributor (5/14)

  • One Year In
  • Collaborator Rare
  • Conversation Starter Rare
  • Dedicated Rare
  • First Post Rare

Recent Badges

23

Reputation

  1. So far yes. until they dropped exterior model update (giving the pace they are now, probably still a while
  2. I think there is different philosophy of small and frequent updates vs big and fewer updates. Clearly IXEG is on the later. while Pat prefer different one. As I would guess, IXEG 733's FMC been an old platform, many issue could only be resolved after completely new system have been dropped, patch it now might be possible but waste of work once new FMC is dropped in. There are other issues like APU fuel consumption and Master caution reset etc. etc. (just see them in bug report forums). Maybe IXEG try to get them once and for all with, IDK, 1.6? Since IXEG still utilize full uninstall/reinstall for simple update, it might be better by making big updates, but...it's kinda fixable as there are many other products using better update measures *Cough* SkunkCrafts *Cough* I can feel Pat's disappointment as there are nothing for over 3 quarter, things are moving slower than I would expected too, and Litjan's reply doesn't really help. Hope when the new update drop, it would be a fantastic one, and sooner rather than later!
  3. Normally I made my custom command with FlywithLua, it works with most add-ons pretty smoothly, but somehow IXEG 737 seems have some coflect between it. What I find is as soon as I use dataref command to announce a read/write on ixeg dataref, it can't be controlled by ixeg itself (or other conflicts), I actually bump into this years ago as this: As soon as I have " dataref("IX3_ENG1S", "ixeg/733/engine/eng1_start_act", "writable") " without any other lines, ixeg will no longer able to cutout that switch by itself. Recently I got another lua to set QNH : https://forums.x-plane.org/index.php?/files/file/90402-lua-barometer-setting-script/ It have dataref for "sim/cockpit2/gauges/actuators/barometer_setting_in_hg_pilot" and copilot, as soon as these line are here, the auto sync pilot/copilot function in IXEG 737 would no longer works. Both these problem can be resolved by add my own lua function to achive what the ixeg system should do then, but recetly I build some new hardware and I try to use it for control IXEG's master caution buttons, however, when I have the line of: dataref("IX3_FIREB", "ixeg/733/firewarning/fire_bell_co_cp_act", "writable") dataref("IX3_MACU", "ixeg/733/caution/caution_reset_act", "writable") dataref("IX3_MARC", "ixeg/733/caution/caution_recall_act", "writable") As soon as this been active, these button would make click sound constantly, and the master caution reset button will also change tilt constantly. Weirdly, although fire bell and system annciator will have click sound, they actually can be controlled by my code and would not click away information without my command, even with constant annoying click sound... I have use this style of fwl code for many kinds of 3rd party add-on aircraft they all works great, so this is quite unique to IXEG. Use dataref tool to active these function seems not having problem, I imaging maybe something else like spad.next would work fine? but at least I can't get it works with FWL, so maybe you can take a look at this issue.
  4. PREF INIT finished? The page sequence is kinda screwed in IXEG's FMC, not sure if it's due to it simulated a very old version of FMC software or just a bug, you just can't R6 to all pages needed for preflight.
  5. When moving FLT/GRD switch to GRD after landing, I noticed the cabin rate goes to 3000fpm when depressurization, that would be very unconformable for people onboard I guess.. When moving to FLT it downs at -500fpm, not great but much more manageable... There is no number on Manual, but I afaik there is no rumor about burst ear eardrum on every 737CL flight then....
  6. With XP's default parking brake system, you can't have parking brake set with brake pedal fully pressed, However it's possible in P3D with FSUIPC, or with Zibo 737. I already got this kind of muscle memory by pressing pedal full in, pull the parking brake then release the pedal, so the current system on IXEG 737 is kinda annoying... I'd like to it works as follows: the parking brake could be set wit both pedals higher than 75%, and will keep engaged all the way you releases the pedal after set, it only resets until break pedal released to like 50%, then require over 75% press on both side to be able to disengage.
  7. Let's hope they are taking time to work on FMC and Autopilot function, as promised before release.
  8. Just made a spreadsheet for calculating landing distance based on QRH data,so far only normal config have done. I know there are some other apps out there, but they sometimes lack some data or use old set of QRH data, so I made my own anyway, and I think it could also be convert to other Boeing type easily. landing distance 733.xlsx All the codes are hidden in the dark, not very elegant but works, seems it could be inefficiency if I try to add NNC part, but anyway....feel free to play around and add your own code/data. I start this project with 733 is because I know IXEG is very good on it's flight dynamics, unlike some other add-ons using the RW data doesn't make sense...But,Wow I didn't expect this.... missed the target by a whole 2 meters!
  9. When loading passengers in the new preflight menu, I noticed that passengers are about 100kg even with wt factor at 1.0, but my company use 74 as average weight per passenger including baggage. I know I can dial down the number to get correct ZFW anyway, but since the new perflight menu already looks really nice, and the Wt.Factor lever is already there, could you just add a function to able it be dialed down to like 0.5? Thanks!
  10. I see this in Quest3 with XP11 once, but after reload the VR (Disable by the button then Enable it back by menu) it disappeared
  11. I just don't think nuke everything and redownload them is the bast way to go... even including the navdata I mean...
  12. ixeg/733/gear/gear_handle_act = 0.5 should do the work. I use FlyWithLua to create a command for that.
  13. 737-300 doesn't support Flaps 10 TO, only 1,5,15 -400 and -500 don't even support Flaps1 for TO.
  14. Hmm, I think I could already do that in FlywithLua, the problem is I don't have much button to spare on something not so time critical. Actually maybe I can just use FWL to hold it for like 5 sec.....But as I remember last time I try to write something like this I find FWL doesn't came with handy timer function like "Sleep.5000" in FSUIPC.
×
×
  • Create New...