Jump to content

_SteelFalcon_

Members
  • Posts

    595
  • Joined

  • Last visited

Everything posted by _SteelFalcon_

  1. I doubt its some magical info that we‘re missing, it‘s likely a question of how the avaliable info is interpreted. Even in the f-5 the rwr tgt sep button works better than the viper…
  2. That only works since recently, as i‘ve noticed now too that a 6shooter amraam loadout finally shows you TTI and TTA for even the last missile, which was not the case for years until recently. question that now remains is if it is correct that TTI and TTA should disappear when an amraam is being guided but the jet automatically switched to aim-9 since no further amraams remain.
  3. This did solve it for me too. VFOV before the change was stuck at 0.00 Backed up the file, deleted the whole F-16C_50 section from Snapviews.lua, started game, upon spawn, the default view is shown. saved the default view, closed the game, checked snapviews.lua in the dcs.openbeta -> config folder under savedgames, replaced all but the first 2 lines of the snapview 13 with the backed up ones, saved, started up the game again and all i had to do was to re-save my desired zoom level. First 2 lines (FOV and VFOV) got the proper values now again and the view upon spawning in is finally there instantly.
  4. there used to be a bug report linked in here: but that has apparently been removed or relocated. it's weird how currently you lose all Link info when your radar picks up a contact that was previously already marked as friend or foe.
  5. This sounds like you have an axis bound to that HUD Brightness knob that automatically resets the brightness if you let go of the mouse button. check the axis binds and unbind whatever is set to the ICP
  6. Track attached Tacan of Akrotiri (107X) shows distance to damascus airbase and indicates as DAM as station code on the DED. but the TCN locator arrow on the HSI points towards Akrotiri Syria_AKR_TCN_error.trk
  7. aaaah it's been a while see here: the tag is sadly misleading, since it wasnt fixed in oct 2022
  8. Make sure you check the HMCS DED page (List - 0 - rcl i believe) to verify the HMCS blanking settings. By default the Cockpit and HUD blanking options are enabled. depending on where you look, it will blank the hmcs if blanking is enabled. also make sure to not accidentially press DMS down long, which disables/enables HMCS without needing to screw around with the brightness rotary.
  9. Ripple is when you set RP to 2 on the sms page, lock a target with the first maverick, step to the other maverick station, lock another target and then press wpn release. Both stations will fire on their target. works only with lau-117 single racks
  10. Havent noticed this, it felt instant. Do you have a track replay showing this behavior?
  11. looking at @NineLine's video, the problem is shown there perfectly. it takes 8!! skeets to kill a tank.
  12. Both work for me tbh.
  13. comparing the cbu_97.lua from dcs 2.8 and 2.9 for that weapon, it looks like the explosive mass value of the warhead changed from 3.0 to 0.3 that‘s a pretty large difference same applies to cbu-105 maybe that’s a typo @BIGNEWY/ @NineLine
  14. they're switched for me too... weird loading the Static template created from it, it imports like that here's the miz: test.miz
  15. it detects ground units now, most notably outside of 40nm but in some cases also closer for some reason. and yeah, you can shoot amraams at them
  16. MP track from a testing session with some friends. Somehow the SA-6 symbology gets stuck to the edge of the HAD page, no matter the range scale. the dashed line of #1 ends at the location of the SA-6 but for me it was always stuck at the edge of the display. Even when nobody was commanding TDOA anymore, the symbol remained stuck in place despite changing direction Unsure how to relably replicate however. I was pretty far away at the point where TDOA was commanded the first time CAC_TEST_GBAD_Regiment-20231019-205656.trk
  17. i watched your track and for the start you are in dogfight mode but did not choose which submode. note how your HUD reads "NO RAD". after a while, you seem to have moved the radar cursor, which then enters ACM Slew mode. it isnt the most ideal mode to use if you are within less than 1 nm of the bandit that is evading. You would get a lock much quicker by using either the HUD acquisition (tms right), the vertical scan (tms aft) or since you use the HMCS you could use the HMCS LOS ellipse/Bore mode (tms up) when in dgft mode. i suggest taking a look at the HOTAS commands in DGFT mode there's a nice graphic in the EA manual page 452
  18. A specific manual even states that boresighting should be done as far away as possible. It doesnt specify range values.
  19. ED has already internally fixed it according to this: so i‘m confident it‘ll be corrected in the next update.
  20. Or you kill the resupply truck with a gbu 38, then drain all their missiles. No reloads for them
  21. That depends on the mission setting the server runs. If they require pure scripts, it breaks IC. If they don‘t, then you can use it without issue.
  22. Almost. I use the AG radar as a workaround. SP on the AG radar, designate the nearest town you deem convenient, switch to tpod, refine, boresight, profit. or set hud markpoint, make active stp, cz pod, bsgt. There is ways to get around the SP bug on the pod.
×
×
  • Create New...