M1Combat

"Edit: I should clarify, this is with SteamVR with WMR set as OpenXR runtime in SteamVR." I think the destructions mentioned to not use SteamVR at all? Or am I not understanding your comment? I'm running a very similar specced machine (I bit less really) and both the clarity and smoothness are significantly better. The frametimes and framerate and very similar to what I was getting when running SteamVR... but the clarity was immediately better and same with smoothness.

Whatever you did with .6 seems to have solved the Apache B/S issue :). I'll edit my OP where I explained it.

That's not the problem. My dark color scheme remains. My forum signature remains. All sorts of other settings remain. My post count remains. Which threads I've read and not read remains... All kinds of things persist. they're based on information stored in my profile and once I log in it keeps all kinds of preferences and settings. There is no reason at all that this particular setting could "only" be a cookie setting that would get cleared with a browser reset... except that it's either set to bug people or it's a design flaw. So.... As I said :)... "Is there any way?" If it's a setting that can be changed to not nag people once they've already chosen the setting... May we please get it changed to not nag people?

Makes sense... Thank you

I'm asking why :). I know what the recommendation is :). I'm asking why this is the correct thing to do.

@CybrSlydr I'm talking about the power levers. @Zap921Right... But... Any idea why IRL they don't crank them up to 11?

Probably depends on if they're far enough through the development to know what that looks like... but I'd suspect they're doing it the right way.

Is there some reason why we shouldn't just crank the throttles all the way up all the time? I could see if fuel use was a concern at some point where you might turn them down as much as you can and still maintain whatever flight envelope you need... but in general... Why not just crank them to 11?

I just turn on the battery, start the APU, Crank left and then right without waiting for anything, B/S the IHADDS and then take off :). Then I usually turn off the APU sometime enroute as I've most likely forgot it before take off... I suspect some day they'll implement whatever breaks IRL when you do it like I do and then I'll need to change something LOL :).

Maybe... I'll test the .6 release later but this only started happening after installing the OpenXR stuff. Aside from this one thing though... SUPER sweet. Very smooth and better clarity. Not much change in framerate but WAY better smoothness.

@edmuss Would you do me a favor with this .6 release if you have the Apache... Start DCS, Do NOT hit the recenter keybind. B/S the IHADDSS and check accuracy. Press the DCS re-center keybind, re-boresight the IHADDSS, Check accuracy. I ask because so far I've been able to make it all work but ONLY before I recenter the headset. Once I recenter the headset in DCS using the DCS keybind... It breaks the IHADDSS Boresighting procedure. Every other airframe works fine because there's no boresighting system like in the Apache.

You might also need to clear your environment data from Windows Mixed Reality Portal and then NOT set a center in there either. It appears to me that OpenXR seems to MAYBE define it's own center differently that WMR or SVR... and DCS works with SVR way. Super cool Edmuss :). I'll give it a shot when I get home... About 6.5 hours or so...

Can someone who is having this problem try NOT re-centering your headset with the DCS binding before doing the B/S procedure? Place the headset on your head before DCS launch. Sit naturally. Don't move your head around just sit there until DCS loads. Once DCS is up, DO NOT use the recenter... just jump in whatever mission you use to test, B/S procedure (the by the book one where you line op the center IHADDSS reticle AND make the circles concentric)... Then check accuracy.

Liberation.

@Jekel @Marco Schaap I've found a workaround... Place the headset on your head and sit "naturally" when DCS is loading. DO NOT EVER use the DCS recentering button. It will work OK until you use that recenter... then it will be broken.

I've answered no to receiving push notifications a couple times now. Is there any way we can get that nag turned off entirely or set to only ask once?

Just put in the time to get it working. Make sure you're using auto range. Once you get it the sight is super effective and allows you to make very accurate and complex rocket attacks. By accurate I mean the sight is accurate... the rockets... well... they're predicatable which is all you really need in a weapon.

