Nuggetz

PC Specs below. 8KX resolution 3840, normal fov and refresh rate 75hz. As many have experienced huge fps drop. For example in my case 50/51 fps sat on the ramp in a F16 at Gudauta in MS server under 2.7 version dropped to 40 fps. (albeit under 2.7 the resolution was 4128 per eye, and fps in general varies between 50-75). Good news: like many I have been experimenting with settings various and 3rd party software to claw the fps back with varying results. This morning I uninstalled the Open XR Toolkit and VR Performance Toolkit and retested at the above server location fps went back to 47. I then adjusted visible range from ultra to high and reduced the anisotropic filter from x16 to x4 and now have 50 fps at that location. There remains a loss of performance; however, the gap has narrowed at least restoring playable performance. While it is true that I could get more fps with VR Performance Tool Kit activated I did notice the occasional game freeze in the PG map for 1-2 seconds. This freeze no longer happens now the files have been deleted. Additionally the image quality is better without VR Performance Toolkit installed. While this approach appears to work for me you may have a different experience but I offer it in the hope it helps at least some of you. Still not happy about increased cloud shimmer especially in the PG map, but one step at a time.

Early days but some noticeable improvements while testing in SP mode. MP tests tomorrow. Downsides 10-15 fps drop across multiple maps but still playable but with the occasional freeze for 1-2 seconds. Also looking down at the ejection handle in the F16 the shadow from the aircraft that should sit below the aircraft fuselage is superimposed over the cockpit instruments. Shadows already set to Low and Off so not sure where to gain back fps without reducing other settings. Summary: some nice cosmetic improvements at the expense of performance.

Sorry I must have missed these replies. Thank you for your input. I have managed to get into VR mode using Open Composite. The only missing component is the lack of FFR (fixed foveated rendering) options in the Open XR Toolkit. My current FPS is typically 50-75 (75 hz refresh rate) depending on map/altitude etc, so the lack of FFR is minimal for the most part. thanks for your input

My set up has been working fine. However when trying to log into DCS this morning I cannot enter VR using OPENXR. I end up on the monitor screen. I have not changed anything software wise other than updated the OpenXR toolkit to 1.2.0 from 1.1.4 and renewed my Norton security software. I had used DCS VR successfully since that software update. I have run the slow DCS repair. I reverted to Version 1.1.4 but still no luck. Checked all drivers are up to date etc. I even downloaded STEAMVR and got the headset working. I then deleted STEAMVR but cannot get into VR via OPENXR and my Pimax 8KX. EDIT: I have reinstalled all the associated OpenXR files. I can get my 8KX to work with another flight simulator via OPENXR but unable to get DCS working in VR. I have checked the Enable VR box in the VR tab in DCS. I would really appreciate some advice on what to check or do next. Thank you.

Please find attached file. No VR connected. Manually enter lat long into STPT 1 and cycle STPT correct value displayed. Enter lat long into a blank STPT and the range is 500+ miles, again cycle STPT and return to STPT the correct range value is now displayed. Once you recognise the error it is easily correctable so not a major drama, but if this differs to the F16 IRL perhaps ED can add it to the endless list of jobs to to do.. Many thanks in anticipation N Tacview-20220809-094438-DCS-F-16C - Caucasus - Takeoff.zip.acmi

Thank you I am aware of the workaround. If the bug is known and a fix is in the pipeline albeit with a low priority the the post can be closed.

I am sorry I have tried to produce a track file but cannot get one small enough to post. As mentioned above if someone would be kind enough to start the Take-off mission in Caucasus Instant Action mission and enter the co-ords detailed above at say STPT 29, the mileage will either be correct or approx 300 miles too much. If incorrect you will have a track file on your machine. Many thanks in advance.

Something new is happening with steerpoints with the F16. Am I alone experiencing STPT/Navigation issues? For about the last 18 months I have got into the habit of overwriting SPT1 (GR STONEBURNER MP SERVER) to N43 06 278 E040 34 534 Elevation 69 feet. The threshold of Runway 33 at Gaudata. This give me a home reference to get home easily especially when low on fuel after dogfighting. However since the last major update this has stopped working. You can change the co-ords but the mileage to the original STPT stays the same and does not change to the expected 001. I also tried the Instant action mission “takeoff” in Caucasus. No success changing SPT1 to the above co-ords. I then pick an empty STPT and enter the co-ords the heading is correct but the mileage was about 530 but should be closer to 230. Flying the route heading remains correct but the mileage over reads by 300 miles throughout The STPT appears on the HSD in the correct place (within the correct range ring). However, no wedding cake in the FCR MFD. The work around for the MP scenario is to use the Overfly STPT Mark Point before Takeoff. The SP solution required me to use F10 and measure the distances involved. Can someone have a go at replicating please before I report as a bug. Thank you.

Totally agree, credit where credit is due the team have transformed the Viper with the latest update (not just the obvious stuff related to the radar). I sense tweaks not mentioned in the patch release notes continue to improve the experience but we now have a fabulous foundation and excellent module, which can only be enhanced as we move forward. Given 99% of my virtual flight time is in the F16 I could not be happier. Thank you ED your efforts are much appreciated.

This is what I used links included. Hope it helps you. Update: Given the inflammatory comments below I wish to add some balance to those remarks. I added this link because I thought it might help someone not to stir up a debate. To be clear when I viewed the video I found it easy to follow all the links worked and I was and am able to use my 8KX with OpenXR. Something I was not able to do using other guides in these forum pages. I continue to do so even after the recent DCS update and obtain great FPS and image quality. So to suggest this was pure click bait is simply wrong, albeit the links have now been superseded.

