Jump to content

Ahmed

Members
  • Posts

    282
  • Joined

  • Last visited

Everything posted by Ahmed

  1. Hi, Compared to publicly available HUD footage, the HUD EW lines in DCS seem to be misplaced. In the screencaps below, notice that the real threat code does not occlude the heading tape when directly at the 12 o'clock position (is above it), and likewise stays out of the airspeed box at most angles. In DCS, the center reference position they use also seems to below the real. The stem lengths in DCS seem also too long (especially the dashed/long) in comparison. Last 2 photos are a rhino but they show cleared footage and seem to match the hornet's. Reference videos for the attached screencaps: https://www.youtube.com/watch?v=up7V79QzCog (hornet screencaps) https://www.youtube.com/watch?v=wPY_BzTTqqQ (rhino screencap) This is aside from the previously reported issues with the non-lethal/lethal/critical logic and the missing flashing long stem. Track also attached. hud_ew_pos.trk
  2. Hi, Noticed that "RTS RWS" from HACQ or WACQ goes back to RWS but leaves the boxed "ACM" indication instead of fully exiting the ACM condition. This doesn't happen from BST or VACQ, where the correct SIL pushbutton is shown on return to RWS. Tracks attached. rts_hacq.trk rts_wacq.trk
  3. Hi, When using AACQ in conjunction with Spotlight, AACQ should try to STT the first target it finds within the spotlight region. Currently it may STT a target outside of the spotlight region instead, if it still hasn't aged up. Track attached and also PM inbound aacq_spot.trk
  4. Hi, currently the only ways to exit AACQ is via selecting gun or A/G MM. This is correct but it is missing the third criteria of AACQ rejection. It should also exit AACQ if rejected via NWS (RWS/VS only) or TDC depress (all). Track attached and PM inbound aacq_reject.trk
  5. Exaclty the above. The main difference of using RAID would be noticeable if radar resolution cell would be modeled. Right now in DCS it is just two ways of "zooming".
  6. The (wrong) way it works right now, you need to select the HPTP prior to entering R/BL (i.e. prior to designating your target). It will still be hit and miss and sometimes will act in odd manners, such as the harpoon overflying the target afterwards without locking into anything. R/BL should be selectable prior to the designation according to the TAC-300 pocket checklist, and this was acknowledged as a bug in the bug reports subforum a few months ago. For now you can try the above workaround.
  7. Good find. There are indeed some odds things with the current modeling of radar physics, such as the findings in the look-down thread, that don't seem to follow the expected result from basic radar theory. DCS would really benefit from revisiting and improving this area.
  8. Good find! Real documentation states that SIL freezes the display, but doesn't state the same for WOW (that just switches to dummy load).
  9. Yes, carrier trapping is definitely lacking "violence"
  10. and Sparrow. Quite important feature to model indeed. But no acknowledgment so far.
  11. Blue Angels hornets have modified FCS iirc, so that video is not the best example. There is no such thing as "particular setup in the FCS" for demo birds though. So the RCAF video and FightsOn comment should point in the right direction.
  12. Range/Doppler gates should prevent locking own missile indeed. Resolution cell modeling would also benefit other stuff such as RAID modeling.
  13. I noticed that, because of the lack of RDR/JMR priority filter logic in the DCS Hornet (that has not been acknowledged as a bug despite documentation stating its basic working), the AI acts in a strange way when locked and equipped with ARH missiles. In the attached track, the AI hornet seems to use its jammer all the way to the merge and thus not employing its ordnance. This is without tweaking anything, with its default settings. ai_jammer.trk
  14. It sounds like you may be in ACM mode. You must exit the ACM condition to be able to use the castle switch in its usual manner. Castle up in A/A master mode enters ACM.
  15. The weights I mentioned were from the ME, to isolate any effect of discrepancies with the CHKLIST page. I'll add a track soon describing this issue, although the track itself won't add much value. This can be better noted in the ME itself.
  16. Ahmed

    AIM-9 drag

    Hi, As the FM is scheduled for review: Currently in DCS, the following results are obtained, as evidenced by the attached tracks: - 2x Wingtip AIM-9: 678 KCAS - 2x LAU-115 with 1 AIM-9 each: 678 KCAS - 2x LAU-115 with 2 AIM-9 each: 678 KCAS rising 2 points: 1) Quick examination of the lua files shows that the functions defining LAU-115/LAU-127 loadouts add the same drag constant regardless of number of missiles loaded. 2) Wingtip (LAU-7) AIM-9 should have lower drag than LAU-115+LAU-127+AIM-9 (ref NFM-210/-200). aim9_lau115_1.trk aim9_lau115_2.trk aim9_wingtip.trk
  17. The secondary radar low altitude warning (HSI -> AC -> RADAR) doesn't work (no "ALTITUDE ALTITUDE" warning) at the maximum selectable value of 5000ft (and many times at slightly lower values too). It should work up to the maximum selectable value of 5000ft. radar.trk
  18. Both of the above are correct, the radar is only commanded back to search if it was in acquisition.
  19. Hi, When empty, stations 4 and 6 show an empty LAU-116 on them. However its weight is never accounted for. I thought that their weight could have been included as part of the empty weight, but this is easily proved wrong by loading the ATFLIR, as this results in adding the 430lbs of the pod but not substracting the weight of the removed LAU-116.
  20. Hi, When unboxing sim, the SMS should do an inventory and report the actual loadout to the MC. In the track attached, the stores page wrongly reports 7M instead of the actual AC after transitioning out of SIM. Regards, outofsim.trk
  21. Yes, primary radar low altitude warning is the one set via the radio altimeter ("whoop whoop" tone), secondary radar low altitude warning is the one in HSI A/C ("altitude altitude"). Double A/P is for the primary one. Whether it is a second independent setting, or just overrides the radio altimeter bug, I don't know.
  22. Now you are making me doubt. It may override the one set via the dial bug instead of being an independent one. I may have misunderstood it.
  23. That's indeed a second low altitude warning, independent from the one set via the radioaltimeter dial.
  24. Agree with the last post by Snappy. The only thing related to this thread that holds up is common feedback by real hornet pilots that the DCS one doesn't have enough nose authority at low speed as the real. We will see when the FM update gets done what changes are made in this area, together with the announced on drag and rate.
×
×
  • Create New...