Hippo

There's already a click and hold solution for toggle switches. Perhaps a new key bind "hold switch" (toggle and hold down) which could then be used in combination with the mouse wheel / LMB / RMB. It could be assigned to a joystick button or spare mouse button (I have eight on my mouse). *EDIT* I've posted a request for this on the 2.5 wish list forum - as this would seem a pretty easy option to implement.

From NATOPS Advancing the throttles from OFF to IDLE (during engine start) opens the engine fuel control shutoff valves and activates engine ignition. Finger lifts, on the front of each throttle, must be raised to place the throttles OFF. With weight on the wheels, launch bar retracted and the arresting hook UP or with weight off the wheels, afterburner operation is initiated by advancing the throttles through the MIL detent gates into MAX. On the ground, an afterburner lockout system helps guard against inadvertent afterburner selection. With weight on the wheels and launch bar extended or the arresting hook DOWN, the afterburner lockout extends and the finger lifts must be raised or a force of approximately 32 pounds must be applied before the throttles can be moved to MAX. A retractable inflight IDLE stop extends with weight off the wheels and provides a higher IDLE rpm and reduced acceleration time to MIL. NOTE During high g maneuvers when moving the throttle to idle, the flight idle stop may retract and allow selection of ground idle. With weight on the wheels, the inflight stop is retracted and the ground IDLE stop is used. Moving the throttles to OFF closes the engine fuel control shutoff valves, stopping fuel flow to the engines.

+1,000. A (optional) click as the stop is hit, to represent the pilot irl feeling the stop. Please.

I was just about to ask about this myself. I only have one joystick throttle axis so was setting up keyboard controls for when I need to manage the engines separately. I noticed that using the keyboard there are three areas for the throttle From (1) full afterburner down to idle*, use finger lifts then (2) down to ground idle*, and (3) idle to shutoff. I also have to wonder if it's necessary to map the range from ground idle to idle to the analogue axis, as I need every last mm for flight. Why not just have it assigned to button / keystroke like ground idle to cutoff? I expect there's a good reason? *not sure if my terminology is correct, sorry.

A quite extraordinary post. I'd accuse you of trolling, but you appear to take yourself seriously. Of all the myriad posts on here with gems such as "fps don't matter", "it's ok as long it looks ok to you", "I don't care what the frame rate is, it looks fine to me", etc, etc, you pick on the one post where someone who actually knows what he's talking about has made a considerable effort to take measurements. Which mission was run isn't of critical importance, because the same mission is being tested across different settings, and it's a comparison between settings that the OP is after. OP - thank you for your efforts, you've gone further than any other poster I've seen to back up his findings. FWIW, my very limited testing is in agreement with your conclusions. OP - my apologies if you're a she; but I can't be bothered with all this s(he) nonsense.

I wonder if you could spare a moment to answer a couple of questions, please don't feel that you have to hold back on detail. "turn qual" - what is that? If, it is not possible (or is it?) to have the radios on before the engines are started, how does the pilot communicate with the ground crew or tower before engine start? I've only ever flown (civil) light aircraft, and am used to being able to use the radios before starting the engines (i.e. on battery), e.g. to get an ATIS. Is there a similar thing to ATIS in military flying? I'm very interested as to how procedures differ between military and civil aviation generally. Does anyone have any good links to this?

I am using an X52 Pro, and am finding precision manoeuvres tricky. Particularly in pitch, and the throttle area around 85% - 95% (which seems to be what is necessary for landings). I haven't usually found the need to adjust curves for pitch, roll or throttle before. Just wondering how others are finding it, and if there has been any official recommendation for stick curves? Refuelling, in particular, I don't think can be as difficult IRL as it is on my computer. I would imagine that the real stick provides much more precise control.

Sorry to hear - thanks for posting your results though.

In civil aviation it definitely DOES happen. In military, I don't know; I'd be interested to get an answer to this. Maybe the pilot co-ordinates with the ground crew, and they speak to the tower?

RE: [uSE LEFT CLICK] I know it's a minor issue, but CONSISTENCY would be nice. All other (2 position) switches work with both LMB and RMB.

Post title.

For the benefit of others who, like me, may not find the above quite so obvious: It appears that *.miz files are zip files - at any rate the above can be accomplished using 7-zip. The case of the folders KNEEBOARD and IMAGES does matter. They don't have to be jpegs. I was able to copy png files produced by kneeboard builder, and those worked - saving some time.

