awjudge

Again, educate yourself before you complain. ED made it very clear for quite some time what the scale and size of the Persian Gulf map was going to be. If you don't like it, it's entirely your fault for buying the map. Personally, I think it's plenty big enough.

With all due respect, you need to go educate yourself. The PG map has been released into Open Beta. You have bought it, which gives you Early Access. You are a tester for the time being. Once ED are happy with the map (and the DCS engine) both will move into the non-beta release. This is how DCS development works, and has done since the first Open Beta release a few years back. If you don't like running betas, or having errors etc, then don't buy early access modules. It's as simple as that.

If you have vSync switched on, that's why you're only seeing 60 FPS. vSync locks your frame rate to the refresh rate of the monitor. Try disabling it? I definitely get more than 60 FPS on NTTR with vSync off.

Hi, We've just flown a sortie, and it looks like the SADL system isn't working? We all had JTRS enabled, and were all part of the same Group ID, but we had no TAD indications of the other aircraft or SPI data. Have we missed something or is this new? Always worked before...

Is it really that hard to check the time difference yourself? 9:00am MST is pretty clear. There are many, many websites that can do the math for you...

This sounds like an Oculus bug. They have a known issue with the current NVIDIA drivers. Try downgrading your drivers to 388.59. Have a look here: https://forums.oculusvr.com/community/discussion/62393/for-users-w-black-screen-on-rift-post-logs-here Sent from my iPhone using Tapatalk

There is a workaround for this. When you connect to a MP server, as soon as you see the list of available aircraft slots, hit the exit button. When you’re back at the main menu, rejoin the same server again. This makes the menu responsive and improves frame rates. Sent from my iPhone using Tapatalk

The next option is to rename your 'Inputs' folder under c:\users\<username>\saved games\<DCS version>\config\ Then restart DCS, it should recreate your control settings from default. See if you still have the same issue.

First thing I would do is check in Windows under Game Controllers. Have a look to see if you can see the buttons getting pressed without your input. If that is happening, it's not DCS... You might have a hardware issue.

The new effects are only in 2.2 and only work with some weapons. Try rocket pods on the Harrier or the A10-C :-D

My understanding is that ED developed the relevant multi-crew code when they made the L39 module. Now the code is available for use by 3rd party developers. Polychop have used it in the Gazelle and Belsimtek are working on integrating it with the Huey. I'm sure there'll be more MC modules down the track.

Yes, it does. You can do this in the Gazelle and the L39 Albatross right now. I believe this functionality is coming for the Huey also. It's not a default feature, the relevant aircraft module has to be programmed to support it.

Letft-ALT + ' (the key to the left of Enter)

I don't think anyone said it would hurt... It's just not implemented yet, and there are ways to get what you want without having to wait for ED/RAZBAM to change the code.

Can you describe your problem in more detail?

For anyone with a Thrustmaster Warthog HOTAS, you can use the throttle detent (also used in the A-10C) to manage the throttle cutoff switch. When the lever is forward of the detent, the cutoff switch is always disabled. Works perfectly.

^^ This. People who buy into Pre-Release modules should have to sign a declaration that they've read the fine print.

Make sure you haven't enabled the Throttle Cutoff Switch. If you do, when you pull the throttle all the way back, it'll stop the engine.

I did this too, 10 minutes ago. Stutter has gone! At last. It's been bugging me for a while.

Yeah, don’t think it will make any difference with VR. Sent from my iPhone using Tapatalk

Touch controllers don’t do anything In dcs yet. I just put mine out of the sight of the cameras. Sent from my iPhone using Tapatalk

2.1.1 is now available on Steam, hence NTTR is also available. http://steamcommunity.com/games/223750/announcements/detail/1451703867052813777

NTTR isn't available for 1.5. NTTR only works with 2.0.

Dinga is pretty much on the money with his advice. A couple of thing I'd add: 1. What you see on the PC screen has already been rendered, it's just a mirror of what's projected on the left screen of the Rift. It doesn't cause any loss of performance. 2. No way to disable it, that I'm aware of. 3. Res should be the same as Oculus. 4. PD is a pretty subjective thing. General consensus is that the image doesn't get any better above about 1.8. Have a play with it and compare your FPS, find what works best. 5. What Dinga said. 7. Perfectly normal. First month of flying in the Rift for me caused me more motion sickness than I've ever experienced! Love it. One other thing, it's very important to make sure the Rift sits on your head correctly. A small deviation vertically can make a big difference in image quality. Just double check the 'green cross' tool in the Oculus Home to make sure your alignment is good.