JakobG

First check the order of scenery you have in your scenery_packs.ini (Its in the the Custom Scenery directory). You can open it with any editor (Notepad or similar) and save it as "ini" type again. General order from top to down. 1. Airport Scenery 2. Global Airports 3. Photo Textures 4. OSM Scenery (like OSM simheaven) 4. Library (like OpenceneryX) 5. Other Mesh (like HD Pro or NZ Pro) If you still have objects not in place; download OverlayEditor from Marginal and open the sceney package and add exclusion zones. Refer to the manual of OE. Be aware of: OSM Buildings is exlcluded by "facades" exclusion

Nice find. For your convenience you can create a little script and load it with the modified settings directly on xplane start-up. You need FlyWithLua Plugin for this. It's discussed here as well: http://forum.avsim.net/index.php?/topic/433908-Experimenting-with-art-controls-(Raleigh-scattering)

Laminar introduced an effect, if entering clouds to generate a complete grey/white layer, in conclusion that the pilot might not see anything. This effects is combined to cloud layers and visibility limits. However it also happens when you fly through a layer, which is only partly. So you have a white out, despite the fact you are not or only partly in clouds. They thought to gain rendering power, when in clouds. Since XP is now 64bit, such tricks can be changed in future...

Holy.... That's the way to go.

The Autopilot in the original aircraft has no altitude pre-select function. You need to fly to the level you want, and then hit the ALT button on the AP panel. This requires a minimal change in planemaker. Make a backup of the acf file before. 1. Open the aircraft in plane maker 2. Go to Standard - Systems - General 1 3. Uncheck the "altitude pre-select is always armed" checkmark 4. Save Than the AP works how the modeled system and equals real behavior. You also may be interested in other modifications regarding the Fuel System of the aircraft http://forums.x-plane.org/index.php?showtopic=74275 This modification represents the real system in regard of refilling main tanks, when aux tanks are selected. If you like to upgrade the engine to the 310hp power version (modeled is the 285hp version), you can do following as well 1. Open the aircraft in plane maker 2. Go to Standard - Engine Specs - Descpription 3. Change "maximum allowable power" to 0,310 4. Change "hi idle adjust" to 0,80 5. Change "lo idle adjust" to 0,80 6. Save This changes had been verified by a real C340 pilot. The aircraft has now a bit more power, and taxiing on ground is better now. Regards Jakob

That's odd... Are you saving in the default folder?

I don't use a mac, but with windows, You can hold the right mouse button and than pan around. You can use the arrow keys as well, I think.

You need to write the file name (exactly how you like to name it) into the white field above the cancel button. Than a "save" button will appear... magic.

This is getting better and better. Thx for this update.

I guess I am always in the "descent mode" as I am arriving at the gate. As calling the descent and approach checklist and the call for flaps 1 is something that I'm not forgetting at all. I will have a closer look in the next flights and will report back.

Hallo FS2Crew Support,many thanx for this great product, as it improves the IFLY to a very realistiv level of simulation. I love it.So far everything runs good on my system, but sometimes my F/O won't start the "shutdown flow" after triggering the Engine Fuel Levers into Idle position. He just remains silent and does not touch any switch at all, besideds he should do a couple of things. Is there a logic to shutdown the engines in a certain sequence (1-2 or 2-1) or do I forget something.My procedurs is to arrive at the gate (turning tx lights of in most cases).Than I set the parking bracke and announce to disarm slides via PA.After I see that APU GEN is confirmed on voltometer and FO is ready with his things and reports "ready for shutdown", I cut engine 1 and than engine 2 after a few seconds. And sometimes the FO does not continues his further actions to do, as to reset the Packs and to turn APU Bleed on, and so on and so on. It can be confirmed that he has done nothing with the Shutdown Checklist. Any suggestion would be great:My System:Win7 64bitFS9 9.1IFLY SP1 Rev3FS2Crew version 1.1

You can assign a key via FSUIPC. The FS2Crew Main Panel has ID 1000, so just define a key for the action "Panel Toggle" - "ID 1000". Works perfect with me.