Nuggetz

Thank you for your reply. I was unfamiliar with the SimAppPro and eventually I figured out the calibration procedure so that the idle and afterburner are set correctly. calibrating each axis Rx and Ry over the throttle full range including the afterburner portion of movement sets the range. Setting the afterburner detent at 78-80% approximately should be a good place to start then using F2 view in DCS allows you to see when the afterburner kicks in to allow you to fine tune the exact point. HTH

Looking for some help please. Just got my new F16 throttle today and managed to do most of the bindings correctly including getting the afterburner to light at the correct place with the detent. However the engine is idling at 75% and hence trying to taxi the jet is a nightmare. Can some point me in the correct direction please. NOW RESOLVED.

I have recently acquired a Pimax 8KX and not being a computer expert wonder if the OpenXR approach listed above will work with the 8KX? most of the posts refer to the G2 hence my question. Many thanks in anticipation

Ok thank you

When using my Quest2 historically the blue/green cross used by the mouse to click switches etc would also move with head movements but eventually stop and hold a static position and then after a few seconds disappear. However, more recently the cross does not disappear and can end up in distracting positions. The behaviour also happens with my new 8KX VR headset. Am I doing something wrong or is there a DCS setting I should be using or is this the result of a DCS update? Many thanks in anticipation of any advice.

I will be delighted to provide a Track file but the size of MP files exceeds the allowable limit. See the opening post. I am astonished that you are unable to reproduce the issue as it is well known amongst experienced F16 drivers especially in MP PvP engagements. Additionally, problems arise with AI engagements less frequently. Today I engaged AI 2x B52 with 2 x Mirage 2000 escorts in the GR Stoneburner Server. All 4 aircraft were clearly visible to the eye (in VR) under 15 miles. The B52 provided a radar return (no big surprise) but the Mirage 2000 were undetected. I also did some PvP against 2 other F16s and all three of us experienced BVR lock and especially RELOCK/DETECTION issues progressing to the merge despite getting an initial lock at 40 miles. I had hoped the recent update would correct this alas, no. There are a number of radar problem related threads in the forum suggesting apparent radar issues exist. Can I suggest you seek feedback from some of your trusted DCS F16 operators if you are unable to reproduce without extensive testing. Please believe me when I tell you that I fly the F16 module exclusively up to 8 hours a day and frequently encounter these issues so you will understand that the unable to reproduce response is exasperating. On the positive side the “LOCK” feature recently provided has improved matters when engaged in ACM. Thank you.

Thank you for the response which makes sense ie as we get closer the bandit ECM is overcome by the F16 radar and then the jump to the 40 mile scale. Regards

I had hoped that the recent update would resolve issues that I experience with the radar and not being able to get and maintain a lock but problems continue. Most of the time when in SP mode or even against AIs in MP I can get a lock and a kill. However when PvP in MP I struggle to get and maintain a lock. Some unusual behaviour includes: my opponent approaches at say 40 miles but the FCR indicates a red hallow triangle with a couple of yellow chevrons at the top of the FCR MFD. I can TMS up and get a lock at an indicated “160 miles” apparently the FCR and target stays locked at 160 miles, but the HUD symbology is not presented with range information. Despite the bandit actual being no more than 40 miles away. Suddenly the FCR range reduces to the 40 mile bracket and the HUD presents the appropriate information. Clearly things are happening differently to how I would expect and differently to SP. Are others continuing to experience FCR issues beyond the recent update? I would add that I do love the improvements made to the F16 performance model and G effects which have transformed the aircraft into the beast it should have always been, so thank you ED.

Yes thank you. I had seen at least some of these posts previously. I intend to fly all future sorties in both SP and MP, for a period of time, without any ECM pods to see if there appears to be a theme of radar performance or any short comings. I think it is fair to say that given the number of threads raised by different people that issues do indeed exist which require investigation. Two threads that I recall relate to ACM/ dogfighting with no lock issues or another where radar performance appeared better looking down (into the background clutter) vs looking up into clear sky where radar performance was less good which appears odd. Can I say to the ED guys I think your work is amazing and I am a massive fan of the F16 module, I can’t even begin to imagine how you do it. Given the F16 is still early access I am blown away with how comprehensive the module is, but the radar does appear to have short comings that detract from an otherwise exceptional piece of work. Thank you ED.

