DD_Fenrir

Hi Chaps, Any help on this issue would be gratefully recieved. Got this warning after an attempted update: https://support.microsoft.com/en-us/help/4514156/updating-to-windows-10-version-1903-on-devices-with-certain-versions-o So hit the Intel driver link at the bottom: https://downloadcenter.intel.com/download/28656/Intel-Rapid-Storage-Technology-Intel-RST-User-Interface-and-Driver However I've no idea which applies to my hardware. Any ideas?

Ok Mick. It's very situation dependant. RWS (Range While Search) Mode Has longest detection range Has widest/tallest search areas available to the radar Only directly provides bearing & range to a contact (altitude can be worked out roughly by antenna elevation but that's more an intermediate level skill) Cannot ID contacts as friendly/unknown/hostile (in F-14) Cannot generate a track so target aspect/heading unknown Cannot be used to launch/guide weapons Best situation to use: Cruisin' , looking for something interesting. (Generally not a good idea to be in midst dogfight... but never say never!) TWS (Track While Scan) Mode Has shorter detection range than RWS Search areas available to the radar are more limited so as to maintain a contact update of under 2 seconds (needed for tracking functionality) Provides bearing, range & now altitude to a contact Can generate a track of contact(s) so target aspect/heading now is known Can ID contacts as friendly/unknown/hostile Can track multiple targets whilst maintaining scan of surrounding area to improve Situational Awareness (SA) Can be used to simultaneous launch/guide multiple Fox-3 type (Active Radar Homing (ARH); AIM-54 Phoenix, AIM-120 AMRAAM and R-77) weapons Cannot guide Fox-1 type (Semi-Active Radar Homing (SARH); AIM-7 Sparrow, Matra Super 530 and R-27R/ER) weapons Best situations to use: Found something interesting, could be bad guys, let's find out! Is bad guys! Let's engage Beyond Visual Range (BVR) with multiple badass boom-sticks! STT (Single Target Track) Mode Has similar range restriction as TWS Used to lock the radar antenna to Track a Single Target - hence Single Target Track (STT) Cannot track multiple targets simultaneously Cannot maintain scan of surrounding area to improve Situational Awareness (SA) during track of target Can be used to launch guide all A2A weapon types, however... Primarily designed to guide Fox-1 type (Semi-Active Radar Homing (SARH); AIM-7 Sparrow, Matra Super 530 and R-27R/ER) weapons Best situations to use: Run out of Phoenixes! Bad guys still inbound! Pick the most dangerous and lock him up for a Sparrow shot! Approaching a furball at BVR distance and want to help my mates out without accidentally shooting one of them down. Want to target a specific bogey for a BVR Phoenix shot to avoid my wingman and I shooting two missiles at the same target In the F-14 all these BVR modes have to be asked for from your RIO; if you have a breather in back then ask him nicely over TS; if Jester is back there then you request the various modes via his Menu. For those flying the single seater a/c, you will have the means to choose these yourself as pilot. As for symbology (F-14 specific): Unknown Unknown sensor track in RWS, TWS and STT modes. Hostile Track in TWS and STT modes designated as hostile by RIO. Friend Track in TWS and STT modes designated as friendly by RIO. Home base Waypoint representing home base, carrier or airfield. Waypoint WCS navigational waypoint, supplanted by number indicating waypoint 1, 2 or 3. Altitude Numerics When altitude numerics are selected for display a number on the left side of the tracks indicate track altitude to nearest ten thousands of feet. The number four as an examples indicate an altitude between 35,000 and 45,000 feet. Available on radar and data link tracks. Firing Order Numerics Indicates AIM-54 phoenix target prioritization (1 to 6) in WCS when in the TWS mode. Next missile launch will target track with number 1 and remove the number from that track to advance the other 5 track numbers one step to prepare for next launch. Mandatory attack selection on a target forces the WCS to always include that target in the prioritization. Next launch selection automatically sets hooked target as number one in the prioritization queue. Time-to-Impact (TTI) After AIM-54 launch the firing order number on a track is replaced with the TTI or time-to-impact indication, showing WCS calculated time until missile intercepts the target track. When the AIM-54 active command is sent the TTI numbers flash to indicate this. Velocity Vector Velocity vector emanating from center dot of tracks when velocity vector display is selected. Vector direction represents track heading and length represents track speed so that the max indicated speed (1 800 knots) is 1.5 inches on the TID. In TID ground stabilized mode the vector direction represents track true heading and the vector length represents track ground speed. In TID aircraft stabilized and attack modes the vector direction represents track relative heading (to own aircraft) and the vector length represents track speed relative to own aircraft.

As a visual aid as to what the Bar search pattern looks like: Note that, depending on the aircraft radar, that 1 bar search pattern is only 2-3° tall... not very much!

Ok gents, first thanks for attending. Second, for some reason the plan to record the session for eventual upload did not go to plan; tech issues, got to do some more figuring out with shadowplay and VR to get the format and sound working properly. Third, we only managed to cover the Beyond Visual Range (BVR) aspects of radar use - in hindsight, I was perhaps a little optimistic of covering all those options in an hour, but no great loss, we'll cover the Within Visual Range (WVR)/Air Combat Manoeuvering (ACM) modes next time. To summarise, we looked at: RWS (Range While Search) Mode TWS/LTWS (Track While Scan/Latent Track While Scan) Mode STT (Single Target Track) Mode If you have any further questions or require clarifications, then please put them in this thread. I will address them as promptly as I can. Lastly, I would welcome any feedback you guys have; ultimately these sessions are designed to help you - if you aren't learning something then then I'm doing something wrong, so please say what I can do to improve the situation. Cheers guys. Fen

