Leaderboard

Hi Enrique, please don´t take this as an excuse that our VNAV is not working very well - it should be and we have full intent on fixing it. But I flew the 737 for 10 years, another 6 years of 747-400 and too many years A320... it is a very rare circumstance that I have descended (or seen my FO/CPT use it) using VNAV. Most of the time your routing is not predetermined (vectors, shortcuts) or you are subject to ATC limitations (early/late descent, advised rates of descent). So for me (and many of my fellow pilots) VNAV is a gadget that serves very little practical purpose. I think VNAV is so important to many flight-simulator pilots because they lack the ability to make accurate descent calculations in their head and they also think that it is "cool" to watch the plane glide down all by itself (and then autoland!). I think that is about as cool as using a Tesla´s autopilot when playing a car racing game . Oh and yes - we do eventually plan on making a cargo variant for the 737 (I see the pattern!) Cheers, Jan

Funny, I always hear that the most important issues are the doors, wingflex and holding? Can you guys get your priorities worked out so we can start working on that? Cheers, Jan

Great news Coop! Thanks!

Figured it out. Moved X-Plane to the internal drive and the 733 works. So for whatever reason, it didn't like being installed on my T7 Touch( yet previous version of the 733 worked just fine). But now to figure out why the symbolic link I have to my custom scenery folder doesn't work, but that's obviously another issue outside of the 733.

Just wanted all VR flyers to know that I have spent pretty much the last 3 days with Mmerelles (Manuel from Patagonia, of all places!) to get the plane VR ready. We (well, mostly him) made a vrconfig.txt file and Tom is right now converting a lot of manipulators that gave us trouble to modern and VR friendly manipulators. I know that I said in the video that we won´t support VR control of the thrust levers in 1.31, but it turns out that we will - there will be a "clickspot" on both levers (towards that center gap) where you can grab and push them simultaneously. The only obstacles remaining to flying in VR that I see now are: poor resolution (depending on your headset it can be hard to read exact values off the instruments) inability to access the IXEG pop-out menus (need to do your flight setup in 2D) Need for rudder pedals (you can steer by grabbing the tiller, but for real crosswind operation you would need hardware rudders) Inability to "trim" easily in VR (although you can grab and rotate the trim wheel very naturally in VR, no pop-out handles yet, though) Necessity to return yoke to neutral to engage autopilot (it won´t snap back to neutral when you let go as it would in a real aircraft). We will have a dedicated thread for VR when 1.31 ships to collect feedback and ideas for improvement. Thanks again for helping, Manuel and also a big thanks to Matheson from VrLabs who also gave us valuable insight and helpful hints in making this happen natively. Cheers, Jan

Ok. Here's the official word. The big update will be a paid update for current customers, but it won't be full price. It will have more features than the current version that is available in the store. It will have more systems modelled (working circuit breakers being 1 of them, as part of a newly coded electrical system. However, this is dependant on us getting our hands on the electrical schematics) 100% new art assets. (3D mesh, PBR textures, lighting) Improved flight model (The flight model is likely the only thing that will not be done from the ground up.) If you can find out where you got this information, I would be very interested in visiting this site and finding out more about the person saying these things.

Hi everyone, thanks for the feedback and reports regarding our 1.33 update for the IXEG 737-300. Naturally some things slipped our quality control and some things we simply *** up . Rest assures, we are working on fixing those, for some there are already workarounds. I will post, update and maintain the list here for you - so if you encounter a problem, check it against this list and if it is already known, you can save yourself the time to post (unless you maybe have some further information for us!). Test button for leading edge devices on aft overhead panel does not work Fuel quantity test button does not work Gauge for brake accumulator pressure on modern instrument option always shows 3000psi (steam instrument option works ok). When reconnecting the GPU to the AC buses after they have been powered by the APU or the engine generators, the left bus will not be powered by the GPU anymore. There are several other things not working right or missing (Doors, FMS, Wingflex, etc.), and of course they are still slated for improvement in the future. You can doublecheck your issue against this list: http://forums.x-pilot.com/forums/topic/8526-things-that-are-not-going-to-be-in-v13/ Cheers, Jan