JakobG

Really nice integration. Looking perfect.

I think that is done through the shaders. Its a dynamic hardware rendering and can't be set directly via an Art Control value.

It would be the best to reports this and your interest in helping directly to flight factor. Send them a mail 757support@flightfactor.aero I am disappointed as well with this product, because its filled with errors and false system programming. I have already reported some issues regarding FMS and Autopilot, which partly cover your observation.

Here is a possible script. Feel free to use it, extend it, modifiy it. Note that this values need to be adjusted for you personal needs. For windows I recommend to use "Notepad++" for editing. 1. Create a file and name it "Atmo.lua" for example 2. Open it with a text editor (recommend Notepad++) 3. Insert above quoted script 4. Save it 5. Copy or paste it to .../Plugins/FlyWithLua/Scripts You can edit the file on the fly and reload the setting in x-plane via the FlyWithLua menu in plugins.

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...

Not now. Laminar has to change cloud rendering and Shaders to achieve such a representation. But we are on a good way towards it. I guess we will see something close to it, within future updates. Or even someone steps up and will develop a complete new wx injector and 3D rendering plugin. Skymaxx Pro is a first step...

Haha. Using them as well since initial release. Nice representation of what I see daily looking up.

Regarding the faulty shadows; its the Shadows Ground dataref. Setting it to 1.0 makes aircraft shadows being rendered false.

Sorry but on Nvudia here. The Shaders provided by Aerosoft Skytool work pretty well. Try to work with the cloud ambient gain dataref, it makes the closer clouds a bit more puffy. Does anybody suffer disrupted shadows of aircraft on ground? Looks like some setting besides shadow lighten is influencing shadow detail as well.

I am loving this stuff... just can't stop flying. See attached picture, This are the setting from tomcat with the Aerosoft Skytools Shaders and Cloud textures...

Thanks... I have already tried some and will write them down the next days, because some need a bit more testing to correctly define their effects, pros and cons.

Can you share your settings Andras?

Got it working with FlyWithLua... unbelievable potential. Just trying and trying.... sometimes things look crazy, but some effects look stunning. Will keep you updated.

Willdo. Just reading through FlyWithLua documentation...

Wilco. Will try that tomorrow... Just thought it needs a special format besides the scripts orders...

Could you guys share such a script? I know FlyWithLua but haven't worked with it by now. regards Jakob

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 one got a bad side effect. Once set to 0, the visibility rendering (flight visiblit) doesn't work anymore, if a METAR reports low visibility. Seems that this ART is connected to the main visibility settings in XPlane.

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