WarriorX

How fast are you going at touchdown? 125-135 knots is optimal.

I agree that the Offset function of the CDU is the best way to manage a bullseye call. Currently there is a known bug that is being worked on, that makes the Offset creation of a bulls call waypoint not viable. The bug I am referring to specifically, changes the pilot's input for bearing by subtracting or adding degrees to the newly created waypoint based on the current Magnetic Variance (MV) value. If the current MV is -6.7 and you enter the bulls call of 250/50 (250 degree radial from bullseye at a distance of 50 nm) You will see the CDU accepts your input of 250/50 correctly, but when you hit the OSB to create a new waypoint, the value of 250 is changed to 244, thus the waypoint is not where the bullseye call is. I have a Tutorial in my sig for CDU Offset if you want to check it out, when the bug gets fixed, making a bullseye call into a working waypoint will be easy.

Here ya go dbeaty. http://forums.eagle.ru/showthread.php?t=74738&highlight=startup+procedure

Are your simped's the USB ones, or the ones that connect via your TM Cougar Joystick base?

The one I suggested is powered. It just does not show in the packaging view. These have worked well for me, I have one dedicated to just my TM Warthog joystick and throttle, nothing else plugged in to it. I agree, that you do not want an un-powered hub.

http://www.newegg.com/Product/Product.aspx?Item=N82E16817111402&nm_mc=OTC-Froogle&cm_mmc=OTC-Froogle-_-Hubs+-+Network+/+USB+/+Firewire-_-D-Link-_-17111402

Try holding your trigger in when you plug the USB into the computer. If I remember correctly, this will re-flash the profile to a default setting.

Hi CaptMorris, welcome to the Forums! Here are a couple of things that may help. http://forums.eagle.ru/showthread.php?t=72125 And there is a Radio Tutorial link in my signature line in this post. Good luck.

Glad to have you new pilot's with us! Welcome. Here are some resources for you that may help: http://forums.eagle.ru/showthread.php?t=72125 ...and there are some Tutorial links in my signature line of this post.

http://forums.eagle.ru/showthread.php?t=74738&highlight=important

Not that I know of, but odds are it will be gone with the installation of 1108.

Known bug in 1107 see here: http://forums.eagle.ru/showthread.php?t=71238 Advise you switch to 1108 ASAP.

Are you sure you have your SPI set to your Targeting Pod? Also, is this a rearmed CBU 105 from a mission where you modified the original load out?

To avoid a hung store, keep the Weapon Release Button or "Pickle" held down until the store comes off the airframe.

BTT for those who recently joined us.

ivanwfr, here is my humble suggestion to really improve TARGET.....remove the restriction in TARGET to 1 Virtual Controller being created in a profile. The main reason is the DirectX 8 axis limit. The reason I ask for this change is because since I run my Simped Rudder Pedals with Toe Brakes through my TM Cougar base, and as it stands now I have to make some serious compromises to include them with my Warthog in a TARGET Profile. Let's take a look at the axis limits as they now stand with the Warthog. You know that the Warthog has 2 axis on the stick, and 5 axis on the throttle. That totals 7 axis combined for the Warthog. This leaves 1 axis left, before we hit the single controller limit of 8 that is bound by DirectX. This is fine, unless you want TARGET to be able to program assignments to let's say your Rudder's Toe Brakes. So what do we do when we have a nice set of rudder pedals that have a set of individual toe brakes? (Like the Simped's that are running through my TM Cougar base right now) This set up has 3 axis, one for the rudder, and 2 for the toe brakes. If we want to use TARGET to control our Warthog and our Rudder Pedals with toe brakes, then we have exceeded the single controller axis limit by 2. Which means, we have to pick which 2 axis we will not add to the creation of our single Virtual Controller in TARGET. This is a shame, 2 perfectly good axis that that you paid good money for, are going to waste if you use TARGET to program them. My suggested solution would be to change TARGET to be able to create multiple individual Virtual Controllers(VC's) in a profile. (1 VC for the Warthog Stick, and 1 VC for the Warthog Throttle, 1 VC for the attached Rudder Pedals). The user created TARGET Profile will then show Windows 3 independent Virtual Controllers instead of just 1. Each VC will still be under the DirectX 8 axis limit easily! Now, if you have a set of Rudder Pedals that are not running through the serial port of your TM Cougar Base, then TARGET is not going to see them anyways. TARGET only will accept TM hardware into it's Virtual Controller creation. (Just a theory, but TARGET's single Virtual Controller restriction, may be the reason TM did not include a set of nice Hall Sensor Rudder Pedals with Toe Brakes with the Warthog).

Bump for new pilot's to 1.1.0.8

I would like to add my congratulations to SickDog for his outstanding work. I would also like to thank SickDog for being so courteous and professional in our correspondence, you are a class act! I am happy to see your well deserved success with the iWarthog app.

Just to be clear, the Predator does do a proper 9-Line, and gives out UTM coordinates. It does not give out a datalink target when it says "Standby Data".

Just ran it in 1108, and the JTAC Predator does not give out datalinks anymore...I think it is due to the Predator is not an EPLRS unit. http://forums.eagle.ru/showthread.php?t=75124 The 9-Line UTM coordinates all work though.

Wow! what scale is that rendered in? Could you please post a link to where you got your toy from?

FYI please check out Paulrkii's outstanding checklist, it may be just what you are looking for! Great job Paulrkii! http://forums.eagle.ru/showthread.php?t=74949

The only change I can see to make in the checklist is really a pilot option. 1108 removed a bug that reset the CDU/EGI when switching from APU GEN power, to L/R GEN run off the L/R engines. This now permits the pilot to start his CDU/EGI alignment earlier in the process, specifically just after APU START, and APU GEN ON. I am usually not in such a big rush that I need to swap these, as I have plenty of things to configure while waiting for the EGI to align to 4.0 0.8. So it's up to you when you start the CDU/EGI. *(be advised, that the CDU INS alignment will show an error message in line 2 of the CDU, if the IFFCC is not in test mode by the time it finishes it's INS alignment to 4.0 0.8 )*

TAIPAN, let me know if you run into any snag's, and we can adjust the checklist. Glad you like it calys, and welcome to the Forums!

A quick search of the Flight Manual for "HARS" brings up pages 109, 116, that are relevant. From my dedicated thread on the subject: "As you all know, 1.1.0.8 is introducing the HARS correctly being the default Navigation Mode when doing a ramp start. It was EGI mode previously. With the HARS mode active, you will not get any FPM/VVI in the HUD, and you will not be able to arm the EAC. If you switch from HARS mode to EGI mode after complete INS Alignment, then the FPM/VVI returns, and you can arm the EAC."