Floydii

I follow this startup exactly, but I cannot get the radar page to show up once completed. I note that the video cuts once Jabbers reaches the runway, and when it fades back in, the radar is running (was the aircraft autostarted for the takeoff portion of the vid?).. So is it possible that this startup procedure doesn't start the radar? Autostart (win-home) works fine, but the only difference I can see is that the AAP buttons are progressively pushed on as required rather than just hitting combat. Does anyone have a written startup checklist that gets the radar running?

In other news, the cannon is belly mounted and canting it up would be physically difficult.

Destroy the launcher / go behind a hill / fly away from it.

Has anyone brought up the basic-ass modelling of Electronic warfare and countermeasures in DCS yet? Complaining about this missile or that missile isn't a reflection of reality is a bit moot when the supporting ecosystem of EW, Integrated Air and Missile Defences and Radar writ large is lobotmised, either through lack of modelling or deliberate (security based) omission. If you're playing PVE, turn down the difficulty on your JF17 enemies to offset perceived inferiorities with the US jets its going up against (or, learn to fight and win as is). If its PvP you're at, you're already playing in a shady world of half truths where the jammer you are running isn't the real deal and your radar isn't only partly functional. Just learn the numbers of the reality of this simulation and play to that. Frankly, the comments that indicate that surely a joint Pakistani/Chinese aircraft and its weapons could not possibly compete with an older block f16C running basic C model AMRAAMs smack of a view that America has the monopoly on good aircraft.

Optical systems are no less accurate than radar guided ones, provided they can see the target. The main issue is usually that the missile flies a much less efficient path as the range of the target is not generally known (so the missile ends up in a big curve rather than flying to an intercept point). As far as using flares on the HQ-7, it'd really depend on the 'IR' nature of the guidance. If it is a thermal camera (most likely), then flares probably won't fool it as its looking for a hot outline of a jet, not just the exhaust. That said, DCS might abstract it, so it may work. Otherwise, forcing the missile to change direction alot by manoeuvring will wear down its range and energy very quickly.

MATRIC is amazing if you have a couple of spare android tablets you can use. Its simple, works straight away, and the drag and drop implementation is superb. If the JF17 setups that Anarchy is making don't quite suit your needs, you can literally drag/copy/paste the buttons exactly how you like. Do try it.

It'd be splendid if the pod just talked the same language as the Harrier's own nav system regarding coords.

Full disclosure up front, I haven't made this.. yet. However, Is it possible to mod a laser guided United States 2.75inch rocket in dcs? The principle of operation would be identical to the S25L large laser guided rocket on the su25T. It'd use all the models and motor/warhead values from the current 2.75inch FFAR and associated pods, but would home in on any laser spot it is set to within an arc to it's front Forum post for proposed weapon functionality: https://forums.eagle.ru/showpost.php?p=4058203&postcount=6 APKWS description: https://en.m.wikipedia.org/wiki/Advanced_Precision_Kill_Weapon_System Thoughts? Ideally it'd be something you could load onto any aircraft that currently carries 2.75inch ffars. I have zero knowledge of DCS modding, so I just wanted to sound out those that do. :)

From what I've read, and based on the forward guidance fins (each of which houses a laser seeker) not deploying until after firing the APKWS doesn't talk back to the launch aircraft. What this means is you could employ it on the harrier/hornet/A10C like a LGB: - Either set rocket code on kneeboard before take-off or use the current harrier method where Laser weapons set to whatever code the LST is set to. - lock target in TGP and designate or aquire and track someone else's laser spot with LST (The endstate is you have a cue on the HUD for a laser spot set to the same code as the APKWS). -Select APKWS rockets, place rocket pipper over laser target on HUD and launch rocket at ~3nm. - Rocket deploys, detects laser spot and flies to target. The only issue I can think of is arcing rocket trajectory preventing early aquistion, but the rocket will get in the basket ballistically. Without a manual, it's hard to confirm this is how it works exactly, but I'd be happy with the approximation.

Page 178 of ChuckOwl's guide: https://drive.google.com/open?id=1Ax...W8tEdAblI_Mc5i To clarify, the AGM65G uses an Infrared-imaging seeker (so.. infrared TV..) . If you are looking for a TV guided Maverick like the AGM65H, the Harrier is not equipped with them. Hope that helps

Husker, perhaps the real harrier's avionics were simply not modified to work like the A10C or FA18 when using JDAMs. This could possibly be because the United States Marine Corps only had enough funding to implement certain features deemed more critical than self-designation of JDAM targets. As an example: In a conventional war, the harrier is generally employed far more often in Close Air Support of friendly troops (who are designating which targets to hit, possibly via the CAS page), whereas the Hornet may go deeper into enemy territory where it must find it's own targets for JDAM via radar or target pod. The different missions drive the priority of system development. The basic interface we currently see for JDAM employment in the harrier (compared to the more comprehensive Hornet) suggests that JDAM use was developed in each aircraft separately despite both aircraft sharing common avionic lineages. I am quietly hopeful that once a markpoint is added, it can be moved like a waypoint in the EHSD data page. In this way you could dynamically designate JDAM targets.

*bump* I've noticed the dispensed munitions still dispense off target if there is any wind. It's been shown earlier that the Bk90 has an INS and the manual seems to indicate that the Viggen can account for wind. In this, I suspect the munition (or the CK37) would adjust it's dispense point to compensate for known wind. So, is the lack of automatic offset for the BK90 dispense point to account for wind a bug, modelling shortfall or a limitation of the real system? Devs: - If it's a bug or a modelling issue, can it be fixed? - If it's a real world limitation, can a table be provided so we can offset target points appropriately?

I'm not sure I'm in the DCS forums anymore, no-one has violently slapped down the OP for suggesting a change that is purely optional and might increase some people's enjoyment of the game. The lack of self-entitled rage feels.. uncomfortable. On a serious note though, an option to disabe drift (which would be ON by default and enforceable by the server), would be fine IMHO. This being said, I won't be doing it as fixing and managing the avionics is indeed part of the Viggen's 'charm'.

Real Viggen pilots ride the lightning all the way in.

https://forums.eagle.ru/showthread.php?t=239623&page=2 Page 2 has an explaination of what is happening (basically autostart timing doesn't account for some weather variables) and further on is a quick guide to manually starting the right engine. Looks like the autostart script logic should be condition rather than time based to alleviate this issue. Hope this helps.

To clarify my earlier point, the jammer does function and reduces the range that other radars can establish a lock (DCS noise jamming effectively). It will allow an ECM fitted AV8B to get closer to Surface-to-air systems and fighters before being locked or fired on. How close depends on the system and likely it's skill level.

Or at least a sticky?

Then that's all we need. :joystick:

:thumbup: Do you have a guide for the different commands that can be put in F10 labels?

Reference the f10 map waypoint system: Has the ability to add time-on-target been added yet? I recall the devs showing something along those lines a while ago. If it has been added, what are label texts that need to be used for it?

It may help to set BX7 and BX9. If they are already programmed by default, they may be out of limits for the missile.

As people noted earlier, it is likely due to less flexible modelling of the Heatblur F14 Data Link propagation (so, it cuts out sooner as LOS degrades or is cut completely). I couldn't comment on 'correctness' as I'm not privvy to the maths ED or Heatblur use for propogation of these signals. It is possible that the Link 16 ability to 'daisy chain' through other, closer aircraft (and higher) aircraft is getting you a signal. I believe LINK 4 is Point-to-point only.

For Doppler radars, the Notch is generally where the target is not moving much relative to the radar (so, flying at the same speed in the same direction or crossing perpendicular without rapidly reducing or increasing range. ) which makes it harder to detect as doppler detects targets based on their movement toward or away from the radar). Helicopters, can instead exploit their ability to fly very low and slow to become indistinguishable from terrain. This works two ways: 1) Doppler radars will start to reject contacts that are travelling below a certain speed relative to the ground. This is so the air-to-air radar isn't picking up cars driving along roads, trees waving in the wind, boats etc. Helicopters can easily get below this speed if required. 2) Pulse Radars, which rely on a distinct reflection from a contact with nothing else around it work best when not looking at the ground (which is one giant reflection for them). It is possible for a Pulse radar to see an aircraft that is high enough above the ground to give a reflection before the ground reflection comes in, but for air-to-air radar, this altitude is several hundred feet. So, a helicopter in the trees will usually blend into the ground reflection. Now, Modern Radars get around this by looking to detect the one thing a helicopter cannot hide, its rotors. The Rotors present a very distinct Doppler effect as the blades are rapidly moving towards and away from the observer as they rotate. If set up for it, the radar will return anything that matches that rapid Doppler flickering as a helicopter. However, due to the smaller comparative size of the rotor blades, a hovering helicopter will be detected at a shorter range than a fast moving one (which presents a normal doppler return just like a plane). So: To avoid detection, your best bet is to stay low and <60kph when moving in areas likely to have radars that can immediately target you. This is on the premise that any of what have just written is modelled properly in DCS (my experience with AI F5Es suggests it isn't really). Once you get close enough to fire Vhikrs it is likely that Tunguska and TOR systems will detect you if you are line of sight to them anyway, so you are simply better off exploiting the game mechanic of the countdown they require before launching. ID them at range, mark on the data link and then use DL Ingress to acquire them and fire at closer range before they can react. This doesn't alleviate the need for an RWR for self protection and target location, but I guess we'll see what ED actually fits. Relying on the Missile Launch Warning is a poor choice as it means a missile is already on its way and it also won't allow you to sniff out search radars either. The fundamental mismatch here is that we are forever flying the KA50 in missions where the threat is far higher than it was equipped for (Chechnya, so no real radar threats) and as there is no other attack helicopter available it keeps getting thrown into MP missions particularly where there are a whole mess of Radar threats.

Regarding the KA50 right engine not starting in very hot/cold weather when using auto start. To fix: - Conduct autostart per normal, wait for it to report 'Aircraft Ready'. - IF right engine does not start do the following: - enable APU fuel by flicking the 'APU Fuel Shutoff Valve' to the up position (its under a guard cover on the wall outboard of the autopilot switches and above that larger red and black switch cover for 'Ejecting System Power'). - Set the engine selector (left side, directly below the clock) to 'APU' and press the 'Start' button. - Wait for the APU to run up and stabilise around 6-700 degrees (gauge on left side wall of cockpit above those yellow levers. - Switch the engine selector to 'RH' (so, into the right-down position) and press the 'start' switch again. You should see the RPM for engine 2 start to run up on the RPM gauge to the right of the ABRIS screen. - Once the engine RPM has levelled at ~80% RPM, hit the 'APU shutoff' button (red ringed above the engine selector). - Finally, flick the APU Fuel shutoff valve down again. You should be good to go then.

What may be modeled here is that you can't shout your request for more weapons and fuel over the noise of the running helicopter. I just use Ground Crew intercom every time.