BarTzi

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.

Correct. Needs to be less than (or equal to) 32,357 lbs for 7.5G.

Currently there are two ways to enter TWS: 1. Using the radar mode PB (PB5). 2. By locking (STT) a target, and then using PB10 (which will put you in TWS AUTO directly). If you choose to use the second method, scan centering in azimuth will not work from this point onwards. This means that TWS AUTO won't follow the target in azimuth, TWS MAN will not react to TDC press, SPOT won't work, and that you won't be able to offset the scan zone when using AZ/EL. It's like it causes the radar to be stuck pointing forwards no matter what. As you can see here, while using TWS AUTO - the AZ/EL page shows the radar scan zone following the target (when in fact, it does not), while the radar display shows the target outside of the radar scan zone (fading). taw auto azimuth- centering bug.trk

Right now, the SA page doesn't show the tacan station symbol. I don't know if it's realistic or not (more of a question fo your subject matter experts. As it stands SA shows you everything related to tacan except the station symbol), but I think it's really odd that it does display the tacan course line without the tacan station symbol. It should display both, or not display them at all. HSI: SA (notice the missing tacan station icon, which makes the course line a little less relevant): tacan sa course.trk

You can now box WPDSG and TCN at the same time, and if you choose to set a course to the target, it will set one for the tacan station as well. The result is two course lines that will be visible. course lines.trk

Thank you very much for making this, it's a great addition!

That's fine by me, but it doesn't make sense that the SA page displays the tacan course line without displaying the tacan station icon (when you use the CRS switch to set a course using the HSI). It should either display the tacan icon and course line, or not display both of them.

It is probably the only difference between SA and HSI in DCS (datalink aside). I was wondering why the SA page displays every bit of relevant tacan infoamation, including tacan course, without displaying the tacan station icon.

Can confirm this is a major issue for harpoons as well in the current OB build of DCS.

Just making sure: are you using steerpoints for the path of the missiles? (we only observed the problem when using a pre planned missile flight path). If your build is different than OB, then this could have been solved internally somehow.

I don't think you can replicate this on your own, as the desync is between clients. Client A sees only his missiles follow the designated path (slam er steerpoints), while the rest of the missiles (launched by client B) don't follow their path and go straight to target. Client B sees only his missiles follow the designated path (slam er steerpoints), while the rest of the missiles (launched by client A) don't follow their path and go straight to target.