Home Fries

Thanks again, IronMike! :thumbup:

Thanks. I originally hooked a waypoint because otherwise NAVGRID was somehow messing with my present position. I don't know if that is because the first times I was entering NAVGRID I was doing so from AC Stab. I didn't really try to duplicate that particular instance. I think I have a repeatable process now.

Just happened again tonight in multiplayer. Pilot had an approach turn stall and crashed, but interestingly enough was able to start the right engine on respawn. However, at taxi time he could not get NWS working at all (checked to make sure we weren't kneeling), so we jumped into another slot. At that point, we couldn't start the right engine. This is just another datapoint. As yet another software developer, you also have my sympathies!

After an evening of flying, I determined that my workaround of selecting a dummy waypoint to protect the present position was actually preventing me from entering the NAVGRID coordinates. Deselecting any active waypoint, then selecting NAVGRID should work. I'm still not sure whether this is a bug, but there you have it.

Ok, I've determined that deselecting a waypoint before selecting NAVGRID allowed me to enter the coordinates. My workaround to protect the present position was actually screwing things up.

That's exactly what I do, and I make sure I have Ground Stab selected. I wonder if my going between the F10 view and F1 while entering the L/L (to get bullseye) is the issue.

I experienced the same issue using the process I outlined in my post on the issue. You're not alone. Do you have a repeatable process for making this work. I select a dummy waypoint before entering NAVGRID so that I don't overwrite my present position, but even then this technique doesn't appear to be foolproof.

@IronMike, Thanks for the quick reply. I was originally thinking the Bullseye from the mission editor for full-time RIOs in multiplayer, as jumping to F10 to copy coordinates can be a pain during preflight (especially when talking on comms with others at the same time, for those like me who have trouble simultaneously walking and chewing gum :D ). However, the idea of adding a special "YY" mission waypoint in the ME in the same practice as DP, HA, IP, etc. would be a welcome feature, and this special waypoint could supersede B/E on the kneeboard. Best,

I have reviewed Jabbers' NAVGRID video many times and have manually entered the Bullseye position in NAVGRID, but somehow I always seem to be updating my present position, or the NAVGRID seems to default to a L/L of 0/0 regardless of my first entry, which makes all references 3000 miles off. Here are my steps following initial position entry and alignment: Select Ground Stab for the TID Select the Datalink drum on the CAP Select NAVGRID (left button 3) Press 1 for latitude, + for North, then the latitude to one decimal place 6 for longitude, + for east, then longitude to one decimal place At this point, I usually see the NAVGRID pointing southeast with no way to change the arc width or orientation, only the number of sectors. The selected position shows the coordinates I just put in, but centering the aircraft on the TID and bugging an object gives a range of 3000nm. I'm not sure what I do to reset this (I think it's switching to A/C Stab then back to Ground Stab), but at that point the NAVGRID coordinates show 0/0 and the second time I can enter it properly. I've also found on occasion that entering NAVGRID will drastically change my present position to the point where TACAN fixes will not properly update the INS (though visual fixes still seem to work). The one workaround I have found to reliably use is to select a dummy waypoint (like DP) prior to selecting NAVGRID. Then any position entry will apply to DP instead of the present position or an existing waypoint. I have also found after doing this that after entering NAVGRID coordinates, selecting DP (in this case) will show that it defaults to the coordinates I also put in for NAVGRID. So the big question: what steps if any am I missing, or is this a bug?

The Jester wheel is also disabled if AIRIO is installed and enabled.

Now that we have NAVGRID and we no longer need to assign Bullseye to something like DP, it makes sense for RIOs to have B/E coordinates available on the kneeboard. The Waypoint page would be logical, but it is also quite full. However, the datalink page has plenty of room, and since NAVGRID is part of the Datalink CAP drum, this also makes sense from an organization standpoint. Thoughts?

Sorry, BlacleyCole, I didn't mean to add confusion. I wasn't aware you were already using the profile with the Warthog. So this brings up a different issue altogether. Since TARGET creates a virtual controller, every Thrustmaster controller that you have assigned to TARGET disappears in favor of the TM Combined controller. This also means that plugging in a new controller won't add it to TARGET, and unplugging a controller will dump the TARGET profile. Also, TARGET will not recognize a Cougar TQS connected with a TUSBA. Right now, my script is set up so that you select either the Warthog Stick or Cougar Stick, and you have another option to select either the Cougar TQS or Warthog Throttle. These are set prior to launching the profile and right now are mutually exclusive (i.e. you can only use one throttle or the other). I brought up the idea of putting both throttles into the profile a few years ago, but there was no enthusiasm for the idea. I may revisit this idea now that the F-16 is a thing. Putting in support for both the Warthog Throttle and TQS shouldn't itself be difficult, but I will need to introduce some error traps for Warthog+VR users. So BlacleyCole, what is your controller setup? Warthog+Cougar? VR? Are you using USB pedals, or do you use gameport pedals attached to the Cougar? I need to know because I might be able to throw you a bone in 2.43.

This is not as much a tutorial as it is a primer on how to tactically employ the LANTIRN in the F-14B. Enjoy! F-14B LANTIRN Guide - Guides & Tutorials - ED Forums (eagle.ru)

Link 16 is compatible across all Link 16 platforms, but think of it like TCP/IP. You put a computer on a network, it needs an IP, connects with a router, and then through the router can share with other PCs on that network. Datalink is similar. Each unit needs its own unique ID, as well as the ID of the net control unit (the "router"). Then the units need to be on the same radio frequency and share the same crypto. But having all of this, a Link 16 capable unit can join a Link 16 network. Where it gets really complicated is when you have all the other Datalink protocols out there, which differ due to age and function. AFAIK, Link 4 is only used with the Tomcat, and is a legacy link that requires the "gateway", or a multi-link capable platform like the Hawkeye, to receive data indirectly from Link 16 platforms. Then there is Link 11, which is more suited for a surface and subsurface picture but still has aircraft in it...

@imacken, So is it cleared up now? The fact that the Navy and Air Force (and French AF in this case) literally do aspect 180 degrees opposite from each other doesn't help either, but the way I like to look at it is that Aspect means more to you pre-merge and Angle Off means more post-merge. Yes, they're both important, but Aspect is something that your opponent has the most control over, and this is the information that will help you get into the merge in optimal parameters. Angle Off is something you can control with your pursuit course once you're in a turn fight. Angle Off is also referred to as Heading-Crossing Angle (HCA), and I actually like this term a lot better because it better describes what is going on post-merge. When you're in a dogfight, youre not only trying to get your nose on the bandit, but you're also trying to get your nose on the bandit's tail (i.e. being on the same approximate vector as the bandit). A low HCA means a better firing solution and less likelihood of overshoot. EDIT: I saw that someone posted Art of the Kill diagrams earlier. That is a great book that does a good job illustrating the difference between Aspect and Angle-Off in the first chapter. The other thing I recommend is setting up a dogfight with something like a Su-25 (maneuvering, but not a fighter), then practice different pursuit courses and watch how your Angle-Off changes based on how you turn with the bandit.

Since you've been using the Cougar, I'm assuming you're familiar with Foxy and programming the EPROM on the Cougar. TARGET is completely different. You must have the TM controller already plugged in (so TARGET recognizes the device), then you load the profile. TARGET converts your physical controllers into a virtual controller (i.e. different Windows ID called Thrustmaster Combined instead of HOTAS Cougar), and it is this virtual controller that DCS recognizes. So you need to 1) plug in the controller, 2) launch the TARGET profile, then 3) run DCS to configure everything (i.e. import the diff.luas). To get my script to emulate the F-16, you must load the F-16 profile from the available profiles (i.e. most of the DCS aircraft). Read the Setup Guide PDF on how to do everything and it will become more clear.

Fixed costs like R&D and setup are spread across all units, so not adjusting for inflation, price per unit actually goes down the more units are produced. Lack of export (except for Iran) for the Tomcat and Raptor kept the production numbers relatively low, which made them more expensive aircraft than many of their counterparts (e.g. F/A-18 ), lower individual production costs notwithstanding.

I don't think anybody expects Steel Beasts Pro (though that would be awesome), but an expansion of scope (wide and shallow) would be just fine too. Heck, I'd be happy with some training missions for CA.

Sorry, fellas, they're for my virtual squadron. See the link in my sig. EDIT: if there is demand, I can make public the generic (i.e. non-personalized) skins.

The Black Veal Squadron approves this message!

When attempting to download from your website (clicking on the MB-339 graphic) I get the following error: I disabled my script-blocker before the download attempt and still had issues. EDIT: Good to go now!

The graphic has been updated. Just run the updater.

Thanks for the prompt reply, Naquaii. Next question: are there plans to make these buttons export-functional at the very least? This would allow third parties to potentially fill the gap.

The news about NAVGRID got me looking at the datalink drum on the CAP, and in particular the buttons used to submit information to the network (e.g. WILCO/CANTCO and POINT/ENGAGE). Are these buttons functional in multiplayer, and do they work with link 4A and 4C? Also, are these commands passed to Export so they could theoretically be used by something like LotATC? Being able to sort targets using link would be awesome.

Definitely looking forward to NAVGRID! Sure beats dialing up DP/Man and reading bulls off the HSI repeater. On the plus side, though, this technique helped brush off the TACAN point-to-point procedures I learned back in the day to figure out intercepts of aircraft called with bulls.