Jump to content

Moonshine

Members
  • Posts

    596
  • Joined

  • Last visited

Everything posted by Moonshine

  1. this is just wrong. it does let you toss the bomb further than you could during a level flight release, which means you might actually survive and egress or not get in range of enemy air defense. it also allows you to lob bombs over mountains, hills or other terrain. yes it is as it is supposed to be. The DLZ indicates the range for the max pull up all the way to the minimum pull up. the end of the DLZ (bottom line) is the level release.
  2. should be correct as the bottom of the DLZ is the release point for a level drop, everything above that point is a DLZ based on your pull up profile
  3. well yes it is in range if you use the pull up maneuver..
  4. also check those threads/bug reports, they might give you some insight as to how things currently are;
  5. should be correct as you cant drop 2 clusterbombs from the same rack parallel
  6. there is posts about it, quite many actually and quite a long time already: plus this in the hornet section of the 2.8 OB update
  7. after dropping 2 single CBU 105 (not BRU57), the pylons look empty and the sms page shows 0 bombs remaining. however upon pressing emergency jettison, you can see 2 CBU-105 falling off a empty pylon. i have tried to reproduce with all other types of cluster bombs, yet only the 105 shows this issue. Track and Tacview attached CBU105_jettison_ghost_bomb_.trk Tacview-ghost_CBU-105.acmi
  8. havent noticed any change to the previous OB version. did you maybe accidentially switch to CAT III or something?
  9. what he says is true, see my track. i am not familiar with how the real jet would do that, yet it is very doubtful it would revert AG radar back to GM every time master mode is changed. AG-radar_mode_reset.trk
  10. since this thread is not a bug report i suggest you open a separate one under bugs with all the info regarding the radar elevation jumping
  11. still falls short, see tracks attached. note: wind set to 0 to avoid drift to better showcase the issue. Target WP was the middle tank of the group of 5. in both scenarios some tanks were destroyed, however the vast majority of the bomblets did fall short. CBU97_falls_short_CCIP.trk CBU97_falls_short_CCRP.trk CBU97_CCIP.zip.acmi CBU97_CCRP.zip.acmi
  12. I think there is more to this; according to wags Viper mini updates, one of the listed points is „GPS target coordinates shifting“. Maybe that has to do with those weird „near miss“ situations even when the solution looked perfect. the other thing is still the damage modelling. A near miss with a 500lbs bomb should not leave any sort of vehicle unharmed..
  13. observed the same in some situations.
  14. sent you a DM
  15. true but also it was not announced in the patchnotes. Probably wait until the october patch…
  16. no need, there is already a thread about this and is marked as reported: there is also enough tracks for it. and yes it is not working properly according to that thread and the tracks attached. maybe just merge these posts oh and this one also exists:
  17. it was fixed once yet since the last 2 patches its busted again. 97 fall short and 105 drop far (curious how that happens since its a WCMD.. anyways..). besides that 87 and 103 dont really do damage still. bottom line, no cbu is currently useful as the one with effective submunitions are inaccurate and for the other ones you migh as well bring mavericks or use the gun
  18. no issues with the default one. since as you said it would be loaded via DTC anyways, we better off just wait for that. as every pilot has his preference in MFD setup, your suggestion for a new default would take me much more time getting things to be the way I like it than it does with the current one as my MFD setup looks very different from yours. so as it will favor you, it will definitely bother me and surely some other pilots too. hence leave as is and hope DTC isnt years away from being implemented.
  19. i dont think you can disable it. for level drop, just ignore and continue
  20. question: in RWS long pressing TMS up in an empty space on the radar screen activates spotlight mode. the longer the press is held, the more sweeps it does. however, even a very short press of TMS up will enter Spotlight mode. is this supposed to be like that or not? Spotlight.trk
  21. Sorry to bring it to you, the last statement is just „feelings and impressions“ and have nothing to do with factual evidence proving or disproving the function this topic is about and therefore adds nothing to the discussion, only derailing it from its original intention.
  22. any news on this? i get it, lower bar settings do not increase radar power so you technically dont get more range out of the radar. however lower scan area, more scans, more returns should in fact apply as TheBigTatanka said here: at the moment with how hardcoded the radar values are (same example is the lookdown subject) i bet it just wont make a difference to what bar setting you put it to, as skywalker explained in his original post.
  23. same for me. instantly goes to STT upon promoting a target manually. this makes TWS unuseable. hope for a hotfix for that stuff. TWS_direct_STT.trk
×
×
  • Create New...