Despayre

That's what I've been doing but it pops up over and over, and then eventually, nothing else happens... I notice it says "object doesn't exist", I'm thinking there's a some trigger that isn't triggering, been up and down the valley, nothing happens, orbited for quite some time too.

No mods, any idea why I'm getting this error as soon as I start to orbit the convoy? null

For reference... all exterior lighting turned to max. nullnull

If you're using VoiceAttack and VAICOM (and if you're flying the 14 solo, I *highly* recommend it, I resisted for about a yr, finally took the time to set it up, and it's fantastic, more immersive too, for sure), try "set TWS MAN" (sets TWS to manual), and then you can tell Jester to "Track Single Target [1-8]". That can also be done with the Jester wheel, but I no longer recall how exactly. Using the voice commands is faster, and obvs, less distracting than using the wheel. So, if you don't like the VoiceAttack idea, you at least know it's possible, time to dig out your F-14 manual.

Not trying to be difficult here, but, doesn't the air get thicker the lower you get, ergo, more resistance for the missile? And if the atmosphere is giving enough friction at 230,000ft, wouldn't that mean there's even more resistance at 50,000ft? (and I guess that would mean the heat is less on reentry at that height because there's been enough braking by then that it simply isn't moving fast enough to generate that much heat anymore?) Also, re: Felix, wouldn't his relative lack of speed, and decreased drag coefficient (from being a much smaller object, travelling much slower), have a huge impact here too? His top speed was "only" 1.25 mach. From NASA, "Typical low earth orbit re-entry speeds are near 17,500 mph and the Mach number M is nearly twenty five"

I would have assumed that too, if IronMike hadn't also posted it at the very beginning of this thread, but ok, thanks.

Anyone else? *tap*tap*tap*... is thing on?! Hello?

We don't have F-22's. (Not officially)

I do not show any missions for the F-14 under Afghanistan... and btw, it would certainly be nice if every new map came with at least *1* flight, even if it's just a free flight with no defined goals. Did this not end up in the patch? Showing: Multithread Preview: 2.9.7.58923

You still have time to finish the entire sentence first.

If you own/use a govt-mandated tracking device cell phone, your entire argument is invalid.

Is it possible to say it's more, or less, than a year away? That would go a long way to avoid the entirely predictable constant weekly "When is..." questions about it (or any other regularly asked issues).

Still shows here. Multithread Preview 2.9.6.58056

Ya, so long tanker, YOU weren't ready pre-contact!

I don't have an answer, only suggestions and observations that might be helpful. I would first suggest looking at the errors above the one that says it can't find part of the path, not only does it say it can't find DCS (I'd try and fix that first), but also follows with several IO level errors. Additionally, and this could just be how it was coded, but I note that all the other file paths do NOT have a set of single quotes around them... making me wonder if it's some dumb network + 8.3 filename violation (the space between "saved" and "games" specifically, and yes, I get how that *shouldn't* be an issue, but, there's clearly an issue somewhere, so might as well start by ruling out the simple things). Also, what OS are you running? It looks a whole lot to me like you're running a linux box... with emulation? If so, there's a billion reasons why this could be broken... Another thing that should make no difference, but linux is way more case sensitive than windows is... your tree screenshot shows drive "x:", but VAICOM is looking in drive "X:"... *shrug* maybe?... And finally, if nothing seems to sort it out, the program is very tiny, I don't see much reason you can't store this in the local drive where it would normally be placed, if that works already. For the mere 50MB is it really worth the hassle of trying to run it from a NAS?

I recall seeing somewhere that the approach is designed for the F-18, so when in the 14, things are a little off. It's not you. Well, ok, it could be you too, but it's not *just* you.

There's already a Jester voice replacement module in the User Downloads section, called "Jest-Her" I think. Female voice. Not bad. Can't speak to 2.0, but I seem to recall that changing the Jester voice was "simply" a matter of creating your own several hundred custom sounds, naming them correctly, and dropping them in to replace the ones that are there, easy peasy! lol...

Not really any preference, I just thought you were under the impression that there was no way to tell them apart. In terms of what I'd like, I would much prefer them to fix some gameplay options over minor cosmetics though, ie, such as being able to bind to air sources so that I don't have to look down to select the Left engine intake when AAR-ing, esp since the coding (a few additional LUA lines) is already done and available (and must be re-applied at every update).

The B does have a few things different inside the cockpit as well, so easily identified as the B, for example, take a look at the Engine Output Display (probably has an official name, but I mean the section that shows RPM, TIT and FF (in the A)). Externally, you can see the different engine exhaust ports to differentiate.

Nothing to add here, just wanted to say it was cool to read a thread where ppl worked the problem, tried to come up with ideas/solutions, and no one's being an idiot... and it's not even my birthday!

Not now, maybe someday. It has been mentioned by HB, but we have not seen it yet.

I know for the F-14, there's an option in Special, that allows you to set the" Radio Menu and PTT behaviour" which allows you to show, or not show, the options. Could that have been reset when you did the repair?

I had a weird thing with the F-4, where every time I pressed my Comms button, the engines would throttle up... (super-annoying when practicing AAR), turned out, my HOTAS was sending a keyboard "+", which was my keyboard mapping for throttle... I removed the keyboard binding, problem went away. Why do you care? Cuz it might be something similar for you. Unless you use them, try removing the keyboard bindings (including the "B") and see if that makes any difference.

This is not normal behaviour. I'm not sure why your speedbrake would come on at an idle at any time. Mine definitely does not do that. Are you sure you're using the right bindings? There's several that are similar, but provide different options. For opening the speedbrake, I use "Speed brake extend", which expands as long as I hold it down, or until it's fully extended, and for closing it, I use "Speed brake retract " which brings it all the way down without any stops when engaged. In the air, or on the ground, no matter what I do with the throttle, if I don't touch my speed brake, it does not move.

I seem to remember that was a change made for... reasons... it used to be done automatically, and at some point they mentioned the totalizer would not be automatically correct anymore... don't recall why.