Floydii

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.

No issues noted here (Day flying only though).

I'm with 3WA, a KA-50ED would be great, but as a separate aircraft in the game (likely part of the paid update). That way the mission designer has control over exactly what version we can use. As LLTV and FLIR rendering already exist in game setting the KA50ED to use them would not be a massive programming hurdle and there are plenty of un-used switches that would make further mods to the cockpit unnecessary. I don't expect ED to model a whole new suite of avionics, just the ability to switch to LLTV/FLIR and change polarity.

Bottom line and full disclosure up front: I support abstracting a Low Light Television (LLTV) or FLIR setup in a separate version of the KA50 along with the ability to designate NATO compatible laser codes. The KA50 in DCS is not a production model, in fact it appears that only very limited numbers of the single seat KA-50 (the model we have or N/Sh, and not the two-seat KA-52) variants were ever produced.* The only combat time these aircraft have seen in a pair deployed to Chechnya effectively for combat testing in 2000-2001. Effectively what we are flying is a pre-production aircraft, and it looks like the paid ED upgrade KA50 will be a subsequent test bed fitted with Igla AAMs and some better self-defence systems. My understanding is that the reason these specific versions are modeled by ED is that they are the ones they could get sufficient realworld physical/documentation access to and nothing indicates either are fitted with LLTV/FLIR Shkval. As far as night attack capability goes, this post shows either the KA50N or KA50Sh.** From research, it would appear that these models have significantly revised cockpits and controls to account for a whole other set of optics. Additionally, the renders for the paid upgrade show no change to the physical setup of the KA50 Shkval, which suggests its the same old day TV only sight and therefore only limited (if any) updates to the cockpit). So, the question becomes: are players happy to forgo some realism to simply give the Shkval a LLTV or FLIR capability? Because, unless they historically managed to shoehorn a Russian built LLTV or FLIR setup into the original nose cavity, its going to remain day only.*** This FLIR/LLTV capability could be accomplished in the current cockpit by re-purposing an unused switch around the Shkval controls to toggle day/night mode and ripping off the SU25T LLTV/FLIR rendering already in game. The same could be done for the Laser Designator to get it to produce US compatible codes.**** To do this, there would be three different versions of the KA50 in game (sort of like how we have A10As and A10Cs): The version we currently have now, the 'authentic' upgraded version that will be released as a paid update (Day Shkval only) and a 'plus' version that is the authentic version with the addition of LLTV/FLIR and NATO laser code compatibility. For those demanding the experience of flying a one-off prototype helicopter in all its tacked-together glory, the first two versions are available. For those that want a 'what-if' variant that fills the gap of an all weather attack helicopter that can allow buddy lasing scenarios, the 'plus' version can be placed in missions. Fundamentally, this comes down to how willing the community is to accept some abstractions in the KA50. Having multiple versions removes the complaint of purists being forced to fly a version of the helo that didn't exist. MP servers can place whatever version they want in to satisfy their needs. Notes: * Likely less than 40. I note this is a best guess based on internet research as it would appear that single aircraft may have been modified over time to become new versions ** The top one appears to have a re-positioned Shkval in addition to a FLIR turret (N model) while the second is likely an Sh model. Or, they are both prototype Sh models.. *** Russian designed LLTV/FLIR optics contemporary to the KA50 are bulky and required the significant modification of the nose as per the KA50Sh **** I note that the SU25T (and A10A) is able to detect code 1113 from NATO aircraft and JTACs, which indicates that ED are willing to abstract this mechanic for gameplay purposes. Donald, David, and Daniel J. March. "Ka-50/52, Kamov's 'Hokum' family". Modern Battlefield Warplanes. AIRtime Publishing, 2004. ISBN 1-880588-76-5.

Based on a similar question I asked about the current pod coord not matching anything else (including the Harrier's own nav system)here the current solution is, rather unhelpfully, 'do maths' Granted that isn't the answer you probably wanted (It certainly wasn't what I was after). Until RAZBAM improve the functionality of the pod /nav system, you will need to do manual conversion.

RagnarDa, in answer to your question, that is what we mean. Unknown's posts of what is happening match mine exactly. Custom F10 generated carts do not allow use of Bx points if they are not inputted on the map*. I've found a (less than ideal) workaround though. In short, load the Mission editor cart THEN your custom F10 cart. The Mission Editor cart includes all Bx points by default, so when you load an F10 cart that is missing them, they are already inputted (the CK37 doesn't appear to erase points if the most recently data cart doesn't include them). From here the usual initial fixing of Bx8 to the centre of the radar display works fine and all is well. Now, Ideally the Bx point entry on the F10 data cart should be automated if they are not stipulated on the F10 map*. This is for the simple expedient that mission editor carts do it, even if you don't include them and not automating it with the F10 Cart just adds extra work that would normally be done by someone in Squadron Operations, not the pilot. Bx points don't mess with fuel plans or anything, so having them in the background shouldn't be a problem for a pilot that isn't using them for their mission. Further to this, please do retain the Bx8 Fix going to the centre of the radar display, in the absence of a plans team to do the maths on where Bx points should be, the main way DCS viggen pilots set up RB15 shots is fixing to a radar target. Obviously if a qualified Viggen Avionics tech or pilot says otherwise change it.. but the current extrapolation is fine. ---- *To the point of adding points on the map, can you please update the manual to clarify the exact syntax required for these marks, as it appears to not be officially stated anywhere. so I couldn't tell you if Bx works if put on F10.. because I don't know what to put in the map label (BX8, bx8, Bx8?). ** More complicated scenarios are easily catered for by allowing manual input of a BX point in the CK37 in response to getting the coords of the target group from another source (recon viggen or some such.

Previously Bx could be created automatically when you were setting Bx8 for RB15 shots etc. There was no requirement to add them in f10 At the moment it just shows B2 if you select any Bx point after loading an f10 marker cartridge.