Thank you for your replies. At least some joint experience of similar problems does appear to exist. Further testing by me as follows: SP MODE: I engaged 5 Migs (veteran level) at a co altitude of approx 25k feet and was able to lock, maintain lock and kill 4 from about 40 miles decreasing. The 5th bandit descended to 6k while I was at 25-20k alt lock was broken and did not re lock until less than 20 miles against the Syrian desert background. ECM Long fitted and active. MP STONEBURNER GR: ECM LONG fitted and active Lock obtained at 40 miles Mig25. F16 Lock broken, I descended into valley looked up to targets, solid red triangles visible in the FCR MFD, no white dots RWS Mode, but unable to reacquire lock before being hit by incoming missile. MP STONEBURNER GR: Almost identical sortie profile against 2 x Mig 25, but no ECM POD fitted. As before F16 lock lost, but on descending into a valley and looking up I was able to reacquire lock in RWS Mode, solid red triangles visible in FCR MFD, albeit with a delay, but this time the result was two dead Migs. I think I need to undertake more tests but am beginning to form the view the ECM POD is not worth carrying at least in MP for whatever reason. Too little evidence to form a firm conclusion so far, but that is what my gut is telling me. more to follow when known….

Thank you for your reply and sharing your experience. I am not sure ground clutter is the dominant factor as I have experienced no lock with the target visible against a clear sky background where ground clutter was not a feature at all. Additionally, while engaging a Mig25 yesterday the radar could not detect the Mig at medium altitude in a mountainous region where the aircraft was clearly visible to the eye. Detection was achieved by the 9X sensor (no radar) once locked with the 9X and good tone I switched back to 120C and at that point the radar detected and locked the Mig25. I continue to investigate but I am convinced there are issues that require resolution. Updates to follow….

Thanks for the replies. I did run a single player mission against two Mig29S after I posted the above and had no issues so perhaps MP is a factor. I am currently exploring if carriage of the ECM pod is linked to the issues experienced. That said targets can be as little as 10-15 miles and I still get no lock with an ECM pod fitted. Each engagement was in RWS not TWS so TWS is not a factor so far. Will update with more information if I discover anything more.

I have been flying the F16 module for about 13-14 months and specialise in air to air missions almost exclusively. I am aware that other threads have been raised concerning the radar performance. Recently the radar performance appears to be worse with no white dot being displayed on the FCR MFD resulting in no lock on TMS up. The red symbol both hollow and solid is present, but no lock is obtainable in RWS. This is not 100% of the time or all altitudes etc. But when struggling to get a lock the inevitable shoot down happens leading to frustration. There are times when you can see the target aircraft with your eyes against a clear sky background and the radar will still not lock. Given I have thousands of air to air kills credited I do understand how the process of selecting and locking a target should work. Has something changed? I know I am not alone experiencing this problem as I have spoken to other F16 drivers via the Multiplayer Server this morning. Is anyone else experiencing issues? I have no track file to offer due to size from the MP server (Stoneburner Grim Reapers). thanks in advance…

Thanks for the tip, but anisotropic filter is already turned up. I think the key issue here from the responses received is people are conflating real life visual acuity with that generated by a GPU especially within VR. Best will in the world there is no comparison even with the finest PC and VR equipment especially in brighter conditions where contrast is not obvious. Hence my suggestion with the aim of closing the gap between graphics and real life visuals. That said you I am now at 100+ refuels so maybe I am adapting. Thanks again

Thank you for your replies. To be clear (no pun intended) if I set up a air refuel mission with appropriate weather at either dawn or dusk it helps to see the lights and hence I have been able to complete 20+ complete refuels hence for me this is less about the skill required. However, when I am in MP you do not have the option to control weather or time of day which can make it impossible to see the right light in particular. If the right hand light were at least as easy to see as the left hand, albeit brighter in relative terms, then there would be less of an issue. I don’t think it an unreasonable request to have the option to boost the light brightness perhaps a tick box for VR users? That way if you don’t want or need the option you can leave it off.

