Moonshine

^ this

You need to be in point track or area track to slew the pod. also if you are in CCIP bomb mode or have the gun selected, the pod is slaved to the pipper location and cant be moved. if your pod is in A-A mode it cant be slewed either and is slaved to the FCR

Yes we dont know the config however, i highly doubt that they fly anything else than clean config with a passenger on board…

This. absolutely ridiculous as it is now. Like a paper plane. I understand it isnt as robust as the a-10 but please..

any news on this? currently impossible to hold knife edge with a clean jet without the nose dipping down towards -5deg even with full rudder input. the video posted by 777coletrain suggests a different behaviour in the real jet than what we currently have in DCS. if you listen to that conversation its quite obvious. plus tracks have also been posted...

this. SPI is SPI, no matter how the SPI was set. the mav does not know the difference between VIS and PRE, these modes are only methods to set the SPI, has nothing to do with the mav itself. after setting the SPI, the mav will then slew to that SPI and thats it. so yes, if the mav slews to the SPI in PRE as the plane starts turning towards it, so should it in VIS the only mode you have seekerhead-limits is BORE as there you set the SPI with the mav itself using the HUD Boresight cross or the mav WPN page and if it would really be limited by seekerhead FOV, then it would even have to take into account which wingstation is used (left or right). makes absolutely no sense at all

Any news on this? seeing the topic still has the "correct as is" tag, yet the last comment and the info @KlarSnow brought up suggests otherwise...

there are multiple reasons for the RWR going silent 1 - you are in the notch, missile cant see you anymore - RWR silent 2 - you are in a bank so that the missile is in the blindspot of the RWR (directly below you or above you) 3 - missile lost track on you and cant find you anymore when defending a Fox 3 (Amraam for example) if it starts again shortly after your maneuver, chances are you are no longer in the notch and the missile has reacquired you and is tracking again or a new missile has been fired. usually you can see a radar guided missile on the RWR as "M". if there is only 1 M showing and the M is blinking, chances are its the same missile that has found you again. if there is a second M showing and blinking, a new missile has been fired. if the M is on the RWR (not blinking) but the RWR is silent, the missile does not see you but your RWR detects the missiles radar beams

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.

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

well yes it is in range if you use the pull up maneuver..

also check those threads/bug reports, they might give you some insight as to how things currently are;

should be correct as you cant drop 2 clusterbombs from the same rack parallel

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

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

havent noticed any change to the previous OB version. did you maybe accidentially switch to CAT III or something?

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

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

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

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..

observed the same in some situations.

sent you a DM

true but also it was not announced in the patchnotes. Probably wait until the october patch…

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: