bonesvf103

I've noticed from time to time the way the view is with TrackIR changes mid-game. If I turn my head to look at something and stop suddenly, my view stops on a dime. BUt then later when I turn my head to look at something and stop, the view doesn't stop on a dime anymore but drifts past that point and then coasts to a stop. I don't know what causes this to happen but the only way I can get it to stop is to restart TrackIR. I think I may be accidentally hitting a keystroke that causes the behavior, but if I am, I don't know what the keystroke is or the keystroke to get it back to stopping on a dime. Does anyone know or know what's going on? I haven't changed any of my settings in TrackIR either. Thanks. v6, boNes

Yup, on my end, I was referring to it from the Navy standpoint--TA. Manual is here: https://www.cnatra.navy.mil/local/docs/pat-pubs/P-825.pdf Good point on the intercept clarification...although in my usual case I'd be slamming Phoenixes in the faces! v6, boNes

IIRC, you have to designate the point track. If you set point track on an object it merely is tracking it, but it has not designated it as the target. You may have to undesignate the WPDSG first (pinky button) otherwise it will go into offset mode. I'm going off of memory right now so I will need to reverify that but I'm pretty sure that's how I do it. v6, boNes

There is the possibility that the bandit was too close to be picked up by the current radar scan. The radar is like a cone emanating from the nose of the aircraft, the pointy end of the cone on the nose. So very close to the nose, there is very little coverage--a bandit can easily be under or over or to the left or right of it as opposed to 50 miles away where the radar scan zone can be thousands of feet wide and high. There is also the possibility of the bandit being in the notch, not just the 90 degree aspect one, but at a co-speed and altitude where there is no doppler shift so the radar filters the return out. This then depends on your PRF setting. It should not in theory do that in PRF HIGH, but then that mode is not effective less than 25 miles out as much as it is above that. MED mode is susceptible to notch. TWS and RWS are both pulse doppler modes so they would be subject to the notch by default. Now as for using the HUD or the JHMCS--that one should work, provided you are pointed right at the target with it and as long as they are not notching you. Wel, actually i think you still can if there is a notch, just not as easily. But these modes are very narrow scans so unless you see them to know where to point the radar, you might not lock them right away. v6, boNes

Also note that the BRA in the DDi is bearing and range, not heading and range. Bearing is where you are looking, heading is where they are, well, heading. To get the target heading, look at the upper left corner of the DDI and it is there. You can use that to calculate your bandit reciprocal heading for your AWI gameplan. v6, boNes

Thanks for your inputs Tusky. Yes it is good to know that there are more than one method of doing it, some more accurate than others. I prefer the one in the AWI manual (P-825) simply because with the ever fast dynamic nature of an engagement, am I going to be able to do that math under that kind of time crunch and pressure? What if I left my calculator at home? Haha. But yes, if you wanted to go sharpen your pencil and you went right to the pencil sharpener to do it or you did a backflip, crawled further toward it, and then hopped the rest of the way to the sharpener, what difference does that make since you still end up with a sharpened pencil? Well, I guess the efficiency is the difference but still... I actually did not realize that there were the data in the STORES page when STT. I remember that was added on later but either didn't pay too much attention to it or was just set in the P-825 way. Great call about what ASPECT means in that. The ASPECT label in that case is somewhat of a misnomer. Another important thing to consider is drift. You have to take cuts to make sure there isn't drift toward the cold side of things otherwise that means you are intercepting too far ahead of yourself and in all actuality drifting across your target's nose (and WEZ). Of course if the drift is toward the hot side, then he is drifting into YOUR WEZ. I also encourage more discussion about this. It is fascinating to me. I would like to know, for instance, how to employ AWI in the real situation. The manual assumes that the target is non maneuvering, like intercepting a Bear or a tanker or other assets for formup. So the whole gameplan thing based on TA and ATA is all well and good, but what about if your're interecepting a MiG-29 that is hellbent on killing you? Also, it assumes that the engagement will go to the merge. So what happens if you are happily following your gameplan then they fire a missile at you BVR? Now I know there is a timeline that employs MRM in the manual. But when does that get implemented? When you are following the gameplan per the manual but then until you get to NLT than 20 nm then you switch to the timeline? Good stuff. v6, boNes

