Recluse

Simple question: We are looking to TRY some dynamic missions (e.g. Liberation, Snowfox, etc..) for our multiplayer sessions. We are just a small group of 3-5 players and do not use any dedicated server, just have one of us host. Can the aforementioned missions/campaigns be run that way on a Player's machine as host? If not, any suggestions for some that can? Thanks in advance.

Another BUMP... as things go, this isn't a huge deal, and I have no idea how easy it is to fix, but, it is rather strange and still occurring in the latest OB.

Just started messing with ACLS in our Multiplayer Flights, but I was conscious of all the reported incompatibilities with mulitple flights/wingmen and carriers. What's the latest word? The first time we tried the other night this was the setup: Supercarrier Host. 1 Client with SuperCarrier, 1 client without. Both CVN-71 RSV and CVN-74 Stennis in the mission. (STN 336 Link 4, RSV, 349 Link 4) Two of us launched off RSV and the other off STN. Same Landing pattern. Since nobody was VERY familiar with the process, I hesitated to ascribe the various encountered problems to bugs. The only thing vaguely buglike thing was for ME when I tried to land. I got within 8 miles, got the CPL PR and the ACLS seemed to have control. It dumped me in the water about 3 miles from the Carrier. My fault for not realizing this and paddling out. Might not have had the greatest lineup either.. Works fine for me Single Player in the same mission, actually with both carriers. Will this setup work in Multiplayer, or not yet compatible with multiplayer/multicarrier OPS? Thanks!

Yes it is, but it really causes a performance hit! I believe it is due to the textures that are very large. They are addressing it in an update, I think.

Ahh ok.. Took mine, but that was just at launch day. Maybe something happened to the site. FYI, the account on my PayPal receipt was: theocolin@orange.fr

Their original OV-10 download link included an optional payment box. https://splitair.gumroad.com/l/fwzxn

Hi rudel, Just a question: In the PDF that comes with the OV-10, these speeds are shown: The maximum speed for the landing gear is 158 knots. The maximum speed for the Mid flaps is 170 knots. The maximum speed for the full flaps is 130 knots. In your VFR Landing, you have full flaps and gear down with 160 knots airspeed. Maybe the actual NATOPS or other flight manual shows different speeds than the Split-Air PDF. Just asking. I have typically flown approaches much slower based on the 130 knot full flaps recommendation. It all worked out fine for you, though, and higher speeds would be preferable to me for sure!

Great!! Happy that it helped!!

I did verify that clicking off BDA on the MISC screen DOES inhibit the kill messages. Not really sure what RALT + ' actually does. It didn't toggle the MISC setting back on, but maybe it disappears the BDA window when on screen. It doesn't stay on very long, so it was never an issue for me. (VR as well).

