Zadren

Ok, thank you. That sort of makes sense. It includes lateral movement of the VV. The follow-on question is though: Should I be merely monitoring this difference in VVs, or trying to counteract it? What do I do with this information?

Hi, could someone please clarify what the second velocity vector marker (without the circle) is depicting when in Nav mode. I have a feeling it's correcting for wind, but I'm not certain. I can't find it in the pocket guide, or Chuck's work. :huh: Thanks in advance :)

Hi there peeps. Today I went to use my Oculus for the first time since 2.5 dropped, and was mortified at the quality and performance. Usually, I'm flying on a monitor and only have to tweak things a little in 1.5 and 2.2 to get decent performance if I decide to fly in VR. (I know, I should do it more.) Could someone please point me towards some recommended settings/tips for both Nvidia and DCS 2.5 to get things moving past 15fps, based on the following specs? :cry: i7 7700k running at 4.8 Ghz Asus Strix 1080ti 16GB DDR4 RAM EVO850 SSD Apologies if this has already been answered, but I seem to be tying myself up in knots trying to get decent info. Cheers :helpsmilie:

The MAW went in here on a GR. The small antenna sticking out of the bottom of the dome is a sidelobe suppression antenna, as the MAW was getting triggered every time the aircraft flew over a busy road and picked up moving traffic. Usually on the A1, right outside RAF Wittering. :smartass:

The Harrier GR7 had a Missile Approach Warning system fitted. It was situated in the radome right in the back of the tail. It was a small Doppler T/R that faced aft only. I can't speak for the AV8 having this kit fitted, but I'm certain that the GR7 had it, because I distinctly recall bolting the thing to my jet for flight trials. :)

Just downloaded this and flown it twice. Nice going, Sedlo :)

Make sure you select IRMV (or EOMV) on the Mav screen, once it is uncaged. SS FWD, I believe. Then you can hit the TDC DN (action position) key to try and obtain a lock.

Thanks all. Now I found the fuel flow meter, it's made it a lot easier. :doh: <100 ppm at 30k ft, at about 400 kts. It really drinks it though when you dive down low to make a run - I guess I'll have to bite the bullet and conquer the tanker.

Harrier fuel load is pretty small, and she's a thirsty girl. What is the most fuel efficient altitude/speed to transit to the target area/RTB? Also, are there standard calculations one can do to figure out: 1) How much fuel I need for a particular trip. 2) The best/most efficient flight regime for a particular trip. 3) What I should set as bingo fuel to get home again. I guess all of the above queries apply equally to all the aircraft, but it seems that you really have to pay attention to it in the Harrier - especially since I'm too much of a noob to refuel in flight currently. Cheers :)

Oh crap...this isn't going to end well. I only just got the old girl to fly in a straight line. Now I have to plummet earthwards into the jaws of death.... :pilotfly: :lol:

Bombs too. :thumbup: How do you drop a bomb, in a Spit, with any sort of accuracy? :huh:

Oooh.....slipper tanks!

It's just been releases on the beta client at the mo. 1.58.

I am slowly getting to grips with the Spit, and am beginning to explore its potential. But she's been a tricky beast to get used to (first serious attempt at flying props.) One thing I'm wondering is at what altitude I am going to get the best out of her? The LF designation would have me think that operating at low level would be optimal, but best speed seems to be achieved at about 22000. Obviously you have to fight where there enemy is, but given the opposition, where is the Spitfire best employed? Any and all advice appreciated :)

Yeah, that sorted it. Thanks for the fix :)

Hi, I'm having some trouble with 1.5 release. When clicking on 'Missions' from the main menu, DCS hangs at the loading screen, with the blue spinning wheel hanging there indefinitely. I can load the missions from the editor, but the missions option requires a restart. Repair of DCS has not helped this problem. In 2.0 clicking missions, gives options to launch the Caucasus missions. I'm not sure if this is right or not. Any takers on the above please? Thank you. :)

