What is schedule for some fixes and new features?

[Fri13]

- ARBS/DMT (Ground stabilization, tracking, slewing etc)

- INS designation via HUD functionality

- New 4th gen TPOD

- CAS page digital datalink with a JTAC

- Axis for TDC

- TDC Action/No-Action mode

- Missing keybindings

 

Anything getting to DCS 2.7?

To see in Q2 or Q3?

 

[CoBlue]

Bump

[Fri13]

I take it that there is no roadmap, no schedule and no idea what to be done and when.

[Aernov]

Also, to add to the missing features list:

 - RWR filter modes besides LIM are missing (Offset is especially needed);

 - EHSD overlays are missing some information (the one that currently displays AAR zones should also show SAM ranges as F-18's SA page does);

 - Engine life count dissipation with corresponding performance decrease if the pilot is "mistreating" the Pegasus and not maintaining JPT/RPM ratings and their time limits;

 - IFF/ACNIP panel - at least limited functionality, or something like JF-17 has, please;

 - Self-protection jammer (the built-in one);

 - Ground power panel.

[Spurts]

3 hours ago, Aernov said:

 

 - Engine life count dissipation with corresponding performance decrease if the pilot is "mistreating" the Pegasus and not maintaining JPT/RPM ratings and their time limits;

 

Pretty sure I've actually killed the Pegasus before.

[Aernov]

The damage is there, but ENG page and engine life count stays the same regardless of engine status. It should dissipate at a rate dependent on JPT, from less than 0.1 "points" per minute on <645 deg. C to more than 1000 PPM at temps greater than 800 C. It is not as important as DMT and other stuff described above, but it would be nice to have still. Also, they could program some power loss proportional to life count (more wear on the engine - less power allowed by DECS/JPTL), if it's not already implemented.

[Cunctator]

From Facebook: Hotspot detector early test:

 

[Spurts]

what is that?

[Cunctator]

All hot spots detected by the NAVFLIR sensor above the nose can be displayed on the HUD, marked with chevrons. IRL, these hot spots can be vehicles with running engines, planes in the sky or simply a hot rock heated by the sun. Another tool for the pilot to locate potential targets. According to RAZBAM's discord they will create a few false positives initially until later, once heatmap textures are implemented for all 3D objects in DCS with the FLIR overhaul, it will work more realistically and not only detect DCS vehicles. 

[Spurts]

That's AWESOME!  

[Arikaj]

19 hours ago, Cunctator said:

All hot spots detected by the NAVFLIR sensor above the nose can be displayed on the HUD, marked with chevrons. IRL, these hot spots can be vehicles with running engines, planes in the sky or simply a hot rock heated by the sun. Another tool for the pilot to locate potential targets. According to RAZBAM's discord they will create a few false positives initially until later, once heatmap textures are implemented for all 3D objects in DCS with the FLIR overhaul, it will work more realistically and not only detect DCS vehicles. 

When is the FLIR overhaul planned please?

 

EDIT: This year

Edited March 10, 2021 by Arikaj

[Fri13]

On 3/9/2021 at 3:16 PM, Spurts said:

what is that?

 

Night Attack Harrier

https://youtu.be/PxNtwZRv92k?t=2143

https://youtu.be/PlSO9ymoON0?t=97

 

The FLIR in the nose will show a carrot on HUD for thermal changes it assumes to be a proper targets. It is not a Hot Spot detector, but system that has own logic to cue pilot to check is there something or is the expected target there. There are differences like is the carrot "dancing" or flickering, or is it positioned at bottom of the HUD (it prioritize further - 5 nmi targets over targets at close range (looks like Razbam does it wrong - based to their screenshot) as that is sign to random heat source and should be ignored as potential target would anyways be too close to be engaged. 

 

Pilot has few options to set it, based to NATOPS page 1-160 (going by memory now)

 

- Number of the carrots: 0/2/4/8 

- Target size: Small/Medium/Large (in milliradians)

- Some feature with setting value between 0 and 10 (temperature or something)

- The FLIR gate size/range by the angle to current flight altitude: 1 - 5 nmi, a second option and then full from 1 nmi all the way 90 degree upwards for Air-to-Air mode. 

 

Prior the take-off, pilot enters the preplanned mission that includes those details, or sets them via MFD. The target size is based to wavelength and heat source size, so "large" or "medium" doesn't mean that the system can identify a heated SAM system from a internally heated MBT or APC from a truck. It is just to configure the system to know that from what given terrain (flat grasslands or mountainous rocky lands or swampy areas with lots of trees etc) the heat sources are more accurately detected. As flying over a meadows and such you can have very warm spots on the ground that system would detect as targets and symbolize them. So configuring the system is required so you don't get too many false positives.

The gate size is about the system to show the carrots when the FLIR Field Of View is looking in that cone. 

 

It is the system that makes Harrier AV-8B a Night Attack capable aircraft. Remove that system and it becomes just any other really. One of the core systems that should be in Harrier in proper manner. And waiting that we would get properly false carrots as well.

The pilot would need to really program the system properly to minimize false positives and randomness. 

[netizensmith]

The original Razbam pocket guide for the harrier does specify that they will not be able to fully implement this system. We will get a subset, which I'm fine with as I knew that going in.

[Shrike88]

Can we please finally get some more functionality to the RWR ? LIM /PRI / Offsets ? 

Also how about the Contrast / Symb +/- actually working and other MCPD display functionality. 

[Bog9y]

What exactly are looking for with offsets functionality? I haven't fully explored every aspect of it but I can put it in offsets for TCN and waypoints. The only issue is that it's creating a true bearing instead of magnetic. This is an old function I believe, the newer jets would create the offset bearing in magnetic. 

[Fri13]

On 3/11/2021 at 2:02 PM, netizensmith said:

The original Razbam pocket guide for the harrier does specify that they will not be able to fully implement this system. We will get a subset, which I'm fine with as I knew that going in.

You can't trust the old pocket guide...

We are still waiting the official manual...

[ReardonMetal]

On 3/12/2021 at 12:50 AM, Bbow said:

What exactly are looking for with offsets functionality? I haven't fully explored every aspect of it but I can put it in offsets for TCN and waypoints. The only issue is that it's creating a true bearing instead of magnetic. This is an old function I believe, the newer jets would create the offset bearing in magnetic. 

RWR Offset is used when the RWR has a bunch of returns "stacked" on top of each other so you can't read them. You hit Offset and it spreads them out. When you do this you are no longer getting accurate locations, but you can actually read the threat symbols.

[Bog9y]

Ah ok, thanks for explaining that. I thought he was asking about waypoint or TCN offsets.