All Activity

Man, its a shame this project never materialized into what it was supposed to become. I used to love flying the ixeg in xp11 and had high hopes it would be completed. Every now and then I check back on this forum to see if anything has changed and unfortunately still nothing. Xp12 is looking seriously good these days, I just wish the ixeg 737 was up to par because it has huge potential.

Dear all, I just upgraded my PC with a Tobii Eyetracker 5 However, as long as the Tobii is active, I cannot walk aorund in the FBO or around the aircraft by using the WASD keys. They don't do anything. Up to now, the only solution I found was to deactive the Tobii Plugin as long as I want to use the WASD keys. Is there any other solution beside this? It's quite complicated to turn it on and off all the time using the plugin manager Thank you in advance for your help! BR Thomas

That looks very well flown!

Apparently, I have the same problem. The batteries and tanks are empty. In the interface guide, I can't fill the batteries or tanks. Ground equipment and settings work, though. And I have no idea what Rosetta is! However, I use Windows as my operating system.

Yes, this is what we have been waiting for. Expect nothing until sometime after 12.3 is final. The radar itself does not warrant the deployment of an update.

So then, what about the stuff here: https://www.x-plane.com/kb/x-plane-12-3-0-release-notes/ Does this have something you can work with for the CL650?

Quite some time ago, but tried it as shown in your video and good enough for me

Will the Laminar G1000 improvements in 12.3 appear in the SR22 G1000?

If you hear nothing from us, assume that the project is not abandoned but no work has been done on it that would warrant us sharing any progress info. If we abandon the project, we will announce this here - so if we don´t - you know it´s not abandoned.

I've flown the B733 a few times since this conversation started back up. Even without any updates, I found the Vnav and Lnav to be incredibly stable. The aircraft, even in its current state, is a lot of fun to fly. There's no harm in giving the developer a gentle nudge requesting the status of updates. The harm here is accusing the dev of completely abandoning the project, which, in my understanding, is not true. In my years of living, and trust me, I've got many years under my belt, I've found that I can generally catch more bees with honey, rather than vinegar.

Can we therefore agree that it would be mutually beneficial if the IXEG team posted status updates from time to time? So that customers don't conclude that the aircraft has become "abandonware" and so there is awareness that issues are being worked on? It's not unreasonable to provide an update every 6 months or so - "Hi guys, the work on version 1.6 is proceeding steadily, our priorities are recoding of the FMS and recording of engine sounds. Lots of work still remains with FMS rework, we've tackled 10000 lines but there is still 600000 to go. This will address some of the VNAV issues of previous versions. We've rerecorded some of the auxilliary sounds. We're hoping to work on some improvements to the cockpit texturing but that's aimed at future updates". The amount of time it takes for a post like that to be collated and written and it'll reduce the backwards and forwards, misunderstandings, wrong assumptions, arguments and offence. People will no doubt say "is there any update" - quote the latest update and say "Our last update remains accurate - work is still ongoing. There is not much else to say"

What gives you the impression the team has shrunk out of curiosity?

everything was fine at start but then I get it fail to engage, the YD works, the bank limit works. do i really miss something?

If I recall in the application there's a feature to export a txt file description, or some such. (However, personally, I just use X-Plane for buttons and axes, as I find the configurable app to be terrible to use.) Good question. Not sure you can. But maybe a question for the authors on the Aerosoft forum. Depressing the buttons should make them appear in white in the X-Plane joystick configuration window. You may have to scroll up and down to find them. I suggest doing any controls configuration or troubleshooting while the aircraft is loaded (use non-persistent mode or a fresh airframe). P.S. Also to not that with the ProDeskSim each lever only supports one physical button, either ATS disconnect or TOGA (the other isn't even wired up).

I set my altitude for the autopilot, use IAS to climb and the plane will level off at the set altitude. I use the VNav calculation on the GTN to determine my TOD and descent rate. I set the altitude bug and descend at the appropriate VS, but the plane continues to descend past the set altitude. Any suggestions out there? Scott

I thought this SR22 aircraft was supposed to start with a FD set at 7 degrees, but I still see 12 degrees when selecting TOGA. Was this fixed?

Latest iteration of the saga. The RXP GTN works when I remove the GTNXI plug in. That plugin is up to date. There is some inter-action between the two that is screwing things up.

Removing the plugins did not help. It got worse. I used to be able to bring the window for the GTN up and operate the GTN from there. Now that doesnt work either. At one point when I removed the RXP GTN from the plugin folder, things worked normally. That doesnt work now either. The window and the panel GTN's are dead. I have re-downloaded the aircraft multiple time without effect. Unless I can find an answer I will have to hanger it.

Update: By deleting my aircraft and reinstalling it, I was able to get the TOGO button to work again. I also had lost the Thrust Reversers. I got them back as well. The only thing I have left to fix is the Autothrottle Disconnect buttons. I even took off the throttles and put them back on again thinking maybe the buttons just don't connect any more. Has anyone had this issue?

Hello fellow simmers, Recently I switched from XP11 to XP12. I downloaded my XP12 compatible X-Aviation planes (MU-2 Marquise, both Islanders, SR22 G1000 and the SR20 Entegra) and did a fresh install, but the SR20 Entegra crashes XP every time; the others don't give any problem. Attached the log file. I hope somebody can help me. Jan W. Log SR20 crash.txt

Thanks. Will give that a try

The arrival fuel on the PROGRESS page is still buggy and does not show the correct fuel. You can use a rule-of-thumb though and calculate your fuel use by assuming that you will need 2400kg of fuel for 400 nautical miles - or 6kg (14lbs) per NM. This is valid for "when at cruising altitude", so you can calculate how much fuel you will use until you arrive at the destination.

We thought about it, but there is a reason why we did not include this. On aircraft without automatic alerting of incorrect barometric setting below/above the transition level/altitude, it is procedure to change the settings separately. For example if you fly at FL 210 and ATC says "descend to 4000 feet, altimeter 1032", the PILOT FLYING will change his altimeter immediately to the QNH setting (so he does not forget and the plane levels of at the correct altitude), but the PNF will only change his altimeter as he passes the transition level (so that if ATC changes their mind and tells you "stop descent at FL190" you have one altimeter set to the correct STD value, still. If we had made the altimeters sync, too - it would be impossible to follow this correct procedure with the sync enabled.

Hi team, I have the SYNC Pilot/Co-Pilot Instruments ticked on the Preferences page however it doesn't sync the baro settings. I still have to action that manually. Is that correct? Thanks in advance. Never mind, it appears to be for the speedbug and altimeter bug settings. Would be handy for baro settings though.