Ogata_Rina

Still same issue. This time AZ/EL scan box is boxing the target the whole time while maneuvering, but it keeps scanning without geting an actual STT lock. Guess it's not getting fixed in this patch.

It is basically impossible to STT a target unless you freeze your target relative to radar line of sight. First part of the track is showing how AACQ line is not stabilizing. Second part is commanding STT from TWS AUTO, where I have a solid TWS track whenever I cancel AACQ, but losing it whenever I command STT. It's very frustrating to see a 6 year-old module that's still having mission-critical problems, and please test it more thoroughly before you release a patch, as there's no openbeta now. Thank you. radar-STT.trk

It's 100% easier to learn and master the 16. HOTAS layout is simply better, easier to land (18's landing config is simply not natural for non-pilot), and much more public materials to train from. The weapon system is less complex, and the pilot interface is imo more ergonomic. It takes more to fly the hornet to the same capability of a 16. But I still recommend the 18 since it's so underrated nowadays, and not like it's that difficult to learn, it's harder to fly gooder.

I had some practice in the "Kadena to Guam" mission. I'm using the winwing orion throttle and it's getting a bit notchy after 3 years, but I loosened the friction a bit and it helped a lot. The biggest trick I found is to catch the drift before it develops beyond correction. I do not recommend AB unless your tanker is absolutely hauling ass, and it shouldn't be. Once I tap AB it instantly overshoots over the indicator light, even with 3 tanks. I still get some disconnects every now and then though, mildly annoying.

It was trivially easy to AAR before the update, as the engine used to spool faster than a F404. Now it spools much slower, and it's pretty easy to overshoot the boom, especially under light load. I can finish refueling only after few disconnects, which is suboptimal. Any tips and tricks to refuel this thing? Can I put a bit of speedbrake to make it more responsive? Thanks in advance.

Thank you, it's properly fixed.

Usually I extremely dislike bumping up a thread, but after almost a year nothing is updated. 18 TDC box slew speed is still different across radar and SA page. Slew box is a crucial part of F/A-18 HOTAS, with incorrect speed it’s almost unplayable, I either have to stick to light speed radar TDC or slow crawling SA TDC. For the love of hornet, please fix this ASAP. Thank you. Steve

apart from what sigfan86 mentioned - It maintains on-speed AOA by itself much better now, to the point I'm not used to how good it is and over correct all the time. - I don't find it difficult to regain speed at all if you unload a bitt, but it does bleed speed much faster than before (correct behavior). It'll be interesting to see how it fares against mirage 2000 now, as the latter was known to be the one-circle king.

DCS 2.9 To reproduce: open radar page and SA page at the same time, move cursor on radar screen and SA screen, and notice the slew rate of the box is dramatically different. SA page's designator box is significantly slower than on the radar page. SA page has very similar HOTAS logic as the attack radar page in terms of switching display range (you can move up or down, and flick it back to change range), and there's zero proof that the exact same cursor have different speed on different pages. The increased radar cursor speed is great, but shouldn't the cursor rate for SA page be increased as well?

How much more do we have to pay, to get the Lazur like GCI system?

AGM-62 Walleye

Current behavior: antenna is not stabilized in uncaged WACQ Correct behavior: antenna should be stabilized to scan zone indicated by HUD Track: WACQ .trk

Current Issue: 1. Due to VR headset becomes more advanced, it is now possible to see the uplook crosshair in effective FOV(my headset is a reverb G2). 2. However, the uplook crosshair is currently misaligned with actual crosshair, and the shape has pincushion distortion when viewed in headset. Solution: 1. Distort the JHMCS overlay itself as an effective sphere over player's eyes, so the actual uplook crosshair is no longer distorted. 2. Realign the crosshair to the actual 9X missile seeker.

Track included below Config is clean https://drive.google.com/file/d/1bbclEkOGlkQvjsHKooC5-W9UKPeY0ZcB/view?usp=sharing

better check your kalman filter code

track: https://drive.google.com/file/d/10CBy7pZYzcOxOxXrzkzbIp6zBzSuwrBa/view?usp=sharing i started off in gun mode, entered a controlled spin to decelerate, entered spin mode and got out, then symbology disappeared

the threat ring is indeed a feature from the original hornet; however, only static sam systems (SA2, SA3, SA5, S300) should have those, SA6/8/11/13/15/19 should NOT have threat ring and they should be hidden in mission editor since they are mobile sams (they are assumed to move every now and then). Apart from that, although the original hornet does not have link16, it did have link4 which has about the same quality as F14. Since in game we cannot pick which link to use, one way to do this is to set up EWR for general blue aircraft, while F14 can receive datalink contact from ships (if applicable), and hornet will be stuck with general MIDS (which is in the original hornet too).

It would be really helpful if you got a winwing f18 throttle: 1. SB switch has 3 positions, backward, forward, neutral. 2. Backward position is spring loaded, you have to hold "extend" to extend speedbrake. 3. Forward position is not spring loaded, if you want to retract SB you keep it in forward position and SB will keep retracting, until it's fully retracted (it's okay to leave it forward, thanks to technology). 4. If you just want to extend a bit or retract a bit, put it either in forward or backward until the speedbrake is at desired position, and return it to neutral: SB will hold that position. Not sure about 16.

So many modules in DCS have their jammer poorly modeled. Without being able to automatically blank your own jammer targets not only put hornet in a significant disadvantage, but also defeats the purpose of a true self protection jammer. According some sources that I have, hornet is able to select between prioritize jammer transmission or radar transmission. I understand you won't take this as priority, but please make it into your do list.

As titled. Do notice pylon drag definitely exists now, so I wonder did you take the extra step to model interference drag as specified in NFM-200

∝

As titled.

I know it has shown in the 2021 roadmap but when???

It's even launchable and has its own LAR track: f14R3S.trk

Ah then it makes sense. Thanks.