Magnate

I've been flying in the F15E the past couple of days, as a change from my usual routine of Harrier, with the occasional Apache mission thrown in, and I noticed that one of the many fine aspects of the F15E cockpit (this is in VR - Crystal) is the implementation of the internal cockpit reflections. These are significantly better than those in the Harrier. So, I was wondering: would it be possible to update the Harrier reflections to this same standard? I'm assuming you can't simply copy and paste code, but this would be a nice refinement of the already excellent Harrier cockpit if it could be achieved.

I appreciate that this is quite an old topic, but one explanation for this issue is that if you are one of multiple aircraft tanking at the same time you have to use the drogue which has been allocated to you. So, if the tanker has authorised you to tank from the right hand position your probe will simply pass through the drogue if you attempt to connect to the left hand station. So, if you approach the tanker and it's trailing a drogue before you announce "Ready pre-contact" you won't be able to connect to that without getting approval.

As an HP Reverb G2 user I noticed a significant improvement moving from SteamVR to OpenXR. It allowed me to increase my pixel density a couple of notches without losing frame rate. I went from .7 to .9 and that made a big difference in the A2G missions which I fly. I did try a pixel density of 1, but that was pushing it a bit far when flying the Apache, I found. So, I'd certainly recommend it. The actual process of switching to OpenXR is very simple, if you read the instructions. That was using a 2070 Super GPU. This month I treated myself to a 4090 GPU, and despite the cost I'd say it was a good investment. I'm now flying with everything maxed out other than shadows, and I think water detail, and am achieving frame rates in the mid-40s. That's about 8-9 fps better than what I previously had on much lower settings and I'm very happy with the results. On my original settings the 4090 was giving me frame rates of around 90, but I was more than happy to trade surplus FPS for enhanced visuals. I should say that this is all solo play - not multiplayer.

It might make sense to a VR user. There's a huge difference in the refuelling experience when you make the transition to VR. So, although a 2D user would see some of the effects I've described, it would be less so than in VR and so the return on investment is lower. That was my meaning.

I agree that eye candy like this is not a huge priority, but it would be nice to see the positive engagement of the probe in the drogue modelled, and also to see more realistic physics in the hose - make it appear a little less stiff. Still, I suppose that there's no chance of ED investing in this sort of effect with only 30% of players using VR (according to one ad hoc survey recently). For anyone playing on a flat screen these effects would probably not be noticeable in any case.

Is it just me, or does the TPOD on the FA18 have a much more limited tracking ability than that same pod loaded onto any of the other aircraft? The blank screen of loss of track appears when, in a similar situation, other aircraft would still have an image displayed. It's as if it's automatically stowing itself when it is in anything other than an ideal configuration.

I'm glad you got them working. Just one note, in response to your question about the MFSs being coded for left and right: I notice that my left MFD has a bright green LED in its top left corner while the right MFD has that corresponding LED in the top right corner. In other words, the LEDs are in the top outside corners. While I haven't tested this, I'm surmising that these lights are there to confirm that you have them in the correct positions.

I'm not entirely sure that I follow what you're saying, but I want to just confirm that Cougar MFDs do indeed work very well with the Harrier. So, do persevere. Silly question, perhaps, but do you have them in the right place - left MFD positioned to the left of the other one? It's conceivable that the column order might somehow be reversed in your Harrier controls page, with the result that the right MFD appears first in the column sequence. That would naturally be counter-intuitive and confusing. I fly in VR and have some little self-adhesive plastic "jewels" stuck to various of the keys to allow me to navigate them without actually being able to see them. As long as you always put them in the same place it's surprising just how quickly the muscle memory establishes and I find it very easy and intuitive to use.

Hi All, I'm the original poster on this topic, but for some reason didn't get notifications about the replies. So, let me start by saying thanks for engaging. And thanks for resolving it - for me at least. Setting a small deadzone - value 2 - in the non-sticking axis seems to have done the trick. I stumbled on this post while looking for a solution to another occasional Maverick problem. Sometimes I can't get a Laser Maverick to uncage. Earlier today, for instance, I attacked a group of four tanks with laser Mavericks and the first 3 all worked perfectly. When I came back for a fourth pass I couldn't get the Maverick to uncage. I tried deselecting and reselecting the Maverick, reset both the Master Arm and Master Modes but had no joy. In the mission I just flew to test the IR Maverick slew workaround I also carried a pair of Laser Mavericks and had the same issue. First missile worked perfectly, but I couldn't get the second one to uncage. I'm going to continue searching for a topic covering this, but if I can't find one I'll upload a trk file.