@nikoel I'm not sure that addresses the issue I'm seeing. I used a similar method with the headset but it appears to me right now that... The IHADDS boresight seems to work ok until you use the DCS recenter bind, then the boresight is bugged. I would love someone to double check this for me. Before the recenter I can get the boresight spot on where using auto range at say 500yards will have very accurate fire. As soon as I recenter the HMD using the DCS binding I can no longer accurately boresight the IHADDS. It's always off after that. When I get a minute I'll remove OpenXR and give SteamVR another shot and see if it goes back to working correctly. Aside from this though... OpenXR has sold me for sure. Very good results related to smoothness, and clarity.

More info on the IHADDS boresight issue... I've cleared the environment data again and left the headset in my lap pointed down. Once DCS was fully started and at the main menu I picked up the headset and put it on my head. This seemed to work fine regarding the initial boresight but a ways into the mission I played I realized I wasn't quite centered any more. I hit my recenter bind and then just to check how the boresight system was doing I queue'd that up and again it was bugged. I'm thinking the bug has something to do with the offset of the environment's center and the currently held VR center that you get after "centering" the headset in DCS. I would love for someone to take another look at this if at all possible. I know both of these things are relatively new here... the Apache and the OpenXR install... but the boresighting procedure was working reliably before I installed the .5 version of this OpenXR software.

I mean the sight is super accurate... not the rockets themselves. Once you get the hang of the sight it's possible to lay down rocket fire very predictably and in a much more usable way than just "kinda shoot them over there a little" like most rockets are.

You checked your general and ui layer? for that 5 bind??

Well damn... It works nice folks. Thank you. My framerate has not really moved at all... BUT... despite that the visuals are clearer AND smoother anyway. /EDIT - The following issue has been solved by .6 release One thing though... It seems to have bugged the BoreSight of the IHADDS in the Apache. I know... doesn't seem likely but I think it has to do with the seated position in the VR environment. Please bear with me as I explain :). Before I ran DCS I did as suggested and I reset the env. dataand headset position in WMR, recreated that via the regular process in WMRP. All good. Launch DCS and 6dof is working... I center the view and all is still good. Jumped in the Apache and when I hit the IHADDS button on the MPD to light up the boresight scope circles they were black. I looked to make sure that the brightness of them was turned up, it was, I moved my assigned axis and the knob moves... still black though. I try a few more times and nadda. Boresight scope still black. I jumped out and did all that again, jumped back in and they're still black BUT... while playing around with it trying to see why I see them flash out of the corner of my eye... bu tI look and they're black... So... I mess around with it for a bit thinking I'm imaginning things but they flash again. I start moving my head around and find that they are there... but only appear when my head is pretty close to what I believe to be is where my VR environment thinks it's center is. The problem is NOT that they are there but way out of allignment. The problem is that they are just plain not there until I get into a specific location and then they appear. So, after learning that... I reset everything and tried again and now I've got it so the VR env. center location is in a spot where I can see the boresight scope with my head in a normal position but I have to align the scope by placing my head in a spot that it didn't need to be in before... AND the boresight doesn't produce a working sight picture. The gun is a ways off. My THEORY is that it's now aligning the sight, but for some reason the VR env thinks the helmet is rotated differently than it is, so the direction my VR headset is facing is not what the DCS thinks it is. I'm sure that's not explained super well and of course I can't get screenshots of the process or results. Point being though... The boresight at LEAST seems to be working somehow wonky directly after installation of OpenXR. Aside from this specific boresight issues though... faster, smoother, prettier... better. It's nice. I just think the environment data is being interpretted differently though DCS and is wrecking the boresight procedure somehow.

Once you wrap your head around the rocket sight system it's "super" accurate and like a cannon but cranked up to 111. I was in the same boat wondering why you might take rockets at all (they're no fun in the shark IMO... they "work" but are hard to make work) but with the way you can change the rocket pod angle with the head mounted sight in the Apache... I would go more towards the direction of only ever taking enough hellfires to kill all the hard targets +1 or 2 and take as many rockets as I can...

It SHOULD be much more unstable in yaw than the shark... It's only got one rotor... the ENTIRE point (or nearly...) of a two rotor set is to stabilize the heli in yaw...

Well... The shark only does that because it has two rotors and they touch. The single rotor heli's aren't capable of that sort of behavior...