M1Combat

You'll have both eventually :). Flip a quarter (or whatever your local common largish coin may be...)

Try the post just above yours

Hey all... I got through mission one... In misison two the other flight takes off before me like they should, I take off and my flight follows me just fine... I can't seem to join up with first flight after that. First flight climbs to about 3K feet and flys a super erratic snake/"S" pattern for some reason. I've flown formation with their flight (maybe 100 yards out, on both sides), I've flown close formation with their flight lead (both sides... 5meters out... while he's doing his super dumb snake pattern flight...) and sometimes it plays what probably is the audio it's supposed to play when we join up (something about a flight of eight ready to go) but nothing happens at all. I tried flying the route across the chanel but it appeared to be a ghost town when I got there. Any thoughts?

I was able to fix my issue by doing the manual open composite style install.

It makes sense... I ran into the same problems with my old 970 with my HTC vive. I worked that bios setting each clock stage to the lowest voltage it would run on, ended up being able to run it way faster and gained all sorts of performance with that poor card. I can't believe it's getting to the point where I need to do that to a 2080 already... This thing was a beast :).

I re-installed the older version of OXR and that seems to work... I'm thinking that means I need to manually pop the newer d3d file in the bin folder... I'll check it out. You're basically implying that we can live with a touch of input lag and it buys us some smoothness yeah?

Can you prove that? Are you saying you gain some MS frame time by having it render frames BEFORE it will know where your head is at? I can try later but... seems not legit based on my understanding of that setting.

I'll maybe grab it but I still have the old version I was using in my OvGME too... but thank you :). Been almost completely a hit for me...

I'm having the 2D issue as well. If I set OC back to Steam everything works. OXR worked before... but I had been using the older version that didn't use Open Composite. I can see the OpenXR environment when I hit the button to show it (more later on this) WMR works. Headset works. How I got there... I removed any mods (only had OXR, using OVGME) updated DCS to the last patch and then ran through all steps of the install on post one... Everything. I ran skate's repair with the all files and extra files buttons. I did not "download" the latest version of OXRTools... But I verified settings and am assuming it keeps itself up to date. I downloaded the Open Composite package and did the things there. As you say in the destructions my app config page was blank until after running DCS the first time, now it has DCS there. Status is OpenComposite. I renamed the D3DCompiler file to .old. SVR still works after this BTW... must be using a default somewhere like OC would. Verified Mixed REality Headset Display settings. Cleared Env Data and then realigned in WMR. I DO get an error but of course I didn't write it down last night. I was just itching to test the new BVR stuff so I just used SVR. Also... Since I've been playing with the Apache so much lately I instead chose a very familiar mission and did that as a SVR/OXR comparison. The SCUD buster mission that comes with the Apache... Please help me get OXR working again LOL :). The Error said something about an incorrect "apptype" as I recall. Another thing to note... When I run the OXR environment... It runs only until the timer countdown (the one telling you to press Ctrl+Num2 as I recall) gets done... then the headset goes black and seems to crash something in the system. I say that because after the headset goes black WMR thinks it's asleep and won't wake it back up for a while even if I close WMR and re-open. If I wait a little while then it will wake the headset again. I know this is likely an odd one... and I can't test anything until about 10 hours from now...

I've been playing with under-volting nvidia GPU's since you had to re-flash the BIOS to get it done (GTX970 I think was the last one I played with)... I've got an RTX2080 now and the concept ins the same but as you mentioned it's just done a little different and uses something like Afterburner. SO... I started messing with it a couple weeks ago... The problem I run into is that, say for example (numbers mostly made up as I'm not looking at them right now...) I've got the top of my curve at maybe 2010 or something. By top of my curve I mean that's where it goes flat and I don't remember the voltage at that spot... If I have it at say 2010 at 1.0V... And I think I can move it to 2025 at 1.0V... I do, then hit apply... It moves right back to where it was. It changes the shape of the aqua colored line underneath the squares so it's retaining the "offset" that I'm assigning... but it doesn't actually stay at the 2025 I set it to. It drops back down to be level with the plateau part, changes the shape of the curve under it and retains the offset number. Is that working as designed? I feel like it's just something I'm mis-interpreting in the curve vs. squares relationship.

For everyone involved in answering questions 47 times or more... Thank you.

Nevermind... I was thinking we didn't get the AI improvements this patch but I was incorrect :). We got the BVR Stuff and didn't get the BFM stuff... as I'm sure you're aware :).

Just hide harder than the manpad...

I can't wait... Love both of these choppers soo much :).

Or... you can use the STICK to fine tune it, then trim again??? Like it's designed... I really don't see how this is any improvement at all. I mean I'm all for people finding ways that work for them to do whatever they're doing... but this is only worse in all cases as far as I can tell UNLESS you have a SUPER jittery stick or you don't have sensitive motor control so you can't gently move the stick.

I don't think that's what throwing out the baby with the bath water means ;).

Why would you touch a button like 25 times just so you can not trim with one button press?

There's a checkbox in DCS as I recall

I think you should lock your mouse cursor to the DCS window... and maybe set the headset to not go to sleep.

I don't understand the problem this tries to solve. I don't recall this happening to me or I am not understanding what's hapening to you :).

They're high tech wind socks

Heli's (they're all low and slow LOL) make a LOT of radar noise as far as I know... seems legit.

If it's what I think it is I think I've seen it while looking for places to build race tracks for Shahdoh's Mustang race series...

Pay attention to the blade pitch angle, that's all you need to do. It's above and left of your left knee. Start your dive. When you get to about 250 turn blade pitch down to ~3 degrees. Pay no attention to the flashing red lights. When you're getting to the bottom of your dive pull out of it and gradually increase blade pitch. Stay below about 5 degrees or so until you're back below "safe" speeds. The closer back towards ~275 you get you can turn the blade pitch back up... but be careful.

It does run smoother for me for sure.