Iain

Aliens!!!!!! You have enabled clickspot markings in your XP options, search for the option in the keyboard commands "toggle of visualization of clickable cockpit area", on my install the key is "n".

Ah ok, but when you see an option for smoother and better performance in XP you have to try it! Anyway, look forward to flying it again later, first flight, Edinburgh up to Sumburgh. I would live stream it but I’m a bit rusty.

Hoi zäme! I just installed this wonderful ac again this morning, first test shows no left hand pop out menu, nothing showing on the ND or HSI etc. Deleted Gizmo (was version 20.xxxxxxx?) and found version 18....no working like a charm. FYI, I googled Gizmo and I think I went to the official site, that site has a bad link to the latest version, and I couldn't find archive of versions there. I found version 18 by clicking a link in Threshold news about a Gizmo release from 2018 and it linked to a dropbox. Maybe worth checking the official website. Congrats on the patch!

It's nice to hear, but I still can't taxi as the brakes come on, and the lights don't work correctly if I fix it. Major updates are good, but small patches are needed also.

Ok, thanks for the clarification.

There really is no news at all? Last patch is coming up on 2 years, I can't taxi and turn at the same time as the brakes come on, editing aircraft files completely messes up the lights. For such a product with known bugs, I would expect some small fixes for things like this to at least keep the aircraft usable. It's not asking for much, FMC re-write is a large task, and most of us understand the complexity behind it, and the challenge regarding the limited time the guy doing that has, completely understandable, but those small bugs that could be dealt with are quite frustrating...unless I am completely underestimating the resources needed to fix them. Hopefully, some small updates soon, the product is too good, Zibo is free, but people like me, want the IXEG improved, which shows that they see the current quality in it and want to support it's development. While I'm here, enjoy your Xmas break, enjoy the time off if you are lucky to get some! Be safe with the fireworks!

Make sure you are not too heavy. Be on speed, ref +5 kts typically Try flaps 30 landings, I find (in the game at least) that flaps 40 behaves much differently, especially in the flare, it can often drop even if on speed. Flaps 30 requires very little pitch up to flare, ground effect works and should prevent a hard landing (but not always) Keep the speed to about 20ft, then cut the throttles, if you always float, try cutting at 50ft, but not higher. Autobrake 2 is fine most of the time, level 3 for runways under 6000ft works for me. Make sure your spoilers are armed. Use reverse (at least idle) after touchdown. Watch guides on youtube, I think Jan has guides for IXEG, or watch some of my landings! https://www.youtube.com/watch?v=fn74haB8xcw A smooth butter landing looks nice but is not always best. Practise makes perfect

Got it! Thanks for the explanation.

Holy thread resurrection Batman! I'm currently flying a TUI 737 from Humberside to Corfu, flaps 15 takeoff, used the full length but got 35ft over the end easy! Anyway, LGKR chart is a VOR approach, minimums at 2000ft, how would you set this up in the IXEG, or simply can not be done due to only having 3 digits. Is this the same story in real life for the -300? Long time since I flew PMDG so can't remember if it has 4 digits. Cheers

I have a backup, but is there a single file that just needs replaced? I hope Jan can update the brakes in the download version. Currently, I switch my rudder to "nose tiller" in the controls once I reach the ramp.

Ok, so what is the best way to repair it, download the aircraft again? Or I might have a backup I can grab the file from. Then the noise wheel assist needs changed in plane maker in order to be able to turn while taxiing, how can I update that without messing up the lights again?

Pretty sure I have the same problem, right and left map lights not illuminating, background light works but when the strip light under the mcp comes on it has not effect. Jan said a while ago to only use 11.26 version of plane maker or it messes up the lights, I used 11.36 thinking it would now be ok but maybe I was wrong. Jan, can you give me some feedback, and let me know how to repair (I guess a fresh install of IXEG?) Thanks iain

I just done a small edit in 11.36, so far everything appears ok apart from the MAP light just to the left of the MCP, it doesn't seem to work. Not sure of this is because of using 11.36, or if it's just a typical buggy light that I sometimes get, maybe due to using UWXP. Other lights seem to work all correctly.

Just a short note to say that this problem came back, I guess due to an X-Plane update. To solve it, the option in planemaker is no longer called "nosewheel spring force", it's now called "right and left brake power to help with steering (middle top)", set it to zero. Not sure if Jan needs to update there download version to reflect this? I don't know if I have broken anything by using planemaker 11.36, but I don't know another way. Cheers Iain

Been busy the last 6 months, new job means more free time so IXEG is getting dusted off and flown again, still loving this little Tin Mouse!

Can you post a screenshot, can you get into the cockpit but then there is an error? I'm sure the team will have you up and running asap.

To be honest, your question is rather vague. What aspect of the single engine handling needs improved? That may help with a possible patch to improve it. I doubt a change of a few numbers will fix it, the developer was a 737 pilot so probably knows if something is off and can probably justify it being like that, my guess being a limit of XP11 or a time limit in developing that part of the flight model.

