DragonSoulkin

Given what the majority of aircraft that people fly, and ground/sea assets used on most multiplayer servers, we need the option to be able to have this "legacy" RWR or this aircraft might as well be an overglorified MiG-15/19, hell the MiG-21 has better SA than the FF-29 during radar use and that's saying something, the F-5 might as well be AWACS by comparison. Plus I soooo love taking off and my RWR won't STFU because every, little, thing, on the damned server is making it think it's being locked.

It's par for the course for ED to give a time-frame on something and almost never follow through with it. Not surprised at all on this one, as much as I'd like to have the proper texture resolution than expanding 2k to 4k to fudge it, don't expect it any time soon or even this year. In fact, don't "expect" anything at all from ED and you'll never be disappointed and then you'll be pleasantly surprised when something pops up that you'd been wanting for ages.

Yup, I've actually created my own keybinds for the Tomcat in the past like the air source switches and creating an axis for the radar altimiter set knob so it should be simple enough to transfer over the RIO keybinds for headtracking to the pilot keybinds to open up the availability. Just didn't think about it beforehand.

Via remote desktop on my friend's computer, I renamed his DCS.openbeta folder in SavedGames and did a cleanup and full repair, launched DCS, and his head tracking tab in Axis Commands is still grayed out and not bindable still. So I uninstalled the Tomcat module, and re-installed it, and it's still greyed out and not bindable. Although, similar to what @Starspeed noticed, I checked the F14 RIO controls and what did I find? You can keybind the headtracking in Axis Commands, just not for F14 Pilot.

Tried that, also had him re-install his tobii software. The problem is it's grayed out like you can't keybind anything in the axis commands for head tracking at all, so resetting to default won't do anything because there's nothing available to fill in, and the weirdest part is all of his other modules are not affected. His tracking works just fine in the F-4, F-16, F-5, just not the F-14s. The only thing I can think of at this point is to have him uninstall the F-14 and re-install it, and if that doesn't work have him do a cleanup and repair.

So I've got a friend who's using Tobii Eye Tracker and with this new update, he's got head tracking available for everything else in DCS, to include the Phantom, but not the F-14s. In his keybinds in other aircraft he has the columns for head tracking filled and functions just fine, but in any of the F14 models, his keybinds for axis commands under the head tracking column are grayed out. Any ideas as to what's going on here and why it's just the F14 that this is happening to and not other airframes?

For a moment, I'm going to ignore the fact that you've ignored my repeated requests as to what manual was referenced in the development of this aircraft, and focus on this particular thing. It would have been appreciative to know in advance that the cost of this module, could include the cost of the NS430, of which I feel is a failure on ED's part as I was not aware I would be having to pay any additional money to try to make this aircraft relevant in modern environments. I feel this is a major shortfall in marketing and consumer transparency and should be placed in the description of the module itself so people can see that if they wan X they're going to have to pay for Y.

Hey I have the NS430 enabled for the MiG-29A but it's not appearing in game, why is that?

At this stage that's not the point, the point is I'm obviously being ignored when I have been on topic with my question after asking multiple times. If they can't release what manual they're using for whatever reason then just come out and f*****g say it already instead of ignoring it.

I'm still waiting for an answer as to what particular manual that is referenced in the FAQ as available on Amazon, is used in development of this aircraft for DCS. At this point it's obvious my question is just being blatantly ignored. Why is this such a hard thing for you guys at ED to answer? Seriously, all I want is to order a copy so I can read up on the material that's directly involved with the development of one of my favorite aircraft and to add it to my collection. For what reason are you keeping that a secret?

I really don't understand what is so difficult about answering a simple question, in a FAQ thread, about information mentioned in the FAQ. What manual, that is apparently available on Amazon, was/is used for the baseline development of this aircraft?

Back on topic, I asked this a month ago and got no response. It's mentioned that the aircraft is being based on a manual available on Amazon, which manual? There's a few of them.

What manual in particular? There's multiple ones available on Amazon.

Who said I was angry? Wasn't me, your interpretation of what counts as anger needs some adjusting bud. Here I'm just pointing out that when a release is planned around a certain time frame that with ED expect it to be much much later than that and you'll never be disappointed. I just don't like being led on and learned to set my expectations of timing really low. Hence why I'm not angry as you seem to think I am. What does make me angry is when people try to disseminate something as superfluous as my emotional state off of incomplete information.

Like I said, can't get upset if you stick with the mindset of "I'll believe it when I see it". I hear switching to summer release, I start thinking maybe next year, then ya can't get disappointed.