Yes, when I followed the instructions I noted a 10fps+ on the runway and 20 fps+ at altitude. That was with the Pitool at 1.0 and XR at 100%. Since then I have tinkered and Pitool is now 1.25 and XR at 100% and 20% sharpening. Some maps give me a solid 75 fps at all altitudes but can fluctuate 68-75 in flight depending on altitude. In MP normally 45-50 fps on the ground and 50-75 fps in flight. All at 75hz. Still tinkering but I think I am close to the right balance of fps/image quality. I would add post installation images appeared smoother especially in close in dogfights. Hope this helps.

Thank you for doing this analysis, while I do not have specific evidence to support your work, this appears to be highly representative of the experiences I have encountered for quite some time. It will be interesting to see if the White paper being written by ED suggests that this profile accurately emulates the actual radar fitted to the aircraft.

Thank you for your reply. Having read the feedback I was concerned I may have been clumsy putting together my track file and was all set to offer a full apology for the track file despite believing issues continue to exist with the F16 RADAR. However: I have just reviewed the track file and note the following: 80 Mile Bracket the antenna altitude is approx 35k to -11k with the approaching Migs at 6k (Link 16) at approx 50 miles the antenna alt is adjust to 17k to -5k within the 40 Mile bracket the antenna alt is 13k to -6k therefore I am not clear what I am doing wrong? It is within this approach from 80 miles to below 40 miles that no detection or lock is possible. Now I accept that there is a disparity between the antenna alt and targets for a short period of time at around 20 miles which required adjustment. it is also interesting the the track file records things happening I have no recollection of ie running out of fuel and getting shot down. But I have experienced odd things with track files in the past and hence this is a side issue. I note threads have been merged and overlapping issues have now been reported/are under investigation for which I am grateful. I await the outcome of your work in due course with interest. Can I finish off by stating I am a huge fan of DCS and the F16 module specifically and am in awe of the talented people that have developed this fantastic product. I fly in VR and find the whole experience completely immersive which is why I have invested thousands of pounds in hardware to reap the enjoyment experienced. Any frustration that may have come across is unintentional and certainly not personal as we all just want the F16 to work as well as we know it can. Thank you for the tremendous work undertaken and I will stand back and await the results of your investigations.

Please see 10 posts above for a Track file. I also note todays video from Growling Sidewinder F16 vs Typhoon where if I remember correctly he gets a lock/launch at 15, 19 and 9 miles. Perhaps worth a look.

Can I respectfully ask that the banner to this thread be updated to Investigating. The “missing track file” was provided 4 days ago. Thank you.

Agreed but I did start this thread in the middle file of February so it has been ongoing for a while. Given the number of threads relating to the RADAR/Missile performance in BVR engagements I am surprised that ED have not been able to identify these issues more readily. Certainly in the early days of the F16 module there were no issues detecting bandits at 40+ miles, gaining and maintaining a lock. Something has changed which often leads to a frustrating end to a sortie

Hopefully I have attached the correct version of the track file. Simple mission me vs 5 x Mig23 (all with heaters to allow me to get closer) Note range the Migs are detected and repeated time TMS is selected without gaining a lock. The Migs are well within the 40 mile range bracket before locks are achieved. It is not uncommon for the lock to drop delaying a relock. In the earlier days of the F16 detection and lock was possible beyond 40 miles - so what has changed? Obviously had the Migs been armed with Fox 1 or Fox 3 missiles I would have been in big trouble. Hope this helps with your analysis. lockFCR BUG.trk

A repeat of the NTTR 9x training mission. Note after the 3rd drone is splashed the HUD returns to NAV mode with no RADAR, Checking the FCR MFD shows ACM mode selected, RADAR range cannot be adjusted. Manually changing the ACM to CRM restores the RADAR and allows the RADAR range to be adjusted. Hope this helps with your analysis. 6FCR BUG.trk

Having flown multiple sorties in both SP & MP since yesterdays update my analysis reveals that targets can be detected between 40-45 but cannot be locked despite repeated TMS up selections until within the 40 mile bracket. Typically locks are achieved between 23-36 miles which is an improvement over the 15-20 miles initially being experienced. That said all locks are achieved at high altitude against clear sky with no background clutter interfering. Hopefully future tweaks will refine the RADAR performance. Thank you

Will do thank you.

I can provide a track file but the size will be much bigger than the 5MB allowed. (see first post) If there is a way to send it to ED please let me know and I will oblige. Current experience can result in BVR targets not being able to be locked until 20-15 miles, placing the F16 of increased risk from enemy missiles.

I have just flown 4 sorties, the first 3 of which appeared to work normally after clearing button 14. However, sortie 4 the problem surfaced again. Sortie 4 was a duplicate of sortie 3. Using the OSB of the FCR MFD I noted ACM was selected and I manually selected CRM which restored normal service and allowed the RADAR range to be adjusted. The sortie was a BVR against 2 Mig29S so I had not used DGFT mode, but did cycle through the switch modes as part of my checking while RTB. Unfortunately I did not save the track by mistake. I can try to replicate the sortie if that would help. Update: I have since flown sortie 4 twice more and about an hour in a MP server without being able to repeat the anomaly. I will continue to monitor and save a mission if and when I can.

Thank you will give it a try and report back.

Please see attached. I use. Pimax 8KX and a WINWING F16EX Throttle and a TM F16 joystick. I think I have tried both the red and green indicated selection during the past week.

The switch is not spring loaded a deliberate selection inboard selects missile override, deliberate centre and deliberate outboard selection dogfight override. I have saved two more missions today where the anomaly appears again. I have not checked the file size yet against the 5MB limit.