adirtynurse

Its a difference in frequencies of light. Lasers in the IR spectrum are visible with night vision devices. You can see that in the video. KW has the mast-mounted sight that carries the laser target designator. Those type of lasers emit a coded pulsing (aka pulse repetition frequency or PRF) invisible (visible only to specific equipment with the exact same settings) laser energy, that is matched to the seeker's settings (laser seeker on bomb/missile or laser spot tracker with another entity). They are coded so missiles and bombs don't get confused as to where their target is, when multiple people are using said technology or some residual/ambient light happens to be in the same spectrum in close proximity to target(s). They're on a different light spectrum in order to mask their purpose. Laser-guided weapons and the associated PRF lasers are newer technology compared to military technology dabbling in the IR spectrum. Tanks, helicopters, etc have sensors nowadays to understand and give warning to the crew when they're being lased at. So back in the 60s and 70s when semi-active laser (SAL) homing was introduced, it was done so to work in a spectrum of light that was unfamiliar to fielded (and soon-to-be fielded) sensors and countermeasures and at the same time was reliable enough to guide weapons on target. Significant limitation of any light/laser technology is that you have to "see" the target in the light spectrum. Most likely if you can't see it with your eyes, most likely the laser seeker also can't see the laser energy. There's also a different invisible laser guidance technology called line-of-sight laser beam-riding (LOSBR), which is what the Vikhr missiles in the Ka-50 and Su-25T use. In this case the laser seeker is in the butt of the weapon and it tries to center itself on the laser beam that you're emitting. This allows for use of less powerful, thus harder to detect laser designators, but the issue with those are that you can't separate the launcher from the laser i.e. I lase or paint (to use the 90s term :D) the target and you fire the missile. Laser beam-riding doesn't allow for this, while SALH does.

The only issue I encounter now is that CY2 doesn't break off and do its thing. Once I reach the orbit waypoint Chevy 2 is still following me and the moment I hit the Orbit WP they say something to the effect of "on our way" and that's it. Its all stuck from there on out. I tried to go and attack my own targets regardless (with Chevy 2 flight following me), but nothing. Triggers are out of order atm from the

Do we know if this is campaign side or another ED AI bug? Because it seems like a trigger issue.

Still an issue as of now

Nvm it was me being an idiot. Didn't check F10 menu for the ATC call, since there was no pop-up.

Thanks for the good work, Baltic. Keep it up!

Nope. Helos departed all nice. Davy said to take lead and take us back to Lavan. Admittedly, I had been hit and nav was out, but the UHF radio was still operational, because Davy told me to rtb. But no conversations during the flight back to Lavan. I will play once more. Maybe it was a DCSism one time fluke

For me everything went fine. Helos departed, Davy said he'll follow me back to Levan. No other trigger the entire way back to Levan and once I landed, it said I didn't follow ATC procedures, even though I was on correct frequencies, but no triggered actions. And because of that the mission was still considered a failure. d fuk. Also looked back on the tape and Davy did not follow me back to Levan, like he said he would. He was still circling above the target area.

It was a great campaign of short action filled missions with classic corny dialogue. It was a nice change of pace from the hardcore sim campaigns. Well done! Loved your campaigns so far. Btw. Idk if this was a bug or not, but in the last mission Elvis didn't break off to lead me back. Instead I resorted to F10 map to do it.

So been trying my hand at this for another few times now. There's another bug I think. Every other time I've played this mission or so, a bunch of F4s jump the Tornados and shoot them down, before all of them can launch their HARMs, not killing all the SAMs and releasing the triggers. Unfortunately I'm going to have to shelf this campaign again at the same mission for the second time.

After Twister cleans out the SAMs, Chevy 2 won't break off to go and engage their targets. Also Chevy 2 reports engaging targets once you get to the anchor point, not after twister tells them to do so. So essentially I still get stuck in the same place. EDIT: To clarify. After playing this a couple of times, it looks like CY2 runs one of its triggers too early...as soon as you reach WP3 for the orbit. And after twister has triggered all of its actions, CY2 doesn't have the trigger to run again AND that trigger did not work as intended earlier. Long story short, no action compels CY2 to unfollow the player.

Currently if you switch to the front seat (George in the back) in MP, you can't create any point, whether by store button or inputting in through the moving map. Day one issues for a new OB update

Thank you! The new update is baller!

Huey is also considered unrealistic in its FM. Just sayin' This convo brings a smirk on my face every time I read it. People complaining about their milk going bad, when the cow hasn't even been born yet

Yep. This bug is still a thing. I chose Option A and go for the tanker, but the tanker is bugged. Doesn't release the drogue, so had to skip it. Adding an F10 option to jump to Mission 11B after choosing Option A would be preferable. Honestly I won't play mission 11 again, because of the first bit being too long and boring just to through it again.

Request NVG hasn't worked for me as long as I've used VAICOM. So about two years. It doesn't work for me in the Hornet nor the Harrier.

Thank you. I've been powering through your campaigns and been loving each one so far.

Just finished First Blood and already loving this campaign. That being said when the Floggers spawn in the scripted radio call gets drowned out by the vanilla AI radio calls. I do love that I can command my wingman though, just noticed it in that moment. And going forward I got a gut feeling it'll happen again at some point.

Entire Shamrock flight was shot down just today by SAMs.

Most likely. They spooled up their aircraft ahead of me. Picked up to a 1-3ft hover for about a minute or so, then went skids down and shut it off again. At that point I left the base. Looking at the .acmi file they spool back up again at some point and again do a slight hover something happens, that they "crash". Don't know what though. No humvee or infantry is near to them during this time. Over-all it didn't take away from enjoying the mission tbh, since with the way you've simulated the Charlie gunships I'm sweating bullets the entire time, careful not to blow the engine

Truly not a big thing. When the Huey goes down, then the directive says 2 LICKS not Klicks. Overall it be nice to be able to give commands to the AI wingmen. Right now they don't seem to do much.

Nope. The attack on enemy outpost one. I remember the convoy escort. That one was scripted. All good on that one. This one seemed to be a bug though. They didn't lift off with me and half way through the mission when I was over the target, they called out "2 ejecting". I get back to base and there they are, still on the pad. Missing the entire main rotor and tail I've attached the screenshot from the end. I also have the .acmi file if you need it. It was too big to attach to this post.

Its not a campaign for the novice for sure. I definitely haven't mastered the Huey, since I jump around a lot between modules, I can hold my own in one. I didn't learn so much about the Huey (as it is an analog aircraft), but it has been challenging af. I'm still grinding my way through it and its a love and hate relationship at this point I'm at mission 10 as I'm writing this brief. Each mission has stressed me out, while have been a huge relief and happiness when I finally land.

Trail helo powers up and power down immediately. Won't take off.

Still as of today. As reported above. The DRYAD red lines of set number codes have a typo. Use the bottom one, that's the one being used by Max. The other two are incorrect. And gives you the wrong coordinate. Only one digit is off and the difference is 290nm