Cameron

Hueyman, Your images suggest that perhaps your CPU is "bored" and constantly waiting for your GPU to catch up, thus you are in some form or fashion GPU bound. This could be for various reasons, chief among them resolution. The data that X-Plane shows in the rendering settings menu for VRAM is not a good indicator at all as to how your card is performing or if it's even struggling. What is your monitor resolution here?

Elements should be fine. Gimp is also a great alternative!

You can assign to buttons. Go into the Joystick Menu and click on Buttons: Adv. From here in the upper right you will see 'custom cmds from plugins' with an empty grey box next to it. Clicking this will bring up a menu, where you will find 'LES' and a list of commands you can assign to your joystick buttons.

Indeed. Looks like Sprint has invested a lot of money in aftermarket hardware for their 'A' variants. It's quite clear in those images that the center pedestal was re-configured quite a bit in order to accommodate that setup.

Peter, I cannot vouch for Sprint. I have never been in their aircraft. What I can tell you is I have sat in the jumpseat of many Saab 340s over the years and have never seen an FMC in any of them except for the B variant. Some A's had added GPS (like a 530), but that's as far as it went. You can certainly look up images on the Internet. Out of the factory, Saab never sold an A with such hardware, and that's a fact.

Can you please post your log.txt file?

Peter, LRN1 is a function of RNAV, which just as in real life, the Saab 340A is not equipped with. Since the real aircraft does not have this we do not simulate it. I do not have any experience with the FMC plugin you are using, so I'm not sure what alternative measures you can take here. Perhaps setting a button on your joystick to X-Plane's command dataref for this will work, but I honestly have no clue.

Peter, Everything you have made in bold is true and accurate per our marketing presented to you. This aircraft is simulated just as the one in real life, so given that, no, a refund is not in order and I am confused as to how you could possibly feel cheated. Thanks for mentioning page 202. This looks to be an oversight on my part after late nights of writing the manual and distinguishing the A vs B variant. This will be corrected. In the meantime the flight tutorial manual perfectly illustrates how to fly this aircraft just as they do in the real world.

If you're looking to clarify that, then your assessment is correct. As usual, when we have more to post we will.

Peter, There's no knob for this because there isn't supposed to be one. Please read the included manuals on how to properly interact with the autopilot system on this aircraft.

Running the standard installer will uninstall your previous version.

Nothing of that nature. That may have been a bit easier to deal with.

I know, believe me. Been battling some health issues, but on the mend. This will be the first place I come back to.

The wait is over, and VATSIM users may now fly under 64-bit! This has been a long time coming and we have really been placing pressure on this as we have dropped 32-bit support in our products at X-Aviation. I'm happy to finally see this public and able to be downloaded. Enjoy! http://www.xsquawkbox.net/xsb/2013/11/xsquawkbox-64-bit-windows-and-mac/

You can do this in whole DSF tiles only, and not in small areas. It's not necessarily an easy task either, and would require you to re-generate the entire mesh from the ground up with your own data. The tool in question is provided by Laminar as MeshTool. You'll likely need to also do some smoothing work in some form of GIS software to ensure the correct areas are smooth around any airports, as MeshTool is a "best guess" tool when it comes to points and where to use them within a particular DSF file.

New purchases are always shipped with the latest.

Goran is entitled to his opinion just as much as you are. You don't have to agree with him for his opinion to be valid, and likewise of your own. To me, the difference is that the tactic appears rather shady. This is my opinion. Liveries should be value added, I think, and help to sell the product itself rather than to drive up the cost of your product. The way these liveries are packaged force individuals into getting multiple packs if they only want two specific liveries spread across two packs. The next thing you know, the customer just paid $20 extra for two liveries...or didn't buy at all because they feel this is a rip off (the beauty of voting with your wallet). I applaud the efforts of those like McPhat and any other third party who wishes to create liveries that make otherwise bland liveries look much better, but to essentially sell 'default' liveries (and to pack your product with four liveries that few people would honestly want) is not exactly consumer friendly. If it works for them, then that's great. It doesn't work for Goran and I, and that's why the Saab was released with over 30 liveries for no additional charge. Is there even a paintkit made available right now for the 757 to get around this?

The biggest difference, Leen, is the amount of time and detail in a product like that of McPhat makes the liveries a worthy buy. They go far beyond that of normal, default paint kits.

You're going to need to contact your original reseller. This is for XA customers. Considering you have a box, I assume the correct point of contact will be Aerosoft.

This really sounds like a lack of reading the manual. Be sure you don't move those power levers above 76%.

Guys, I really don't recommend this on a wide scale. Leen makes sense because he's working on Liveries for both versions all the time. Doing this WILL break your upgrade path in the future to the extent it will not be a smooth process for you (and 1.1 is right around the corner). This is just a solution for someone who is developing like Leen.

Julio, The installer will auto-install the correct version for your computer if you selected your correct video card during the install process.

What do you mean?

This is not a -400.

That's correct, AJ.