@MaxWaldorf said in ECM pod power switch - STBY position:
@Viperdriver47 expected on ccip
This is inop
But the -34 manual does describe STBY positionas working for the CCIP version…
@MaxWaldorf said in ECM pod power switch - STBY position:
@Viperdriver47 expected on ccip
This is inop
But the -34 manual does describe STBY positionas working for the CCIP version…
@MaxWaldorf said in New JDAM LAR incorrect?:
@Adam106 Just bear in mind that CCRP and Slant range was completely reworked in 4.36 because it was inacurate before…
So is it wrong? I don’t think so…
There might be room for improvement but @Mav-jp might have more insight!
My problem is that the IAM mode (not regular CCRP mode, which is much better), now bears little resemblance to the real world documentation out there. The rightside LAR bracket for the azimuth/terminal setting is now missing completely.
BMS now uses it’s own JDAM/WCMD/JSOW symbology, made to work within the sim, but it’s not matching the reference material. I recognise that actually alot of the other systems are made that way, and are functional if not entirely accurate (MITL weapons etc). But in this case there is a correct reference, that indeed you’ve used before, and now you’re combining that with your home grown ‘hybrid’ solution. Seems a backwards step, even if it functions more reliably.
Ok, so in the first image from BMS 4.35 you can see a particluar Dyanamic LAR for a IAM release. Conditions were 480kts, 15000ft for all tests. In this case WCMD was used but results are very similar for JDAM.
Take note of the range to target (7nm) and the position of the range carrot. Range carrot is at the top of the ‘inner staple’. In 4.35 this ‘inner staple’ represented the LAR region - weapon had to be pickled in this staple to hit the target.
In the next image, from BMS 4.36, with same approx conditions, take note of range scale. At 7nm the range carrot is now below the ‘inner staple’; the bottom of the inner staple now represents the max level release (0 loft) range. IAM won’t release until within this region. Which is a change from before.
The third image show the loft angle displayed when range is in the ‘inner staple’ region. Similar to the new CCRP range display…I believe the LOFT Angle for a IAM release should display differently, per real docs.
Did the IAM HUD symbology/release logic get changed in 4.36? It sort of makes sense, and functions, but now doesn’t match the real documentation (mainly MLU tape 3 manual). Curious why this was changed, and if it was intentional?
I used the instant action mission, as it illustrated exactly the behaviour I was seeing in my TE anyway.
Thanks.
With 4.36 the JDAM LAR scale on the HUD seems to be an incorrect implementation.
The new behaviour shows a very small dynamic launch zone (R1 Max/R1 Min) staple that resembles the normal CCRP behaviour rather than proper previous IAM implementation.
The scale (R1 max/min) is a very small range compared to previous bms versions, and even has the loft angle displayed, which again seems to take it’s behaviour from the new CCRP stuff. And a level release is inhibited until the loft angle reaches zero. But it shouldn’t…the JDAM/IAM dynamic range scale should be far larger and allow a release anywhere within that region. The new behaviour doesn’t show the inner LAR 2 scale for aziumth settings either…it’s literary too small.
This is a real downgrade over the previous modelling of JDAM. I know there was a bug with JDAM not releasing except at max-ish range, but this wasn’t a change I was expecting, and certainly doesn’t match any IRL behaviour.
I found this
. He explains each one (GS, TI, NC, SD, LOTG, EOMG). With regard to NC (will Flex and EOMG but not LOTG) he says the missile will Flex and glide EOMG to find a target. But if it finds a target then loses track, it will not glide LOTG but fly straight to the last known position. There is but it doesn’t quite explain NC. Both do not say what NC stands for but they call SD “Search Destruction” or “Self Destruct”.
NC stands for ‘Non-cooperative’. I.e the targets are being non-cooperative and they don’t like being found and killed. They may shut off their radars in an attempt to throw off the HARM. Your HARMs will flex to find an alternative target, but once tracking and tracking lost the HARM will attempt to attack the last known location and hope that it’s close enough to do damage.
There’s no need to alter the manual’s table, it made sense and was correct as is.
Profiles don’t contain PRE/VIS preference anyway. Also station 3 initializes to profile 1 and station 7 to profile 3. Profile selection is memorized per station so pressing missile step back and forth will change the profile that was selected as the station selection changes. “RDY” shouldn’t even appear on SMS until inside LAR1. These are errors in BMS.
Anyway, getting two sequential releases of JDAM is problematic. Forget multiple targets or multiple profiles or even LAR2. You fly directly at a single target with the default PROF1 and try to drop 1 bomb at 33% inside LAR1 and 66% inside LAR1. First bomb will go but second bomb will not. Try to drop a single bomb 2/3rds inside LAR1, can’t be done. BMS has a problem where it says you’re inside LAR but you’re not.
100% agree that there’s a problem with 2nd JDAM releases still in 4.35U2.
1st will release fine, 2nd won’t, even when well inside LAR and on axis. You often have to fly back way outside the LAR and back again to get the 2nd one to come off.
The Tornado geometry sounds very similar to the Viper - plus I doubt you can even get a wing into the FOV on that one…so, yes - I’d expect less of a masking issue.
But it’s sounding like the situation with the Hornet is slouching closer to correct for the Hornet.
…I thought the Gr.4 had an EO system mounted directly under its chin? I used to share a hangar with a developmental Gr.4, but that was a LOOOONG time ago, and I haven’t actually seen one since.
Tornado has a LRMTS (Laser ranger and marked target seeker (i.e LST)) under the nose. Gr.4 additionally has a NAVFLIR in a similar location.
TGPs, either the TIALD pod or latterly Litening III were carried on the weapons pylons under fuselage.
Sorry I’ve found my mistake. I was expecting the LIST/MISC/WPT menu to be the entry point for Harpoon data, but indeed it’s LIST/DEST with a Harpoon selected. All working as intended.
But it does leave the question of what exactly LIST/MISC/WPT does?, because that’s clearly HPN related as well.
It should work yes. Please post details if it’s not working for you.
Ok, I’m trying to activate TGT-to-WPT mode for RBL. I’m using the LIST/MISC then option 9 for WPT. Once there I can’t ‘mode sel’ anything nor will it accept any changes. This is with STP 90 already filled in with data (and that shows correctly on DEST and STPT pages).
Harpoons work perfectly fine in RBL with a FCR derived SPI, it’s just the HPN waypoint modes that don’t seem to. I still have the green target waypoint and dotted lines on the HSD, but that’s being driven from the FCR SPI.
Thanks.
I feel like I’m going crazy, but I’m trying to enter a HPN target waypoint in either WPT-TO-TGT or TGT-TO-WPT mode.
I’ve entered the location in a steerpoint 90-99.
I then select that STP as my current SPT, and for the life of me can’t get the DED page to accept any changes. The LIST/MISC/WPT page is stuck in a random STP 18 and doesn’t accept a SEQ or dobber down or anything…. I can’t mode select the WPT mode ‘on’.
It’s new in the manual, but did this get implemented yet? What am I missing? I’ve tried with and without the Harpoons powered up, in flight and on ground…BOL and RBL…
Pretty sure SD is Self Destruct - although not explicitly stated in -34…… You’re not going mad.
No idea about NC…
@Master:
I think its “UNCAGE” long press. Wont hang my hat on it though.
You’re correct. Long press UNCAGE.
Were you using Drift C/O? Not sure at all if this would have any effect. Just a curiosity on my part.
No, I’m in normal and it doesn’t make a difference.
I’m seeing this error in TE and Campaign missions. In Instant Action the SPI diamond in JHMCS aligns with the TGP track perfectly….
Could this be related to DTE load in any way? I’ve cleared out any VIP/VRP and OA data that was there, but still problem remains.
I’ve had a recurring problem now since about the time 4.34 was released.
My SPI diamond both in the HUD and JHMCS don’t align with the true SPI generated by INS/FCR/TGP. It’s always offset by about a mile in a random direction.
I’ve cursor zeroed, and have a good alignment of INS (not sure if that matters, but happens both cold and hot start).
Occasionally the problem doesn’t occur and the two locations line up perfectly. But more often than not I see it, I simply don’t know what causes it, I’ve got a good understanding of SPI / system delta etc……
Anyone else experiencing this?
@Master:
So, here are my 16 things I’d like, with items gathered throughout the years.
-Link 16
-Expanded RCS values (front, side, rear, load-out effects)
-Expanded radar simulation (radar formula, pulse strength, gain, PRF, frequency simulation, frequency hoping)
-Expanded EW (barrage jamming, spot/swept spot, false targets, trackbreaking RGPO & VGPO)
-Multiple target engagement for SAM’s
-Stand off weapon engagement by SAM’s
-ADM-160 MALD
-ALE-50 Towed decoy
-Kinematic (thrusted) flares
-COMAO radio commands for individual flights (hold, push, retrograde)
-HTS slewing SPI (HTSv7)
-Ambiguity zones for older HTS versions
-HTS PT ranging
-HAD to POS handoff
-TGP colored croshair
-A-G JHMCS symbology
Amazing list. +1
I would be a happy man if we could get all that!
After nearly 20 years with Falcon, I’m finally starting to find AAR easier and more interesting.
However, I can’t get the tanker to fly his whole tanker track. I’ve got tanker target waypoints set 50nm apart, and understand the tanker will fly a 2 min holding point at the first point (his anchor point). However, it doesn’t matter where I call for fuel, the tanker never seems to enter the full track, I get the dreaded ‘tanker entering turn’ every 2 mins…
Is there a specific place in the join to call the tanker? Anytime inside 10 nm? Join obs position, then call? While he’s inbound / outbound during his holding pattern?
What’s the reliable way to make him fly a 50nm tanker leg?
jhmcs alignment, A-G markpoint and DTOS
Please this…… +1
JHMCS A-G functions very much needed
I managed to find a hard copy a few months ago for less then £15. Well worth a read.
Not in BMS. I think some blocks/tape have one, but I’m not even sure. It would be handy though
I’m pretty sure a second TMS down after break Area/Point/ inertial track should CZ. At least in some blocks. An F-16 pilot confirmed it in these forums a couple years ago.
I’m really enjoying the SPI diamond visible in JHMCS….we would greatly appreciate the ability to generate HMCS markpoints, please at some point?..… fantastic job on 4.34.