Andy

This sounds very nice indeed. Good (accurate) sounds provide for a great immersive experience and the added 'promise' of a refresh for this XP classic would really do it justice. This for me was the best XP9 add-on and pioneering work by Javier Rollon, a real labour of love which deserves to be done justice to in XP10, good news all round.

You should absolutely check out http://fred-e.net/x-plane-sceneries/ for some excellent airport layouts for the US. Also Ted's Scenery Updates - http://theosdavis.com/xpfiles/downloads_v10.html - is a good source of US airports. Of course there are hundreds more but that will get you started in the US. That is the beauty of X-Plane, there are many talented and selfless souls who have dedicated a lot of their time and effort to provide us all with payware quality products which are available at no charge. Happy hunting.

The Malacca Straits have featured because the Malaysian military have apparently reported tracking MH370's flight path right across the Malay peninsula - a 90 degree left turn from it's projected course. Unfortunately conspiracy theories abound in circumstances such as these where there are limited facts. I couldn't agree more that primary radar traces should be a starting point to shed some factual, if limited, light on the aircraft's trajectory and to guide the attempted rescue efforts. This is an interesting theory based on factual information (the Airworthiness Directive) that appears to come from a voice of knowledge and experience and could explain the quirky cellular communications - but it's still conjecture. However if the main communications antenna was lost and the plane deviated because of semi-conscious pilots making haphazard decisions due to the accumulative effects of hypoxia then it would be easy to lose track of a large aircraft with enough of fuel on board to fly for thousands of miles out into an ocean. Either way it is all very tragic.

I think we are probably digressing substantially from the OP’s intentions for this thread but since we seem to have strayed into the minutia of aircraft type differences, then from the point of view of a pilot (which is what we simulate with these products) these are absolutely two distinct aircraft (Boeing would not have gone to the trouble of years of designing, developing and building the Classic Series if that were not the case). A pilot of a 732 cannot fly a 733 without completing an exacting transition course, also called a “Differences” course (the clue is in the title), which normally takes three days. There is no point going into what all the “differences” amount to here but with regard to the two products on offer then they are ‘horses for courses’. Any successful flight sim needs a variety of both aircraft types and levels of complexity of any particular type of aircraft. In this case take your pick and I am sure you will enjoy either one - or indeed, both. I honestly don’t believe that FJS are looking for reflected glory from the IXEG product or even necessarily consider that they are in direct competition with IXEG. From numerous comments here and elsewhere their products offer a ‘sweet spot’ of complexity and fun and their 732 will be a very different beast from IXEG’s offering - and not in a bad way. I still wish they had gone for the 707 but hope that the 732 is a stepping stone to that other iconic classic and wish them well. I will be another happy customer.

Rhard, Is this KLN 90B integration only valid for the XP10 version of the JS32? I ask because I am flying the JS32 in XP9.70 and have tried installing this as per the .pdf instructions and overwriting the original files but I get the standard XP unable to open aircraft message and get bounced to the default plane. I have read through a couple of threads but can't find anything which indicates this XP10 only, however there is only one .acf file included in the package which leads me to think us poor XP9 users can't enjoy this add-on. Thanks, Andy

Well I went through a complete reset of the Mac and XP but unfortunately I met with the same fate and exactly the same double assignation of the throttle. So I'm back to where I started. At least with my simple setup it's not too big a deal to reset the axes, although since I'm on XP9 I might just stick with v.1.01 of the aircraft for now to save me the hassle. I plan to upgrade to XP10 in the near future, along with a change of joystick, and just maybe that will change the assignations in XP and it will work. This issue seems more a question of black magic than science.

Morning to everyone and many thanks for the feedback. Javier, yes, as an extra precaution I plugged the Saitek into a different USB port - but reading Woweezowee's reply (a big thanks!) it looks like I will have to try a much more thorough "re-set". I am now rushing out the door but will have a go at this tonight and report back. Andy

OK, I have read the whole Woweezowee story from the sidelines with avid interest as I have been suffering the exact same fate. V. 1.01 of the aircraft worked a treat for me but from the start of v. 1.03 every time I load up the JS32 I get a double assignation of throttle. I have a simple XP setup, I am on XP9 with Mac OSX and a Saitek X52 throttle and joystick, and have followed the aircraft's manual to the letter. I have tried the various advice shown in this thread without any joy. I have loaded up the aircraft with engines running as well as cold and dark with the same result. I have even tried loading it into a demo version of XP10, again with exactly the same situation. This is my joystick config for the default King Air 200: The moment I load up the JS32 it switches to the following: What was the reverse thrust is now doubly assigned as the throttle. As a result I cannot adjust the throttle of the aircraft using the X52 throttle (but I can by moving the reverse thrust lever!). When I close out the JS32 by loading another aircraft (i.e. the default King Air) the faulty double assignation remains and I have to recalibrate my joystick settings - not an arduous task, but frustrating. I have tried unplugging and replugging the joystick and even deleting the XP preferences folder but the problem remains. At present the only way I can fly the aircraft is to activate (turn green) the JS32‘s Joystick Assign option on the control stick menu, reset the assignations in Settings/Joystick, Keys & Equipment menu and leave the JS32‘s Joystick Assign option green whilst I fly (if I change it back to orange the problem reoccurs). Not an elegant solution but it’s all that is available. As I say, it worked perfectly well in v. 1.01 and my preferences haven’t changed since upgrading to v. 1.03. By the way, if I close the JS32 with the “corrected” joystick assignments and the Joystick Assign option green and load up another aircraft (e.g. the default King Air) I get the following result: A different double assignation of the throttle - this time on a "bar" that doesn't even correspond to any axis on my Saitek joystick. Again I have to manually delete the double assignation to be able to fly that, or any other, aircraft. Also if I disconnect the Saitek joystick altogether, fire up XP and then load up the JS32, the Settings/Joystick, Keys & Equipment menu of XP still appears to “recognise" that there is a joystick connected and yet again applies a double assignation to the throttle as follows: In this condition, if I use the mouse to click on the throttle in the 3D cockpit it won't budge. I again have to click on the Joystick Assign option and turn it green before it will work. I am therefore completely bemused by this. I am also intrigued to know how Woweezowee managed to move the position of his 3rd party equipment axis assignations as this sounds as if it might be part of the problem. XP automatically detects which Saitek axis movement is which “bar’ in the Joystick & Equipment menu and I cannot see how I can manually alter those settings. I only have one joystick connected so cannot see how there might be a conflict. Grateful for any advice. Andy