Further to that post, here's a track file which demonstrates the unrestricted slewing in the TPOD and limited slew in IRMV mode. Some downwards movement is visible but there are repeated inputs which don't show any downwards response. Mav seeker slew.trk

I'm having a very specific problem with slewing the IRMV cursor. A couple of years ago I put the excellent DeltaSim ministick into my Thrustmaster Warthog throttle and it works very well. I'm currently flying Harrier, Apache and FA18 and the slew works fine in all modes. However, I've recently had problems specific to slewing the IRMV seeker head on the right MFD in the Harrier. It slews perfectly up, left and right but doesn't want to move downwards. Or, it will stay stationary and then suddenly move down way past the desired point. There's no problem at all in the TPOD. I'd read somewhere that unplugging the throttle might help, but that didn't work, and I've also changed to a different mission in case it was something specific to the mission I was flying. Also, on a related note - the appearance of the Maverick seeker box on the HUD is a bit hit and miss. Sometimes it's there, and sometimes not. Any ideas?

I noticed an interesting thing just now, on an Apache mission. I took out four BTRs using Hellfires, and the smoke and flames from the destroyed vehicles were fairly modest, both in terms of height and volume of plume. I then moved in to take out the final BTR in the column using the gun. Not only was the smoke plume possibly ten times higher and larger, but I also got a nice secondary explosion a good couple of minutes after the initial one. I can't swear that the units hit with the Hellfires didn't also have secondary explosions at some point, but the difference in smoke height and volume was very apparent and also much more realistic-looking. In fact, before I'd destroyed the last of the BTRs with the gun I had been mentally comparing the smoke from the destroyed units with that seen in an earlier mission against trucks and tanks and had assumed that the smoke level was associated with the vehicle type. I should also say that I orbited the burning BTR for several minutes just to check that this wasn't an issue of timing. I wanted to be sure that I hadn't missed an earlier, larger plume from the first four vehicles because I was head-down in the TADS. Also, for clarity, I don't have any 3rd party smoke mods installed. So, that's what I've observed, and I'll now fly a mission to see if I can replicate these results and establish whether there is a correlation between weapon type and subsequent smoke/explosion effects. Good old scientific method: observe, hypothesize and experiment! I do enjoy the current smoke effects, and when I'm creating a mission I usually add a little wind at low altitude to make the smoke plumes look more varied and interesting.

I completely agree, which is why I went looking for this topic in the forum. I have created a practice mission for the Apache and it includes several trucks, two groups of infantry - of six and three men respectively - and a group of tanks. When telling George CPG to engage, the list presented to me shows the tanks first - even though they're a few km away - and then each of the individual soldiers, before the trucks. Now, it's true that the soldiers shoot at me, while the trucks don't, but this is only relevant if I'm engaging at close range. So, it would be nice to have a bit more control, although of course that has to weighed against a more complex interface. As a G2 user I also find that the placement of the list - low to my left - is not great, particularly when I'm trying to maintain a hover (without recourse to active pause!) and really don't want to be looking down into the cockpit more than I have to. Having said all of this, I do find the system reasonably intuitive, and I'm enjoying using it. And, there's also the argument that if the situation on the battlefield in front of you is that complex you should really be in the front seat.

I use a variation of this approach with my Cougars. I have little self-adhesive rhinestones/jewels, rather than the silicone dot, but it's the same principle. I put one each on buttons 1, 3 and 5 in each row (horizontal and vertical). In addition I have one of the dots mounted on the horizontal surface of the MFD frame above the centre buttons on the top and bottom rows. And then on the vertical rows I have the same on the inside of the frame next to the centre buttons. These dots on the frames are useful for centering at the start of a session as my muscle memory gradually kicks in. I believe that using dots on alternating buttons is the best solution since it means I never confuse buttons 1 and 2 or 4 and 5. I bought the dots on a sheet which included a few different sizes but I don't think my fingertips are sensitive enough to distinguish one size from another. I'm also planning to make use of the corner rocker switches. So far, I'm using just the top left one (Gain) on the left MFD which I use for Master Arm On and AG Mode in the Harrier. I must check to see whether I can use the Pinky switch as a modifier with these rocker switches to get even more functionality out of them. As you'd expect, I position the MFDs so as to closely correspond with where I perceive them to be in VR, so the whole setup works very well and feels very intuitive.

