Hippo

Firstly, thank you for your wonderful guide. I posted to mention that on p334 (v 31/12/2019) the item on the HSI described as aircraft heading is, if I'm not mistaken, aircraft track. Sorry if this seems a bit pedantic, but if you wanted to fly to the waypoint and correct for wind (assuming a crosswind component), you would place this symbol directly over the waypoint triangle symbol (or below the TACAN one). It would then not line up with the vertical line above it (which is the heading). This is actually quite useful, as I don't believe that there's any other way to work out a heading correction to compensate for wind and stay on the desired track.

What is it? How is the value entered into the IFEI before takeoff calculated? Does it change as the flight progresses? I realise that there are other posts covering this, but it all seems a bit vague.

Not sure if this is even a bug, or if it's something peculiar about my mission. Apologies if it's me. If I set up a mission at an airbase with the aircraft parked and powered up (ready to taxi), I am unable to activate AUTO (for WP switching) on the main HSI page. As soon as I start to taxi the aircraft I can. On the carrier, however, I am able to select AUTO with a mission set up in the same way (aircraft ready to taxi, powered up).

QFE gives you your height above the runway. I don't know what the USAF does IRL at Nellis or elsewhere, and I'd certainly be interested to know (QNH?). I think QFE is used by some airforces around the world (e.g. UK RAF), and for some reason ED has hard coded using QFE into the game's ATC, and so we're stuck with it (for now). Clearly you'd not have the same issue at the Caucausus airbases. Still, it's a curious choice, since using QNH is much more common throughout the world. *EDIT* From a quick browse around, it seems that QFE is used in Russia, so that explains the ED choice. For Nevada, I would just dial in the QNH into the altimeter instead (available from the briefing iirc, or just dial in the airfield altitude from its chart). *EDIT* And it seems that I Don't RC. QNH is not given in the briefing (althought it really, really should be) - sorry. *EDIT* PS Shamelessly copied and pasted from elsewhere: 1 inch mercury is approximately equal to 900 feet. This calculation is therefore also approximate but is good for airfield elevations to several hundred feet since we round to the nearest hundredth inches. Divide the airfield altitude in feet by 900 to get the number of inches above MSL. Add this to the QFE to get QNH or subtract it from QNH to get QFE. For example, the airfield elevation is 300 feet. Diving by 900 gives us 0.33r. The QFE is 30.12. Add 0.33 to get 30.45 which is the QNH. If the airfield elevation is below sea level, subtract rather than add and vice versa.

:) You and your active pause ;) again! ;) Although I used a very specific example, what I am trying to achieve is to have the aircraft appear in a state that the pilot has supposedly already configured previously, not to take the pilot through it. Your very useful suggestion is appreciated though, and I'll be sure to try it out in other missions.

I have been trying to create a mission that places a player in an F18 just about to commence the descent for a case III approach. The aircraft is supposedly in the hold and about to reach the IAF at 25 nm, angels 10 and commence its descent. I am looking for the mission to start with the aircraft configured so that: TACAN set 27X, with CRS 159 for final bearing set, displayed in AMPCD and RMDI, HSI page. ILS CH 11 set and selected on HSI and displayed on HUD Some checklist items e.g. hook down. Some other minor MDI / AMPCD configuration. The attached mission does what is required, but man, it took several hours of extremely tedious trial and error for me to get there. I have used triggers of the type: X: COCKPIT PERFORM CLICKABLE ACTION (DEVICE, COMMAND, VALUE, "") to accomplish this. Some of this works as I would expect, but some of the UFC buttons seem to require delays for them to register, meaning it takes nearly 10 seconds for the aircraft to be configured. I was hoping that someone who (unlike me) knows what they're doing in the mission editor could kindly take a look at the attached mission and tell me if there's an easier, more elegant way to do this. Thanks. Case III Test.miz

I'm afraid I wasn't even aware of its existence, thanks for pointing it out. To go way off topic, does it work with P3D under Oculus? It would be invaluable there. TBH (and I'm sure I'm in a minority), I've invested so much time and effort with the default kneeboard, that, even with its MANY limitations, I'm feeling very draggy about changing. Anyway, I'm currently away from my VR rig, and I'm sure I'll give it a go when I get back. All the best with it, btw.

Whilst I'm here, I just thought I'd mention that I noticed that turning off the OBOGS OXY FLOW (F18C) on the ground no longer kills the pilot. THANK YOU for listening, and for sorting this out - it's much appreciated (even though it might seem like a small detail).

