Leaderboard

Parked in Innsbruck

Near Sevilla (LEZL)

A new delivery Straight off the assembly line No idea if Boeing know it's missing yet, not had chance to repaint her Just trying to impersonate a pilot !! So far, it's not going too well lmao Trying to make my escape to KSFO (well, that southerly direction anyways)

Been doing a lot of A320 flying lately!

Dear all, you seem to have discovered a very interesting electro magnetic phenomena, involving microwaves in the radar spectrum hitting metal wires at the appropriate distance and angle, known to cause optical hallucinations with aircrews. Edit: fixed in next patch,

Hello, I created this checklist that might be helpful to others too. You can grab it here : http://forums.x-plane.org/index.php?/files/file/32937-ixeg-boeing-737-300-custom-checklist-pdf-png/ PS: Let me know if there's something silly in the checklist and I will fix that Version 1.2 released: Many additional checks and limits added, still packed in a compact format.

Sound mix bugs are being addressed. The team has been trying to ensure that people with low-end sound cards get an equal experience to those with normal hardware. Getting sofware working is one thing, getting it to work for everyone with every combo of hardware is quite another. All dev machines have no problems at all letting us use as many sound sources as we felt like. (It's nearly all software mixed on our Quad+ Core machines now anyway) Some customer machines seem to have a 16-voice limit so Nils has been reviewing the code to "swap" sounds around between those maximum 16~ active voice. Sadly this means we went from a perfect sound mix to a bunch of sound bugs while we try and pull in support for the lowest end hardware. The dust will settle, the awesome sound mix will return. Thanks for your patience. Known bug: No. It's a hardware feature of the real aircraft. Winglets take up the same physical space as the logo light bulbs so they're simply removed during retrofit. A sticker or label or "something" will probably get added to the switch at some point because this item does catch a lot of our users out. Cheers, br.

I didn't see any other posts with this reference. I've been looking online for this and finally found it, it's like the Holy Grail. I'm not aware of any copyright issues, i.e. it's on Google Docs, so I assume it's legitimate. Enjoy!… https://docs.google.com/file/d/0B06WSw8-Y2wHdXBwY085S0dMOG8/edit

think I have this one fixed. I was able to reproduce the soft crash, fix it, and finally entered the ILS without the crash. A good fix! -tkyler

Well I can't really comment on real life stuff. I'm just a simmer with no real life aviation experience and in the end of the day I have no clue what am I doing Generally I used the included IXEG QRH as a basis for this checklist but I'm currently working on new version expanding it with some more stuff that I'm finding in those real world documents linked in the QRH thread. But again, I don't claim that this checklist is realistic at all. But there are many people around here who have real life experience in aviation so maybe they can comment.

Its a known issue - sometimes the plane boots without any fuel - so the APU dies immediately. This will be fixed in the next patch. Jan

How did you managed to start the engines without doing the short turnaround checklist which starts the APU (and hydraulics) ? Did you start the pushback with ground power & air supply attached ? Anyway it's quite simple really : 0. Start cold & dark 1. Long turnaround checklist (which is like a basic system and electrical setup). The difference between long and short turnaround state is in whether the APU is running or not and you're supposed to decide which turnaround state you want to be in. If long (without APU) then do just the long. If short then do the long checklist but substitute the short items where appropriate. Now obviously you will need to do the short turnaround checklist eventually (before pushback) if you're starting from cold & dark. 2. FMC setup --- at this point I do short turnaround checklist which starts the APU etc. which makes me ready for pushback --- 3. Pushback & startup 4. Taxi & Before takeoff 5. Takeoff & after takeoff -------------------------- 6. Before descent & below 10000 ft 7. Before landing & landing 8. Taxi to gate & parking --- At this point when parked go back to turnaround checklists. If you're going to stay for long time (45 min and more) on GPU (with APU off) do just the long turnaround checklist. If you're going to stay less than 45 minutes (without GPU with APU ON) do the long turnaround as well but substitute the short turnaround items where apropriate (indicated by color and > symbol). The turnaround state (being long or short depending on whether APU will be running) basically resets the aircraft back into a pre-start condition ready for next leg. PS: Dont take this checklist too seriously It certainly is not realistic or even trying to be. It's just a simple straight-forward combination of flow and checklist to help me fly in the sim. For realistic stuff look into the QRH thread :

Well, yes and no. There are several cases where procedures won't draw correctly by the FMS, some of them a general problem with more or less all X-Plane aircrafts, some specific to one or another model, some even specific to the IXEG B733. Let's have a look at those: Freaky (i. e. not flyable in accordance with the chart) procedures just like the one you dug up. This is indeed a very rare case, but with great potential of hitting a lot of aircraft models. Real world limitations. If creators of a model did a good job (and IXEG did!), you will probably hit some limits with procedures you wouldn't be allowed flying with a B733 in real world. This applies mostly to procedures marked as "TURBOPROP ONLY", or RNAV with RNP limits (ok those will work since X-Plane doesn't simulate RNP, you are always on spot where you are...). Procedures where nav data do not properly describe the procedure as per chart. In my flight sim beginnings they were quite common since procedural data quality then was not at the level it is today. Today you encounter this with rather esoteric procedures; I just caught one yesterday, seeing that the LOWS RWY 33 RNAV-V procedure data (at least with NDP) are missing the two final waypoints (ok that one's not sooo esoteric, but also not that frequently used). Programmers stand no chance capturing these errors, even with a sophisticated plausibility test (which would probably deliver more false positives than real issues). Blotted or imprecise nav data. This again is a quite common issue; for instance I would categorize all those virtual waypoints with imprecise fly-by / fly-over tags under this umbrella. Here the nav data allows the programmer to interpret what could be meant. Most issues I dug up with the B733 belong into this category; for comparison I usually check also with the FF B763 - simply because they seemingly coded around this issue and determine correct turn direction in most cases where IXEG doesn't (yet). Incomplete FMS implementation - just have a look at all the payware aircrafts with a FMS out there and count how many of them correctly deal with radial or alt interception, bearing/distance or bearing/bearing intersections, etc. There are more than just a couple only understanding FIX, VOR and NDB waypoints. OK this one doesn't touch IXEG so much; they announced the FIX page will be delivered somewhat later, so no limits on procedure oddities from their side Implementation bugs. Yes, they exist, too. Usually they're hard to find and prove, since you first have to understand the nav data and their correct interpretation. IXEG has made this a lot easier by moving to a very explicit nav data format. Trade-off: you have to scroll a lot in those XML files, but the readability is much better than any other format I came across so far. I only spotted on potential candidate for this category with IXEG yet, where the draft route shows correct routing, but EXEC blows the thing... So for me this boils down to three simple things: Yes, IXEG has done an exceptionally good job on LNAV so far. Nav data for simming purpose will most probably never reach the perfection they would need, so as an aircraft developer, you will hardly be able to avoid implementing some work-arounds for the most common flaws (e. g. the fly-by / fly-over tag issue) For the same reason, as a pilot you have to check what the FMS draws before EXECing it or even (auto)-flying it. When in doubt, fly the procedure as per chart by hand or using other modes (i. e. HDG and/or LOC) for lateral navigation.

Working on it

I also want to confirm the issue. Did some tests and found out that you don´t need to power up the Plane. In Cold and Dark you only need to switch the WX Radar on and the blinking begins, but only in the Cockpit view, not on an Outside view. Removed all Plugins from Plugins-Folder except for Gizmo and removed all Custom Scenery, but it didn´t change anything, blinking is still there. Sven

Working on it

GIT 1.0.4 fixes the issue, go and download it

Curious as to why people are so fascinated by VNAV. Seems like real 737 pilots rarely use it. Seems they either hand fly, or use the MCP. LNAV already takes away the fun of navigating, why have VNAV suck out the fun of planning descents? Tim

Ben's reply was rather long, so I'm going to re-iterate for other readers... Not a bug. The real one doesn't have logo lights when winglets are retrofitted either.

Thanks for the info on ESC Yes, I have heard about the Mac slowdowns due to heat. I'm a recent Mac convert myself, and also have a home-built PC in "mothballs" that I could use (my significant other bought me one of the new 5k Macs in December of 2014, which wasn't cheap either , so I figured the "safest" thing to do was to not use the PC for simming-. Which was also my intro to XP, for the obvious related reason. Now I love both the Mac and XP..... Thanks again, the support here is the best! Bruce

Hiya, The above link still gives the wrong file, but .............. http://forums.x-pilot.com/applications/core/interface/file/attachment.php?id=17923 That link gives the livery just fine Edit : Checked it just, it works fine off that link i posted

Hi, this is correct, the FL CHG mode will switch at a different point than the FMS. I am not sure what the underlying logic or algorithm is, we simply tried to mimic what the real plane does. The FMS switchover is a bit more involved - the FMS knows what the desired "new" speed is, and can switch over at the exact right altitude. The FL CHG has no idea what kind of MACH no. the pilot wants to fly after switchover, so it just does it at a "safe" speed. It´s up to the pilot to catch this switchover and adjust if desired. Jan

http://forums.x-pilot.com/forums/topic/10166-slowing-down-braking/

Why re-invent the wheel? Go to X-Plane Gateway and download LR's 26th April 2016 nav update on their NOTAMS page? If you don't want to apply the whole update you could just edit the existing earth_nav.dat to contain these lines: (Note: Always backup any X-Plane file before you edit anything!). 4 52.16065300 020.98527800 328 10990 18 114.535 WAS EPWA 11 ILS-cat-I 4 52.18056700 020.95416400 328 11030 18 331.880 WA EPWA 33 ILS-cat-II 6 52.17116700 020.95204700 328 10990 10 300114.659 WAS EPWA 11 GS 6 52.15266700 020.98071700 328 11030 10 300331.864 WA EPWA 33 GS 12 52.17116700 020.95204700 394 10990 18 0.200 WAS EPWA 11 DME-ILS 12 52.15266700 020.98071700 394 11030 18 0.200 WA EPWA 33 DME-ILS [Source: 810 Version - data cycle 201605, build 20161503, metadata NavXP810. Copyright © 2016, Robin A. Peel (robin@x-plane.com).]. Note if your using a Custom Scenery for EPWA you may have to "hand tune" the figures to "fit" in with where every the scenery developer decided to place the Rwy. See LR's docs on X-Plane's file formats. Note1: Following the above advice will ensure you can tune the NAV radios in X-Plane to the ILS Rwy33 at EPWA and that the ILS Fan (Arrow symbol) appears on X-Plane's localmap. Note2: You may have to toggle "Shut down tailwind ILS's" if your not landing into wind for that ILS to be ON. Note3: It does not guarantee that every 3rd party FMS/GPS will show/list a Rwy33 ILS as they use different database files. (It does appear on the GNS430 using Navigraphs 1605 data). cessna729.

1. If you want better ground textures in addition to uhd mesh you will need ortho photoscenery. Use uhd as your mesh, with ortho photo scenery on top of it. Then put World2Xplane on top of your photoscenery. Do this and you should have no further reason to go back to 32bit simulation again. Take a look at some of josjjgibbs twitch steams as an example of what your simulator could look like. Default ground textures are terriable in my opnion. 2. As for seasonal textures, I believe there's a company working on them at the moment. However I'm so impressed with w2xp and orthos that I really don't think that I can ever go back to default textures, even if they where seasonal. See SeasonsXP here http://maxx-xp.com/?page_id=23 3. I think this is dependent on the skill of the developer. Have you seen Richard Nunes's SBGL scenery? X-Plane is in constant development. You should keep an eye on the X-Plane developers blog to see what's coming done the pipe. One of the most exciting things I'm looking forward to in 10.50 is better and more static aircraft models at default airports. The nice thing about X-Plane is the default airports are actually worthy of flying in and out of. KSEA and KATL are awesome just to name a few. Default airports are built by the community using a standardized set of tools and textures from Laminar. Keep in mind you need a good computer to get the most out X-Plane 10. Here is a list of specs to get the absolute best out of this great simulator. I7 4970K or better GTX 980 or better 4gb of VRAM is must, recommend Titan X with 12gb VRAM for the very best performance with the most autogen. At least 16gb of RAM, recommended 32gb of RAM... don't be skimpy with this. 960gb or greater SSD for X-Plane and add-ons 460gb or greater SSD for uhd mesh 6tb WD black for all of your photo scenery. Add more WB Black drives as needed but 6tb should be more than enough to get you started. 16zl is sufficient. Anything more than that , you will have a lot of stutters as your HDD works to keep up with the sim. If you have the money then 6tb of SSD with 17zl or greater, but unless you're VFR flyer you want see much difference.

NO its not the 737. But its still my baby when not in my GA's

Yep, too late for that .

Just turning the switch on will not radiate - only when the WXR pushbutton is used, will the weather radar start transmitting... Jan

Sir, Stop being ridiculous. You actually got caught stealing/sharing your software and you already admitted to this. You tried to rub it off a bit by saying it was just someone in your family (in completely different geographical regions, I might add). When you purchase software, that software is for you. If you share it, that's piracy. End of story! We absolutely did have proof, and you acknowledged that in e-mails! You and yottaflopped did not have the same situation. I know of no others complaining but you two, and you're only complaining once caught. No, because we know you were. It's clear as day. We even told you the exact name of the person you were sharing with and you acknowledged it. There is nothing more to discuss here. Don't share products. That's the bottom line.

Hi guys, I justed wanted to say congrats and thank you for this wonderful addon! You really did a great job! I started flying the 737 classic in FS2002 with the dreamfleet 737 (does anyone remeber? ) and since then I always hoped for a 737 calssic like yours! The atmosphere is unbelievable (the sounds, the lighting, the graphics, the symmetry of the flight deck, the....)! I'm an P3D pilot but I only bought myself Xplane, to be able to enjoy your work. And I have to say that it was the best thing I did for a long time in flight simulation! This bird is going to be heads up with PMDG and Majestic as soon as you implement all stuff you listed. And making a thread where you show all the "shortcomings" of a product is just amazing! Such honesty is really trustworthy and I'm happy to support you and your hard work with spending some money on this airplane. I wish every developer would handle things like that. You're rellay a great role model in this part. All the best, (I have to fly it now ) Julian

We have no control over a bank declining a card. This is controlled by the credit card company. Declines can happen for a number of reasons, not just lack of funds, so if in double, I would call your card company and ask them why they are declining. They'll be able to see the transaction and inform you right away.

Boeing 737-236/Adv, reg. G-BGDJ, above Swiss Alps during British Airways' advertisement photo shoot in 1993.

after buying the amazing LES SAAB, SSG 747 and all FLIGHTFACTOR payware......PMDG is the last thing on my mind besides the IXEG 737.....screw PMDG. They're charging over $100 for their P3D 777 with no rebate for FSX owners and they don't even have their own forums....lol AVSIM....yuk!