Jump to content

SeaBass80

Members
 View Profile  See their activity

  • Posts

    46

  • Joined

  • Last visited

 Content Type 

Everything posted by SeaBass80

  1. SeaBass80
    Hi, a longstanding bug in the F-16 has been nearly solved in 2.9.9.2280, I link to the original description here. This is with respect to the guidance provided when pressing weapon release in CCIP mode if the weapon impact point is below the HUD. In this case, the F-16 provides both steering guidance to the release point via the release cue and the azimuth steering line (ASL). Solved bug: Contrary to before, the ASL steering line now indeed guides towards the designated CCIP target point as long as the weapon release button stays pressed. Thanks for finally solving this, ED! Remaining bug: The target designation cue (circle with dot) should become ground-stabilized at the selected ground point upon depressing weapon release in CCIP mode. Currently, it becomes ground-stabilized at the calculated impact point at the moment of button press. This is incorrect for the delayed release, as that ground position does not correspond to the designated target point used by the FCC. Evidence: redacted please use PM next time. Track file: Provided track file shows this behavior. Target selected by holding WPN Release is the center of the two runways. After target designation, airplane is maneuvered to reveal CCIP designation has been ground-stabilized at a point well below the original flightpath. The approach and release can nonetheless be completed correctly. 241101-CCIP post-designate.trk
  2. SeaBass80
    I tested CBU97 in CCIP post-designate, specifically for falling long or short. Seems fine on my side to within 50 yards/meters or so. Good enough from where I released it. This was flying straight ahead without steering input exactly aligned with the original flight direction. See attached track. So there is nothing wrong as long as one the exact azimuth is hold between designate and release... not that this would be realistic for the post-CCIP designate mode. More testing needed, but I presume the problem you describe might somehow arise when azimuth error is introduced and you cannot steer back to the correct one due to lack of azimuth guidance. 240315-CCIP post-designate CBU97.trk
  3. SeaBass80
    Hi, this pertains to the employment of free-fall weapons like MK82, MK84 and such. The mode becomes particularly important for slow bombs such as CBU-87 and -97. The manual section is on page 354 "Unguided Bombs CCIP Attack (Post-Designate)". If you have the HAF -34 document, it is described in the section "CCIP Visual Submode", page 1-429. It is correct procedure to fly the CCIP pipper onto target and depress WPN REL. If the actual impact point is below the HUD though, the HUD will still display the pipper. Upon press and hold WPN REL, guidance to release point is provided in azimuth and time. Just to clarify. Essentially when holding WPN REL, it behaves just like the CCRP submode.
  4. SeaBass80
    Hi, my original post of this problem from April 2022 became stale and has been locked recently. As the problem still persists, I repost it here. In CCIP mode, when the time-delay cue is visible and the actual impact point is below the HUD, the following should happen upon holding WPN REL: (1) the target designation pipper (visible in the HUD) should get glued to the chosen target point. BUG: the target designation pipper gets glued to the ground position that would have been hit if the bombs actually had released the moment WPN REL was pressed. (2) the flight computer should guide to the release point using the azimuth steering line (ASL). BUG: The ASL stays vertically centered in the HUD and does not provide steering guidance to the target. (3) the flight computer should release at the right moment to hit the target. This is working as intended, although the azimuth offset cannot be zeroed by the pilot due to missing ASL guidance. The "correct" behavior is described as such in the DCS F-16 manual, so I don't think there can by any doubt about whether this is correct or not. 240229-CCIP post-designate ASL.trk
  5. SeaBass80
    Here's how I finally managed to join: my account didn't have an age set, and this is difficult to see in the discord app. Go to your profile settings and select "Family Center"... if no age was ever set for the account, it will just ask for the age. After confirming that you are a grown-up, you should be able to join the server immediately, no further settings required. Let me know if this solves the issue for any of the others!
  6. SeaBass80
    I get the same "link is invalid or has expired" - really strange. Does anybody have luck joining the server using the link?
  7. SeaBass80
    Same as above, "unable to accept invite" or "no longer valid". I have the same problem, all known invitation links seem to be not working anymore.
  8. SeaBass80
    This is still an issue. And a big one for usability of the jet. One can adjust the IR Maverick page to allow one to identify targets with the gain settings for the MFD, but switching back to the EHSD page will burn your retina in nighttime flying.
  9. SeaBass80
    Not sure what the status is - maybe ED can update us on the GM radar efforts. Currently (2.8.3.37556) the F-16 AG radar in GM mode can see everything between directly below the aircraft up to the horizon even with the aircraft nose pointing vertically up into the sky. This is not a matter of evidence needed, as it is simply impossible with the radar antenna. Would be great to see improved realism with the GM radar modes one day.
  10. SeaBass80
    When firing a single round with the gun in high fire rate mode, the shot sound is cut off at the end. Expected: the same single-shot gun sound audible when shooting a single round in low-fire rate mode.
      • 1
      • Like
  11. SeaBass80
    Compare page 6-52 of the flight manual... there is extra variation built into the magnetic compass simulation that includes the effect of the airframe around it. This leads to direction-dependent extra degrees added or subtracted. Up to -2deg to +3.5deg as far as I understand. This might contribute here. Second thought, I take that back. It only seems to relate to the tiny magnetic compass Kl-13. Forget what I said.
  12. SeaBass80
    Hi, the "Light landing-search On/Retraction/Off" keybind only offers "down" and "up" keybindings, not the "retraction" one. The "up" and "down" keybinds literally do what they say... they switch one position up or down, respectively. Expected: keybinds for the individual positions "on", "retracted", "off".
  13. SeaBass80
    Hi, I found a minor bug with the new pilot model. The HMS sight flip-down glass hinge is on the right side of the pilots body when viewed from outside (the new pilot body). From the pilot's view though (at least in VR) the hinge is on the left pilot's side, though.
  14. SeaBass80
    Is there any public info on the vertical beam divergence in GM mode? Can the APG68 switch off parts of the emitter surface to get it to emit from a narrow strip in order to achieve a high vertical beam divergence? [Edit: beam spoiling would probably be accomplished by phase scrambling.] Such beam shaping would likely severely reduce the available beam intensity (power per solid angle) due to using onmy a fraction of the planar antennas and due to the increased divergence. Thus the distance range would be limited, right? The OP still has a point, even if there was this kind of extended divergence. At the moment, the ground radar does not respect the airframe orientation. You still get the same radar map even when you point the airframe vertically upwards. This is physically impossible and something that should be addressed for realism.
  15. SeaBass80
    This unrealistic ground mapping is present in both the f-16 an the f-18. For the F-18 see here: Sadly there was no response to this since July. Let's see whether we can get a comment this time.
  16. SeaBass80
    As a suggestion for further improvement: It would be more immersive seeing just a tiny amount of stick movement due to user input, reflecting the fact that forces are applied to the stick. This would tremendously help in visually seeing that the hotas binding is correct and indicate to the pilot/user that something else is missing (hydraulic pressure) to go ahead.
  17. SeaBass80
    Same problem here in VR: approaching the mirror apparently zooms the mirror image. Very eye-twisting effect - I thus have the mirror switched off for the time being.
  18. SeaBass80
    Since the 2.8 update, the cyclic stick and collective lever cannot be moved before an engine has been started. I presume this is a bug? Here's hoping that I don't have to produce a track file for this, as it literally is the first thing noticed upon cold start.
  19. SeaBass80
    I haven't used them for some time, so you may be right that this is not something that broke with 2.8 but sometime earlier.
  20. SeaBass80
    Hi, sorry for the delay. I attach a short track that shows the sounds for the gun pods missing when inside the cockpit. Externally, the gun pod sound is OK. The main gun is audible both in the cockpit and outside. I don't have any mods for the Ka50 installed and ran a slow file check via the repair tool, which returned OK. Thanks for taking a look. 221105-Ka50-gun pod sound.trk
  21. SeaBass80
    Hi, after the 2.8 update I am missing the sounds for the external gun pods. They are completely silent upon shooting (at least when listening from within the cockpit). Can others reproduce this? No mods are installed on my system.
  22. SeaBass80
    BigNewy, I think this is worth revisiting by ED, even though it is marked as "correct as is". At the moment, the scan time for DBS1/DBS2 is independent of azimuth setting, and I guess this is correct as based on the what I can see in documentations. There should be no speedup for these modes when swithcing to A3 or A1 scan azimuth setting. For the EXP mode I don't understand why there is no speedup, as it is just the expanded NORM image from what I gather in the available documents. There is a closely related issue that the azimuth scan shown by the little "T" mark indicates the radar actually does two full-angle A6/A3/A1 sweeps for each DBS image. I would assume that the radar actually only scans the angle ranges needed for the patches for such images to keep the update time and data gathered from ground reflections optimal. Another related bug is that in EXP/DBS1/DBS2 and A1 or A3 sweep setting, the radar dish is indicated to sweep around the 0° azimuth even for off-bore targets. This is very likely a bug. In NORM, the antenna is correctly indicated as sweeping around the cursor position at an off-bore azimuth. Edit: attached track 220829-radar scan azimuth indicator in EXP.trk
  23. SeaBass80
    I just noticed that the switching between real beam mode (RBM) and enhanced ground mode (EGM) has an effect on the NORM GM radar image resolution even in FREEZE mode when the radar is not updating and not emitting. On the other hand, in the EXP expanded field-of-view mode, this is not the case. Switching RBM/EGM does not affect the EXP image until FREEZE mode is exited and the radar image has updated. I feel that only one of the two behaviors can be correct. As the EGM likely involves on-the-fly processing magic during the radar sweep, I presume the behavior of the EXP/DBS1/DBS2 modes in this regard is correct and the behavior of the NORM mode is incorrect? Edit: attached the track 220829-RBM-EGM-FREEZE.trk
  24. SeaBass80
    lethal205, the "why would one expect" wasn't meant as an offense if this is how you understood it - sorry if you have read it this way. I just really couldn't belief this is how the real system would work. Thanks for clarifying, Frederf. This is indeed different to what I expected. So, from what I now read in the public documents that I have flying around, the DBS1 will always be the same patch size as EXP, which is 3.5nm x 3.5nm at 10nm range setting and 21nm x 21nm at 80nm range setting. The DBS1 will provide a higher resolution "up to 24:1" compared to NORM though due to the Doppler-processing applied. The DBS2 is described as "roughly half that size" in nm x nm at even higher resolution "up to 64:1" compared to NORM. Is there some usability logic for the pilot as to why the mapping goes to NORM when changing the range scale?
  25. SeaBass80
    Why would one expect that the DBS modes respond to range scale settings in the first place? To me this feels incorrect, as the range setting only determines the maximum return times for the AG radar image to be displayed on the ground map. The two DBS modes I would expect to have the same scale whatever setting is used for the NORM AG map range. I don't have evidence unfortunately but this is what I feel would be correct based on my understanding of the radar. Maybe Frederf knows more, he seems to have a lot of in-depth insight.
×
×
  • Create New...