Bunny Clark

Hmmmm, didn't see that in any of the missions I tested, which mission are you having trouble with? Do you own the Super Carrier module?

"Score" can mean two things here. I'm specifically talking about the score that the mission designer assigns for objectives, which shows up in the debriefing screen as the "Results" number. That's different from the "score" that DCS assigns you for killing units, which has no bearing on the campaign at all.

I've seen this problem before when the mission score goes over 100. I've not played this campaign, but downloading it and looking at the scoring it appears if you complete both objectives and land your score will be 150/100 which can cause a problem.

Overall, I'm loving the new cockpit reflections, especially on the MFDs and DED. At night with NVGs it's a mess though, the canopy reflections obscure everything but well-lit areas on the ground. It's impossible to make out anything where there is no light. You can see at night better with the NVGs off right now.

A pretty minor thing, but AI F-16C Block 50s equipped with TER-9As and GBU-12s will drop bombs in the wrong order off the rack. It works correctly on player controlled aircraft though.

My guess is because they're hella bright with NVGs. Before the dimmer function was enabled for them NVGs were barely useable in the viper because of the enormous bloom to the left the HUD all the time.

Mavericks seem to have gotten a little love too: In PRE mode after a failed lock attempt resulting in Break Lock, TMS Down reverts to a ground stabilized cursor at the handoff location, rather than a wobbly mess as before. In VIS mode, the next missile in sequence comes up already pointing at the DT, allowing much faster multi-target attacks in one pass. Very happy with both of these

The radar in SEA mode should help a lot with this mission. Also, the easiest solution to spotting units in DCS is always to just turn on labels.

This is correct to the real Hornet. Per NATOPS page I-2-66: "During landing, nosewheel steering is automatically engaged in the low mode with weight on the nose gear."

Awww man, I'm on the last mission and now there's a Super Carrier version Awesome work, if I come back and play this again I'll get to do it with a pretty carrier.

That sometimes happens normally if you're on the edge of the detailed portion of the DCS map, the whole terrain isn't covered by the map layer. You can check this out yourself by going into the mission editor and selecting the "map" layer. Otherwise I haven't noticed anything unusual with the map in my playtesting on the Persian Gulf so far.

New version, with new clouds! Oil In The Water version 2.7 **REQUIRES** DCS version 2.7 (that's a happy coincidence), which for now means you need to be on Open Beta. 2.7 Changelog: -All missions updated with new clouds. -LIGHTENING replaced with ATFLIR in all relevant missions. -All mission scoring updated: now if you end the mission without being shot down and select END MISSION you will advance to the next mission in the campaign regardless of if you completed your objectives. If you wish to immediately try the mission again select FLY AGAIN, if you wish to come back and try the mission again later select CLOSE and confirm that your progress will be lost. If you are shot down without completing any objectives you will be forced to fly the mission again. -Missions 10 and 11 updated to add new AAA barrage fire. -Mission 12 updated with a new, hopefully more reliable, trigger for the strikers completing their objective. I have not taken the time to playtest every mission again, so it's possible some of the weather I selected will make the missions harder than they should be. If something seems dumb, let me know!

I'm also having this problem. My OpenBeta install isn't new but it's mostly clean as I primarily play in Stable and only have Open Beta for testing.

I have my Radar Elevation Control bound to a slider axis and I'm having a really hard time using it with any precision to control ATFLIR zoom. I already have the axis saturation set to 20 with a curve of 20 and I need to move it off center for less than a split second to get it to switch magnification levels. Usually I end up jumping 2 or 3 levels in a row while trying to just do one. Can the sensitivity of this get turned down a bit? I'd like to be able to use magnification levels between full wide and full narrow with my throttle.

Just tested it, Mark Points are no longer erased at all. If you takeoff and land there is no change to the Mark Points at all. If you shut the plane down and restart it the HSI/SA MK OSB will be reset to MK1, so any new Mark Points you make will overwrite previous ones, but the old ones are not erased and still selectable. That segment was talking about A-10s doing killbox missions, which is a pretty different thing. Aircraft carriers operate cyclically, so there's not much opportunity for that sort of thing to happen. Any aircraft that lands is going to be on the deck for at least an hour until the next Event launch, and even if the airframe is being reused for the next Event it'll probably be with a different pilot doing a different mission. And fast turnarounds aren't nearly what they are in DCS in real life anyway. Depending on the aircraft, number of weapons, and number or crew working on it a full rearm will probably take between 10 and 30 minutes, and refueling won't even happen in the same place as ordnance loading on a ground base. The idea of landing, doing a full rearm and refuel in less than 5 minutes, then immediately taking off again to get back in the fight is totally a DCS fantasy.

Just edit the keyboard bindings in Controls just like you would a joystick or any other control device. They are bound to pan view by default, which I imagine you never use. Keep in mind that for VR use you'll probably want to bind them as they're arranged in the jet, which is different than how they're labeled on your keyboard (1 is in the top left on the UFC).

That's really interesting, I had no idea the G limits on the TGP were so low (relative to the Viper's otherwise 9G rating clean), especially since you can't punch that off. I'm guessing that's more to prevent damage to the pod rather than the airframe? ... Mover has flown Vipers into combat IRL.

Agreed. Though I also understand as BN said that modeling radar shadowing in real time is something that's not feasible with the game engine right now.

Did you define a target emitter and was that emitter on? Impacting at the waypoint location sounds like it didn't see an emitting target to home onto.

There were a number of notes in the change log about changes to stores, which should have an indirect effect.

Doesn't surprise me at all, DCS handles visibility in some pretty weird ways. I once spent hours troubleshooting why an AI flight of Hornets wouldn't attack in a mission using AGM-65Fs only to discover it was because it was night time with a new moon. Changing the mission to a night with a full moon solved the problem and they attacked just fine.

Huh, so the Hornet IRL can only mount missiles in pairs on the wings? I had no idea.

That's partly because the current implementation of Zoom on the Lightening looks too good. The Zoom 1-9 levels on Lightening are all digital zoom, so the image at Zoom 9 should appear quite pixelated.

There are two objectives for the mission. You get 30 points for Colt 1 completing their strike, which is measured by one specific Silkworm launcher being destroyed. Then you get 20 points if at least one member of Colt 1 flight survives to leave Iran. My guess is Colt 1 isn't hitting the target for some reason, though that happening 20 times in a row is odd. It always worked reliably for me in play testing, but I'm thinking I need to build a more reliable system for measuring when Colt 1 has hit the target. Can you take a screenshot of the target area after Colt 1 has finished their strike? Or save a track of the whole mission?

That box is primarily intended for AI aircraft, it's annoying that it copies over to that radio preset. You can bypass this behavior by assigning the Set Frequency command as a waypoint action.