I fly the F16 in VR almost exclusively, this aircraft has a reputation for not being the easiest aircraft to air refuel. The Tanker director lights are too dim especially in VR and especially the right hand light (forward & backwards) light. Is there any chance these lights could be boosted in brightness at least for VR users where the graphics are of a lesser quality when compared to 2D? Many thanks in advance N

Prior to the last DCS update there was a change in the sensitivity of my TMWH joystick primarily in pitch. Previously I had pitch set with a curve of +10 and was routinely able to gain sniper shots on the cockpit of AI aircraft. I have tried changing the curve to as much as +60 but even the most gentle of touches causes the pipper to over correct even against a stable turning AI. I now have the curve set to +15 which allows normal control of flight in terms of general handling and landing of my F16, but guns dogfights remain problematic particularly with manoeuvring AI in a fight. I am not aware of any other software/driver updates which may have caused the change in sensitivity. However this may be possible. Given I understand the use of curves and believe I have at least a skill level to hold the pipper on target under normal circumstances- Can anyone offer some advice on where the issue may be rooted? I have run a DCS repair and reinstalled the TMWH drivers. Many thanks in advance

I stand corrected. However the process works hence fixing the issue

With the throttle at idle and elec on but before you start the APU select cut off then start the APU and once the engine has stabilised at 20%+ then open the throttle to idle and you should be good

Thank you. I have deleted the fxo and Metashaders2 folders multiple times trying different approaches. I don’t use any mods of any description in DCS.

I am running a 3700X CPU, RTX3080 TI, 64GB RAM and 500GB SSD. I am also using a Quest 2 headset with Link cable with most DCS settings turned right up and getting a good image and FPS from 45-120 at 120Hz. Using DCS Open Beta. When Oculus released the new Link Sharpening feature there was a real wow factor-very noticeable. However since the recent DCS update image quality has reduced and can be inconsistent, furthermore FPS can be down to 30 with 45-60 at altitude. A friend who uses a G2 headset and an AMD GPU has also commented on a massive reduction in FPS. I don’t know if the recent DCS update is the cause or Windows or Oculus or Nvidia drivers (but rolled back anyway). My question is anyone else suffering similar problems within the last week or so? I have tried endless setting changes and cannot get back to where I was happy. I have also switched back to a 1440P monitor to test the GPU and the 3080 TI is performing to an excellent standard so I think the GPU is good. Thanks in advance for any advice or feedback.

Thank you for your replies. I have flown multiple sorties in both SP and MP modes and the problem did not reappear. However, this morning after about 5 hot rearm/refuels I landed at another base from the one I took off from and the problem turned up again. Obviously the track file would be massive so you can’t upload. I will try and reproduce and send a track file if I can in either SP or MP. As far as switch positions go I am not sure what you mean. If the switch goes left dogfight mode (9X & Guns) is selected. If the switch goes right AIM 120 is selected (if fitted) switching cycles through eg 9X/120/NAV modes with changes to radar and HUD symbology accordingly. (TMWH HOTAS). regards

After returning from a mission in the GR Stoneburner MP server to rearm/refuel followed by a take off it is not possible to select AIM120 via the Missile Override switch on the throttle. Instead 9X are selected. However, selecting A-A mode followed by SMS page allows 120 missiles to be selected and corrects the symbology in the HUD. No track file is included as it would exceed the upload limit. Thanks in advance for investigating.

Thanks Frederf, Perhaps higher WP numbers do behave differently (now), but given I have used the same procedure ever since I started in DCS with the F16 (exclusively)back in Dec 20, something has changed. If that is planned then fine but it would be good to know what is correct. There are other HUD bugs but I need to raise a separate post to high light accordingly. regards

Thanks for your input guys. Following your inputs I logged back into Stonerburner this morning and started a F16 at Gudauta (no stores) waiting until the jet was ready to taxi and then manually entered WP33 and set the coords for the threshold of runway 33. Same result 55 miles to WP33 which as you know is in sight from the parking area. I then rocked the rocker switch and back to WP 33 - work around restored the distance to 001 nm. There is either a bug or something has changed/been updated since the recent update as the F16 did not used to do this. In the interim I am happy enough because I have an easy solution. Perhaps ED would be kind enough to investigate a little deeper. Many thanks in anticipation, Nuggetz