Effective use of F-35A/B/C?

[Cinnamon]

Hi everyone.

I picked up CMANO today for the sole purpose of using the F-35 JSF (Yes, I'm fanatical).
I picked up Northern Inferno too and I'll certainly get COW DLC also.

My question(s) today is, how accurately do you feel CMANO represents the F-35?

And.. will there come a time where the DAS is implemented as well as the Datalink communications unique to the F-35, with capability of meshing with B-1B's and B-2s, specifically its ability to guide ordnance to target? (as well as the Aegis)

And how would you use the F-35 in CMANO to its fullest capacity?

Now obviously there's some stuff that can't possibly be added because most of the information is well.. secret.

My general overall question is, to what accuracy do you think CMANO represents reality and how accurate to reality can a scenario get?


Thanks everyone, very impressed with the 'game' so far.

[Peter66]

My personal experience with the F-35 is limited but I can add input to the other areas.

My general overall question is, to what accuracy do you think CMANO represents reality and how accurate to reality can a scenario get?

I think Command represents reality very well if used correctly. How accurate you can get a scenario really depends on how much effort your willing to put in to creating the scenario. If you put the time and effort in I'm sure you will get the results you want.

If you want to see F-35's in action check out this scenario by Coiler http://steamcommunity.com/sharedfiles/f ... earchtext=

PS: As a new user I'd recommend joining Discord too so we can help you with your many questions you are likely to have. https://discord.gg/dyQDesj This will take you right to the server.

[Cik]

it's about as close as you can get.

as for best use I'd say as a numerous medium-range strike platform to attack threatening and well-defended targets. the stealth is good, and for anything less you can send F-16/F-15E/B-52/something else

[Sakai007]

I can say that my time in Command (since 2013) has pretty well sold me on the F-35. It's like having a stealth mini-AWAC that can be a shooter as well and a sensor. Some of the features you mention are somewhat abstracted as far as guiding weapons from other platforms. You can certainly use the targeting data you get from the F-35 to assign a target for another shooter, but I don't think you'll see specific datalink connections. There is a cooperative engagement capability (CEC) in game, as the Aegis system can guide AIM-120Ds fired by the F-35 and SM-6s fired by other ships and that is a direct, in game visible, data link connections.

As far as your specific interest, I think Chains of War is going to be a must buy. Anything set in the near future is pretty much has to include F35s in the OOB, lol. It is the 21st Century Fighter we're getting, even if some aren't very excited about the prospect.

[Dimitris]

ORIGINAL: Cinnamon
And.. will there come a time where the DAS is implemented as well as the Datalink communications unique to the F-35, with capability of meshing with B-1B's and B-2s, specifically its ability to guide ordnance to target? (as well as the Aegis)

I'm pretty certain the general abilities of DAS are already modeled.

For comms, part of what you are asking for is in our Pro version roadmap. If your interest is professional please contact us privately. Thanks!

[kevinkins]

Scenario designers often place a severe penalty (vs other a/c) on losing the F-35. Use them carefully and bring them home alive. Never think they are invisible Star Trek types with 100 percent cloaking ability. Losing one would be a geopolitical embarrassment in scenario terms. I am not sure if the military exactly knows how to use them yet. Which makes this sim so interesting for players.

Kevin

[Cik]

trick with the -35 is just to never get tangled up. leverage the stealth to get to an optimal shooting range, then blow down the enemy fighters (or ground assets, whichever) with a barrage of ordnance, then once you shotgun, RUN.

done correctly you can inflict losses on the enemy all day, without losing much if anything. the stealth helps strategically; you can generally choose the enemy's weakest point for your strike and the enemy will not be able to pool his resources to oppose you as he cannot see you coming until you are almost in WEZ.

once you are in WVR the plane suffers badly. once you start cranking or beaming the stealth basically stops working, and the very numerous high off boresight weapons that will be flying at you will inevitably hit something. you can win fights still at that range, assuming you brought external sidewinder X, but usually not by much, even if you outnumber the enemy handily.

basically: pool your -35 to target the pressure points, use the stealth to mask your approach, hit and run. make sure you include a trail element to pick up any bandits that may survive the first wave. you definitely do not want anything chasing you full defensive with no recourse.

[mikeCK]

I would guess it's fairly accurate. Just remember that the F-35 isn't invisible, it's low obervable. You can get a lot closer to the enemy than you can in a 4+ generation aircraft. So you can't fly over top of enemy SAM sights...but once you detect them, you can plot a course that gets you within weapons range of your target and allows you to navigate around threats. Use it in conjunction with EW aircraft as well. Basically, if you send an F-35 in to destroy a sight like it's an invisible plane, you won't get the results you think you should

[Dragon029]

DAS is indeed modelled (and reasonable well), as well as the EOTS's IRST functionality.

I do have two problems with the CMANO F-35 however - the first is that its radar is seriously underpowered; the APG-81 should have about double the range as it does at the moment (a lot of AESAs in the database are rather messed up in relative performance; I've submitted recommendations).

The second is that if the database RCS values are in dBm, then they're about 10dBm (at least from the frontal aspect) too high. On the flipside, rear aspect RCS values are currently equal to frontal aspect RCS values - that shouldn't be the case. Side RCS values I have no idea about.

As mentioned, data links with the F-35 are currently fairly generic; using MADL for cooperative EW, passive IR / RF sensor fusion / triangulation, etc would be nice, but it doesn't sound like that'll be coming to the consumer version.

As for using the F-35 effectively:

1. Bring along some EW support; a pair of Growlers can seriously degrade enemy radar, allowing F-35s to get within and escape enemy missile engagement ranges without being detected.
2. When F-35's go or are about to go Winchester, you can let them stick around, but don't let them get close to the enemy.
3. If done right, flanking the enemy and harassing them can force enemies to divert forces to deal with an enemy of unknown (to them) size (just be sure to get those F-35s out of there as soon as the AMRAAMs launch; you want to be able to flank back around those enemies). This can tie up enemy assets while your main force overwhelms their other units.
4. If you're dealing with advanced threats (Su-35s, etc) then bring more than 4x AMRAAMs per target. If this means bringing 4th gens, then so be it, just be sure to make the 4th gens high-tail it after firing and let the F-35s provide target updates.

[Agiel]

The F-35's EOTS is also incredibly handy for providing targeting data for other platforms, such as Tomahawks and non-stealthy aircraft armed with stand-off weaponry like JASSM, SDB, and JSOW.

[Cinnamon]

ORIGINAL: Dragon029

DAS is indeed modelled (and reasonable well), as well as the EOTS's IRST functionality.

I do have two problems with the CMANO F-35 however - the first is that its radar is seriously underpowered; the APG-81 should have about double the range as it does at the moment (a lot of AESAs in the database are rather messed up in relative performance; I've submitted recommendations).

The second is that if the database RCS values are in dBm, then they're about 10dBm (at least from the frontal aspect) too high. On the flipside, rear aspect RCS values are currently equal to frontal aspect RCS values - that shouldn't be the case. Side RCS values I have no idea about.

As mentioned, data links with the F-35 are currently fairly generic; using MADL for cooperative EW, passive IR / RF sensor fusion / triangulation, etc would be nice, but it doesn't sound like that'll be coming to the consumer version.

As for using the F-35 effectively:

1. Bring along some EW support; a pair of Growlers can seriously degrade enemy radar, allowing F-35s to get within and escape enemy missile engagement ranges without being detected.
2. When F-35's go or are about to go Winchester, you can let them stick around, but don't let them get close to the enemy.
3. If done right, flanking the enemy and harassing them can force enemies to divert forces to deal with an enemy of unknown (to them) size (just be sure to get those F-35s out of there as soon as the AMRAAMs launch; you want to be able to flank back around those enemies). This can tie up enemy assets while your main force overwhelms their other units.
4. If you're dealing with advanced threats (Su-35s, etc) then bring more than 4x AMRAAMs per target. If this means bringing 4th gens, then so be it, just be sure to make the 4th gens high-tail it after firing and let the F-35s provide target updates.

Yea, I did some tests on it, it can't detect a Nodong-2 launcher even from within the AESA range, only the launches, which tells me DAS isn't completely implemented yet, but it does detect any radar outputs from other systems, like SA-12s

[Dimitris]

ORIGINAL: Cinnamon
Yea, I did some tests on it, it can't detect a Nodong-2 launcher even from within the AESA range, only the launches, which tells me DAS isn't completely implemented yet, but it does detect any radar outputs from other systems, like SA-12s

Terrain? Flat valley or mountain ridge? (Has severe clutter effect on sensor calcs). LOS? Time of day? Weather? Other factors?

If you think there is a problem with the sensor models, please submit a suitable save for investigation on the Tech Support forum.

[Cinnamon]

ORIGINAL: Sunburn

ORIGINAL: Cinnamon
Yea, I did some tests on it, it can't detect a Nodong-2 launcher even from within the AESA range, only the launches, which tells me DAS isn't completely implemented yet, but it does detect any radar outputs from other systems, like SA-12s

Terrain? Flat valley or mountain ridge? (Has severe clutter effect on sensor calcs). LOS? Time of day? Weather? Other factors?

If you think there is a problem with the sensor models, please submit a suitable save for investigation on the Tech Support forum.

I wouldn't want to look silly and say there's a technical issue, particularly when my experience with the game it self is limited.


Using the God view I can see the Nodong is within AESA range, but it's only detecting the missile launch.

The launcher is on a flat surface, time day, no cloud.

It detected the launcher within 6.3nm which seems absurdly close and it actually detected it with EOTS IRST not DAS, even though I was still continuously launching the Nodong with the F-35 right on top of it.

I'm about 99% sure this is something I am neglecting, but from the things I've seen of DAS if this really is how it performs, it's pretty underwhelming, having to be right on top of something like a Scud or Nodong launch and even then only being able to see the rocket once it hits +30,000ft while the launcher is completely hidden.


I compiled images but I obviously can't post them yet : http://imgur.com/a/FLCD6

So for users who can point out what's going on I'd like that.
Still pretty fresh in the game so I in no way want to say the game has gotten anything wrong.

[Dragon029]

DAS is only meant to be a short-medium range sensor intended primarily for detection incoming SAMs / AAMs; if you're thinking of the video where it detected and tracked a Falcon 9 rocket from >800 miles away, remember that a Falcon 9 is a heck of a lot brighter than an MRBM and that the test aircraft was also using the APG-81 to help maintain a track (you are correct in assuming that the AESA should have tracked the missile after launch).

Ground targets too are then orders of magnitude harder to see than an MRBM, especially if it's day time and the vehicle isn't moving - each DAS sensor is only 1 to 4MP, yet has a very wide FOV, so a TEL and a hot rock aren't going to look that different from tens of kilometers away. One thing I'd like to see with new 5th gen and ISR aircraft is either the automated / periodic or manual ability to perform synthetic aperture radar scans, where for a certain boxed area within radar FOV, any ground / surface targets that have an RCS some multiple (eg, 8x) of the radar's angular resolution is detected, and anything larger (eg, 16x) is classified.

I think one of the things that isn't exactly simulated well is the max range of the sensors - the DAS for instance has a set max range of 60nmi in CMANO, which is appropriate against other aircraft and likely appropriate against SAMs / AAMs, but not so much for special cases like ballistic missiles. With the current system, once a target goes beyond that max range, they become 100% invisible. Ideally those limits shouldn't exist and instead should scale with visual / IR / radar signature to infinite if a target is infinitely bright and remains above the horizon.

[Cinnamon]

ORIGINAL: Dragon029

DAS is only meant to be a short-medium range sensor intended primarily for detection incoming SAMs / AAMs; if you're thinking of the video where it detected and tracked a Falcon 9 rocket from >800 miles away, remember that a Falcon 9 is a heck of a lot brighter than an MRBM and that the test aircraft was also using the APG-81 to help maintain a track (you are correct in assuming that the AESA should have tracked the missile after launch).

Ground targets too are then orders of magnitude harder to see than an MRBM, especially if it's day time and the vehicle isn't moving - each DAS sensor is only 1 to 4MP, yet has a very wide FOV, so a TEL and a hot rock aren't going to look that different from tens of kilometers away. One thing I'd like to see with new 5th gen and ISR aircraft is either the automated / periodic or manual ability to perform synthetic aperture radar scans, where for a certain boxed area within radar FOV, any ground / surface targets that have an RCS some multiple (eg, 8x) of the radar's angular resolution is detected, and anything larger (eg, 16x) is classified.

I think one of the things that isn't exactly simulated well is the max range of the sensors - the DAS for instance has a set max range of 60nmi in CMANO, which is appropriate against other aircraft and likely appropriate against SAMs / AAMs, but not so much for special cases like ballistic missiles. With the current system, once a target goes beyond that max range, they become 100% invisible. Ideally those limits shouldn't exist and instead should scale with visual / IR / radar signature to infinite if a target is infinitely bright and remains above the horizon.

Absolutely.
The developers must have a nightmare on their hands trying to accurately model stuff that is classified.
Speaking of...

Is the YF-12 due to be added? with AIM-47?
Or the D-21?

[kevinkins]

I compiled images but I obviously can't post them yet (:
it's on imgur with the URL: /a/FLCD6

Don't forget the save file when you can upload. Sunburn (and all of us) want to have as accurate F-35 as possible (if it is not already) since that platform will be around a long while.

Kevin

[Schr75]

ORIGINAL: Cinnamon


Is the YF-12 due to be added? with AIM-47?
Or the D-21?

It´s already in there and have been for some time[:D].
CWDB aircraft # 3105

[CCIP-subsim]

With DAS, like any system or sensor really, I'd always take the stated range (in the DB) with a grain of salt - there's virtually always interfering factors, of which the most important one isn't even the sensor itself but the unit's OODA loop.

I also thought I'd mention that I actually have had better experiences with the A-12 that's in the database than the F-35[:)]
They're not that different from each other, truthfully (at least in the direct comparison case, the F-35C).

[Cinnamon]

ORIGINAL: Schr75

ORIGINAL: Cinnamon


Is the YF-12 due to be added? with AIM-47?
Or the D-21?

It´s already in there and have been for some time[:D].
CWDB aircraft # 3105

Hmm.. I can't find it by searching for it under "YF-12"
I do mean the YF not the SR.

Must be my noobness.

[CCIP-subsim]

ORIGINAL: Cinnamon

ORIGINAL: Schr75

ORIGINAL: Cinnamon


Is the YF-12 due to be added? with AIM-47?
Or the D-21?

It´s already in there and have been for some time[:D].
CWDB aircraft # 3105

Hmm.. I can't find it by searching for it under "YF-12"
I do mean the YF not the SR.

Must be my noobness.

Are you looking in DB3000 or CWDB? It's only in the CWDB list, so you wouldn't have it in post Cold War scenarios.

Here it is, by the way: https://wiki.baloogancampaign.com/index ... ID=1003105