Ladies, gents and those of a non-binary gender persuasion, This coming Monday July 29th at 2230BST, I will be hosting the first of my After-hours DCS Training Sessions, starting with Radar Modes, to give you guys a better understanding of what they are for, when to use them and what limitations they have. Primarily for F-14, F-15 & F/A-18 though some of content will be applicable to MiG-29, Su27/33, J-11 and M2000c and to a lesser extent the F-5. I will create a specific mission for this task which I send to FT and ask him very politely if you would mind loading to our DCS server for hosting for the occasion. I will endeavor to record the session for upload to youtube for those wanting but unable to attend to benefit. What you need to do before you start is at the very least be familiar your particular key mappings/cockpit switchology for (and assign if necessary) RWS (Range While Search) Mode (F-15C & F/A18C) TWS/LTWS (Track While Scan/Latent Track While Scan) Mode (F-15C & F/A18C) STT (Single Target Track) Mode - often noted as lock target PAL (Pilot Automatic Lock) Mode (F-14 only) Pilot Lock On Mode/Boresight (F-14 only) VSL (Vertical Acquisition) Modes

A Japanese 3.7l V6 vs an American 5.0l V8? Lol! Think you've lost that competition before Dad runs out of fuel trying to get to the Start line!

So for the benefit of those who didn't get to Flying Legends this year...

You'll enjoy this

Funniest damn thing about flying I've ever watched... and yet I've learnt more about the SR-71. Make time for this one, it'll make your life better. Trust me.

Yes Bill, whilst designed initially for the F/A-18 it was updated to facilitate use of F-14 also.

Want to brush up on your Case I recoveries? https://forums.eagle.ru/showthread.php?t=221412 Download Banklers excellent mission and get practising. Nuff said!

FXO & metashaders folders deleted from your "C:\Users\Username\Saved Games\DCS" folder?

Hello Doggy DCSers! New DCS update to stable release. Nothing ground breaking, just a lot of little fixes and tweaks to various modules. No fix for Spitfire gunsight randomly failing yet... grrrrrr!

Awaiting the fix to the F-14 Jester/radar bug introduced in the last patch to commence the radar training. Might be a while yet. Any systems unrelated to A2A engagements and radar you guys might like to cover? Air to Ground terminology? Carrier ops? WW2 dive bombing?

Gents, there's further issues with the F-14 in this release; Jester seems to refuse to switch the radar on after takeoff with hot-start aircraft in Multiplayer. If you wish to use the Tomcat on our dedicated server and you don't have a buddy to be your RIO, you're going to have to start cold and dark and do a full INS alignment if you wish to go Air-to-Air at mid-long ranges. PAL lock mode still works for engagements <15nm. Beta fix is due for 03/07/19 but as for those using the Stable, we're looking at a another week or more. Another brilliant bug allowed through to Stable release by ED....

Hi Crasherooney, I have: Stalingrad Premium Edition Moscow Standard Edition Kuban Standard Edition Bodenplatte Premium Edition Collector’s Planes: Yak-1b P-40E Spitfire Mk.Vb La-5FN

FT, you - unlike ED recently - are a legend. Thanks.

Well ED have pulled a prize cock-up and pushed an OpenBeta to stable with unresolved bug which has a pretty profound affect on our multiplayer server. Any AI which depends on "visual" methods to engage - so all ww2, Korean era aircraft and non-radar equipped modern jets plus any ground units that would normally fire at you using the traditional mk.I eyeball will now now longer engage if the server/host is using the no-render option. As ours is. I have made some pretty forthright remonstrations to ED over at their forums regarding this. In the meantime I don't know what else to suggest; either push our DS to the render version (is that possible?) or obliged to have someone host like the bad old days.

Curves my man, custom curves. Partiularly on your pitch axis: The Spitfire is unlike any other Warbird in that the power of the elevator authority is such that, according to the NACA report, you need only move it 3/4" (19mm) from neutral to reach critical AoA. Compare that to the full fore and aft range of deflection of the entire control column and then apply a similar scaling percentage wise to your home joystick and you start to see the problem. Attempting to fly it on a 0% curve and a traditional PC gaming joystick of only 20-30cm length is artificially difficult as the displacement covered by that range to critical AoA is going to be in the range of 5-6mm. Ergo making small corrections in pitch for gunnery and landing are harder than in reality and are more likely to result in the virtual pilot over controlling and in turn overcorrecting. Even a standard curve of 15-25% isn't really gonna alter that very narrow margin much. You're gonna need something a bit special: Go to Adjust Controls Spitfire LFIX Sim> Axis Commands Find the "Pitch" control row and single click the cell with the axis binding in it. Now select the "Axis tune" button that has been activated. New window with the control curve screen now available. Leave deadzone at 0 Leave Saturation X at 100 Leave Saturation Y at 100 Leave curvature at 0 Select "User Curve" option check-box Now input following values: 0,2,4,6,8,10,12,24,50,100 Click "OK" Aileron and Rudder do to your normal, happy, mustang-esque favourite settings. Enjoy!