Follow up: I looked at the MFD data as shown by the other poster where it shows aspect as being 180 deg and that it means the bandit is heading toward you. I just tried it in the sim and although the stick showed straight down in the L&S star (0 TA) the MFD data said 180. This leads me to believe that the MFD data aspect is a angle of the tail angle aspect (the star is angle off the nose). To check this, I placed the bandit so that he had TA 20 off of the L&S star. Sure enough, the MFD data said 200. So it does appear to be off the tail. The pages from the AWI manual above also confirm that TA=0 (off the nose) when the stick is straight down, and this angle off the nose approach is what is used in the AWI manual for intercept calculations and methods. v6, boNes

I think a TA of 180 means the target is heading directly away from you (you are chasing his tail) not toward. Toward would be TA=0 (you are nose to nose). For instance, let's say the bandit is right in front of you and you are heading 360. Let's say he is also heading 360. Bandit bearing=360 Bandit reciprocal heading=180 TA=BB-BR=360-180=180 Thus TA=180 is he's heading away. Let's try it with bandit bearing=0 and you are both heading 360 (or 0) 0-180=-180 which is still 180 degrees, bandit is heading away. Let's try different headings. He is heading 090, you are heading 270, nose to nose: TA=BB-BR=270-270=0. Thus bandit is heading toward you. Recall his heading is 090 so his BR is 090+200-20=270. Now let's try with him off to the left of your nose by say 20 degrees. You are heading 270, he is heading 090. TA=BB-BR= (270-20)-270=-20. Thus bandit TA is -20, or 20 left. And if he was right of your nose by 30 degrees, you are heading 270, he is heading 090 TA=BB-BR=(270+30)-270=+30. Thus bandit TA is +30, 0r 30 left. Don't want to do math? VIsualize it from the DDI and HUD data. In the DDI, the little stick does not show the bandit's heading but rather the bandit's TA. So if you have him as L&S on your DDI and the stick is pointing straight down, that means his TA is 0. That does NOT mean he is headed right for your nose unless he happens to be dead center in your DDI. He can be left of the center of the DDI and if the stick is pointing straight down, that means his nose is on you. It is a common misconception to think that the stick is his heading and so if he was left of center on your DDI with the stick pointing down, one would think that he is flying parallel to you. He is not. It means he is to your left with his nose on you. You can verify this by looking at him in the SA page. You will see that he is heading right at you in the SA page, even though the stick in the radar DDI stik is pointed straight down, giving the illusion that he is flying parallel to you. The way I visualize the stick for TA so I don't need to do the math is the stick shows me where the pilot of the bandit is looking straight ahead. So if the stick is near the bottom right leg of the L&S star, he has to turn his head about 20 degrees to his right to see me. Thus his TA is 20L or left 20 degrees: The same in the NIRD circle. What shows in the NIRD circle is his TA, the same as on the L&S start in the DDI. Interesting to note is there is actually a number of degrees associated relative to the points of the L&S star: v6, boNes

I just noticed this this morning. I used a slider on my HOTAS to bring the wings back to 68 deg as I usually do. Then I opened the cover, popped up the handle, and let the bags deflate. Then when I pulled the wingsweep lever back with my mouse, it would just shake there. It never made it past the spider detent hump thingy. See at 01:29:57 it is stuck: Now, the thing was, this is the first time I flew the F-14A in a while. I had flown the F-14B just before that mission and the lever worked fine there, went into oversweep right after the bags deflated. So maybe it's only an F-14A issue? At 01:18:45 you can see it works: v6, boNes

I've noticed the same issue. The HUD is washed out, even when not going into the sun. in fact, the windshield has a way more green tint than it used to even, making it even harder to see. I have also noticed this on the F/A-18C. v6, boNes

Neat. Now if I can just get my Photoshop to work again! v6, boNes

@winorlose Thanks so much! No problem re: the diagram. This at least confirmed to me that I truly did understand what you were trying to teach. The diagrams were great nonetheless. I'm excited to try this out. v6, boNes

