Silversmith

Yes it works fine in VR

The current Mistral Missile is totally ineffective against flaring targets, a PK around 10-20% which is pathetic. The mistral missile IRL has excellent flare rejection due to its advanced Image processing and Narrow FOV. . Military Today quotes "The Mistral missile has a high kill probability. After firing more than 3700 Mistral missiles of all variants during training it had a success rate of 92 to 95%" . The Manufacturer suggests 97%. Other public sources suggest around 80%. I suspect that DCS is now using a generic 'Manpad' seeker model which is totally inappropriate for a modern missile such as the Mistral. Its like using an AIm 9b seeker for an Aim 9x ! The ORIGINAL mistral model used in DCS was pretty accurate representation of actual performance.

You don't need a profile, just map the controls in DCS.

Any intention to make the L pilot sight adjustable (e.g. like the UH1H). Using the sight currently is 'guesswork'. Currently for guns the sight points short of where the rounds impact. For Rockets the sight points Long beyond where the rockets impact. In the existing L you can see visuals for the sight adjuster, but it is non functional. Ideally the pilot would surely adjust the sight depression to suit the weapon being fired?

Im see that an existing Normandy map Mission works on Normandy 2 with no action required. But what about missions on the Channel Map? WIll they just work, or does the mission need to be converted to use Normandy 2?

Nothing in the patch notes for the last patch DCS Open Beta 2.7.6.12852 and the subsequent Hotfix regarding the mistral missile, but suddenly since the patch seem unable to get a head on lock, only rear aspect, and even then at far shorter range.

Don't know if this is what you were thinking of from a few months ago... Putting this line in your ,,,\Saved Games\DCS.openBeta\Config\autoexec.cfg file MAY give you a VR frame rate improvement . options.graphics.stereo_mode_use_shared_parser = true I believe it was a testing setting, may by now be standard, or may no longer be functional. Does no harm to try.

Is it correctly trimmed to remove slip? If not trimmed the speed will be hugely degraded At 2,600 rpm and 46 MP in level flight at 5,000 ft I get 420kts easily

HA HA, found out how to defeat a bomber squadron. Attack so there is a bomber in line of sight/fire between you and the 'target' bomber. Your target will shoot down his own wingman whilst firing at you !! Just saw a JU88 shoot down 2 of his wingmen!

oops.. apologies, just noticed another thread on the same subject

Bomber Gunners insanely effective? A general observation that the defensive gunners in the Ju88/B17/A20 etc are WAY too effective. Seem to have Unlimited ammo and an insane continuous rate of fie that is totally unrealistic. Bombers like these have no need of escort fighters, they are totally lethal if you get anywhere remotely near them. Makes any interception attempt pretty pointless, not possible to recreate mass bomber raid interception as per Battle of Britain which is a great shame. Needs to be made more realistic.

You can kill them with either Bombs, or around 7 HVAR rocket direct hits from a P51. P51 machine guns do noticeable damage too.

I'm having no frame rate issues at all in VR with the channel map, far smoother than Normandy map. All on High settings & Maxed out pre-load radius (P1.5 and Oculus S'Warp switched off to allow > 45fps). I'm getting 60 to 90fps . For me limiting factor (on any map) comes only in missions with a LOT of units where DDR3 dual channel memory performance is a limiting factor. Graphics card barely ticking over. The latest Nvidia drivers (446.14) gave a big frame rate boost across the board. (Specs: Intel i74970k @ 4Ghz/4.4Ghz Turbo, 32Gb DDR3 memory, MSI GTX1080TI Gaming X (11Gb) Oculus Rift CV1)

There is a +ive side to this, on the FA-18C the central colour MPCD has been largely unreadable with the MAP on for the HSI and SA pages , especially in VR. Since the last update the map and symbology is really clear. I hope any hotfix that might be done can retain that.

Not sure its a channel map issue, I had the identical thing on the Caucasus map after the update. I dropped down to 1.3