WarriorX

Hi Coolts, I think the trick is the speed, combined with following the procedures. I would try slowing down everything, your channel changes, preset dial changes, and make damn sure you hear that click when you load each preset. Let me know how it goes.

Tutorial is up for the Hung Stores Procedure: http://forums.eagle.ru/showthread.php?p=1142155#post1142155 Feedback as always is welcome, if anything needs changing or correcting, sound off!!

I only knew the answer because after being caught in a trance by the sight of your impressive MidgetPod, the number 291 came into my head as if he was talking to me....I don't think we yet know or understand the full capability of the MidgetPod.

Page 291 in the manual is what you are looking for. There have been some additions to the procedure since that vid I guess. "In addition to using DSMS Inventory to create virtual Training payloads, the other two most common uses for these pages are to clear hung station errors and setting the burst height for cluster bombs. Clear Hung Station. This is a common error when the pilot does not hold down the weapon release button long enough when dropping a bomb. This warning and ability to use the weapon is resolved by reloading the hung station. This is done by: 1. Press DSMS INV (OSB 5) 2. Press the OSB (1 - 11) that corresponds to the hung station. 3. Press the OSB that corresponds to the store class of the hung weapon. 4. Press the OSB that corresponds to the type of hung weapon. 5. On the store page, press LOAD (OSB 9) to reload the station. 6. Press STAT (OSB 1) to return to the main DSMS page. Note: After clearing a hung IAM loaded store, you will then need to reset the power to the station in the STAT page and then reload ALL from the DTS page to make the weapon functional again"

FYI PoleCat, unfortunately I get a server connection time-out on both links.

I wish I could toggle in game between two axis curves....it would be sweet to swtich to the "Smooth Hog" for refueling and then back to "Twitch Hog" for the rest. I just tried the curves on X and Y, and I found out how accustomed I was to no curve when I failed to pull out of a steep gun run with Smooth Hog.

I have seen it. If I had to guess it is a layer just below the cloud base that is rendered differently. You can pass through it many times, effect is the same every time.

Jessi, why are you using the keyboard assignments for throttle movement when you have the Warthog? You should only be using the throttle for engine starts.

"and then hitting APU switch?" No, APU + APU GEN first....then Boost Pumps...etc

Are you guys forgetting the Left and Right Main and Wing Boost Pumps to the ON position? Also, when you do start one of the engines, look at the top left button in the Warning Lights Panel (Caution Panel) It will say something like Eng Start Cycle. When the Engine Start Cycle lamp goes out, you can go ahead and start the second engine.

Wichid...try turning the frequency knobs to the RIGHT of the decimal point, VERY slowly....at least a full second between clicks. Try that and let me know. It is a known issue that Headspace reported.

Wow, what a screw up that was...I will edit it out...thanks for the save.

edited as to not confuse anyone...

effte, if I am reading your problem correctly, you were having problems getting TARS to see your MIC SWITCH UP as a DX button? Well as you already know set the switches on the WH Throttle to default. The thing I had to do, which took a lot of trial and error, was change a setting in the USB Game Controllers menu. To get to it, go to Start, then type in the search box "USB Game Controllers" When the app pops up click on the Advanced button. A window will pop up that let's you change the preferred device to use with older programs. Choose your HOTAS Warthog Throttle, and click OK. You should now be able to have TARS see the DX buttons on your throttle.

Hey bob, I put together a Radio Tutorial. It is based on using realistic radio settings. The link to the Tutorial is below, in my signature.

The words "Transfer Complete" coming over the radio sure sounded sweet! I dont know about you all, but it took probably 9-10 hookup/disconnects to get to Transfer Complete.....I need more practice obviously.

I applaud your work, and that you are offering it for free. I mentioned Helios to provide information, sorry if it seemed in bad form.

So the question is if the Wind Edit part of the LASTE system in the CDU is just a placeholder for future functionality, or if it is just a visual representation of a system? Can we get an answer from anyone at DCS in the know?

Thanks BiPod, thank goodness for the Unit Converter module in AppBox Pro. Im gonna have to keep the iPhone handy during missions for just that reason.

Helios has the whole cockpit modeled, but it is not free, it's $69.00 If you want to check out Helios: http://www.scsimulations.com/index.php/software.html

("MR PERFECT":megalol: Just ask my wife she will definitely disagree with that one..) noticed that you did not switch the AFT and FWD to LEFT and RIGHT on that Coolie graphic

I encourage you all to grab one of the many fine Ramp Start Checklist's floating around here and learn the startup procedure. Many of the switches you interact with during startup are used in Emergency Procedures, so becoming familiar with them will help you when every second counts during a engine flameout for example. I believe you will find it does not take a lot of time to master, and it will add to your appreciation to DCS for the level of detail that they put in to this.

Regarding units of measurement when entering wind altitude levels and speed, if we have chosen Imperial Units of Measurement in the Options, do we need to convert the data provided in the M/E and the mission briefings before entering it into the LASTE?

Your Coolie Hat graphic needs to be rotated 90 degrees counterclockwise so that HUD SOI and MSG Peek are aligned with the UP text. I would switch the AFT and FWD to LEFT and RIGHT on that Coolie graphic as well.

I just posted this on the SCSimulations board, but I thought I would repost it here as quite a few here use Helios, and have had this error. I think I just found a way to clear the MFCD Stuck Key error, but I need some of you to help me see if I am right. I cleared it just now by putting my mouse cursor on the stuck MFCD Key in Helios, and then right clicking, then left clicking the stuck key. I may have been holding down the right mouse when I was left clicking multiple times.