deadpool

The secret is to apply a bit of that superglue-grass to the tires then you decelerate at 20g.

Not sure if related, but I do frequently record my flying sessions in DCS using a screen capture software. Recently I would see the whole recording be black (with the exception of the mouse cursor (ingame crosshair, not windows one) showing either immediatly upon launch of mission, or after 30 minutes or so. The game itself played out perfectly well for me. I did a repair and removed third party mods, still persisting.

The TMS aft (boresight) mode is actually quite usable if you want to pick up a visually aquired target with your TPOD. Otherwise it's a huge hussle. But yes, sadly you can only use assigned steerpoints at the moment and not all slots available, while also at the same time having an excuse for a tpod, which means that you should have the coordinates of the original waypoint stored somewhere else (in written form). Irl you would have "fixed" steerpoints, and slew corrections to them. Meaning, you set steerpoint 4 to your target farp or something. and then you can control the tpod to for example 100m south, 400m east. The system will still have original steerpoint 4 saved, but it will have the offset as an additional information. So if you switch to Steerpoint 5, it will be dead on the money, and if you change back to 4, it will give you that + your last offset. To "reset" that offset if you will, you press the CZ button zo "zero" the cursor. Combined with the easy marking system in the F-16 where you can fill additional steerpoint slots with targets either overflow, looked at by TGP, pointed by TDC on FCR, etc. gives you the option to take one steerpoint as an anchor, look around and quickly "mark" and thus save individual targets to your computer. These targets can then be shared via IDM with your wingmen, or they can be used to unleash JDAMs / SDBs on a multitude of targets at once. tl;dr: One everything is running, it will be glorious!

You'll be glad to know that Tacview would even work with ACMI as well ;-P

True. That is the one point where chaff makes sense. In reality you would want to make sure to have little doppler shift to the target, dump out an ample amount of chaff and cause the radar that's painting you to go back to search mode to reaquire you among the mess. Then you want to do an in plane maneuver (split-s or something) that points you at a place where the radar doesn't expect you to be by the time it reaquires, so that the lock breaks. In DCS however chaff is currently working very weirdly. Let A (flying upwards) be the target aircraft, C be chaff and M be the missile flying and steering towards A. Then there is still a change in the depicted situtiation that the missile will turn 90° and go for the chaff, and that's wrong. A | | M | `--- | C

It should see the chaff as target with windspeed doppler shift .. so essentially chaff is in the notch filter immediatly if below horizon or otherwise should be rejected quickly by track integration and doppler shift of the real target.

On that note and because I learnt something more. There is CW. There is PD-STT guidance and P-STT guidance. For the F-14 it will (unless overridden by the RIO) go to a CW mode to give the Sparrow something to home in to. This change in radar mode is detectable for a RWR and it will then most likely tell you loudly that there is most likely a missile incoming. Even though it doesn't detect an active seeker. As for modern variants of the Sparrow they seem to guide in on PD-STT locks (which makes a huge amount of sense) So now the question for me would be, how do things look for the opponents RWR. TWR with FOX3 on the way before pitbull -> large scan volume -> sometimes the RWR would see the F-16 painting it .. SAM with FOX3 on the way before pitbull -> intermittent paints by the radar on the opponent STT with FOX3 on the way before pitbull -> constant pulses from the opponent recognisable by the RWR .. he would now know that you're interested in HIM in particular STT with FOX1 on the way -> should be the same as with the FOX3, right? if there is no change to a different radar mode, then how would the opponent's RWR give you a missile warning. I had the feeling that in DCS i would get a missile warning as soon as someone else would FOX-1 at me. This should be the case for when it's an F-14, but not for a FA18 or F16 in my opinion. Please correct me if I am wrong!

Would be nice if this could be converted to an "indexed" track. Sort of have DCS replay it all once (or potentially even while it's being created ) store a status of the "universe" at regular intervals. Let's say you have a 1h long track file. Right now there is one start and 1h of "additional" data. If DCS was to save the universe in addition to the inputs once every minute or 5 minutes, you could fast forward and go back more easily. This could also be "enriched" after the fact.

I'd just recommend leaving CCRP mode. That's quickest and only requires you to tap MSL STEP button.

Hi Freccia02 .. I'll look into that as soon as I am home. Most likely something odd in the METAR data or potentially the MIZ file. Since the MIZ file isn't kept, please hold on to it should I need some info from that. But I'll go for logfiles first :-) BR, Deadpool

I am not sure if it is correct behavior ( I doubt it ), but if you fire a FOX-3 in STT, it seem that it's not guiding on datalinked updates like in TWS, but instead uses CW illumination of the target, which will make the target aware that a missile is coming. So if you want to slow down their reaction time, SAM or TWS modes are quite useful. Against AI, just use STT, as they will know immediatly when you launch anyhow.

I'd say stick to the ones you can cycle through with your MSL STEP button. CCIP, CCRP, STRF

I know this is not a track file, but this is how it is at the moment, and it's really, really frustrating and doesn't seem realistic at all. I can't be expected to fly formation with the hostile for a minute or so before getting a radar lock.

Right now the whole TPOD isn't close to accurate. Please do not learn any of the stuff "too well" that you currently have to do. There will later be ways to have your weapon computer fire the laser automatically once a certain TTI has been reached. The settings for that will be in the same page as laser codes are currently set.

If you don't mind a staring content, use STT anyways instead of SAM or RWS for a more solid lock.

The F-16 really needs updates. This is a beta of an early access plane. Just release what you have, it can't be worse as it is now. Half broken radar gunsight? Better than none. Just merge everything that's halfway usable into a branch and release it, please. Don't wait until everything is ready and let feature creep set in.

The F-16 is early access and most things don't work satisfactory or in a way that would make it mission capable.

1.) If the image is supposed to be pushed to another device (Android, iOS), can DCS then run in fullscreen still? 2.) Is Raspberry Pi a planned "satellite" next to Android and iOS? My current setup involves me rendering MFDs to a non existent fake screen with mirror drivers for RealVNC installed and then showing those via VNCViewer automated on the MFDs via a Raspberry Pi. I might be able replace it then.

Build this over the course of the last few days. If it helps you guys I am glad. Happy for any pull requests or issues on github. https://github.com/destotelhorus/DCS-WeatherInjector Or if you just want to use it ad hoc without any big hassle: https://dcsweather.dth.rocks/ to get weather into your MIZ file as an online service.

Did you rearm while doing that? There is a defect that if you rearm, it will interrupt INS alignment. It has been reported already.

Affirm. Should *not* drop target.

This is a big negative. Switching from AA to AG obviously drops lock due to changed Radar mode, but switching between NAV/AA/DGFT/MRM does *not* drop target.

That behaviour is not correct, I tried to open a defect thread for it but my track didn't work for ED .. maybe you have better luck.

And it looks like nothing of the heavy stuff was addressed in the long awaited update aside of the sidewinder uncage thing :-(