Sinclair_76

A 1000 button pushes to start a -64D? What is he doing? Typing a 200 worded IDM message to his wife? Did he drop his DTC, and had to fat finger a complex deep attack? To be fair I bought the book but never read it. The hyperbole killed it for me after the first pages.

Completely unrealistic. Repair might take a minute. Paperwork will take 13 minutes at least.

Something like a training mission. Maybe some traffic patterns followed by some hover work. IRL it pretty much stops there, but I imagine that in DCS you could augment it with some NOE type flying from a to b, where you will get penalties for flying too high. Understanding the symbology could be done by some kind of familiarization flight with the IP and some theory (manual). It's DCS after all and the big rig is a serious helicopter, it will demand some study and training.

The point I was trying to get across that the bag was considered a right of passage in the AQC and it would be cool to offer the same experience in DCS.

No night is dark enough to simulate the bag.

Although sensationalized in Firebirds, or whatever it's called state side, the bag was (is?) considered as a right of passage for the Apache pilot. I would love it to have the option to close the backseat cockpit with light blocking curtains to train NVS flight operations. Especially in VR it could give the simpilot pretty much the same experience as the real deal.

The latest update introduced a bug into the collision model (of the ventral fins?) of the viper. If you are landing with an AoA of higher than 13° this will force the nose down on landing immediately. If you land with a an AoA of around 10° (iirc), the FPV around the top quarter of the bar you can avoid the problem. Although you have to maintain this lower attitude during the rollout as well. Apparently the lower AoA technique is preferred anyhow according a posting on this forum about viper landings.

It's accurate. The faster you fly the more air flows throught the engine the more fuel needs to be added to the mixture for optimal performance.

It escaped me you were the same person. My apologies.

JSOW objectively corrects for wind. It releases the bomblets upwind so when they drift down they will bracket the target. Key to GPS guided munitions and PB targets is to make sure the altitude of the target is correct in ME, elevation of target should be the same as the stpt altitude. Not doing this will introduce errors which will compound with wind.

Thunder! It's not the sound that hurts.

I've created a multiplayer server. It can be seen on a third party website (x51squadron) but not in game. It worked without a hitch before and as far as I know didn't change any settings on any of my hardware. What can I do to get it up and running again?

Proof is in the pudding....

I was/am being pedantic, as I thought that both the Munroe effect (HEAT)as well as the Misznay–Schardin effect (EFP) are both created through a shaped charge.

The AGM-154 in DCS does compensate and releases the bomblets upwind. Seems weird the CB-105 doesn't.

How is it not a shaped charge? It has a shaped (albeit not as sloped) copper liner and a charge.

One thing that immediately stands out is that the Blu-108 seem to be ejected upwind to compensate for drift.

The 3d models in tacview are exxagerated. Distances between tanks and platoons are tight but well within specs.

I wanted to see how much damage 4x CB-105 could do to a armoured company logistical site. To up the challenge I put up a SA-11 site about 4.5nm behind the main site. As well as 2x ZSU-23-4 and a SA-9 as point air defense. The main idea was to toss a CB-105's, one directed at each platoon, in a 30° climb with full burner and bug out before anything could lock me up. Pre-empitve chaff & flare the whole time I am above 100'. Plan worked. Aftermath is scary, the whole site was annihilated. And I was 20nm out when the first T-72 got hit. The SA-11 managed to get 1x missile off, but self destructed due to loss of lock. Tacview-20210823-101822-DCS-Training - CBU-105+.zip.acmi

IIRC. When you save the profile it saves all the profiles of all the devices (columns). But when loading you have to select a device (column) for it to load in.

Try pressing SMS, even if you're on the SMS page, and then S-J. If nothing happens S-J again.

My guess is the Auto-Step Option of the STPT page switched your steerpoint. Supposedly in the real viper the Auto-Step Option is disabled in the A-G mastermode but in DCS it isn't. Happened to me a couple of times that the TGP slewed to the new steerpoint when lasing a GBU resulting in a miss. In the trackfile, after fat fingering in your steerpoints you seem to set the option to Auto-Step.

You're doing everything right if your target gets covered by BLU-97's.

The most common error with PB JSOW employment is not taking into account the altitude of the target. When you put a steerpoint over the target you have to double check that that altitude corresponds with the altitude of the target. A difference between the two will result in the BLU-97 being released in the wrong spot and drifting off course. Worsening in windy conditions. Doing the above gets me mission kills pretty much all the time.

Do you have a mission and track file you would be able to share?