VC

I thought it was just broken but I was doing some testing with the game only on screen and I could see it fine. But in VR it's missing. Am I doing something wrong or is this a bug?

OK, on your screenshots it looks fine but there's something odd about it in VR. It's really hard to get screenshots that actually show it but I took some to try to illustrate. This is me with a comfortable upright head position. First shot looking forward. Horizon is where it should be and at eye level of the other F-15. I can see 15 degrees down, but the heading tape is above the top of the glass. Second picture looking behind, eye level is almost at the buckles (screenshot doesn't show it how I see it in the headset). I'm actively cranking my head up to see the headrest, which should be directly behind me. Last picture looking down, it feels like the seat cushion is where my thighs should be. This may just be a mental dissonance because I'm quite tall (6'2") and I have an expectation of where my body should be in VR even though I can't see it. Maybe pilot body in cockpit would help but it doesn't seem to work. I'm willing to handwave this as an issue with VR and my height, but then if the real plane had an adjustable seat, that would help a lot in game to get proper immersion.

-15 is indeed a bit too much. But, the sensitivity around the center is not that bad overall. It seems the plane is quite heavily damped, with curve to -10 I can see the stick in the cockpit move a lot for small inputs of my actual JS on my desk, but the plane just doesn't respond a whole lot.

Probably not related to mode but I mentioned it as it's another part of TWS (not necessarily Auto) functionality not implemented.

The advanced features of it are not implemented. Yes, it will track and prioritise targets by default, but it's meant to automatically slew the scan zone to follow the centre or mass of the targets. And the AIM-54 active indication is missing.

I see your point but your drawing exagerrates a litte. In game, the default position is horizontally behind the centre of the HUD glass/picture. Sure you can still see downwards a bit over the nose, not like you're squinting at the top of the instrument panel, but if you look around, down and behind, the seat is not in a natural position, and it's really obvious in VR. Have a look at these guys: https://c8.alamy.com/comp/MXR4WW/us-air-force-captain-patrick-odell-56th-operations-group-detachment-2-climbs-into-the-cockpit-of-an-f-15-eagle-in-preparation-for-a-training-mission-at-kingsley-field-in-klamath-falls-oregon-december-2-2016-the-56th-operations-group-detachment-2-is-an-active-duty-detachment-that-is-fully-integrated-with-the-oregon-air-national-guards-173rd-fighter-wing-the-home-to-the-sole-f-15c-training-base-for-the-united-states-air-force-us-air-national-guard-photo-by-master-sgt-jennifer-shirar-MXR4WW.jpg https://media.defense.gov/2017/Sep/29/2001819997/-1/-1/0/170927-F-IN679-037.JPG They're almost waist-high out of the cockpit. Their eye level is in line with the windscreen frame. It's above the top of the HUD glass. They need to look down a good 10 degrees to be seeing through the centre of the HUD picture. If you move the head position in game to match this, the HUD renders above the glass and you can't see it.

How exactly does this mod work in VR? Tried it and saw no difference. I put the files in Saved Games/DCS/Config/View

I noticed something while flying the F-15 in VR and it's really bugging me. The default head position is directly, horizontally behind the HUD. Sounds OK? Until you look around and see that the seat cushion is where your chest should be, and the headrest on the seat is way above you. Your head position is way too low in the cockpit. Looking at external shots of the real thing, the seating position on an F-15 is very high. If the pilot looks straight ahead he's staring at the windscreen frame. To see "through" the HUD he needs to look down along the nose of the plane. In game, you can adjust this position to a realistic level, that's trivial... but then you can't see the HUD, because it renders way too high in your field of view, outside its own screen. Is there a way around this? A way to move the default position (height) of the HUD picture?

Anything that can fire a 120C shoul also be able to crank to 60 degrees BTW. In the Cat, TWS Auto will handle all this when implemented. In the meantime, just ask Jester to move the scan azimuth. Just be careful with this as it "jumps" and you can lose the target. I would do it in steps e.g. crank left to the edge of scan, ask Jester to move scan left, crank to new edge, ask Jester to move scan far left, finally crank to that edge.

Yup, I kept then MSAA and it's OK. I think my previous test was unfair because my targets were Fulcrums (small) that were also firing at me and being obscured by their own missile smoke. Against a Flanker guns only I can see him fine at 10 miles, and in a dogfigt I could keep track. Fulcrums head on I can see at 6 miles.

You can bean the AI Su-27 in the "dogfight" instant action mission in a single loop. F-5s take a few but are basically sitting ducks because you have so much more power than they do. The key here is to use the F-14 almost purely in the vertical, AB only on the way up, throttle back on the way down. Practice some loops starting at about 400 knots, get them really smooth and tight with constant AoA and minimal speed loss. Eagles have more power than you but you turn better, so flip tactics here and practice tight consistent turning at ~300 knots.

I'm assuming ECM is working because it's not in the list of things not implemented. If you know for sure it isn't then that would be good to know. This doesn't seem like a Tomcat specific question. When do you use ECM in other planes? Basically it's there to frustrate someone, who already knows you're there and is tracking or locking you, when you want to press the attack on them to close range, and you don't care about being subtle (or are unable to). I believe ECM really neuters the R-27ER, if you're up against reds and need to get into Sparrow range without being harassed. A Flanker will burn through quite quickly but not at his max launch range. A Fulcrum will really suffer...

Awesome sauce! Thanks! :thumbup:

I take your point and to an extent it doesn't matter as long as I'm over 45 and can't hit 90 anyway (which might change soon). But it does make spotting worse, which is not as easy to handwave away.

I've read so many contradictory experiences now with regards to VR settings I don't know what to think anymore. I tried 2x MSAA on top of 1.5 PD and yes, the clarity goes up. I also lose between 10 and 15 FPS so maybe it isn't worth it. And spotting is worse. Initially I thought it was a lot worse, I felt like I lost half my spotting range, but actually it's not that bad. Still, dots of enemy planes are not as sharp. I'll keep it for now and play a bit more see if I like it.

Can I ask why you use MSAA with PD 1.5+? Normally it's not worth mixing AA and PD, they do the same job. Also are these settings tuned for better spotting of enemy contacts, or just for the game looking pretty?

True, but in the real world if the pilot physically can't read the labels on things I think the aircraft would be sent back for maintenance.

This was my setting with my old rig that couldn't handle any PD at all. My spotting was OK but I didn't measure distances to know if it's actually better or worse than now. I might try this again to check, but my instruments and everything else looks so much better with PD 1.5 I'd have to see a really huge improvement in spotting to go back to PD 1.0.

I tested this, not with Oculus (because I have Vive), but with Steam VR. So PD 1.0 + SteaVR to 225% is the same amount of supersampling as PD 1.5 + SteamVR to 100%. As far as I can tell there's no difference in terms of visual quality or performance, so you can supersample in game or in your VR tool and it won't matter which. I also tested AF off, 8x and 16x and it seems AF has no impact on spotting airborne targets, at least not against the sky.

But that's not when you need to look. You turn it on downwind after gear and flaps down. Look back, pop spoilers to check it's working, then start your final turn knowing it's on.

Yup, it works. I agree it makes absolutely no sense but it does. No wobble or inaccuracy for small movements, but much better control at high AoA with lower risk of wing break. I also "dirtied" her to landing configuration and could accurately hold 15 units AoA no issue. I see the stick in the cockpit making big deflections around the center as I move my real stick only a little, but the plane doesn't seem to respond as much as you would expect.

A quick glance over the shoulder is enough for me. When you are actually using it and go from full closed to full open spoiplers, you feel the plane drop like a brick, especially if you're already over the deck so you have a very good visual reference.

Yeah it really is great :) maybe it will get old eventually but for now I'm very much enjoying it, definitely completes the experience. My favourite so far, after diving at the sea and pulling up last second: "tell Meg I love her..."

+1 HB have done a great job on the cockpit, but I would also like a slightly cleaner and sharper look for VR while still being able to play MP.

See, I thought I "knew" that as well, but when I went to PD 1.0 my spotting went to hell too. I could barely see the dot at 4nm. Back to PD 1.5 and I could see 7 miles again. So for me PD 1.5 is the best compromise between clarity, performance and spotting. I don't use MSAA at all though, I knew about that one. Does AF actually affect spotting much? That's one I didn't really test except for checking between 8x and 16x for performance. Maybe I'll try that too!