Thanks for these. As someone who spends a few weeks in one aircraft and then goes back to another, trying to keep track of HOTAS set-ups can be challenging - and frustrating - so this is a very useful resource. I haven't tried it in earnest yet - just loaded a mission to confirm that they were in place. I like the fact that you've included a graphical representation of the button/switch too, and I'm sure that will be really helpful to users who are relatively new to their Thrustmaster Warthogs. I've always thought it was a shame that DCS doesn't include a graphical representation of the stick and throttle in the controls configuration interface. Trying to remember button numbers is a bit of a challenge - particularly in VR.

If you're using VR then my advice is DO focus on the basket, since the hugely improved depth perception makes this possible. By contrast, when you're flying on a flat screen you're never entirely sure where the basket actually is in relation to your probe, so concentrating more on your general alignment with the tanker does make more sense. Another tip for a learner is to create a mission using the KC130 - easiest airframe to refuel from - and start with a relatively slow airspeed so that your aircraft's response to any stick inputs is relatively sedate.

One of the least pleasant things about the VR experience - for me at least - is the nasty shimmering and flickering effects which you get in the loading screens. To avoid these I simply close my eyes and try to estimate how long the loading process will take, but it's a bit hit and miss. What would be nice would be a simple audio cue to confirm that you've reached the next stable screen in the mission loading process, so that you open your eyes at the correct moment every time.

I've been flying DCS in VR for about 15 months or so, first on a Rift S and now on a G2. I used to play on my 65 inch curved 4k TV with Track IR and I was really happy with that, but once I tried the Rift S I was hooked, and haven't played DCS in pancake mode at all since then. I'm using an RTX 2070 Super GPU and - with the exception of the Syria map which is completely unplayable - getting good results with the G2. However ... I've come to the conclusion that for Microsoft Flight Simulator 2020 I need to ditch the VR and go back to the TV. The trade-off of resolution against immersion is simply too high, I think. While I'm writing, I might just mention that I bought prescription lens inserts for the G2 from VRoptician.com recently. They took about 3 weeks to arrive and I'm very happy with them - in fact I've just ordered lenses for my Quest 2 as well. And, while endorsing kit which I've sourced from Germany, I might as well say how much I like my Monstertech mounts for my Warthog Hotas. They're not cheap, but they're very well made, and I certainly wouldn't want to go back to a throttle and joystick sitting on top of the desk.

Just an update on my earlier post. I received my G2 headset just before Christmas and have discovered that it exhibits this same problem - in other words, it's not a Rift S-specific bug. Over Christmas I took advantage of the free-to-play offer and have been enjoying the F16. However, this also exhibits the same behaviour - looking back over my shoulder can result in sudden dramatic pitch and/or roll inputs - even if I've taken my hand off the joystick with the aircraft trimmed out in stable flight. I came out of active pause once and the jet immediately did a full 360 degree roll. I think I'd been looking down at the rear of the consoles - behind my elbows. I don't recall having had this issue at all when flying the Hornet or the Harrier - just the A10 and F16. While I'm writing, my experience of the G2: much nicer in terms of resolution in the sweet spot than the Rift S, but much less good at the periphery of vision. Also - for me at least - far less comfortable than the Rift S with its halo strap. So, my VR sessions are shorter, but I'm enjoying being able to spot ground targets from altitude and being able to recognise other aircraft - such as the tanker - from longer distances.

I have an occasional problem when flying the A10 C II with a Rift S headset. Sometimes when looking back over my shoulder I experience a sudden dramatic change in pitch. This can even happen when the autopilot is engaged. Anyone else experienced this?

