zildac

Thanks for confirming. Yeah, it's certainly a handy feature. Sent from my LE2120 using Tapatalk

Openvr_api_dll has been deprecated in VRPK it's now using dxgi.dll as its shim (so the original version of openvr_api_dll file from the DCS build needs to be in place). Which means if you want to use any version of Reshade and VRPK you need to rename one of the clashing dlls to d3d11.dll. I have the VRPK dll renamed to d3d11.dll and have left the Reshade5 dll as default (dxgi.dll) HTH.

Those keys don't appear to work for the HMD image anymore, even if set in the .ini. You can toggle them in the shader list, but yeah, it's a bit of a pain. My posts further up cover the same finding.

Thanks for looking. Odd, I'm pretty sure I did the OAP right based on the BE call, but it was the first time I’d tried it in anger, so perhaps not

This is not witchcraft....

Hi, In mission 4 when Wizard gives the location of the crippled Tabletop as 008 for 40, if I set up an OAP using these coordinates and distance from rock the TGP is nowhere near the ship. Is this supposed to be the case, I set the bearing as True should it be Magnetic? Thanks, Z

Having played some more between "work" I have noticed that in certain lighting conditions the interference pattern that seems to be generated as a result of the render quality ring radius settings is quite off-putting. I also have an after market face gasket for my G2 which may be making the issue worse as my eyes are slightly closer to the lenses. I have cranked up the values for inner middle and outer and it's better but I'm not sure if I can live with the "jiggle" in my peripheral vision. Perhaps I'll tune it out automatically after some time, will see how it goes. These are my increased settings, but the effect is still noticeable. Any higher and I may as well just not use the feature tbh. But i get that's how the process works. fixedFoveated: # enable (true) or disable (false) fixed foveated rendering enabled: true # configure the end of the inner circle, which is the area that will be rendered at full resolution innerRadius: 0.6 # configure the end of the second ring, which will be rendered at half resolution midRadius: 0.8 # configure the end of the third ring, which will be rendered at 1/4th resolution outerRadius: 1.0 # the remainder of the image will be rendered at 1/16th resolution

Yeah, I guess it's one of the downsides of an EA product when referring to older videos. Happy that it works the way it does, just wanted to make sure I wasn't missing something obvious. I guess they also removed the numbering of the selected WPT in the SA page in a more recent release too as that also appears in older videos.

Gotcha, thanks

I'm assuming you’re not using VR_CAS in reshade hence the sharpening set in vrperfkit?

Just ran a quick and dirty test using my existing Reshade 5 settings (VR_CAS etc) and the same vrperfkit.yml settings from the "non foveated" build but of course with fixedFoveated:enable. I too see an increase in performance around .5 to 1.0ms decrease in GPU Frametime. There is some "fuzziness" in the outer area of the FOV but this is basically how this works. Either way it's not noticeable (to me at least) and I'll take the perf increase.

Many thanks, I'll take a look at that.

Thanks. So presumably the behaviour seen in older videos was incorrect. On that basis what is the correct procedure for getting the pod in the general area of a bullseye call?

I originally posted this over on the Raven one forum, but it may be better placed here. I'm not sure if it's a bug or by design, so any info would be much appreciated. In many of the tutorial videos I have seen when trying to place the TGP in the general direction of a bullseye call for an A2G tasking you simply use the SA page and the TDC cursor to slew to the general area, switch to the TGP and then move the pod so the pod marker in the SA page is within the previously placed TDC cursor. The thing is as soon as I SCS right for example to make the TGP SOI on the right MFD the TDC cursors on the SA page disappear. This doesn't seem to happen in any of the videos I've seen. Is this new behaviour, a bug or just "user error"? Likewise, I see no threat rings and the only waypoint that is numbered is Bullseye, have I missed some setup on the AMPCD? I'm following what I believe to be the correct cold start procedure, running the latest OB 2.7.10.18996.

Bit late to this party, but just started the campaign and am currently up to mission 4. Really enjoying it even though it is pretty challenging for me! I have a question re the SA page, which hopefully is simple. In many of the videos I have seen when trying to place the TGP in the general direction of a bullseye call you simply use the SA page and the TDC cursor to get in the general area, switch to the TGP and then move the pod so the pod marker in the SA page is within the previously placed TDC cursor. The thing is as soon as I SCS right for example to make the TGP SOI on the right MFD the TDC cursors on the SA page disappear. This doesn't seem to happen in any of the videos I've seen. Is this new behaviour, a bug or just "user error"? Likewise I see no threat rings and the only waypoint that is numbered is Bullseye, have I missed some setup on the AMPCD?

Thanks for taking the time "screwing around" It's much appreciated

Would you mind sharing your Reshade config files in regard to Luma and Vibrance? Am I correct in assuming you are not using the Reshade VR_CAS shader, so are performing sharpening in vrperftoolkit exclusively? I think you had it set around 0.2 if I recall a config file post from a while back?

I think it's the nature of the beast now, and the release notes seem to suggest they are treated as two separate environments controls wise. It would be useful to be able to map a key to enable/disable all, and that only affects VR though. Like you say, it may get implemented. Thanks for testing

Possibly a TAB or CRLF or similar...at least it's sorted now.

OK, so if you bind a key to "KeyEffects" in your Reshade.ini or via the 2D UI (the below uses END to toggle) do you notice the effect being enabled/disabled in the HMD. Because I do not, and previously, I used this key to quickly disable all the currently active Reshade shaders or re-enable them. It's this behaviour that I think has changed with the official VR version. Reshade.ini [INPUT] ForceShortcutModifiers=1 InputProcessing=2 KeyEffects=35,0,0,0 KeyNextPreset=0,0,0,0 KeyOverlay=36,0,0,0 KeyPerformanceMode=0,0,0,0 KeyPreviousPreset=0,0,0,0 KeyReload=0,0,0,0 KeyScreenshot=44,0,0,0

It makes sense, and I do. However, I still seem unable to enable or disable ALL the effects in the standard 2D menu, it only applies to 2D not HMD. In HMD mode I obviously need to bring up the SteamVR overlay to select Reshade 5.0, and then I can toggle quite happily.

Very strange, no nothing left from sharper eye, all cleaned up. So are you saying that you can toggle the effect (in the HMD) on and off using the standard keys? Because I can definitely only do it via the SteamVR overlay menu, which of course requires a controller to hand. I can change settings in the 2D home menu fine, but they are NOT applied to the HMD image unless I reload from the SteamVR overlay, likewise I cannot toggle on and off the effect (in the HMD) using the normal enable/disable key (END).

Something is definitely off, but I'm using your archive and the included .INI files from the archive. The only change I’ve made thus far is to map the "END" key to effect enable/disable. Odd. And it does indeed register as such in the "Home" menu when toggled. But no change to the image in the HMD. The dxgi.log looks fine too I can see the shaders compiling etc. Is it perhaps that you HAVE to use the Steam VR menu to toggle the effect in the HMD, the statement from the release notes suggests possibly. I'll dig a controller out.... Update OK, mystery solved. In order to enable/disable the effects in the HMD you have to use the controller to open the SteamVR overlay and use the Reshade menu in the HMD. Not a major issue as the effects are enabled by default, but a bit of a faff if you want to simply try real-time comparisons of settings, as you need a controller to hand. The "old" way of doing it via the menu on the mirror (when pressing HOME by default) ONLY seems to affect the 2D mirror....

Something odd going on my end, I’m only seeing the effect in the mirror, not in the headset. I can ramp the sharpening up to 15 (just to make the enable/ disable obvious) and I can see it applied to the 2D mirror, but no change in the HMD