Vortex225

Thank you for the update! Have these latest changes been published yet and, if so, where is the best link to download?

I have the Realsimulator R3L Ultra and the DCS Viper feels absolutely amazing with a proper force-sensing stick. They have upgraded the FM quite a bit over the years and, in combination with the updated FLCS deadzone and stick gradient options, it's never been more responsive and realistic. https://youtu.be/TzdE4lysN-I?si=Sk2JtCSf_QWVWXJm I would explore your HOTAS setup and tweak the curves, deadzone, and stick gradient options to produce the best feel for your gear.

I wonder if the resolution of cockpit displays is controlling this. Maybe 1024 Every Frame? I'm using a Reverb G2 and it still looks crystal clear to me in VR. Sorry if this isn't helpful.

My kneeboards look sharp and clear to read. I haven't noticed this issue in my flights this weekend, but I'll take a closer look next time just to compare. It will automatically appear if you have the pilot body selected on. You just need to have binds for next and previous page set.

+1 This would add so much immersion to the Viper and seems like a quick and easy win for the devs. We need this ASAP!

+1 Please do this ASAP! It will add so much immersion. Seems like an easy win for the team now that we have JHMCS toggle properly modeled with the new pilot model.

Thanks for looking into this, Lord Vader. Per your request, I did some additional testing today; I created a brand new mission in the editor on DCS: Caucasus this afternoon to test this behavior more carefully. I was able to duplicate the issue (i.e., late release/missing long) in the three attached tracks (i.e., cbu_87_long, cbu_97_long, and cbu_87ccip_long). I also tested the CBU-105 and standard MK-82s, but both of those are working correctly for me. Please note that this mission was created from scratch with default map and fuse settings after the most recent beta patch using an ED preset CAS loadout for the Viper. I'm using a standalone version of DCS that was originally a DCS open beta standalone install that is now fully updated. To summarize, the bug I believe I'm seeing is that CBU-87s and CBU-97s are landing long (late drop) when released in CCRP, CCIP, or DTOS modes. I first observed this behavior in the Nevada quick mission for CBU-87/CBU-97 last night, and then I more carefully reproduced it today in a fresh mission on the DCS: Caucasus map with default settings for the map, editor, and fuses. GPS/INS weapons appear to work just fine, and standard Mk-82 also work fine too. Hope this helps with testing! cbu_87_long.trk cbu_87ccip_long.trk cbu_97_long.trk

Assuming this is the same bug, my CCIP and CCRP drops were far too late this evening. I think I observed the same behavior.

Not a full answer to your question, but I recommend you use OpenXR Tools for WMR (to control HMD resolution) and Quad Views Foveated to get the best performance boost without eye tracking. OpenXR Toolkit is popular too, but I prefer the combo of the two above for best performance and visuals. https://youtu.be/NZVp7Ya1GZM?si=pUpKIfwiXXvsmbVw As for DCS settings, I would start with the VR preset and work upwards from there. Good luck!

How do you manually update DLSS for DCS again?