In the case where vnav isn’t engaging, you can help prevent this during fmc programming. Is sometimes a problem with the fmc design but in my experience is usually human error. Keep your FL realistic, an easy way is to check flight radar 24 and look at a previous flight that flew the route and see what level they used. I do this for short flights like Edinburgh to Dublin, bear in mind our old lady takes a little longer that a nice -800. Make sure that the route is built correctly including sids and stars, review it using the legs page and nav mode plan so you can step brought it. Make sure your pref page is complete and that you activate it. The most important and common reason I can sometimes not get vnav to engage is after you have done all off the above, check the legs page again and you should now see and speed or height restrictions on the right side of the fmc legs page, if any of the waypoints is missing a restriction or an estimated height, the vnav won’t be happy and won’t engage. This can be fixed before or after takeoff but is easier to sort out before takeoff. Missing info can be manually entered or if a waypoint isn’t working out just delete it. Also check that when you try to engage vnav that the aircraft is at a speed and height that it expects ie. the fmc legs says 250kts and 6000ft for the next waypoint but you are at 8000ft, it won’t engage. Vnav works really well for me, in descents too, i usually switch to flt change or vs below 10’000ft anyway but it can work all the way down to the ils. Final tip, for short flights, try a high cost index in the perf page, something like 140, it gives you a nice climb, high cruise etc.

For icing, have a look outside at the wiper blade, if ice is building up on it, switch on the anti ice on the overhead panel.

Almost certain it is the cabin alt warning. Make sure you have setup the air con panel on the overhead panel correctly before takeoff ie. Cruise altitude set Toggle switch to FLT mode Everything else to Auto Slightly to the left is the big dial and the small dial. Check them during your climb, big dial shows the differential pressure, keep it within limits, small dial shows the rate the cabin is pressurizing, should show a positive value to show it's pressurizing. If you get the beeping, sounds like the cabin isn't pressurizing, so the big dial will be in the alarm zone, there is a Alt Horn Cutout button where you can silence the alarm. See pic below (not from IXEG, but is same or very similar).

No reply in all this time! Anyway, can give details on how to fix it later but have a search on forum or google and you will find the answer. Think it’s a file that needs deleted in the IXEG directory.

Guys, friends, Nasa boffins, I have flown every sim since 1985 (I'm 43), Tomahawk, DI Tornado, Gunship all FS series, FSX to death and now XP11 and DCS. I switched to XP11 only because of the IXEG release. I can say that this is the best aircraft out there for immersion, physics, atmosphere etc. Those things are not easy to program, but they are there in abundance. I will admit, I got interested in Zibo, tried it and can honestly say that it's a freeware plane with lots of bells and whistles, but the base is freeware, you feel that and you see it every time you look up at that overhead panel. IXEG is payware, you feel it more than anything and you see it, obviously some bells and whistles are missing, and some VNAV things need improved, but we are flying a classic, things will be broken on classics that are flying today, the shortfalls in this model make you a better pilot in my opinion! I look forward to future updates, free or paid, and wish the developers good luck, and ask them kindly to checkin with any tiny bit of news to keep our heads up

Regarding realistic vs instant refueling, you need to be careful with realistic, the sequence can stop. I often use realistic, starting the fueling before doing other stuff like FMC setup etc, then at the end, check the total amount and off you go. However, the sequence can be broken, I am not sure how, but I am sure it's been discussed in the forum before, something like alt tab to windows and back, or checking something in menu's, correct weather for example, something like that can stop the sequence. I know because I have also had short fuel on flights and sat scratching my head then realised I used realistic fueling to, lets say 12'000kg, then I checked my reply and can see I took off with 10'000kg, so the sequence did stop. Now when I use realistic, I stay in the cockpit and don't do anything apart from cockpit prep and FMC stuff, and check the gauges and the FMC prog page to check final fuel amount...then tell the pax that the wx has changed and we need more...haha. To add, I adjusted the landing gear parameter and it works perfect, might be worth making that a sticky? Cheers Iain

Hi Jan Yeh, off topic, but very good info, so you can confirm with WED 1.8 that I will become addicted to it Look forward to it, like I said, I tried WED a few weeks ago, but with limited time to learn I had to put it aside, sounds like a nice winter project PS, I adjusted the landing gear value in planemaker, will try it later, flight will be my new location for real world ops with Norwegian, JFK and Fort Lauderdale to TFFR & TFFF (Caribbean area), interesting place to fly.

Hi I looks like your cockpit view is being blocked by the seat, which could happen if your head movement goes backwards during climb out. Normally you would need to move your head over the seat as it's a solid object so it's quite unusual for that to happen, unless you have your aircraft config set to non solid, which some people do (like myself) to allow for better camera movement. Try changing the time of day so you can see what's going on, you can change time of day with a keypress, also try moving your camera forward or up and forward to unblock your view. Of course, it could be something else completely! Good luck.