Hello, thanks for the replies. This issue, if it is indeed an issue and not just me, is something I've only seen with a radar update. I'm still on the learning curve and it seems that radar update would be much more accurate. I tested it out, by plotting a course on NTTR, with my waypoints over landmarks. I was specifically using Hoover Dam as a test waypoint, and flew out of Nellis on a short route (was trying to replicate a Youtube tutorial.) What I found was that on approaching the WP, the cross was not over the dam, where I had plotted it. The PCN displays a correction when I perform a radar update with the reticle directly on the dam, but the WP cross just doesn't move at all. Are these 'smaller' corrections not possible, for accurate bombing etc? Thanks again.

Thankyouthankyouthank!! :pilotfly:

Thanks for your inputs, folks. I have no idea what the Oculus tray tool is. I'll investigate. Was there not some trick involving increasing the resolution in the Nvidia tray past what is needed by Oculus in order to increase detail levels? Or am I way off track here?

Hi guys. I've just fitted my new Asus Strix 1080ti card, which is rather nice. I'm still using the stock settings at the moment, and am fishing for tips on how best to set this card up for DCS. I'm currently running a 1080p monitor, or an Oculus, (with a 4k monitor to come soon.) I can get about 180+ fps in 1.5.7 on screen, and not much shy of that in 2.0. In VR though, it's a different story. In Caucasus, the frame rate seems to be capped at 45 fps, and it doesn't drop below that. In Normandy, the cap remains, but my fps is dropping to less than 30 at times. Is that a hard cap for VR? Can someone please steer me towards the best settings that I can use in both DCS and NVIDIA settings to serve my purposes? I am aware that they will need to be altered, depending on my display medium - but I'd like to have a clue where to start. The major pain at the mo, is having the gunsight in the Spitfire act like it's 'swimming.' The whole thing is really distorted. I had the same issue with my 980ti, and never got to solve it, what do I need to do to stop that? Grateful for any help or pointers offered. Many thanks.

Cheers mate. Didn't see that. :doh:

Hi guys. I've just fitted my new Asus Strix 1080ti card, which is rather nice. I'm still using the stock settings at the moment, and am fishing for tips on how best to set this card up for DCS. I'm currently running a 1080p monitor, or an Oculus, (with a 4k monitor to come soon.) I can get about 180+ fps in 1.5.7 on screen, and not much shy of that in 2.0. In VR though, it's a different story. In Caucasus, the frame rate seems to be capped at 45 fps, and it doesn't drop below that. In Normandy, the cap remains, but my fps is dropping to less than 30 at times. Can someone please steer me towards the best settings that I can use in both DCS and NVIDIA settings to serve my purposes? I am aware that they will need to be altered, depending on my display medium - but I'd like to have a clue where to start. Many thanks. :)

When I'm flying the training mission that includes updating the INS, I cannot get the waypoint cross on the HUD to reposition over the waypoint in radar update mode. VAL is lighting up on the PCN, and the windows are providing the error, but pressing VAL to accept the update does not shift the cross. What, if anything, am I doing wrong? Thanks for your help. :helpsmilie:

Thank you, I had it pointing elsewhere. :doh: I've been struggling with DCS crashing with the script running, and and some erratic behaviour from my controls. It's left me wondering what else I may have done wrong...

Hey there. I am new to this TARGET malarkey, and have up until now just mapped the controls to my Warthog in-game. But after several re-installs and the addition of VR has compelled me to try and use something a lot less fiddly. So, right now I'm trying the initial setup. I am using TM HOTAS Warthog, Saitek Pro Flight Rudder Pedals, and Oculus Rift. Have a question re the 'Default Initial Configuration' step (Page 9 of the setup guide.) The Selection Options title states 'The first thing you need to do is input the full path where you extracted these files. This is new in 1.60 and is a requirement for the new audial feature that is now part of aircraft selection. Where it says alias ScriptPath =, insert your path in quotes, including the drive letter.' What file, or folder is it referring to here? Where should this path be pointing? I've looked for an 'Alias' file, to no avail. Is it referring to the aircraft profiles? Some sound files, or what? Thanks for your help :)