JayPee

They'll have to release Tatooine (NTTR) first.

Not true. The camera unit does have 4 IR LEDs to light up the cap reflectors, should you use a cap. However, when you use the Pro Clip (and you should) the 4 IR LEDs are turned OFF completely because IR light is generated from the LEDs on the Pro Clip. This way there is no IR light source pointing even remotely at your eyes, should this be your concern.

Dude, really? Check your calendar.

Yes. There is no such thing as an IR freq/code for the IR beam which only makes it visible to certain NVGs tuned to that freq/code. Atleast not in DCS.

This.

Still works here. Double check folder structures..

If, for whatever reason, you want another helicopter sim from time to time your best bet is either the Dodosim Bell 206 for FSX or any helicopter which is supported by the HTR (hovercontrol.com) add-on for FSX. You can't consider it proper training software but their flightmodel is the closest to realistic behaviour currently available to the consumer market, besides the Mi-8/UH-1/Ka-50 of course.

I really hope that if people take simming seriously they do not buy a TN panel in the first place...

Then I was probably talking about an earlier build/version which still had the requirement of FPS into the 90ies in order to provide a smooth and accurate experience. Still, 60FPS constant is not something easily achieved on the mid-end rigs of today.

Join a squad. Seriously, join a squard. There is nothing that beats proper training of TTPs and flying in general than an experienced instructor.

Perfectly said. For games other than fast paced FPS, so that would include flightsims, in case your GPU can't keep up you're often better off with a constant 30FPS instead of a continuously changing FPS between 30 and 60. Back to the OP, for the current dev kit of the rift you do need a constant 90 (or was it 95?) FPS in order for it to work and to not puke your guts out after 30 minutes of simming. I believe this is one of the major drawbacks of the current build since there are hardly any modern games that can run at a minimum of 90 FPS at all times with decent settings. And since we're in the FPS/Hz discussion anyway, there's a new technology called G-sync monitors. G-sync monitors have a dynamic refresh rate (as opposed to the fixed 60 Hz of the majority of screens) that can be controlled by the GPU. This means that vsync is no longer needed as the screen will only refresh its image when it recieves a new input by the GPU. It is supposed to offer a smoother experience in cases where your GPU can't pull 60 FPS. Whether it is actually worth the bang for buck (around 450 or 500 for a G-sync screen) I'll leave up to those who actually have a G-sync screen.

You guys have to be careful with what you assume and/or conclude from ED's updates as half of all the DCS 2-related discussions arise when people (accidentally) spread false information...

EDGE, which is basically the name of the engine used in DCS 2 so by EDGE I assume you mean DCS 2, will be free. Naturally you will keep the Georgia map in DCS, for free. However, NTTR and SoH are said to be payware add-ons, just like aircraft modules and (since recently) campaigns.

It's the default behaviour. I've fixed it by setting the X saturation to 85% and tick the slider check box. Now when I enter the pit I just push the slider forward or backward and back to the center detent. Gives a very nice zoom ratio for a 1080p 24" screen.

http://www.earthpoint.us/Convert.aspx

Thats the point, adaptive vsync does not lock 30fps if you cant manage 60fps.

DCS offers adaptive vsync as well if you turn it on ingame and leave the nv panel set to app controlled. As a general ROT when an option is offered to be set in the nv panel as well as in the game itself you will want to use the game's setting for optimal performance. Basically the nv panel enforces settings that the game by itself might not support.

You gotta be kiddin' me, right?

I think you're better off playing wannabe gangster GTA.

Lol, yeah. Nice quote.

Note that vsync in most games nowadays (including DCS) is adaptive vsync. Meaning when your GPU renders at 60 FPS or higher it'll kick in and limit FPS to 60 as to prevent tearing and maintain consistent smoothness/accuracy. When FPS drops below 60 however, vsync is turned off so the game won't limit you to keep a constant 30 FPS or even 20 FPS.

I'm sorry, it must be something you are doing wrong... Are you sure you are trying to bind a KEYBOARD key in DCS? Not a MOUSE or JOYSTICK key/button?

Can you verify in Windows (notepad for example) that mwheelup and mwheeldown do indeed give the NumPlus and NumMinus input? You can indeed use the left mouse to turn the knobs but 'ticking' them up and down with the wheel is more convenient imho. EDIT: Make sure you download AHK from http://ahkscript.org/ and not from http://www.autohotkey.com/ The latter is the old site (with the old version of AHK)

You need to make sure you use the proper way of implementing the script in an application. Not every game requires the same method. DCS requires SendMode Input. Make sure the first two lines of the script are: SendMode Input #SingleInstance Ignore PS - I do wonder how you are going to turn your dials and stuff if you block your mwheel to use it as a throttle.

Use AutoHotKey (AHK) to create a small script which turns mwheelup and mwheeldown to two key combinations you don't need for anything else in DCS. E.g. mwheelup > CTRL + ALT + Pg Up, mwheeldown > CTRL + ALT + Pg Dn. Then go into DCS and bind this two combinations to both throttles up/down.