Lt_Jaeger

If you tic the hot mic box in the config ex Page, hop into the F-14, set the pilot ICS switch to hot mic, everything spoken will be send thrue vaicom / VA which will try to make sense of it and execute commands if they are issued. This is basically the default SP setting, to make use of the hot mic function to talk to jester. In MP / multi crew you might consider to untic, so you are able to have a tea time conversation with your human RIO, all while making sure Vaicom / VA isn't eavesdropping and performing commands not ment to be done. If you need to talk to VA/ VAICOM, press the ptt and issue the command, srs/voicechat is muted until released again.

I will be happy as soon as I can land and take off my favorite plane from the Aircraftcarrier. Make no mistake though, as soon as the E is out, I will take her for a ride. I don't care about all these bells and whistles mentioned, I just want to "fly" the most beautiful ugly plane ever build. For that date chasing. I think it's kinda fun. Sure, I would prefer to have the Modul in my hands sooner rather than later, but I also can wait a little longer, I still have my current favorite ride, the Tomcat, to offer me comfort. That's said, merry Christmas to all.

Imaging it drops today, whole Europe(?) closing down for Christmas tomorrow and something is wrong and the module is not playable for any reason. Would riot describe it right?

For me it is still the same. I did the cold Nellis startup, I could remove and put them correctly, but then I rolled for a meter or two and the chocks, then placed again, were still baked in an odd angle to the wheels. So no changes in that regard.

Too bad your wish did not come true, but for what it is worth, happy birthday.

Run a DCS repair

I summon the Spooks, ehm Ghosts of a happy Christmas

That would be great indeed. I might then see if I can get a xtx

From the manual Because of the way the radar operates the doppler filters it will have two blind ranges. The main lobe clutter (MLC) region which contains most of the ground returns, including those returning with zero groundspeed and is 266 knots wide, centered around own aircraft groundspeed (133 knots slower and 133 knots faster). This is the reason that the radar can be notched as a target with the same relative groundspeed as the ground will also be filtered out. This is however only true for look-down conditions as when the radar antenna looks up into the sky this filter isn’t necessary and can be turned off. If the MLC switch on the DDD panel is in AUTO the radar will automatically turn off the MLC filter if looking more than 3 degrees above the horizon. It can also be turned off manually by the RIO but if the antenna looks down this can make the displays unusable in RWS and TWS as all of the ground returns will be sent to the computer for tracking. In whichever case, with the MLC filter off, the target cannot notch the AN/AWG-9 if it is above the radar. The second filter, and second blind spot, of the radar is the zero doppler filter. This blind area is centered around a closure rate of negative own groundspeed, meaning a target moving away from own aircraft at the same speed as own aircraft. This blind area is a hardware limitation as it is a doppler radar mode it cannot detect targets without a doppler shift. The resulting blind area is 200 knots wide, meaning that a chased target moving at a speed of within 100 knots (+/-) of own groundspeed will be invisible to the radar. This means that when chasing a fleeing target it may very well be necessary to use the pulse modes instead. These numbers are the magic behind most of the broken Radar stuff..... then the "small beam"+ the "computer" of the WCS - there you got it

If you are too slow behind them, the targets get lost in the zero Doppler/MLC Filter. Same thing as notching. That you kill all in STT is due to the C getting active and is looking for a target on it self. If they are close enough together..... . If you do this with an A you will waste the MSL. So all is working as intended, exept the STT thing, but that is a dcs shortcomming.

Did download the mission and was able to see them all and shoot them all. It's a far fetch with the two CANDIDs, since they circle and thus wander twice per circle thru the MLC Filter and thus the AWG9 losing track or better going into memory (You see this in your Video as well (x) on the track.), but since they are nice to the MSL the Phoenix picks them up in active. That thing you declared as the Helicopter is actually the Steerpoint Homebase.