@WinOrLose Thanks for the help, and diagrams! In step 1, I understand the math that gets you 7.5, but where do you get the 60, the 20, and the 1%? And by a half standard turn you mean a 1 minute turn rather than a 2 minute turn, ie, you round a circle in 4 minutes so you are turning at 1.5 deg/sec rather than the usual 3 deg/second? In step 2, did you get 082 because 090-7.5=82.5 which is about 082? In step 3 the ADF shows pointing at near 360 but you said it should point 090, is it pointing correctly? On the point to point, to make sure I understand, the way you described would place you 10 miles east of the runway, heading around 40-50 deg. So you would have to turn hard left to face runway 27. To get to runway 9, you'd have to turn around and come around to the west of the airport before turning back on 090 to land on RWY 9? If we wanted to be 10 nm west of the airport to land on RWY 9, then we would place our desired point left of center on the BDHI (as opposed to right of center as in your diagram), draw our line, then move it up to center to show an approximate heading of 010-020? Then it's a right turn another 80 deg to get 090 for RWY 9. v6, boNes

Thanks. The details on that page are missing in the latest versions, V3b v6, boNes

Can someone post this file again., please? v6, boNes

Per the USAF, FENCE in: Fuel Emitters Navigation Communication Electronic Countermeasures v6, boNes

I've noticed that Jester will hook a target, giving you all that info at the top of the TID, and then he will unhook it presumably doing something else. That is annoying because I need that information and I lose it when he does that. Alternatively, he will hook say lead, and then he switches to hooking trail and leaves it there. I need to know the most information for the #1 target over #2. The other things I wish he would do better is call target clock codes correctly. Most of the time it seems like he has the clock code in a queue as the bandit goes by, and so he calls them off in order which means by the time you hear them, the bandit is already gone. There have been so many times when he calls they are on my six when they are already right in front of me, for example. The only time he is accurate is when I'm straight and level. I enjoy everything else he does though. With a new Jester I'd also look forward to hearing more lines from him, I think I've heard everything he's had to say already haha. v6, boNes

say it with me... "...OOOHHHhhhhhhhhhh!!!!!!" Thanks. v6, boNes

Hi, Everytime I in flight refuel, my total fuel (in front cockpit) always seems to stop at 12200 lbs. Any ideas why? Thanks. v6, boNes

I flew the short version last night and Smoke attacked the Jeep with guns no problem. (I killed the other targets myself). There were some minor bugs though (see my other post). v6, boNes

Hm, yes, I am using VAICOM Pro. Although when I said I told him "Cut Away" I meant my virtual self Flip told him "Cut Away," not real life me. But good to know, I'll try to run without and see what happens. v6, boNes

Nice! Thanks! v6, boNes

Despite it being shown as fixed in this latest open beta update, Mission 2 is still not working for me. Smoke and I hit all the waypoints, we both tanked, we both gossiped about Saint's incident, we both got to WP4 and I told him "Cut away"...and he didn't. So I don't know what is wrong. I'd send a track but don't know where the campaign ones are. I do have video if that helps. Please help! v6, boNes

Some minor bugs in mission 3. You are told to tank with Exxon but there is no Exxon. It turns out the KC-135MPRS which is labeled as Arco is actually Exxon. Also the TACAN as shown in the kneeboard for the tanker doesn't work. Smoke disappears for a bit then reappears trying to tank and then he promptly runs out of gas and ejects. Otherwise, great mission, and I love how you could play it in parts! v6, boNes

I had thought that when VAICOM Pro went open source that there was a wishlist posted, but I don't see it anywhere anymore. So here is somethings I'd like to suggest: 1. Make the VAICOM Pro tabs clickable instead of voice activated 2. Make the voice activation keywords for the tabs actually match the tabs (ie, say "ATC" rather than "Traffic." 3. If you are looking at a non VAICOM Pro kneeboard page (such as an approach chart or mission card) and someone makes a radio call, it always jumps to the VAICOM Pro page. Any way to have it just stay on the page you were looking at? It's really annoying when I'm on approach and the AI calls me on the radio and I lose my approach chart because it snapped to the VAICOM Pro page. v6, boNes