Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 04/26/2019 in Posts

  1. 12 points
    Hello again. I'd like to give another update. During our investigation into updating our NavData to the XP1100 format, it became apparent that this must be the way to go for long-term future compatibility and more reliable route calculations, including holds, but would require a significant rewrite of the FMS base architecture to do so. So over the last 4 weeks, we have done exactly that. We now have the beginnings of a 2nd FMS running in parallel with... but independently of.... our original FMS. We are running 'newFMS' on CDU1 and 'oldFMS' on CDU2. We will NOT be simulating dual FMCs though. This old/new arrangement only exists so we can compare the new with the old while developing the new. It is much like building a new bridge alongside an old bridge...and when the new one is ready, we will remove the old. Much of the challenges we have faced with regards to drawing routes / vnav have been related to the limited nature of the navData format we have used since we began the project. Moving to a format which have been designed expressly for "navigation processing" will go a long way towards easing our algorithm development. The image below shows the two CDUs, both on the "IDENT" page, but clearly displaying differing data as they use differing algorithms/databases....and for those curious, the pilot CDU displays 'odd' formatting simply because we were testing our new display drawing code. We are very excited moving to this new XP1100 format. We have, in 4 weeks, accomplished what took us over 24 months to accomplish originally. Of course we have the benefit of experience, but the elegance and efficiency of the new navData format and architecture allow us to focus on the FMS functionality by orders of magnitude more than before. With the new infrastructure complete, we will begin working on the route editing. The current navData set only supports about 8 different waypoint types. Arcs are not supported, as is common in today's RNAV procedures, but the new format contains all path/terminator types typical in today's procedures. As usual, we thank you for any patience you have managed to muster as we work to improve the IXEG 733. P.S. Jan and myself will be at Flight Sim Expo in Orlando, FL/USA in a few weeks if anyone wants to talk shop. -Tom Kyler
  2. 9 points
    Hello All, This will serve as a formal forum announcement that we have released the version 1.1.9 update for the TBM 900. All customers who have purchased the TBM 900 up till now have been sent an e-mail by X-Aviation with complete instructions on how to obtain your update. We have made this a very simple process! For those that purchase the TBM 900 from today forward, your purchased download will already be updated to version 1.1.9 for you. What if I didn't get the update e-mail? If you did not receive your update e-mail don't fret! X-Aviation has updated our system to allow all customers to update with ease, regardless of whether you received an e-mail for the update! Here's what to do: 1. Login to your X-Aviation account here: https://www.x-aviation.com/catalog/account_history.php 2. Find your original TBM 900 download and re-download the file. It will download as the latest version! The following is a list of additions/fixes included: What's New / Changed: Improvements / New Features: New ground steering model to put an end to the unstable takeoffs & landings. Implemented GPU rental costs. Added hand-towing option to the sidebar drawer. XP11.30 engine changes during startup to produce a lower startup ITT spike. Added inertial separator transition sounds. Pressing TIMER on the yoke automatically brings up the TMR/REF page. AviTab support integrated into yoke-mounted tablet. Tablet now stows in the door pocket. You can still use the USB ports to summon it, but this will be removed in a future update. Reworked pressurization schedule. The system will now gradually change the cabin pressure target as we are nearing the destination, instead of going to it immediately on takeoff. Pressurization won't fling open the OFV fully on landing, but modulate until equalization has been achieved. Corrected high-altitude performance to be within +-2 knots of POH tablets. Implemented configuration-dependent KIAS errors to match POH values. Implemented sidebar drawer smooth animation. AOA sensor failure separated out from AHRS and now individually settable in "Edit Failures" window. Visual configurations window now includes option to use older custom heatblur effect. Expired databases show in amber on MFD splash screen. Replaced G1000 manual link with one for the TBM850 & TBM900. Bugfixes: Battery recharge button in maintenance manager was incorrectly disabled. Restructured battery voltage drop with load to give more realistic red battery voltage indications during start. Fixed CAS message pixel alignment issues. GPH indication on EICAS should properly respond when moving into or out of CUTOFF. Electronic checklist was asking for "FUEL SEL" to OFF in a few places, when it should have called for MAN instead. Gear wear was using incorrect sideslip computation. Rudder propwash force correction could end up taking reverse thrust into account, when it shouldn't. Fixed missing pitot & static covers Low-fuel instability wasn't powerful enough. Fixed prop overspeed on reverse with slow forward motion. Workaround for ReShade bug causing hang in its OpenGL hooks DLL. ODB was missing minimum download speed clamp to abort if the download is slow. Don't try removing the odb directory if it didn't exist to avoid a spurious error log message. glutils drawing wasn't properly disabling vertex arrays, leading to potential crash. As always, thanks for being a customer with X-Aviation. We appreciate your feedback and support! Enjoy these latest updates, and stay tuned to the forum as we continually announce the latest happenings.
  3. 5 points
    Hello All. This post will be locked as its only intended for public statement. While many people are aware of the IXEG Development status, many others will not and so this post is intended to provide clarifying information. For a while now, IXEG development has sat relatively idle. The reasons for this are multiple and have been stated in other forums; however, two significant factors contributing to that idleness have since wained and IXEG are looking at how to best move forward with IXEG updates again. There are two areas we are looking at for updates, 3D cabin/doors/animations and the FMS. Regarding the FMS, IXEG are looking at transitioning to the XP1100 Navdata format, which is derived from the ARINC 424 standard. Moving to this dataset format would yield increased accuracy in the representation of procedures and more practical data with which to improve LNAV / VNAV / performance caclulations. If it turns out that porting our code to the new XP1100 format is too cumbersome in the short term, then we will seek to patch what we have now and transition at a later time. The important thing is that IXEG are moving again to improve the FMS. Regarding the 3D, this will be a bit more of a undertaking. The development tools IXEG used for 3D development are nearly fully deprecated and there has been a major transition to newer tools and methods. This necessitates IXEG reconfigure our source material to the new formats and we have a LOT of 3D material to translate. This means that the 3D updates will be longer in coming than the FMS updates. Once the 3D is ported to the new tools though, any updates we implement thereafter would come much quicker, simliar to what was done shortly after our release for those that recall. We apologize for the idle time and appreciate all our customers and any patience you've exercised. We are sincerely committed to making the most immersive and accurate simulation of this aircraft as we can and will continue to push towards that goal, no matter where its end may be. -Tom Kyler
  4. 3 points
    Lets see how we go 1) Turning it off after takeoff, slowly rotate the setting knob anti-clockwise, then turn off the switch. 2) The auto-coarsen on the A model doesn't actually feather the propeller, just moves it to a minimum drag position. Theoretically if the condition that triggered the auto-coarsen event was to relieve itself, such as a momentary power interruption, the prop will go back to its set position. In order to feather it, the engine failure memory items need to be completed, i.e. power lever flight idle, condition lever fuel off. It's only designed to buy the crew time to deal with it at a safer height, a V1 cut where the prop stays at full fine (max rpm) is lethal if not dealt with immediately. 3) Yes, but safety departments would hunt you down. Always done with the control off a tug, but it is possible providing you don't touch the brakes, the inertia will cause a tail strike. 4) The tiller is connected to the nose wheel, the rudder pedals is connected to just the rudder. Below about 80 kts you won't have enough aerodynamic power from the rudder to turn. 5) You can use brakes, but typically not until reverse has brought the speed below 40kts. So much as breath on the brake pedal above 40 kts with anti-skid inoperative and saab suggests you will blow the main tyres. 6) Don't know, LES version doesn't have that info that I know of, never really looked for it. 7) Max on the ground, take-off and landing, 1230 RPM climb, cruise, descent. 8) Don't know where they are listed in LES stuff, but XP11 engine model was changed not long ago and v1.5.1 has the old XP engine data so half a chance you'll hit temperature limits anyway. Power circa 60-70% Trq / ITT below 850 on the climb/cruise seems to work, Descent, whatever is required to stop the overspeed buzzer annoying the crap out of you....
  5. 3 points
    Well after a couple trips with v1.1.9 all is great! Hats off to the Hotstart Team I even like the addition of the GPU rental charge for $50 in keeping with the realism, and I'm even more happy that I'm not paying for my Jet A+Prist every time I fuel for a trip. On second thought, I haven't received my credit card statement for this month....
  6. 3 points
    Maximum cruise speed of 330 knots dictated by the manufacturer is TAS not GS (Ground speed). Si, if you were getting 314 knots of GS under a 14 knots headwind component your TAS was actually 328 knots. Pretty much exactly what the manufacturer says. So i would think the TBM 900 performance simulatiom from this guys is SPOT ON. Also note the manufacturer states 330 knots under ISA conditions at FL280. So if you are flying higher or lower, and ISA conditions also doesn't match (temperature) it will also impact performance
  7. 3 points
    There is one more important thing to know about "crossfeeding": If you open the crossfeed but have BOTH sides pumps on, fuel will not get evenly burned from both tanks. You would think so - and inititally this was also how the big, official "Level D" simulators that we used for training had it. But they found out in the real aircraft that - since pressures are never EXACTLY the same, the "stronger" side will COMPLETELY "take over". So you yould see that fuel only gets used from one tank, even if all pumps are on and the crossfeed is open. So just like mmerelles said: If you have an imbalance, open crossfeed, turn off the pumps in the tank with less fuel. We used to say "less fuel, less pressure" to memorize this. THEN you need to set a reminder (I used to clip the tip of my tie to the card-holder clip on the yoke! ) because its easy to get distracted and then you suddently have reversed your imbalance. We used to call this "fuel yo-yo" . Cheers, Jan
  8. 3 points
    Hi I must say with the new update the ground handling is much better. Thanks guys for correcting this. For me most of my breakages has been from crashing on takeoffs or landings.
  9. 2 points
    We should hopefully be able to get the VR graphical fix for the synthetic vision working this weekend, otherwise, we may split the update so we can get the other bug fixes (such as this) out!
  10. 2 points
    You are correct, I had the pitot cover on. Thanks! Now that I've figured out the mouse cursor issue, and can actually read my airspeed, I love this thing!
  11. 2 points
    Because IXEG was not about trying to sell you a product with gimmicks to make up for something else it couldn't do. Realistic cockpit simulation is and was the primary concern. To this date there are still essentially no airliners that come close to simulating the actual systems in the way IXEG does. Wing flex is so minimal on a 737-300 it's pretty much not noticeable. Yet another reason why it was senseless to put that as something to focus on rather than the incredible systems simulation that it is.
  12. 2 points
  13. 2 points
    Guys you are awesome! You nail it! Now take off is how it suppose to be! I know sometimes it is frustrating to wait for update, but it was totally worth it. Thank you for listening!
  14. 2 points
  15. 1 point
    Bootsie you are a marvel. this worked now i can start the bird up thanks so much.....Bryan
  16. 1 point
    Yup, worked for me, and the fix removing the smudges, thank you! Still having mouse issues, and it seems that interacting with the RealityXP GTN 750 to change freqs will also make the mouse disappear.
  17. 1 point
    I've never had any problems taxiing the TBM. Even before the latest version, it only became really skittish at higher speeds... now it handles well at all speeds.
  18. 1 point
    Also think such a prominent feature should get higher priority.
  19. 1 point
    A fine addition, thanks for your work on this! Again, we (besides having so much else on our plate that we need to do first) don´t want to really model any of this aspect, because I as an airline employee am under special scrutiny for divulging any security aspects. But if someone else provides something like this, hey, what can I do about it? Thanks, Jan
  20. 1 point
    thanks budd. I just clicked "forget my password" and reset it with the exact same one before. And weirdly, problem solved~
  21. 1 point
    I have find my new password without unusual characters like you said and i have could install my TBM900. Thanks again you save me.
  22. 1 point
    Thank you for the devs hard work! Takeoff and landings are MUCH more manageable now.
  23. 1 point
    then you can code like : if joytsick_x > |0.95| then "no trim" end If you look carefull is not a layer order problem for the FD : the FD in the real aircraft are 0.80% to 0.90% opaque. Not 100%. That's the deal. I'd like to draw 'n add a custom 3D object with static texture for the TV monitor. That would be cosmetic, not functional, (so not simulating security-related functions) but fun to design.
  24. 1 point
    I've already lightened the switches to be more easily seen. I can work with them a bit more, but we're getting into "grey" territory if I do. So in the shadows, they'll be dark and visible, but when daylight hits them, they'll be very washed out. I can work with them a little, but no promises.
  25. 1 point
    Turn off the option "show vertices" in the IXEG side-bar menu. Cheers, Jan
×