Greyman

That'll probably be down to the latest release. I've got a lower spec PC than you and have no problem flying the previous version in the Rift. I'm waiting for these issues to be fixed before I update and you might want to revert to the previous version too. It's possible that ED might drop a hot fix in, but if they do and it works, I will update then.

Incoming F-14? Hi Hollywood. Have you had any contact with Heatblur, about their soon-to-be-released F14 mod? From their latest update, it would appear that they've been working on a new interface with the peep in the back seat, RIO, and I wondered if this might also work with VAICOM PRO? It's not clear whether they're using the radio, hence my question about whether you've been in touch. It'd be great, particularly for VR users, if we could talk to the RIO, in a similar way to the way we can talk to the flight. Edit: thinking about it, which is usually the better route, even if they don't use the radio system, as long as they provide commands, I suppose those could be easily added to the VA profile. Let's see what they do.

Especially for VR users, where finding and pressing the right F keys can be a challenge and immersion breaking, I'd recommend that they at least look at VAICOM PRO, which virtually removes the need to use the comms menu.

Do you know if the chase plane a Viggen too or some other turbo nutter bast of a plane?

My point was that DCS sometimes doesn't react to "request taxi....", but will react to "request takeoff". Whether it is a logic issue, relating to where you are in the dialogue with the tower when you make the request or whatever, i don't know, but request takeoff does seem to have the same effect as request taxi to runway, when you are not already at the threshold of the runway. Edit: ah, never mind. i see that you have fixed it now, so all's good.

Try "request takeoff". I've experienced similar behaviour and to me it looks to be more of a Dcs issue than a Vaicom pro issue.

My Rift is on its way back from being repaired at the moment, so I haven't had a need to start Oculus Home for a while,but is it possible that their software has also been updated and might be causing the issues and not the latest update of DCS?

Maybe Ray tracing would help? ;)

Did you put any weapons on the AI planes? Edit: alternatively, as it seems that wingmen will not engage targets until they have reported them, could it be that for some reason they are simply not seeing them?

Thanks. I'm grounded at the moment, as my Rift has had to go back to the Netherlands, to get a right earpiece issue sorted, but I'll try this when the replacement arrives.

Thanks for that, including the spelling lesson :)

Ah, ok thanks. That seems a little odd, but I'll give it a try. Maybe I had radar altimeter selected when I adjusted it before?? Edit: Yup, that did it thanks. With Baro altimeter set, the altitude reading and baro setting readings both changed as i adjusted the standby altimeter knob, but with Radar altimeter set, just the baro setting reading changed. I suppose that makes some sense, although "standby altimeter" does appear to be a bit of a misnoma if adjusting its setting also amends the primary altimeter.

Do I ever need to input the barometric setting on the Hornet and if I do, how do I do it? I've skipped through the NATOPS and checked Wags' startup video and Chuck's Guide and although I can find references to Barometric/Altitude setting, there doesn't appear to be anything that tells you where and how to do it. I've found the adjustment on the standby altimeter, but as you'd expect, changing this doesn't appear to change the main altimeter reading on the HUD. Maybe I've flown too many airliners, but I would have thought that ATC, at least would require that all aircraft fly at known altitudes, between the 3,000ft, when the Hornet is on radar altimeter, and the standard altitude, 18,000ft on the Nevada map.

Being a bit of a VR nut, the phrase that I noticed and that not a lot of commentators appear to have picked up, was "foveated rendering". When combined with eye tracking, that would dramatically reduce the need for as much graphics horsepower to render the same scene, whether or not it is ray traced. I'm wondering and hoping that this might signal the arrival of the next generation of headsets, maybe at next month's Oculus Connect 5, but either way, when they do arrive, foveated rendering will give VR another boost, when compared to monitors.

It's probably just as well that you said "i ordered too" rather than "i ordered two" then :)

Just get a wheelstand pro and allow your chair to be used for other stuff too. ;) http://www.wheelstandpro.com/products/wheel-stand-pro-for-thrustmaster-hotas-warthog-saitek-x-55-x52pro-x65---deluxe-v2-

NTTR was one of the modules moved onto the new copy system, at the last update, so it looks like they might not have got it totally right.

If you look at the bottom of the screen, you should find a button that combines all of the commands into a single line. The instructions will then make more sense. Also, unless it has been fixed recently, when you paste all of the keywords into the field, you won't be able to see them, but they will still be there.

Maybe check that you have your wheel brake axes set to invert.

A "bug" that nobody else appears to be experiencing. Good luck with getting that fixed. Maybe keep practising and perhaps make sure that you raise the hook so that it disengages when the tension goes out of the cable, as in the video that I linked?

I've just flown that approach, despite ATC telling me to fly the reciprocal approach, and had the red flags on the ADI all the way down. When I had landed, I thought I'd check if it was caused by a dodgy setup of the air-start mission, by shutting down and then starting up the aircraft. When I took off, the behaviour on approach to runway 08 was different, in that the localiser (vertical) needle was displayed, but the glide slope needle was not. This might have been caused by a rather steep approach, aka crap flying, but I would still have expected to cross the glide slope and see the horizontal needle during my dive for the runway. I did do a touch and go, to try again, but I could still not get the glide slope needle to appear. Apart from crap flying, It could also be that the airfield only has a localiser and no glide slope sensor, but I can't find anything about that. Either way, it looks like the instant access mission isn't quite right, in the way that it sets up the in flight aircraft. Maybe give the restart a try and see if you can get the glide slope needle to appear.

the cable will be under far too much pressure for the deck crew to be able to unhook it, even if they didn't mind losing limbs in the process. if you watch RL videos, and maybe trust the people that have already offered advice, you will see that the aircraft unhook themselves, in the manner described by @ESAC_mirmidon, allowing the cable to return ready for the next arrival and your aircraft to taxi out of the way. will save you searching for a video.

ah sorry. it was eagle's "I get constant red flags until I land." that made me think it might have been a touch of finger-trouble, but maybe i misunderstood.

you could check the calibration/axis tune settings for your pitch axis? maybe find a mission that starts you in the sky and see if the aircraft behaves itself when you pitch then?