krad_1337

Ok. I didn't realize that was a thing -- Thanks everyone for setting me straight. More deets . https://www.youtube.com/watch?v=y2v9ct9cEzY

Practice bombs such as the BDU-45B and BDU-33 cannot be dropped using CCIP. When selecting CCIP mode, the jet goes into 'AUTO' mode. Steps to Reproduce: Load up an FA18C with both BDU-45B and BDU-33 bombs. head to a bombing range, arm the jet. Stores Page -> BDU-45B or BDU-33 boxed; Click 'Mode' -> Click 'CCIP'. Expected: CCIP symbology in the HUD. incl 'CCIP' letters. Actual: AUTO symbology in the HUD, incl 'AUTO' letters, countdown to auto release.

Great campaign! I'm half-way through and really enjoying it. I just 'completed' the SEAD hawk at Bandar Abbas mission (miz 6?), although both times I flew it I got a 'draw'. Both times I launched both harms and landed on the boat.. The second time the harms killed 2 components of the site. I was doing pre-briefed shots. Is there some conditions I'm not meeting to get the 'success' on that one? Small bug report - some kneeboard cards have the wrong push time. I noticed this on this mission (:20 not :40) and on one of the earlier missions. And final question, should I be being 'pushed' to marshal on these missions? I usually get the message to fly direct to the carrier, but then when I get to 50 MI I hadn't been pushed to marshal freq and so I switch myself. Do I get 'pushed' over closer to the carrier and I just need to wait till I'm closer and already within the marshal's airspace?

This got me on a mission last week. Not doing the ATFLIR TDC-depress and then waiting some time before dropping GBU-12's resulted in the AUTO HUD cue / drop point calculation to drop the GBU-12's at the WPDSG point. By then a mile plus from the actual moving target point. Result was 2 misses and then eating an SA11. Later testing showed that doing the TDC-depress correctly updates the drop point. Both these issues already tracked internally at ED? or does there need to be one-forum-topic-per-issue? let me know if its the latter I'll open another topic for it.

oh interesting. I may have WPDSG'd the airstart.. commonly I use the AG attack radar in GND mode to find convoy targets and then switch to the ATFLIR. no idea if its related just providing that detail as an extra data point.

I attached a screenshot. If I get a chance I'll record a video and put it on youtube. Sorry for the low rez/pixelated. Laser is armed and lazing. in my testing I'd do some passes at the convoys, verify 'X' symbology, and then go designate a ground target, and verify 'square' symbology. Basically ensuring its failing to acquire moving targets (the bug) but acquiring static targets -- while maintaining all other parameters/configuration in-common. a few notes. your miz file had a lightning pod, I've observed this with the atflir (I dont know if that matters I did not test with a lightning). I am on current openbeta, single-threaded, VR. I can try 'autostart' to see if that makes any difference at all. I figured you'd have my alterations to the 'miz' for cold start w/ the track file I sent but if it didn't load you wouldn't have it. I've attached the altered MIZ directly. main changes are to switch pod from lightning to atflir, switch from 'player' to 'client' (was just seeing if that made a difference, it did not for the hot-start) and to add a coldstart at a nearby airport. agm65e hornet.miz

Air start does not exhibit the problem. However I added a coldstart to your miz and was able to reproduce with the coldstart. track file attached. mav-colds.trk

Sorry for the large trackfile, it was a flight where I was practicing convoy attacks with a bunch of different munitions on a popular multiplayer server (hoggit tnn). I'll give your miz a try tonight and see if it works. If it does work (not broken) I'll try on a multiplayer server and see if its multiplayer specific.

The Laser Maverick / AGM-65-E will not track a moving target. The mav will show acquisition of laser if a static point on the ground is target-designated -- maverick symbology switching from 'X' to square. However if the pod is slewed (to fine-tune the laser designation point) or the pod is tracking a moving target, the maverick will go to 'standby' with the symbology going to 'X' and the MAV being crossed in the HUD. Steps to reproduce: Initial state: Ensure ordinance, atflir, and flight parameters are suitable for maverick employment ( can be verified by shooting a maverick at a static target) Have the MAV display in the left DDI, ATFLIR in the right. Box TRIG in ATFLIR. have a target ahead in the forward view of the maverick seeker. To Reproduce: Use the ATFLIR to track a moving target (point track). use the trigger to laser designate the target. Expected: MAV symbology goes from X to square as happens with a static target Actual: MAV remains showing the 'X' symbology indicating no lock. Second Reproduce: Designate a static target, use trigger to laser designate the target.. then slew the ATFLIR to fine-tune the designation point. Expected: MAV goes X to square when laser-designating target, remains with square symbology while ATFLIR is slewed. Actual: MAV goes X to square when target is laser-designated. When atflir is slightly slewed, MAV goes to 'X' symbology and remains that way for several seconds after the movement/slew of the ATFLIR has stopped. Anecdotally if the laser is moved while the mav is in flight, to fine-tune a laser designation point, the maverick will widely miss the target (likely due to a lost laser lock) The reason to carry a maverick vs say a gbu-12 is because its better suited to moving targets then a bomb, but unfortunately due to this bug it makes mavs useless for that case. TRK: https://drive.google.com/file/d/1XrVtQDrMvnNbbYA-my5trwcqOS96W4yi/view?usp=sharing