A long time ago, I recall seeing pictures maybe in Aviation Week and Space Technology magazine...(i don't think it is video) of early Hellfire tests against a concrete bunker. My recollection was that the missile penetrated one wall and the high velocity molten copper jet blew out the far wall as well.

(As an aside) Do yourself a favor and pick up the FREE Community A-4 Mod! Tons of fun and challenging Carrier Ops. Steam gauges and weapons delivery take some getting used to but it is really a nice mod rivaling any of the Paid DCS modules. Really makes you appreciate not only how far technology has come but how skilled those pilots were without all the computerized assistance! If you fly in VR at all, it is even more impressive!

Well, it fulfills the role of the missing TMS switch for me. I flew with a Cougar for many many years, now I have the WinWing Orion F/A-18 stick and Throttle as I mainly fly the -18 and Harrier for which it works well. When I periodically go to re-learn the A-10C I have to program a lot of stuff in odd places to make up for the differences between the Warthog HOTAS and the -18. It was similarly difficult with the Cougar, but at least the STICK portion could be mapped 1:1 with the Warthog.

Hmmm... MODE (PP/TOO) yes, but honestly, I have always boxed the J8x on the Stores Page, set the release type and Efuz and it seems to apply to all stations without further setting. Seems to be the case whenever there are multiple stations with the same type of weapon, Release type and Fuzing apply to all when set.

I think you can turn it on or off in the MISC tab: (Battle Damage Assessment).. not 100% sure it is the same BDA window that you are talking about which indeed can be set in the Mission Editor per mission. nullYou should also be able to HOTKEY it based on the settings in the UI LAYER: null

YES One JDAM per station: Program 2 stations for PP and enter the coordinates on PP1 for each station Program 2 Stations for TOO and with one of those Stations Selected, feed the coordinates to it with TPOD/WPDSG/HUD etc.. STEP and repeat for the other TOO station 2 JDAM per station: Set one station for PP and program the Coordinates for PP1 and PP2 Set one station for TOO and with the station and TOO1 or TOO2 selected, feed the coordinates to them when they are respectively selected. In both scenarios, when you drop, you need to be VERY CAREFUL about which Station (and -1 or -2 coordinate) you have selected when you drop. I don't recall the logic by which DCS willl step through the stations upon each release, except it is always different than I expect it to be

I agree with the other posters about re-designating, BUT also: Have you actually: - Set the correct laser code on the bomb(s) AND on the LTD/R of the Targeting Pod? - turned on the LTD/R (L-ARM should appear in the HUD) before dropping and verified the Laser is firing after release? You should see a countdown to LASER in the HUD followed by a Time to Impact. If you ONLY see a TIME TO IMPACT then the laser is not set up. Even if your original target waypoint is a LITTLE BIT off, but it is close enough, the bomb should still pick up and follow the laser spot and the targetting pod will fire the laser where it is pointing not at the original designated point. You might be dropping the GBU as a DUMB bomb, and the AUTO release cue of the original point is close enough to get it to the originally designated target as a dumb bomb.

Note that, in my case, I have gotten the ABORT ABORT ABORT! even when doing the SPOT-->IN calls. It may have been due to the JTAC losing sight of the target, but I have had it happen in cases where both JTAC and Targets were stationary.

I have had the same issue with a Mission Editor enabled Ground based JTAC (intermittently). I switched to CTLD for my JTAC/AFAC needs. Not as much immersion as there are no comms (I don't use SRS) but it works well (maybe too PERFECTLY, but I can live with that )

Thanks! That is a good suggestion, but I do not have the SYNC Controls checked in my options, and this only happens intermittently. I DO have an axis mapped to the Throttle for use in COLD STARTS, so I guess it is possible, that occasionally there is a "wiggle" or some spurious input that knocks the throttle out of FLY mode. When I re-watched the Track, the throttle lever was indeed bottomed out. Thanks for the insight!

Starting here vs. posting as a bug just in case. As in the title, every so often upon Spawning in initially or sometimes after landing, I will get this failure: Random system failures are OFF in the Mission. This screenshot is from a HOT START on the TARAWA on Caucasus map but it has happened to me from airbases in SYRIA as well. Anyone seen this? Happens upon spawning in. (SINGLE PLAYER). I haven't even touched anything. null Tarawafailure.trk

Bump? Anything? Just verified it still happens with latest Open Beta.

Thanks Rob! Appreciate the info! I see you provided it on that thread I referenced as well I have never noticed any Safety/Arming delay. The point of CCIP is to PUT THE THING ON THE THING and PICKLE. Even in AUTO, the delay is due to the computer waiting for the calculated release point. If you happened to hit the PICKLE at the instant the Release Cue crossed the Velocity Vector, it would release instantly as well.

Apologies for a potential FAQ, but I couldn't find much in a search or in the Manual or Chuck's Guide relating to this other than this one post - Can someone refresh my memory on the AIMPOINT logic for multiple dumb bomb drops in CCIP/AUTO deliveries. I believe I remember reading that it was different depending on whether an ODD or EVEN number of bombs was dropped. (But maybe that was in the Harrier forum section) My recollection (and the statement in the linked post) was that with an ODD Number of bombs, the AImpoint (CCIP or AUTO?) was the CENTER of the drop, so, if you dropped 5 bombs, the AImpoint was going to be the 3rd BOMB target and two bombs would fall before and after based on the interval, so if 100 foot spacing, BOMB 1 is 200 feet before the target, BOMB 2 is 100 feet before the Target, Bomb 3 is on Target, Bomb 4 is 100 feet beyond, Bomb 2 is 200 feet beyond. I thought that for EVEN number of drops, Bomb 1 was on the Target point, and the next ones were all spaced after the target. I may have gotten this hopelessly reversed. Can someone clarify the Aimpoint logic for me? (Point of AIM vs. Centroid of mulitple release) - Different with ODD or Even? - Different CCIP vs AUTO? Thanks in advance!!

Unfortunately, without one of the available MODS (which I have not yet tried) the NVG's don't work in VR. That is, they work well to see your environment as EVERYTHING is shown in the NVG Green, but that renders the cockpit displays unreadable as there is no "Peeking Under" the circular NVG FOV.

This was reported here: But I haven't seen it in this Bug Report Forum. To Reproduce: Put an Apache on any carrier. Unlock the Tail Wheel. Note the Error in the EUFD and MFD "UTIL HYD LEVEL LOW" Does not happen on a Land Base. Some Anti-Skid setting I am missing? See attached TRKs for reproducing on STENNIS, LINCOLN, FORRESTAL, TARAWA and working fine on the Batumi runway ABEFluid.trk BatumiFluid.trk TarawaFluid.trk StennFluid.trk ForrFluid.trk