One little tip for anyone trying to learn AAR with a Warthog set-up. I found that no matter what friction setting I had on the throttle it was too stiff and this impacted badly on my speed control. The cure was to disconnect the left and right throttles and to just use the right-hand one. This results in much greatly reduced friction and much easier fine control over speed. Not a solution for the purists, but it worked for me. I use this configuration for both the Harrier and the Hornet, with the left-hand throttle serving as nozzle control for the Harrier. When flying the A10 I have the throttles connected, but I haven't tried AAR refueling in the A10 in ages.

I'd endorse what others have said about VR - the huge improvement in depth perception makes this much easier and also more fun. One piece of advice which I don't think I've spotted in other replies is not to try to learn this with a "clean" aircraft. Do this with some external tanks, even some bombs and plenty of fuel. I may be imagining this, but I found that a heavy jet was more stable and so more forgiving of unwanted control inputs. The training mission has a clean jet, so I'd set up your own mission and give the aircraft a bit more mass. Also, set the tanker to a relatively slow speed at first. And once you're connected, continue to avoid any unnecessary control inputs. Less is more, when it comes to control inputs. Once you're experienced you will find yourself making constant inputs to throttle and stick, but these will all be tiny and done completely by reflex. One other thing: try to build up a mental image of what your path to the basket looks like on your near misses. That way you'll be able to recognise quite early in your approach whether you're on track and so you can avoid unnecessary control inputs at that stage. I learned to do this during a week off work between Christmas and New Year - many, many hours!

Well done for identifying this, and thanks for sharing. Problem sorted for me too!

If you haven't already sorted this out, then this might help. I had this problem myself. In the Mission Editor the newer weapons and the TGP aren't shown in the sample loadouts. So, you need to create/edit a new loadout and then go to the (empty) centre station and then select the TGP from the drop down menu. It may take a right click to access the menu - I'm away from my DCS computer. Once you've saved a loadout with the newer weapons/systems they'll appear in the Armament Loadout page for future missions.

A bit of feedback from another new user of the Rift S: After dithering for several months, I finally ordered a Rift S last week and had it on Friday in time for the weekend. I'm used to playing on a 65 inch 4K TV which looks fantastic. I'd endorse most of what I've read on this forum, in that the sense of immersion is great, but after a 4K screen the resolution is very poor. However, the poor resolution is only problematic part of the time. The chief issue is with things in the middle distance. So a tanker in the distance is just a fuzzy blob, and the same is true for the carrier. However, once you get close this ceases to be an issue and the sense of immersion takes over. You see the whole of an enormous C130 floating above you, and refuelling becomes even more fun than it already was. Being able to see the precise relationship between the basket and your refuelling probe is great - no comparison with the 2D version. The carrier is a blob until you get close, but those last few seconds as you land there's a real sense of the size of ship. Reading cockpit instruments is not a problem for me, and of course there's the zoom function if you ever do have an issue reading a particular figure. I understand that the Rift S is a big improvement in this respect. Speaking of cockpits, the sense of being inside a cockpit is extraordinary - no amount of TrackIr is a substitute for this. The inside of the canopy actually exists as a real 3D object, and the HUD is also transformed. Lighting effects - sun's glare - and volumetric clouds also work very well. I had been a bit apprehensive about narrow Field of View, but haven't been aware of this as a limiting factor. IRL a helmet would limit a pilot's FOV to some extent in any case. Sense of height and speed is enhanced and I occasionally found myself with a moment's vertigo. However, I see this as an endorsement of the realism, not a problem, and I didn't feel unwell at any time over many sessions over the weekend. Mountains, hills and valleys all become far more 3-dimensional - flying low and fast over a ridge feels real - there's a genuine sense of an actual hill top. I'm a ground pounder rather than an A2A fan, but I did fire up a WW2 dogfight and the first time you have an enemy zip past you in the initial merge is a revelation. The only problem with dogfighting is going to be resolution and identifying aircraft. My hardware is decent - 32 GB RAM, 1080 card - but not extreme, and I can say that I haven't yet been conscious of any performance issues. I've found the headset as comfortable as one could expect, and no problems as a glasses wearer once you work out a routine for putting the headset on and off. I just loosen the retaining knob at the back and rotate forward from the back so that headset falls clear of my face. Could I go back to my pin-sharp huge TV with TrackIr? Probably not, but I'll certainly be looking at upgrading to a higher resolution VR headset before too long, I suspect.