Cameron

No sir.

Clouds are NOT always blue: http://www.x-aviation.com/catalog/skymaxx-p-101.html <---- These images are unaltered. This is dependent on your settings, including the sky colors AND time of day. Be sure that when you select a new sky color you properly re-load it within sim. No, you cannot change such saturation without changing sky as well. The sim depends on these things as a whole. You can certainly create or download a new sky color set to your liking, however.

You would know if we were.

It is implemented as intended.

Indeed, this is just old SASL developers using past logic that should have been changed back about a year ago but they never updated their manuals, even for the 757. There are no known conflicts.

This would be when CTOT is active. After you've disengaged the "airplane is yours". This will maintain speed based on angle of attack (or adjusting it). You still need throttle power to achieve optimal configuration.

CTOT is not a system to be used during the climb phase; only on takeoff.

This leak does not apply to the Saab. It is for SMP and potentially the CRJ.

No sir.

You don't have to wait. There's ways to avoid the error. A search of topics already discussed here will bring it up.

Likely not, only because SMP is already written (and the likelihood of such data becoming available is next to nil anyhow). This is really a job for a weather injector; something I'm sure will come by someone, somewhere (it's only logical), but not by way of something incorporated into SkyMaxx Pro itself.

Nothing has changed since the last update provided.

The required data to do this is not accessible, so the quick answer is "no" for now.

I don't know of any conflict with SASL. Just the A320 NEO, which the author already created a beta patch for.

That's correct behavior. X-Plane is telling SkyMaxx Pro that the weather has changed in the pocket/area you are flying, and that the weather should change. There's a topic here somewhere on this. If you fly in areas with heavy precip, then fly to an area of a pocket of clear sky, X-Plane will tell SMP to re-draw for the area currently being flown in. We haven't figured out how to tackle this yet for such real weather scenarios.

I think you have a misunderstanding as to how this all works. NOAA (a weather injection app, but using close to default X-Plane real weather standards), tells X-Plane's weather engine what to do. X-Plane's weather engine tells SkyMaxx Pro what to do. The problem with NOAA is the refresh rate at which it updates weather, which will make the pauses more visible. In comparison to something like XSB or X-Plane real weather, NOAA will perform worse. This is not something we can control, as we did not program this NOAA application and how it deciphers when to change weather state (or how often for that matter). I quite clearly stated that from a pause standpoint, we have essentially got the best we can out of this. MOST of our customers who reported pauses now report less than a second to NO pause at all with 1.2, whereas others report better results, but not satisfactory from a personal point of view (read: people like you). I can't offer much for you here other than to say you should try flying without NOAA. You must realize that you're bringing in more plugins to play with one another, and we are not magicians for everything here.

We draw clouds in true 3D, non repetitive form. X-Plane default clouds do not. In 1.2 our draw code was optimized by roughly 75%. I do not anticipate we can squeeze much else out of this. If you have uniform weather in X-Plane I do not understand why you have any pause. It only seems logical if you have real weather or randomly generated, non-uniform weather. There's give and take here, guys.

This "random" re-draw you speak of would be because you are using real weather and X-Plane is communicating to SkyMaxx that it's time to re-draw the scene. SkyMaxx doesn't decide anything. X-Plane does.

Your warning starts now. Quit the attitude or kiss this place goodbye. You've had a knack for snarky responses for quite a while. Think before you speak. I mean it. Calling anyone names for the sake of sarcasm isn't going to fly.

Thanks for the kind words, Ralf! Happy New Year!

Likely to be this. You're asking your computer to do quite a bit more over default scenery with this mesh. I would temporarily remove this scenery and see if that solves things for you.

They are visual. Remove them like you should. We don't plan to simulate something you should take care of when you know you should.

Uh, what? That's not what's in the screenshots.

Read the posts before yours.

Also see this thread of a similar issue on the 777.