zildac

Could you perhaps include the link to the file in this post to save people searching for it?

Without wanting to sound like a bell end, those dates in the screenshots are the install dates of the components, not the release date of the version installed, right? Advanced shows the actual version installed:

Have to say, really enjoying this campaign so far even though I am finding it hard as a new Harrier "pilot". I hadn't appreciated quite how many night missions there would be but I guess the clue is in the NAme

Many thanks. I'm trying to use the vakue from the kneeboard page.

It happily drops from 45 - 30 and works great but as you say the artefacts are worse than SVR. If you sit in the cockpit for example and perform a slow left->right scan can you not notice the slight jitter present, i would describe it as akin to VSync off in 2D but obviously with no tearing? This is with repro on. Agreed, and I commented something similar when I first tried it...it is incredibly useful to be able to drop to 30!!

Yes, it works and I can lock at 45FPS, but the artefacts seem far worse (to my eyes at least).

I have played with this quite extensively for the last couple of weeks, and for me personally whilst it is great to remove the SteamVR layer, the reprojection artefacts spoil it for me. I know people are harping on about not needing repro, and I get that school of thought, but the other school of thought and one which I subscribe to is, the G2 has a native refresh on 90Hz if I can't run 90fps then I need reprojection to enable a jitter free experience. I can maintain 45FPS pretty much everywhere (except in the system slayer which is DCS Liberation!). If I disable repro I can sit at around 50-70FPS, however even if the FPS stays at a constant 50FPS the movement of my head is not as smooth as with repro on and locked at 45. This is not dissimilar to people who play with VSYNC On (in the pre GSync or FreeSync days). The slight jitter when scanning the cockpit with repro off, just ruins it for me. And the "wobble" on objects with repro on (whilst slight) is substantially more pronounced than SteamVR. In regard to shimmer, I see zero difference in shimmer with OpenXR vs SteamVR, it's still there and noticeable. I still use the TAZ version of Kegetys MOD as this reduces the shimmers in cockpit via Albedo texture SS. I have to caveat all of this by saying I’ve performed no scientific measurement of performance increase as quite honestly 45FPS constant is good enough for me. The major benefit is the removal of the seizure inducing loading screen images Now if we can get reptojection up to where SVR is then I would seriously consider using this full-time.

Thanks Yup, I worked it out Edit: As an aside, I couldn't enter the BE (for Mission 2) LAT/LONG given on the knee board. I had to round up the LAT in order for it not to reset to 00.00'00 when entered, could be something I'm doing wrong.

Many thanks, will have a read up. I've used the same procedure in the Hornet so hopefully it'll be reasonably intuitive.

Relatively new to the Harrier so just picked this up and played through the first mission, really good! But there are a lot of bullseye calls, and I can't for the life of me work out how to use this info effectively in the Harrier. The Hornet is easy in this regard. I've had a quick search around and can't see anything obvious for the AV8. Edit...I found one YT vid, but it's in German, and my German is non-existent. Anyone have any links for some good tutorials on effective bullseye use in the AV8?

Only been flying the Harrier for a short while, and I'll be honest, to my untrained eye I didn't really notice a huge difference

OK, many thanks. I'll remove Taz version of Kegetys mod and try again. I would have expected the loader to detect DCS though. I'll also try running the loader with elevated privs, as DCS is running as admin. Update So the issue was the loader process needed to be run as admin as DCS was running as admin

The screenshot with the loader running from the archive was just for illustration. I unzipped the archive into the bin directory. Well I actually used ovgme. What is the correct folder structure?

So the folders in the bin directory? The command prompt windows just kept saying: even once DCS was at the main menu. I do have the TAZ Shaders (Kegetys derivative loaded) for 2.7.11.21408.1 pehaps this is the issue. I will try without. So just to confirm, all of the folders in the archive should be in the BIN directory as per your previous releases? Ignore the path in the screenshot I ran it from the archive just to capture the message.

I'm perhaps being a little stoopid, but what is the correct folder structure for this to work? Looking at the original mod PDF help file it seems that the "Replacement Textures" "Shader Cache" etc folders should be under "<DCS Install DIR>\bin" if I use this structure with this version of the MOD I get an OCC error. However, if I just unzip the archive and activate via OVGME (and keep the structure), the loader never registers the fact it has successfully injected.

I still have "wobble" with this, when MR is enabled. Hornet ready on the ramp, Caucasus tops of their trees and the hangars. No mods.

New version has the menu fixes in. https://mbucchia.github.io/OpenXR-Toolkit/ Not sure if the hot keys issue is fixed.

I had the same issue, and even if the keybinds weren't already used in DCS the menu failed to open. In the end I just randomly chose some keys, my arrow keys on my numpad which aren't mapped wouldn't work. No ideas. And some keys on my keyboard didn't even register in the OXR toolkit drop down select, very odd.

I seem to be having a similar issue. I take off, the tower explodes (I'm flying 330) get told to go to Strike on Pri (use rotary dial on throttle to select channel 1) and then nothing, I can fly to wypt 1 and anchor at 2 (Alika) and no comms. Using the latest OB.

Still crickets.....

Definitely

Just to add, that performance improvements aside, the Albedo supersampling alone also seems (for me at least) to significantly reduce the shimmering in the cockpit. So there is still benefit to this mod IIMHO

@BIGNEWY Any chance you can ask the team to look at this issue. It's quite frustrating and incredibly simple to reproduce?

Reshade 5.0.2 still works fine. A number of mods that rely on modified shaders however do not. A number of the mod authors have already updated there's to work with the latest OB