glen.a.williamson

Is it possible to follow and locate the source of an FM signal ( for example 31.0 FM) using the ADF system in the Apache? And, if so, could you tell me how to do so ... what steps are involved ?

Virtually all the answers you are looking for can be found here ... in these basic videos. https://www.youtube.com/results?search_query=dcs+apache+take+off

There are many videos that can help get you started. The official ones posted by Matt Wagner on the Eagle Dynamics channel were quite heplful to me ... as were the Casmo TV, VOLK, and Overkill Simulations Apache websites. https://www.youtube.com/results?search_query=dcs+apache+take+off

You may want to consider "boresighting" your IHADSS first ... to give you your "best shot" at hitting what you are aiming at.

Was your collective all the way down, set to zero ?

Did you remember to raise the trigger guard ?

Once you use the dobber to select "manual" ... are you then hitting the "zero" key (the m-select key) on the UFC to select change from manual to auto ?

Here's what Charly Owl's most excellent Viper Guide has to say on this matter ... ( I believe full normal alignment status may have changed since the above excerpt was written ... It may now be "10 ready" for both cases.) But, it seems that NOT CONFIRMING your Lat, Long, and Alt at the start of your INS alignment degrades the next Waypoint Number and Distance to your next Waypoint ... and the ETA information as well. It seems that the issue of the "ETA and Distance Not Showing on HUD" may not be something the Development Team necessarily needs to get involved in ... it seems the problem may have simply been due to a procedural error, or oversight, by the OP. Hope this helps.

Position NOT Confirmed during Alignment .trkPosition CONFIRMED during Alignment .trk

This may relate to another topic ( ETA and Distance Not Showing on HUD) which has already been locked and referred to the Development Team. I was not seeing the Waypoint Number and Distance to my next waypoint on my HUD .... and ... at first, I thought I had one of the HUD Display switches in or wrong position, or perhaps the system was not working properly. But, then I began to wonder whether I had remembered to confirm my LATITUDE, LONGITUDE, and ALTITUDE within the first two minutes of commencing the alignment of my INS. I went back and started the mission again, doing the whole alignment process as described in Chuck's Tutorial Manual (including confirming my Lat, Long, and Alt during the start of the alignment process) .... and lo and behold ... Waypoint Number and Distance to my waypoint were now shown on my HUD and worked flawlessly. If anyone else is experiencing this type of problem ... I hope this info my help.

+1. On my system the LSO call lag so much that they are utterly useless.

Ramsay, Thank You for looking into this .... your comments make perfect sense. When I first built this mission, I actually DID have my plane starting on the runway. After I flew the mission a few times, I decided to change the mission to a ramp startup instead, so that I could practice the startup procedure as part of this mission. I did not realize that this change would impact the ETAs for the subsequent waypoints ... I guess I mistakenly thought the waypoint ETAs somehow would have been automatically updated by the system when I changed the type of startup. Now that I understand what is going on, I'll go back into my mission and add about 9 minutes to each of my waypoint ETAs, and I believe this should resolve this matter. Thanks again for your time and insight.

I was not able to attach a track file, as it got to be quite huge... but, here are a few image files which demonstrate the problem. As you can see, the first waypoint in my mission has a target altitude of 6,500 feet at a target speed of 350 knots. As I approach waypoint 1, my altitude caret tells me I am roughly at the right altitude; but, even though I am already at 495 knts, the speed caret tells me I need to increase my speed (even though the target speed in only 300 knots). I'm sorry I was not able to attach the track file for this mission; but, here is a copy of my mission file if you want to give it a try. JF-17 Evening Flight to Maykop in the Rain.miz

Thanks uboats ... I appreciate your feedback ... will investigate a bit more than to see what's going on in my rig.

ReyCandy ... Thank You for taking the time to reply. Yes, one of the two brackets seem to be stuck at the top of the scale. My altitude caret seems to be functioning correctly... when I set the altitude of a given waypoint to say 6,000 ft, and then fly toward said waypoint, my altitude caret responds correctly to guide me to the specified altitude. But, if I set the desired speed for the same waypoint to say 300, and then fly toward said waypoint, my speed caret remains stuck at the top of the scale and does not seem to be responding at all. I have even tried running my speed up to 350, or 400 ... and still the darn caret remains stuck, calling for even more speed. Very strange ... a small problem, but one that bothers me none the less.

In my JF-17 installation, the caret which is meant to indicate your desired air speed at a given waypoint does not seem to be functioning. On my rig, this caret seems to be stuck at the top of its range, and never seems to move. Does your desired airspeed caret seem to be functioning correctly for you ?

Procedures in the Harrier seem to evolve with virtually every update. I believe deselecting the TPOD and returning it to INS is now part of the required procedure.

Could your parking brake still be on ?

I personally think that if Razbam or ED were to add that line of code as you suggest, it would lessen some of this confusion considerably. But, If I am understanding correctly what Pikey said in his earlier post above, it unfortunately doesn't sound like that is something Razbam/ED is likely to do.

Some of the information may have been a little off topic ... but, hopefully some of it was of use to you. Glad to be of help.

You may also want to check out this thread for additional information ....

So ... what's the current status ...any potential Buyers todate ?

It was truly a community effort ... a lot of people chipped in to try and assist you with this ... glad we were able to help.

myHelljumper raises an excellent point. Activating the Historical button at the Bottom of the Editor page removes the TARAWA from the list of Ships in the ALL category. You may want to double-check that the Historical mode is not turned on ....

Gerrard ... I really hope the re-install solves this for you . Pikey ... Thanks for putting the art of classification in perspective ... I can appreciate why that can often be problematic. ( Now trying to work up the courage to take a look at the historical mode ... curiosity can be a dangerous thing sometimes ... lol. )