GunSlingerAUS

Once I add this to the LUA, how do I then bind it to my Virpil throttle?

Any chance of an SC version?

Yep, I've tried setting controller sync both on and off, and also the special option for pressing the weapon selector. No diff either way - let's chalk it up to DCS being DCS.

Is there a way to see radar locks for aircraft and missiles? I remember reading that locks was limited to FC3 aircraft in the past - has this changed? Even better would be a radar "cone", showing where my aircraft's radar is scanning. I'm guessing that'd be extremely difficult though, due to the intricacies of radar?

F-14 Displays: added fullscreen support What does that mean?

Update to my issue - my issue seems to have been caused by using the beta software. Andre told me to go back to the release version, and it's now working perfectly - v 2.1.0, which now also includes support for the F-14A

Unfortunately there is no way changing this setting could have any impact on DCS VR performance, as it's a totally different API than what DCS uses (OpenGL vs DirectX). Might I suggest re-testing this setting in a standardised environment and test scene and then posting your findings. I think it's best not to promote incorrect settings as fact, as the combined effect of dozens of these "facts" make it both confusing and time-wasting for users trying to obtain a playable VR experience.

There are many different types of logs that Windows churns out - which one are you referring to? And what am I looking for within that log?

I've been running the v2.1.5 beta with absolutely no problems for a couple of weeks. Turned on my PC today, and it's stopped working. I can start the app, and the icon appears in my list of running apps in the bottom right of the desktop. When I go to right click it to get it going, the icon disappears. No warning, no nothing. I haven't changed a single thing on my PC. I've tried uninstalling and reinstalling, and also checking it's on my list of excluded items with BitDefender AV, also ran as admin and did Windows Troubleshooter. Still no go. JetSeat is showing up in my list of connected devices in Windows. Here's a quick video showing that I've excluded it from AV, the seat is detected, and what happens when I try to run it:

So, when can we expect the super talented, amazing, generous developer of this fantastic app to be able to output radar and RWR screens on to our tablets?

Try breaking the speed barrier in straight and level flight and you'll see one of the obvious issues. Turn rate is also incorrect as of the last patch

I don't use any mods. Tried changing that, no difference. Heatblur?

You'd think so, but our Cat has been effectively grounded for a fortnight now.

It's not crippling, just freaking annoying. What bind should I check? My weapon selector does work and correctly select the various weapons, including guns.

Any update on when we can expect fixes for the missiles and flight dynamics?

I've noticed that if I start a mission with the weapon selector on my Virpil VFX stick set to anything other than the OFF position, I'm stuck with the G6 letters (indicating gun is selected but safe) on my HUD for the rest of the mission - screenshot attached. It doesn't matter if I cycle weapons, turn master arm on or off, or cycle HUD modes - I can't get rid of it. Is this normal, or a bug?

I think these were first glimpsed in screenshots more than two years ago, so their existence doesn't suggest we're nearer to a release date to me. However, GlowingAmraam's recent comments have been new, and suggest that we might get an Xmas surprise. I highly doubt it, but it is possible.

Not all journalists felt the same way. Here's one piece I did back in 2014 predicting it was going to be massive, but in reality the uptake in HMDs has been much slower than I anticipated: PressReader.com - Your favorite newspapers and magazines.

Wow, I didn't even know lens mods were a thing. You'd assume that the HMD manufacturers would be the best at making the lens for their kits, not a third party. I wonder if there are mods for the Reverb G1, as the sweetspot is pretty small...

Sorry, should have been clearer - I have indeed been activating alt-hold mode, turns out that the AP ref (NWS) button needs to be pressed again if more than 10lbs of force is applied to the stick during any AP mode. So, I just need to start banking at the correct angle, then hit the NWS button again to re-engage AP.

I'm practicing flying Case 3 Marshals in the clouds, and am struggling with using the autopilot to maintain altitude. I can engage it fine, no dramas, she'll fly straight and level at the required altitude with no dramas. As soon as I give it a little bit of bank, the A/P Ref light turns on - is that normal? If I turn in a shallow bank up to 20 degrees of bank, she maintains altitude, though she does start slowly descending, at around 100fpm. However, if I hit 30 degrees of bank, she starts dropping out of the sky at around 400fpm. But I've been told it can handle up to 45 degrees of bank during altitude hold - this seems to be untrue?

Would you mind please clarifying? I'd really like to keep my existing configuration, as I made a lot of mistakes the first time I set it up and would rather not do this all over again! "Modules" folder with that in the zip file with what you have on drive C" - so do I just download the file you linked to, extract the modules folder from it, and overwrite my modules at C:\Users\benne\Saved Games\DCS\Scripts\pw-dev_script\Modules ? "You can also copy the contents of the zip file (without the Config.lua file so as not to overwrite the IP addresses in this file), and then, when you need to update the script again, just run the file: update_pw-dev_script.bat located in the folder with the script (the file is fixed so the automatic update should now work fine)" - why would I do this instead of just copying the modules folder, which seems simpler?

Hey mate, how do I "update the modules folder in the script"? Would love to get this going with the 14A. BTW, awesome work on the engine guages, was a very pleasant surprise indeed, and will be extremely useful.

That definitely sounds like a DCS issue, not a Reverb issue. I'd suggest trying the Reverb with a bunch of other programs before you get too concerned. I'm betting they'll all run perfectly.

Pretty much - come in at an angle that should utterly destroy any aircraft, no matter how hardened the naval undercarriage, somehow snag a wire, then watch the nose float from about 60 degrees nose up, gently down onto the deck. It feels rather weird.