At 06:19 you see that your upper scan limit is something around 44k and the lower around 22k, so there is no way you see the targets Later on, you are waaaay to close to pick them up in the selected RADAR setting. Then there is a thing as a Zero Doppler and MLC Filter, which basically filter out targets with no closure rate. Mashing some unrelated button doesn't help. You are talking about lock. TWS never locks the target, it just paint it while still sweeping the area. Targets 5 miles off the nose, with a 50mile radar setting, will be roughly over your aircraft symbol IF they are picked up. For a symbol in TWS to appear, the WCS has to build a track file, which needs the radar to paint it for what, like 4 consecutive scans(?). TWS sucks in close. That what the pilots mode are for. You should take a look in the manual about beam "sizes". basically, you are trying to poke with a pencil straight ahead, trying to hit a paper ball on the floor. Agreed that Jester lacks the talent to actively looking for a close target, but by 10 miles you as a pilot should take over the radar anyhow and guide it with the whole plane. TLDNR , Radar is fine, you just expect things outside the performance envelope

I don't understand the problem then. The rudder move on the carrier with no pedal movement. That is "normal" even so it shouldn't, but that should be no problem after launch. I had a problem because I screwed up my rudder calibration. I used the tool coming with the MfG Crosswind pedals to recalibrate. I don't know your brand of pedals. They would come either with their own tool or you could try the windows calibration. If there would be anything wrong, you will see it in the cockpit, glancing in v the foot well and look for unnormal actuation of the pedals

Nope, no log. Re-installed 2.5.5 but no joy. Not even starting or showing up in the Task manager. One odd thing so, installing let the old version 2.5.4 still show up in the installed up Tab. 2.5.4 works again.

Had also to revert back, die to the newest version not starting.

Had this today as well, luckily still on deck when I saw the rudder pedals moving. Turned out that the calibration of my rudder pedals was off. Another reason for this might be double bindings. DCS does crazy things if you got multiple axis on different devices, you might check this as well.

PM him in discird, though I think he is out of town in the moment. He will sort your replacement needs very quick, I bet.

Ich habe mein ganzes Elektronik / Schalter Zeug direkt aus China, bei AliExpress bestellt. Man sucht sich ob der oft kuriosen Bezeichnungen einen Wolf und eilig sollte man es auch nicht unbedingt haben, ich finde es lohnt sich aber wenn man nicht nur einen Schalter braucht.

Oh joy, that are great news.

ACLS works fine, exept that it most of the times lead to a bolter. The only problem I see currently, and that might be a Vaicom thing, is, that Jester don't tune the ships data link. Most of the time I have to look in the kneeboard to find the actual frequency and set it. After that, engage AP very quick so the Voice light comes on. After that, it is like in the manual and works like a charm. I just guess that Autothrottle screws stuff up for a save landing.

Weight bug? Did you have a flight suspended before spawning. As far as I know that bug is still a thing and would add what, like 10klbs to the weight. If that happen, there should be some sluggish feeling on the boat as well.

That should absolutely be in EDs hands

Which would lead in the end to do the "Finish" step in the Config GUI. Should be standard anyway, especially after updates / re installs.

Military equipment breaks, especially after getting older and abused, and this most of the time at the most inconvenient moment. Not for any silly reasons spares are kept ready. I think system failures and most important the correct modeling of the subsequent systems is needed. I'm too lazy to learn emergency procedures just yet, because it don't happens BUT l gladly would and also gladly would pass on any silly diddle diddle bomb to get all this. So, bring it on and forget about the outer space star wars bombs and missiles for the time being. Let's break things instedt. Would even like to need to abord a squad mission for a faulty system. Making the decision of the airframe is still save to fly and combat worthy should be part of every flight.

Because older Stuff is Semi Active / Command guidance. To hit another target, there need to be exeptionell circumstances involved. I don't see that moddled in DCS and to insert just a random factor would suck in my opinion. Active Msl are another thing in that regard....