4.33 u1 Maverics issues questions
-
Hello there,
first I would like to thank you very much for amazing job being done here.Recently I watched the following video:
I’ve noticed few possible issues in this video, also confirmed them personally in 4.33 u1:
- Mavericks are VERY slow now, I usually overtake them 20 seconds after release are they modelled correctly? It looks wierd, definetely something has been changed, not sure if realistic.
- Mavericks have shorter range now. I know it depends on my speed and altitude but this seems to be changed as well. If yes - why? Is it more realistic now?
- When boresighting the mavericks, although I put the aim cross (on WPN page) on the target (BSGT available), the circle on the HUD does not match to what I can see on WPN page.
It used to work correctly in 4.33. Is it done on purpose? It just looks wierd. - When in AG, with FCR locked on target with mavericks loaded, when entering MARK mode, it defaults to HUD, I’m pretty sure it should be FCR mode instead.
Anyway, these POSSIBLE issues with mavericks really bother me. Can someone confirm above?
Maybe it’s done for purpose, if yes, please confirm this too.Thanks in advance,
Fly safe -
- Mavericks are VERY slow now, I usually overtake them 20 seconds after release are they modelled correctly? It looks wierd, definetely something has been changed, not sure if realistic.
- Mavericks have shorter range now. I know it depends on my speed and altitude but this seems to be changed as well. If yes - why? Is it more realistic now?
It is more realistic.
- When boresighting the mavericks, although I put the aim cross (on WPN page) on the target (BSGT available), the circle on the HUD does not match to what I can see on WPN page.
It used to work correctly in 4.33. Is it done on purpose? It just looks wierd.
Done in purpose, and also more realistic.
To display the HUD circle exactly at the correct spot, the MMC would need to know where the missile looks exactly, which means you wouldnt need boresight
-
Damn never noticed that offset. Now it’s spoiled
-
Damn never noticed that offset. Now it’s spoiled
Normally you boresight to remove that offset anyway.
-
What about drastically reduced range? Can relate to the author of that video re: making boresighting pointless (if mavs are workable only from short range wpn cam should be enough).
-
-
Modular Mission Computer. Basically the hardware that replaced the different individual computers that used to exist on the older jets; the computer that runs most of the jet.
Sent from my SM-N910G using Tapatalk
-
Not that i would know it anyway but… the reduced range seems legit, the insane slow speed seems a bit unrealistic.
-
Whats the insane slow speed we are worried about? Its not like the rocket motors fire continuously for the entire time of flight, is it?
Sent from my SM-N910G using Tapatalk
-
making boresighting pointless (if mavs are workable only from short range wpn cam should be enough).
Oh, it makes a HUGE difference if you can identify and lock targets 20 nm out with the TGP.
-
Yes, the kinematics of AGM-65 always was over modeled so far.
-
Whats the insane slow speed we are worried about? Its not like the rocket motors fire continuously for the entire time of flight, is it?
Sent from my SM-N910G using Tapatalk
No no, i’m not worried about anything! And of course since is something most of us couldn’t know, i have no problem with it, it just feels fat
-
Not that i would know it anyway but… the reduced range seems legit, the insane slow speed seems a bit unrealistic.
Well, the motor characteristics of the Maverick makes it go to M1.3-1.4, in 4s, give or take.
After that, remember that this is a large missile with a big flat noise which is bound to drag a lot, especially in transsonic.
-
So, no workable visual cues of being within launch envelope for mavs?? Correct? Keyhole cross symbology means nothing basically as a mean of knowing when to launch? No DLZ cues too?
How should i know that i am in an envelope?
Perhaps (from that video) there was a mistake having slight nose-down pitch when launching (i know it’s better to loft mavs)?
Need. much. clarification. -
So, no workable visual cues of being within launch envelope for mavs?? Correct? Keyhole cross symbology means nothing basically as a mean of knowing when to launch? No DLZ cues too?
How should i know that i am in an envelope?
Perhaps (from that video) there was a mistake having slight nose-down pitch when launching (i know it’s better to loft mavs)?
Need. much. clarification.Define “enveloppe” ???
There’s a DLZ, if you are in it, you are in-range. if the cross is steady, you can fire and the missile will track.
-
I was under the impression that the HUD and WPN formats displayed a Missile Launch Envelope (MLE) scale to indicate when in range to launch, although it as I recall bases this indication on the range to the SPI, and slewing the maverick seeker does not also slew the SPI. Still, the location of the FCR track is usually a good approximation for in range indication.
Define “enveloppe” ???
There’s a DLZ, if you are in it, you are in-range. if the cross is steady, you can fire and the missile will track.
If I recall correctly, the Dynamic Launch Zone applies specifically to the AIM-120.
-
Yup sorry for terms mixup. So, keyhole is an indicator of good track. Ok.
So, (re: wiki lol), 12nm seems to be Rmax for mav? -
So, no workable visual cues of being within launch envelope for mavs?? Correct? Keyhole cross symbology means nothing basically as a mean of knowing when to launch? No DLZ cues too?
How should i know that i am in an envelope?Please see the BMS-34, pg 158 for specific answers, but the whole Maverick chapter is worth reading.
-
The top of the MLE should always be 10 miles. It should not be possible to indicate a launch range above that (not sure if implemented in BMS).
Also, you should only get the MLE in the case that the seeker is within 30 degrees azimuth of the nose, and the SPI is within 15 miles. Not sure if thats implemented, but if it is, that might be why you are not seeing the MLE scale in the HUD and WPN page.
-
The top of the MLE should always be 10 miles. It should not be possible to indicate a launch range above that (not sure if implemented in BMS).
Not sure, if your talking about the MLE range scale . If you are its is not fixed at 10nm. For the AGM-65A/B range scale is fixed at 10nm. For the AGM-65D, it is fixed at 15nm. For the AGM-65G, range scale is fixed at 20nm
@Blu3wolf:Also, you should only get the MLE in the case that the seeker is within 30 degrees azimuth of the nose, and the SPI is within 15 miles. Not sure if thats implemented, but if it is, that might be why you are not seeing the MLE scale in the HUD and WPN page.
It is