_Pv_

Stormy clouds are just part of the turbulent wind and pressure system affecting a wider area, often thousands of miles of it. Typical for where you live where the entire East Coast and Gulf States can be affected by the same system. -Pv-

AS16 and ASCA are designed to work together. ASCA provides the textures appropriate to the season, lighting, geography and intensity of the weather (calm, stormy, overcast, etc.) Without AS16, only the static themes are available, the dynamic themes are not. The static themes however can easily be underestimated. If you have a certain look you expect of the clouds no matter where and when you fly, you can try out the various static themes, find one to your liking and use it all the time. No different than loading a cloud texture set before you fly. You still get lots of variety even with a static theme as you do with all FSX cloud sets because of the seasons, lighting, conditions, etc. CBs with TS, different kinds of cirrus, mix of layers, etc. One of the most outstanding features not discussed much here is something the other texture tools do not do. Load textures on the fly- AS YOU FLY while FSX is running. Among all the static themes from which the dynamic themes draw from is over 150 different cloud textures and cloud types usually not contained with other texture libraries. With AS16 and ASCA working together, ASCA will dynamically choose appropriately from the different theme library sets ON THE FLY. This adds thousands of variations to your flying experience you will never get with static libraries. With that said, the simple way of thinking is you can choose a static library which has the type of cloud appearance you prefer to fly with all the time. This does not mean the clouds will always look the same. Or, you can (with AS16 running) let AS16 dynamically control ASCA's theme switching to provide infinite variety. You may not like every cloudscape generated. We don't always flip over the weather outside our home, but since the dynamic themes are also able to draw from your favorite library (among others) there is the chance you will see portions of your favorite theme once in a while. A "Static Theme" is a combination of various low, mid, and high altitude non-cirrus, a collection of cirrus, and lighting intensity and coloration. A "Dynamic Theme" is controlled by AS16 and is a mix and match of Cloud, Cirrus, and lighting from each of the static themes, not always from the same theme. Since there is no better weather engine than AS16 and there has never been a better weather engine by anyone other than HiFi's Active Sky, there is no reason and no advantage to mixing and matching another weather engine to ASCA's effects. On the contrary, you throw away many of the advantages ASCA provides. -Pv-

It's good Tom you are reaching out to expose your fears so others can care for and encourage you. Soak that up. It's a free gift for you. Regardless of your time left, I pray you are able to tap into a source of comfort this world cannot provide and gifted people can find ways to distract you from disappointment and focus you on accomplishment with your friends, co-workers and family. Your legacy isn't in this time of extreme vulnerability but in your life long service- particularly the hidden sacrifices no one knows about but God. Most of us don't know when we're leaving this planet. That you know is a gift to you and others so you and they can make the best of this time together without the false front of invulnerability we all wear to defend ourselves.. -Pv-

Looks like the domain name is up for sale according to Network Solutions. -Pv-

There is nothing at all unusual about these images. Moon, star, and cloud reflections on the water is a normal FSX effect. -Pv-

I need the Simulation Variable to check the status of the Center-Center2 fuel transfer pump activated using "Set_Fuel_transfer_off", "Set_Fuel_transfer_aft", and "Set_Fuel_transfer_forward". I've not seen any documentation for this feature but the pumps work fine as XML key commands in FSX. If anyone knows simulation variable for the pump status, that would be very helpful. -Pv-

aha... sorry for the incremental thinking and posting. Got it. (A:PRESSURIZATION CABIN ALTITUDE RATE,feet per second) 105 <if{ 3.23 (>K:PRESSURIZATION_CLIMB_RATE_INC) } This effectively set the rate of compensation at 3.23 ft every second of sim time which would be like clicking a gauge once per second, or ~ 30 clicks to get me to the desired change rate of 105 or ~ 6300 ft/min.I see what's going on now. I can effectively use this to create a useful auto pressurization system. -Pv-

Actually the rate is 8.32 ft/sec so without using a switch just to see if I could change it I tried:(A:PRESSURIZATION CABIN ALTITUDE RATE,feet per second) 100 <if{ (>K:PRESSURIZATION_CLIMB_RATE_INC) } This runs on a 1 second loop. Still no rate change.I did the same search you did fsxttcb with no hits.-Pv-

Thanks. I have the FSX Deluxe and didn't have the benefit of the F18 example. Seeing if I can figure out how to set the press inc and press dec rates. Documentation is not much help.By default it's 0008 fps. This didn't have any effect:0010 (>K:PRESSURIZATION_CLIMB_RATE_INC) Rate remained at 0008 -Pv-

Any time you see KEY_ you substitute with K: which is the intended convention in the FS SDKs.so in XML code:1 (>K:PRESSURIZATION_PRESSURE_DUMP_SWITCH) ...which is interpreted as:1(>K:PRESSURIZATION_PRESSURE_DUMP_SWITCH) Activates the pressure dump switch. In testing this switch seems to work. Yes the command is misspelled in the SDK. The above works. Monitoring the following values:(A:PRESSURIZATION CABIN ALTITUDE,feet)(A:PRESSURIZATION CABIN ALTITUDE RATE,feet per second)(A:PRESSURIZATION CABIN ALTITUDE GOAL, feet)(A:PRESSURIZATION PRESSURE DIFFERENTIAL,psf) ... Ive not been able to set these system variables. The goal always stays -2000 and the PRESSURIZATION CABIN ALTITUDE always tries to obtain -2000.-Pv-

I think if you just flew DIR GPS you'll do better than trying to replicate this plan.-Pv-

One of several problems I had with SFP is the limited altitude and speed supported in the flight plan. It's fine for GA and airliners, but Concord and other high altitude/mach aircraft are problematic.-Pv-

In the interest of a full discussion of this topic I'll mention a technique I've been using for years. Unfortunately, I doubt it will be of use to any but a very select few, but has been VERY useful to me.One of the very 1st (if not THE first) add-on software flight planners for FS is simply called NAV (http://nav.consequential.org/) When other flight planners came out shortly after, which were virtual copies of this freeware, the author abandoned the work. I still think it's the best flight planner ever made.One of the major drawbacks is there was never a FS9 database importer for it. Since I've been using every FS version since the beginning, I was able to use the FS2k2 database I created and imported into NAV and continue to use it. Now that I'm thinking about it, I'm considering making this compiled data available on my public site space to download if these is enough interest.NAV has the ability to click anywhere on the map and create "fixes" on the fly which you can then name. This is perfect for adding any kind of waypoint. What is even nicer is NAV's ability to create SIDs and STARs which then become part of the NAV approach and departure databases. When creating flight plans within NAV, these SIDS and STARS can be loaded and unloaded on the fly while creating/editing the flight plan.When I create a new approach or departure, I will use published plates I've collected or downloaded. Using NAV's ability to use the mouse to draw radials on the map with heading and distance readouts, I can then click into place fixes which are very accurate. No need to fly to a location in order to know it's geographical location. Nav has a continuous readout of every coordinate in the world right under the mouse location. Using FSUIPC it also shows your plane location if you want to do it that way. I then give these fixes names and added them to a partial plan which may be only the departure or arrival stage of the plan. I then tell NAV to SAVE this partial plan as a SID or STAR for a particular runway and blam. Every time I click on a runway as the start of a plan, the SID list comes up and when click on it at the end of the plan, the STAR list come up. Click and blam, the waypoint are added to the plan. Another click and BLAM I can try another approach or remove it. I have also added aircraft fuel calculation data (which includes the effect of wind direction and velocity) for many popular aircraft.Around the time the author was abandoning the program, he sent to me a spacial test version of the program which he has not released on his site which has a couple special features I requested. This program has been stable and useful (which minor graphical glitch) but still doesn't not import FS9 BGL data. I don't have permission to distribute this version. I wish the author couple be persuaded to continue the project though I understand why he doesn't.-Pv-

35 fps is SLOW on my machine in FS9. 65-100 is what I typically expect, and I only have an average gaming machine.-Pv-

http://home.comcast.net/~pvarn01/index.htmlUpdated gauges, sound, effects and dynamics in support of the freeware FS9 release of AlphaSim SR-71a. The files on the above server are an update to the "SRa_" collection of files in the AVSIM FS9 library as of June 2009.Please see the included docs and updated HTML manual for more details of the changes and feature usage.I will mention a few items here:1) A new hidden gauge which tracks tire temperature during taxi and roll.2) More uniform and practical throttle power scaling.3) Some gauge bug fixes.4) Increased flight stability.5) Aileron is less sensitive.-Pv-

Recent Shuttle Fleet, update 4.01, STS126 expansion pack for 4.00, etc contain scenarios that will not load and crash with error logs pertaining to ISS model configurations soyus, etc.Any suggestions? I suspect these "all inclusive" installs do not have certain ISS elements in the archive with no doc hints what might be missing.-Pv-

I've been collecting Orbiter Shuttle Fleet "expansion packs" for years. Unfortunately, older ones stop working when files distributed with newer ones are installed. You almost need to install a separate Orbiter every few mission packs. It's way too frustrating.-Pv-

Be aware the above file claims to only apply to C gauges.-Pv-

Now for a variation on that theme, I've been wanting to DETECT the sim rate so I know when it is NOT X1. Advice?-Pv-

I've had the same problem. slash-n \n does not place the following text on a new line. I've resorted to stacking multiple text lines on top of each other.-Pv-

Please take note that some planes have high idle power in real life and constant breaking is required to control taxi once the plane starts moving. Two planes I know do this are the Concorde and SR-71. If your joystick is holding the throttles above idle this should be obvious to you by inspecting the throttle stack and N2 and seeing what happens when you press and hold F1.-Pv-

Regardless of how the model is configured, the AI aircraft uses the settings in aircraft.cfg to control how fast the plane flies at cruise and take-off/landing. Of course if the flight model is ridiculously off, the plane will look funny trying to fly at these speeds. Note also that the AI will use this cruise speed when flying the direct GPS routes programmed for it. So, if the plane is not arriving then it should, this speed is set wrong:[Reference Speeds]// Knots True (KTAS)flaps_up_stall_speed=full_flaps_stall_speed=cruise_speed=-Pv-

The TO/GA setting is controlled by:[autopilot]autothrottle_max_rpm=... in the aircraft.cfg file.It may or may not be set correctly in your aircraft. It sets the maximum N2 which will be used while the TOGA is engaged. This also controls the maximum RPM which the autothrottle will use when IAS or Mach is selected.-Pv-

Many people have this problem. It is often aircraft/panel specific and it can be solved by installing a hidden gauge called "SelectCorrect.xml" into your main panel on all aircraft affected. It also fixes pushback and exit door selection. The problem is timing errors when multi-selecting key combos related to 1,2,3 or 4. The sim gets stuck on 1. This gauge fixes the timing. Another good habit to get into is always tapping BACKSPACE after every command involving zooming, sim rate changes and any key combo pressing involving the 1,2,3 or 4 keys. BACKSPACE tells the sim to stop expecting more key sequence presses. You can find this gauge on nearly all the common file libraries. I have a custom modified version of this gauge I distribute with my mod for the AlphaSim SR-71a freeware which uses less resources than the original and fixes the problem more reliably. The gauge has to be copied into your /gauges directory and your panel file modified to load it.http://home.comcast.net/~pvarn01-Pv-