Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by Harker

  1. Used it. For our Hornet, it should do what it does in DCS. Blank the HMD when the TDC is not on the SA page and command EXP when it is.
  2. Yes, the radar presents a range-azimuth scope, while the elevation is determined via AG ranging. Thus, upon TDC Depress, designation will be created on top of the desired point, with correct elevation. All other sensors, including the TPOD, will be slaved to that point now and the TPOD will be looking at the correct elevation. Although the ground radar is not particularly useful for precision targeting, it can come useful if you're looking for large structures, large aircraft, ships or even stuff out in the open (after a lot of gain and contrast adjustment, you might spot small blips), if you cannot use the TPOD and your eyes to spot the target. It's not easy to use, but it does comes useful in certain scenarios, I've found.
  3. If you can't find the target with the TPOD so you can get elevation, you can always create a designation via the A/G radar, which will be at ground elevation. Then, the TPOD will be automatically slaved there and display the correct elevation.
  4. It's not related to the pods, any ground designation, done in any way, will move the currently selected WP. It's a reported bug in the Hornet section.
  5. With so many operators, do you realize how many liveries we'd need for 3-4 per country? As BN says, it's very easy to get bloated installs and some other modules are guilty of doing that. People can install whatever livery they want, very easily, there's no need to bloat the vanilla install more. I f someone cares about using or seeing a particular livery, they can install it.
  6. Thank you for running by the team. I don't have any documentation specifically stating that "the designation continues to be updated by the designating sensor, even after the TDC is taken away from the page". Manuals logically imply that the designation is driven by whatever created it, regardless of TDC priority. The TDC comes into play if you depress it, while on another sensor page, in which case, that sensor becomes the designating one. The current logic in DCS is also not described or implied anywhere and furthermore makes no sense, at least based on anything I've read. Anyway, I'll see if I can find a document that clearly describes the process, however I don't think that TDC priority will be covered in it, because it's never stated that it affects anything in the first place, at least according to what I've been able to find.
  7. That's not the issue, the real issue is that the designation diamond stops being updated as soon as TDC priority is moved away from the FLIR page. That's wrong, since the FLIR is still the designating sensor, as indicated on the HUD (it says FLIR) and thus it should continue updating the designation no matter where TDC priority is. As for the Maverick, it should slave to the designation, that part is not wrong. The problem arises from the fact that people move TDC priority to the IMAV page, in order to uncage it and then the designation stops being updated from the FLIR.
  8. not related to pods only, every way of designating will cause the bug
  9. Observed the same, but with any sort of designation. OP, maybe you can change the title to reflect this. What happens is that merely depressing the TDC to create a designation, will permanently move the current waypoint to that location. Selecting WPDSG or having a WP boxed before or not makes no difference, it always happens. It occurs with the ATFLIR, but also with other modes of creating a ground designation, such as via the HUD while in A/G mode. EDIT: added track I really hope we see a hotfix ASAP for this, this makes navigation and A/G impossible. FA-18C_AG designation moves waypoint.trk
  10. The actual issue is that the ATFLIR, while in AUTO track, will not continue updating the designation if the TDC priority is moved to another display. Normally, it should continue to do so, until another sensor is commanded to designate, regardless of where TDC priority is.
  11. The CIT should receive replies (and even create CIT-only teackfiles, but let's not get into that) even without a radar contact. IF a radar trackfile exists, CIT data can be combined with it, via the MSI system and the ROE matrix, for HAFU classification. But a radar trackfile is not a prerequisite. Look at how the F-16 and JF-17 do it in DCS, it's modeled there. They can interrogate the airspace in front of them and receive replies, even if they don't have a radar contact (the F-16 lacks the ability to combine a reply with a radar trackfile, but it can still receive it). So, in the Hornet, if you run an interrogation and there is a friendly aircraft inside that space (with an enabled and correctly set up transponder), then you should receive a reply from it, even if you don't see it on radar or datalink.
  12. That behavior was wrong and was fixed in the meantime. There might still be a bug here, according to OP's video, however. The Azimuth selection option should not affect the DBS scans.
  13. It never had it, in DCS. The ability to use the Hand-off to step though and monitor threats is not removed, just the ability to route the PRF audio for the Hand-off threat to the pilot's headset.
  14. Why not both? A chart from the devs would be very welcome, to at least get us started. And people like you will surely fill the community part of the equation. I know I'd be grateful for both, since I don't have the time (and to be honest, the inclination as well) to test often.
  15. Your cockpit seems set up correctly, but you're outside of the detection range of these air defense units. The ZSU-23-4, for example, will only show up on the RWR when it's tracking you, which it'll only do if you're close enough. I start from cold and dark all the time and I don't have your issue. If you determine that the above is not the solution, post a track of a small mission, so we can see what exactly is happening.
  16. Harker

    Auto AAR

    Flex your hands and your toes regularly and remember to take slow breaths. Focus on keeping in formation with the tanker, nothing more.
  17. That sounds reasonable. You need to actively select a weapon for it to be available for firing. So if the HARM isn't boxed, the only mode that should work is SP in Pullback mode, which activates when you're being locked by a surface threat.
  18. I don't have links readily available, but there have been both reports and discussions about it in the Hornet (and I assume the Viper) forum(s). They should be easy enough to find with the help of the Search function. The short explanation is that the HARM should detonate with a proxy fuse, so that shrapnel shreds the radar aperture, which is very sensitive. In DCS, it does use a proxy fuse, but the problem is that radar apertures are not separately coded from the rest of the vehicle, so if the unit is armored, the radar is armored. Coupled with the lack of shrapnel modeling in DCS, this means that the "armored radar" takes no damage at all. As for my first comment, I was just referring to OP's suggestion that Hornet pilots are lazy for not extensively testing against every single unit in DCS, as it if was their actual job. Every good bug report is a kindness to both the developers and the community and should be appreciated, not expected.
  19. I really hope you're being sarcastic here... In any event, this has been brought up, reported and acknowledged multiple times, perhaps not specifically to the Roland, but certainly in general. If the Roland has armor, it'll likely not receive proper damage from the HARM and that's a problem with the damage modeling.
  20. The Viper has more than enough liveries now. If people fly with the default Gamblers livery, it's because they choose to. Anyway, it's more realistic to have multiple jets of a single squadron flying in the same AO, than single jets of every squadron out there.
  21. The POWER button on the THREAT WARNING AUX panel. Left of the CMDS panel, left side.
  22. It absolutely should, all aircraft detected are shared. That's the entire F/F part of the DL. I think you're talking about the TXDSG function, which will show designations and dashed lines to L&S targets.
  23. By what logic is the pod drifting with the motion of the aircraft, with a designation present? If the current behavior was desired, the pilot can simply undesignate. Designations slave sensors to them. Furthermore, the pod cannot be commanded to stop drifting by TDC Depress. If the current behavior was correct, then a TDC Depress would stop the pod and maintain a new designation at its current position.
  24. That's not what the problem is though. The issue is that the trackfile is deleted, which should be the end of it. But if you create a completely new trackfile, on the same target, the system somehow knows that it's the same aircraft. This shouldn't be possible.
  • Create New...