WarriorX

Hi Sluggo, There is a Radio Tutorial in my sig line. It is set up for Realistic Radio settings, not Easy Communications. It may help you get things sorted.

Thanks! Glad you got it sorted....This is one of the best Forum Communities I have ever been a part of...great people here.

Hi Charlie, Here is what I remember, but it was from a very old thread on this topic, so I am not sure if it is still valid. I wrote it down, because this is what the discussion distilled on this topic. CDU Wind Conversion Process: 1) Convert Mission Editor elevation values from meters to feet. 2) Add 180 degrees to Mission Editor wind bearing values. 3) For Mission Editor windspeed values, you need to convert M.E. provided values of X m/s to km/h for the CDU. (Where X is the windspeed value, provided by the Mission Editor, multiply X by 3.6 to get km/h) 4) Enter converted data into CDU, and test. Someone else will need to chime in on the JTAC/ATC values. Hope this helps.

Hi James! Welcome to the Forums, and the Warthog. I put together this tutorial for entering UTM coordinates into the CDU to create a new waypoint for a JTAC target. The link is in my sig, or here is the direct link: http://forums.eagle.ru/showpost.php?p=1126958&postcount=4 I think you should create the new waypoint (MFCD OSB 9) before entering the UTM coordinate. This may be your problem. Let me know if you need any more help, I will be glad to lend a hand.

I concur.

The box with the XXX's in your DSMS screen is for the GAU-8 cannon round count. The X's mean the gun is not functional, either through damage taken, or random fault. The CBU 105's aborted message may be due to a "quick pickle" or a failure to release the weapon within it's drop envelope. You can not reset a hung 105 IIRC, you have a short 15 seconds (hope I am remembering the right number!) to attempt a re-release after the first attempt. Multiple CBU 105 releases in one pass require multiple SPI's and the time to switch between those SPI's and still be in the weapon release envelope for each SPI.

Hi Swabie! Can you watch this YouTube vid I made on Ground Crew interaction, and let me know if you are doing all the required stuff? The sound came out very low..so please turn up your volume. Don't forget to turn your volume back down when your done! Watch it in HD for best results. Also, in order to contact Ground Crew/Rearm you need to be at an airbase that is under control by your coalition, and is populated with units at the base. I dont know if the training missions met that requirement, as it's been a while since I flew them. Welcome to the forums, and the HOG!

Looks great!...thank you very much for the time and effort you put into this. I use it all the time.

I noticed that also, ver 2.0 the Enfield flight never fired on the SA6 at the airbase. They just called RTB. Any suggestions? P.S. This may be caused by a known and reported bug affecting SEAD action in 1.1.1.0. Hopefully it will be in the Hotfix.

I have had a SA-15 TOR shoot one of my Mavericks out of the sky. This was during the beta, so I dont know if they still can. It was an amazing engagement. Here is a link to the original post:http://forums.eagle.ru/showthread.php?t=63517

I have found that in order to avoid the ground crew yelling at me, I have to do 2 things. First, when I am done repairing and rearming, and am done with the ground crew, I start my APU, then turn on APU GEN. Then I ask the ground crew to turn off the ground power, then I switch the intercom dial back to VHF. Second, I contact the current airbase tower and request engine start>taxi. This seems to satisfy the ground crew.

Why did you not go with the 64 bit version of Win 7 for your new build?

I think the trackclip shows it's true worth in situations where the conditions for the TrackIR camera view are less than ideal. (e.g. Using TrackIR in a room with some IR reflections in the camera view) The fact that many people use headphones for the sake of a mandatory TS3 microphone and the wife does not want to hear a GAU8 rumbling the whole house...means for me, the TrackClip free's me from wearing a hat with hat clip under my headphones. I do agree that the TrackClip needs to be handled VERY carefully. There may have been a few design compromises that were made for the sake of being so lightweight.

Thank you very much for that link! Great pics.

Correct, that behavior is a bug and has been reported, and fixed. Which future patch the fix makes it into however is hard to tell.

Back with 1108, the memory needs of this sim outgrew the memory address limitations of a 32 bit operating system. That is why you are seeing the low setting restrictions. You will notice that the minimum system requirements now show a 64 bit OS. My advise is to move up to Win 7 64 bit, if you want the higher settings.

Let me be the first to say welcome! I encourage you to take on the challenge of mastering this sim, it is a real joy to learn, and this community can't be beat!! There are quite a few existing threads that deal with the learning curve, so do a search for them to get the most opinions and views on the topic. For example: http://forums.eagle.ru/showthread.php?t=72125&highlight=pilots+inbound Your controllers look fine, I would post your PC specs, and consider getting a TrackIR. Glad you are interested, and post some pics of that pit!

There is one more important feature of the Targeting Pod (TGP) that will aid you in finding targets. There are 2 field of view's: WIDE and NARROW, and you switch between them with the China Hat FWD Short or V key. There is also a ZOOM for both WIDE and NARROW field of view by using the DMS UP/DOWN buttons.

Here is what I do to quickly get the CDU to recover from an asterisk error, or off a Z mark point. Just press number 1 for example on the UFC or CDU, then press the top left LSK on the CDU. This will bring up waypoint 1 data, and from there, you can create a new waypoint.

Just in case you want to use the hardware (TrackIR) that you have, you can get another powered USB hub and "daisy chain" it to your existing USB hub.

Here are a few others...

Well if you really want to stretch for some hope for the Apache, it does have a pair of fixed stub wings....so that makes it technically within the "fixed wing aircraft" realm. Mind you, this is completely my personal opinion.

Although 3D is a large part of this driver, there are other improvements as well. Check out the release notes completely before you dismiss it.

http://www.nvidia.com/Download/index.aspx?lang=en-us

Noc, regarding the editing or insertion of a JTAC provided coordinate set as a waypoint, here are your options. First off, you will not find it easy to insert a new waypoint in-between two existing waypoints in your flight plan. The reason is that you would have to edit one of the existing waypoints to make it your JTAC target, and by editing it, you have lost it's original position. The easiest way is to create a new waypoint in your flight plan, and give it a unique name. Then to access it, switch the STEERPOINT dial on the Auxillry Avionics Panel (AAP) from FLIGHTPLAN to MISSION. Then you can cycle to it using the steer point rocker on the UFC. I cover all this process with pictures in my Coordinate Entry Tutorials. You can also use the CDU to create a new flight plan that has just your targets, and then switch between them. Hope this helps answer your question.