Sorry PEBCAK. I was somewhat confused and thought I could assign a DTOT, or that the TOT was a DTOT, or something. Anyway, I see now that I'm just supposed to match the TOTs from the briefings. Is there no way to alter the DTOT for the mission waypoints?

Set up a quick mission to practice landings at BESLAN on RUNWAY 10 at NIGHT. Mission Date 1 Apr 2018 2300 Full moon Runway lights* only became visible once I was very close to the runway (possibly on touchdown). Mission Date 14 Apr 1018 2300 New moon Runway lights never became visible. Are the runway lights dependent on moonlight? Taxiway lights were visible. imho all ground lighting is far too dark (using Oculus Rift). Gamma = 1.8. *I mean the white runway edge lights.

To add my 2c. The low res and fov (think viewing the world through a diver's mask) are a big drawback, expect to make compromises. But still not enough of a drawback to beat the gain in immersion. It's been a bit of a double-edged sword in that once I tried VR, I just haven't been able to go back to using a monitor. I doubt I ever will. For recent versions of DCS (2.5.1 and up), you'll most likely be wanting a 1080Ti. Another surprise for me has been how much I'm enjoying "proper" VR games (clue: I'm not young). I really thought I'd only be using it for flight sims, but since my original purchase, I've bought a 3rd sensor and have had to make room for a play area. Echo Arena, Sprint Vector, Sparc, Brass Tactics... these are types of games I'd thought I'd got bored with years ago. Fun and exercise! I have not regretted buying the Rift, not once. I've had it for nearly a year now.

+1 Not to mention the lack of common courtesy of not communicating a very significant change to their CUSTOMERS. Afaik, there's only been one short sentence in a readme file.

Can you try the test I suggest here: https://forums.eagle.ru/showthread.php?t=210356 You should get over 30 fps with that. I say this in case there is something odd that may be locking your frame rate - but it does sound, as you say, that you have a CPU bottleneck. I can definitely get over 40 fps in VR (as can others). What is your CPU doing when in 2D? I don't have PG btw - not sure if you're only seeing issues in that theatre? "If my GPU is not busy in VR, it should also be possible to get 51 FPS." That doesn't really follow. You're talking about different resolutions and other overheads in VR - the frame rates are very unlikely to be the same. (assuming the CPU is at 100% in both cases).

Not quite what you're looking for, but might give you an idea: https://forums.eagle.ru/showthread.php?t=210356

You've answered your own question. *EDIT* I'm being somewhat unfair, as I'm running in VR. Without AA the jaggies ruin it for me. I was getting over twice the frame rate before the imposition of deferred rendering. Oh good, that's ok then. Everything ED does is wonderful. Criticism is not permitted. We must just hand over our money and smile, smile, smile. Because everything will be ok in the end.

Does anyone know if it's possible for the bookmarks to be saved permanently?

"Those settings are far from optimal for the 1080 ti" Yes (since deferred shading was enforced). Also, DCS image quality in VR without AA is on another planet from optimal (imho).

XMP yes. Turbo boost off - no. Wasn't aware of that setting - will take a look. I haven't (for the first time ever) even bothered overclocking. I'm only air-cooling. As far as I've seen (for me, anyway) it's GPU that's the bottleneck. Thanks.

I'd actually ordered the F-18 back in January, but asked for (and was given) a refund last week. This was the only way I could think of to make my displeasure known RE ****ing deferred shading. I know, I know, big difference that's going to make. Of course, I couldn't resist buying it again on Tuesday. I also got a refund on Persian Gulf. I don't think I'll buy that until I have a system that can run it properly in VR (or it goes on sale). So. I will be staying on 2.5.0 for my other modules, but will tinker with the hornet on the beta branch. So far, I'm managing to get by for very simple training type stuff at minimal settings. The aircraft itself is wonderful. Hopefully by the time the finished product drops 1080 Ti's will be cheaper. I thought I'd settled on 1.5.2, with its excellent performance. But in the end, there were too many little niggles - that will never be fixed. Your seem to have a similar spec to me. I feel your pain, but it's probably worth giving in to the temptation.

Your opinion on 2.5.2.17978.385?

Have you checked the log file? autoupdate_log.txt from your DCS folder.