No need to apologise, especially as you were only trying to help.

Thank you for the suggestion. I was aware of this possibility, but it was having the functionality during "full" pause that I was after, and restate my request that it kindly be considered. Thanks.

As per post title, I'd be grateful if this could be considered. Thanks. (In case it's not entirely obvious, for those who depend on the kneeboard (esp. in VR), it would be nice to be able pause the sim and navigate through kneeboard pages at the same time.)

The correct location is \Users\<USERNAME>\Saved Games\DCS<VERSION>\Kneeboard\C-101EB To remove (almost) all the crap* that's there by default, I delete \DCS World OpenBeta\Mods\terrains\Caucasus\Kneeboard\*.* \DCS World OpenBeta\Mods\terrains\Nevada\Kneeboard\*.* \DCS World OpenBeta\Mods\terrains\Normandy\Kneeboard\*.* \DCS World OpenBeta\Scripts\Aircrafts\_Common\Cockpit\KNEEBOARD\device\init.lua (other terrains are available) (after backing up). Also, it's all replaced following every update. Incredibly, it simply isn't possible to permanently save kneeboard bookmarks. The best I can suggest is that you request it in the Wish List forum. *sorry - imho.

Are you able / do you think it might be possible to position the MFDs so that their physical positions "match" their VR positions? In such a way that moving your (real) finger to a button (in VR) means you hit the physical button? (Hopefully my question makes sense). I have a set of these lying about and have been meaning to try this out, but keep putting it off.

Many thanks for that, what a great tip. Since VR I haven't been in to nVidia settings as I didn't think they did anything in VR. But this certainly appears to work. It does indeed appear to need a restart in VR - I don't recall that being the case before. I'm sure I did restart before - but I could be wrong.

Thank you all for replying. I now have MSAA working, with expected performance drop. Not sure why or how - it "just started" working. Apologies for any inconvenience.

And further issues... tried the C-101CC Nevada practice mission. Get severe artifacting in cockpit when I turn on 4xMSAA. Anyone else seeing this? Only in the Rift S, it's fine in non-VR.

I thought the Oculus AA setting only applied to Home. Anyway, tried changing it, but nothing. I have restarted, makes no difference. I don't remember ever having to restart for MSAA to take effect. I'll say that it could just be me - but I just can't discern any noticeable difference when I turn MSAA (x4 or x2) on. I am assuming from your responses that turning on MSAA makes a noticeable difference for you.

HI. I've just gone from Rift CV1 to Rift S, and had been away from DCS for a few months. Now I'm going through the usual tweaking / testing, and it could just be me, but when I turn on MSAA I can't see any difference. I'm also running MSI Afterburner for performance monitoring, and there is no difference there either. On the CV1 turning on MSAA made a big difference to the image and to the performance. Is anyone else seeing this, or is there some setting I've missed? Running 2.5.5.40647 (not Steam). In non-VR, MSAA does work.

The update I was hoping for was related to the recently-released optimisation, which was supposedly going to bring a 50% fps increase, for which ED's customers have been providing benchmarks, and the findings relating to such. Still, good to hear that new optimisations are now being looked into - thank you.

Bump... anything further on this?

Thank you for that. Please note that labels have been borked for months now, and that they no longer fade in and out, which was a major component of what I was trying to achieve. https://forums.eagle.ru/showthread.php?t=230253&highlight=labels Labels can be turned on and off. There are keystrokes for turning on/off aircraft, ground, and missile labels individually, and a keystroke for turning them on/off collectively. Unfortunately, I can't check what they are at the moment as my PC's on the fritz. But there's a Labels section in the controller options.

The reason it is not clear is because it has not been communicated properly. A change of this significance should be communicated by the change log the weekly update e-mail published every Friday To my knowledge, the only official mention has been in the VR test post by Matt Wagner: This was sent out weeks after the optimisation was supposedly included. This is not the way a commercial organisation should conduct itself, and I'm not surprised some of its customers are left scratching their heads, wondering what's going on.

Thank you. Quick question - is it possible to enable only the anti-aliasing bit of the mod?

Your rant is a collection of straw men, and misrepresentations of what the OP wrote. Have you missed that ED has already promised stated as goals the features that he refers to? https://forums.eagle.ru/showpost.php?p=3977841&postcount=33

Good.