DragonSoulkin

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.

Me sitting here when I initially heard Q2 being planned release "I'll believe it when I see it." Can't get disappointed if you already have the bar so low that you don't believe a single thing that's ever said from any representative of ED about a release date. It does feel like a bit of a slap in the face though when another plane (yes, I get it, it's not an ED product) gets released before this one, without a pre-order, and here we get to see all those people play with their new toy and we're stuck here just watching or flying it just to have something new while we wait. Of course I don't want a botched, bug filled near or completely unplayable aircraft, but I also don't think ED should be getting people's hopes up by putting out a release time-frame if they're not going to hold themselves to it. Just release it when it's ready and stop giving people false hopes on a projected time-frame, and then we reach that time-frame and nothing and then get told some time later, then later later, then later later later, then later later later later.

I'm a livery artist and usually participate in the livery contests so that's probably where most of it went. Freaking dumb how they can't come up with a better way to post your submissions sometimes, the last two they wanted full PSD templates of your works. Any idea how large a Hind Livery is in the templates? That file can get over 50gb easy. And I bet PMs take that space too doesn't it? Wouldn't surprise me that the crap uploaded into userfiles contributes too.

Dunno how I'm supposed to upload a track file when even a couple minute track file exceeds the limit of 37.14kb, what the hell kind of file these days anymore is that small in the first damned place? Freaking dumb, alternative method I uploaded it to my google drive and you can download it from there. https://drive.google.com/file/d/1SSSW2-nd8hY2WLD9sXIsAUSK2MHOK3yG/view?usp=sharing

This is literally the ONLY game out of well over a hundred that I've played on PC that this has EVER happened.

Problem is for me EVERYTHING relating to the radio and ARK are locked and I cannot for the life of me figure out how to unlock any of it outside of random chance that when I spawn in I can use it.

I was just thinking this.

I'm currently trying to resolve this as well, so far adding the exceptions isn't working. Edit: Eventually got it working. Had to run a repair after adding the exceptions to re-install the missing files.

I'm running into a weird intermittent issue with the MiG-15bis. Some days I can click the radio and ARK-5 controls just fine and others neither will respond to any mouse or keybound inputs. The mouse changes when hovering over the knobs, dials, and switches but clicking right or left mouse or scrolling does nothing and I cannot for the life of me figure out what's going on. Is there something somewhere in the aircraft I'm missing half the time or is this a bug?

Heh...no. Steam is fed up with scummy developers and wants to hold them accountable.

Something I'm curious about with the FF MiG-29 seeming to be around the corner finally, how is ED setting up the RSBN beacons? Are they doing the same thing with R_NAV_data.lua files? Or is it going to be something that'll be built-in to the maps and an additional option to put a beacon like we can with the TACAN beacons in the mission editor? And if that's the case will the MiG-21 be able to utilize them? This would just compound the BS that the MiG-21 is just an abandoned module when the MiG-29 can utilize RSBN on all the maps and the MiG-21 can't because it's an abandoned module and won't be getting updated to fill those gaps.

Not just yours, but yes they're in there as well.

Hoping someone has an idea as to what's going on here. I use OMM (Open Mod Manager) and as of a couple updates ago my cockpit mods stopped working. They're just reskins with English labeling instead of Russian/Chinese and they were working up to about a month or so ago. I re-packaged the mods in OMM and they worked and figured I was good but the next time I logged into DCS they stopped working. Any ideas as to why this is happening? The files are all still there in my SavedGames/Liveries folder but DCS is not using them.

Manually clicking "Save State as..." and saving from there also crashes the server.

On our dedicated servers I haven't been able to get this to work. I've got the option selected to automatically save the .sav file upon mission restart or end but it's not saving.