BarTzi

Isn't it just another way of setting the RALT warning, and not a completely new independent warning?

Yeah it's probably AOA just before touchdown.

Even if DCS doesn't use the tracking methods the pod does (and it shouldn't), there's a small QOL improvement here in the form of the expanding acquisition window.

You are asking them to change their development priorities based on your opinion. To be honest, there are other more important features they should add to the SC module before the barricade. It's in EA, so you should work around the current limitations. Divert or eject - it's just a computer game at the end of the day.

Then the mission maker should consider the supercarrier is not complete yet (missing the barricade), and deal with that in some other way. HB changing hook mechanics for their module should not change ED's priorities.

Just divert, honestly. I guess it's a low priority feature anyways.

Same Issue here. Did you manage to solve it?

Yeah It's my bad. You can't in DCS because they don't load both of those cats at the same time.

As it should. You can't connect two aircraft to cats 3 and 4 at the same time.

I'm not against adding it. All I did was to mention it serves no purpose, unless you have a way of telling if the missile hit or missed. The way it's done in DCS is with live weapons and scripts, which I'm sure those milsim groups are already using. It will make the module more complete, but it serves no real purpose other than that. Please note that the video is a hud recording of a super honet. I don't think ED will be using it as a source.

There's a video online showing a simulated FOX-3 shot (It's a super hornet). I'm not sure if it can even register hits or how it can register hits. It won't add a lot to the game in my opinion. People who want to simulate BVR shots probably use MOOSE (FOX), or other scripts.

I will take the alternative anyday, if the system provides false information. I get it that the refresh rate plays a role here. However, it seems odd, as nickos said above, that it just deteriorated over the last few patches. There are probably zero videos of legacy hornets with JHMCS from that time period anyways, so we can't prove anything.

Ft-lbs is what matters, not just the weight. You should sonsider the distance from the center of the airframe, when calculating how balanced the loadout is.

Did that yesterday The tag doesn't matter.

That's how it should work (just like it does for waypoints at the moment). Selecting LAT of LON via the UFC as an extra step, doesn't exist in the real jet.

Don't waste your time. This ia a bug report, and you are wrong. Move along and let the development team deal with this.

I'm looking at a document that says otherwise. Can you please elaborate?

This bug report is about the gps guided weapons ddi display, which is used when configuring one of the following weapons: JDAM, JSOW, SLAM and SLAM-ER. 1. Typing coordinates for TGT UFC, LP UFC, and slam-er steerpoints involves one extra, unnecessary step. When you use the UFC to type the coordinate, you have to specify wether it's the LAT or LON coordinate first, via a ufc menu. This is redundant, since you already have to type W\E\S\N as a part of the coordinate. As you can see here (why do I have to select LAT, if I already have to type the letter N?): In fact, typing coordinates for all of the above should be identical to creating a new waypoint. (LAT, LON shouldn't be selectable or appear at all. Only HDTH and TTHO should appear when you type the digits after the decimal point). 2. The format of the coordinates you type should be affected by the type of coordinates selected via hsi->data->a\c (either LATLNDCML or LATLNSEC) More on this here: All of this can be backed up by documents that I can't share over the forums, but I believe the team has access to (can provide more info via PM). I think the development team has access to the same documents, so I suggest they take a look at this.

He flies a Viper, but it doesn't mean F-18's work that way.

Because Hornet didn't skip leg day.

When Shimmer asked you what were your sources, your answer was 746. Make up your mind. If you can't describe this feature yourself, you can't expect ED to add it (if it exists at all).

Asking for a feature that isn't described in a document you mentioned, without explaining it at all. Sounds about right...

746 is the series of doduments describing the way ATFLIR works, afaik. Nothing to do with radar.

There is a delay, but it's not the isue that's reported here. It's completely inaccurate for almost all ranges. Should it really be like that? In that case, it's better to turn it off.

NATOPS, and yes- this is for the legacy Hornet.