Update/Edit: I figured out how to disable Turbo Mode for QVF on my Reverb G2 thanks to the QVF Wiki and Str][kerTV's YouTube tutorial. While the default settings do work well overall, I found that motion reprojection wasn't working properly until I disabled Turbo Mode in QVF and enabled it via OpenXR Tools for WMR. Problem solved and I'm very pleased with my results using QVF! Question for @mbucchia on the Quad Views Foveated (QVF) app. Which app is the best to enable Turbo Mode (does it even matter?), and how would I disable Turbo Mode for a G2 in QVF if I want to enable it via OpenXR Tools for WMR? Background: I'm a Reverb G2 user (no eye tracking), and I'm using OpenXR Tools for WMR to adjust resolution, turn on motion reprojection, and enable Turbo Mode (instead of through OpenXR Toolkit). However, I do use OpenXR Toolkit to enable CAS sharpening (100%) and fixed foveated rendering. I plan to try your Quad Views Foveated app for the first time, but it's my understanding that Turbo Mode is enabled by default in the app and will cause conflicts with other apps that enable it. I would like to continue using Turbo Mode via OpenXR Tools for WMR, because it's my understanding that version works best with motion reprojection (which I use) and the OpenXR Toolkit version does not. Thanks in advance for your help and, of course, for these awesome VR tools for our DCS community!

I agree that this is a significant change that needs to be documented a bit better to help us understand. I'm still struggling to use this properly in my AG workflows for both DTOS and VIS--even after Lord Vader was kind enough to explain it to me. What entry are you referring to? Is this something in a recent change log? ETA: Found it, my mistake. The single SPI logic update was documented thoroughly here; however, we may need a few tutorials to help us understand how to use it properly. https://forum.dcs.world/topic/209147-viper-mini-updates/?do=findComment&comment=5288681

@Lord Vader Ok, thank you for taking another look. I do understand what you're saying, and I will accept it as working as intended. Please know that it was not my intent to be difficult; it was simply hard for me to understand how these refinements could reflect reality when they ostensibly provide less situational awareness and require more HOTAS presses and/or MFD button interactions than the previous implementation. All that matters is realism. If you're saying these changes were intentional, then so be it. Thank you again for your time.

Thanks, @Lord Vader. I do appreciate you taking the time to provide a detailed and thoughtful reply. I think we may still be misunderstanding one another, so I took time to carefully read your post today and review all applicable DCS material I could find relevant to this issue. Please note that my observations may be distinct from the other issues raised in this thread. To this end, I would like to make another respectful and earnest attempt to explain the steerpoint issues I feel are not behaving properly for the Viper in DCS 2.9.0.47168 Open Beta. Terms and Definitions: To begin, I want to avoid any confusion about terms, whether I am mistaken on definitions or otherwise. To clarify, I understand the steerpoint diamond as the diamond visible in the HUD or HMCS that shows you the location of the currently selected steerpoint. In the tracks I uploaded, this is always steerpoint 1. Additionally, I understand the TD Box to be the box and dot that that is visible on the HUD or HMCS that shows the location of the current target designation/SPI. Scope of Discussion: To simply our analysis, let's restrict the discussion just to VIS mode for the moment. Please consider the following graphic, which is numbered according to the order in which the screenshots were taken: #1 shows the HUD view after initially selecting VIS sub-mode with the steerpoint diamond clearly indicating the correct location for Steerpoint 1. The TD Box is caged to the HUD because I have not yet slewed it to a desired target location. #2 shows the HUD view after slewing the TD Box to a target location chosen arbitrarily for this demonstration track. I have already pressed TMS FWD once to designate and ground-stabilize the TD Box to that location. Notice the missing steerpoint diamond where it was previously located in #1? #3 shows the HUD after I have reset/re-caged the TD Box back to the FPV with TMS AFT. Notice how the steerpoint diamond has shifted to a new location? I haven't modified the currently selected steerpoint; and yet, the steerpoint diamond is now located where the TD Box was previously designated from #2. The correct location for Steerpoint 1 is annotated for comparison. #4 shows the HUD view immediately after selecting the PRE sub-mode; no other changes have been made. Notice how the target designation box now correctly reflects the location of Steerpoint 1, which makes sense for a PRE delivery. The steerpoint diamond is occluded, but I believe that is intended based on another video from Wags showing JDAM deliveries in PRE. The second screenshot below (single HUD view) shows a frame from Wags' video DCS: F-16C Viper | Air-to-Ground Helmet, in which the VIS sub-mode is used for a standard JDAM attack. Please note the presence of both the steerpoint diamond (showing the location of his Steerpoint 2) and the TD Box in the HUD/HMCS at the same time. In summary, I'm describing two separate issues. - The first issue is shown in #2 below. Why does the steerpoint diamond disappear? See the second screenshot below (single HUD view) from Wags' video for what I think the correct behavior should be. Please note that I could not find any reference in any DCS Open Beta patch notes that describes a change to steerpoint diamond symbology that would have modified the behavior away from that depicted in Wags' tutorial video. - The second issue is shown in #3 below. Why does the steerpoint diamond shift to a location other than the currently selected steerpoint? I interpret the HUD picture in #3 as Steerpoint 1 is at the location of the diamond, but I *know* that Steerpoint 1 is actually located in the position from #1. This seems like a bug to me. Thank you again for your time and consideration.

Just following up to say I haven't noticed this particular issue with markpoints since the hotfix; it seems to have been fixed with the hotfix. Nevertheless, I'm having trouble with steerpoints in VIS and DTOS modes and I'm working through the troubleshooting in another thread.