maxTRX

Instead of doing this: tf = lim Σ ⌠ (SVR/OXR) √Toolkit) 1/ChatGPT ... I simply kept my settings from the single thread DCS.exe, fired it up and voila! On my first VR hop I noticed a bit of 'grinding'. Occasional micro stutters when looking right or left. On the following hops over the same area, smooth!!! Once in a while, on a long flight, when looking at around 60deg to the side, there is some barely perceptible jitter but when I look further to either side (90deg and beyond)... smooth! Go figure. In single play that's definitely acceptable with FPS over Syria between 70 and 90. I did finally switch to OXR in the SteamVR setting but I never installed any Toolkits or anything else, which is probable a bad idea but... one of these days. The res. in SVR was set to 150% with no AA of any kind and ASx16 in DCS.

@Gierasimov I tested this today and got the same results you had initially. Regardless of 'INTL' (boxed or unboxed) it showed the terrain in the background. In the hills, it was impossible to see the target symbology. Instead of repairing, I lowered the gain from default 5 to 2 and the bricks showed up over the dimmer terrain. Once the target was locked, the terrain disappeared. In standard DCS.exe the terrain only shows up when 'INTL' is boxed.

No, it wasn't documented. I was just shooting my mouth, hehe. To me, it does seem like there is a slight difference in FM. I just finished some BFM setups and I also noticed that I was able to control my energy a bit better in a spiral dive with full blowers. Previously, I had a tendency to let the a/s build up rapidly in the same situations, even with full boards and w/o AB. It could be just me, after being away from simming for over a month. I can make a bet the mods would say no changes had been done to FM...

I finally jumped off the fence and updated to the new OB. While everyone is anxiously watching frame times and bottlenecks, the first thing I checked is the Hornet's behavior... I would encourage all Hornet fans to check out the new pitch authority and it looks like perhaps some yaw oscillations dampening got better? I only flew for few minutes and didn't have a chance to run it through the grinder yet. Oh yes, I did notice steady 180 fps on a pancake screen over Beirut (everything maxed, no MSAA) Next step... VR, tomorrow.

OK... since 'karens' and Germans / Pearl Harbor stuff have been covered... I have a different outlook: perhaps ED's code spaghetti became self aware and is wreaking havoc 'after' the thorough internal testing

C'mon Gman, just pick any of relevant threads above and below and read through it and take your time. It's almost like quizzing a VR oriented 'ChatGPT' here...

I've been pretty happy with my rig's 60ish performance... even after this 'update' and didn't bother tuning anything with this CPU. Out of curiosity though... when going through BIOS after the initial setup, I noticed 'Legacy Game Compatibility Mode' in one of the menus. I know this is a fix for some DRM crap. I guess some old games see P cores and E cores as 2 machines... Basically, all it does is 'park' the E cores. They can be re-enabled with numlock at any time when in Windows. I wonder if this would have the same effect, hmm. I guess I have to try. Well, that's not the answer you were looking for. I'll give it a shot sometime later (when I 're-enable' DCS sometime later ), by disabling E cores both ways... see what happens.

I usually don't get melodramatic but the decision to roll it out without any considerations for all OB testers and giving them some idea what to look for was a bit arrogant. Not everyone here is as well versed and on the cutting edge of VR development as Mbuccia and few others... Even after the latest 'patch' or more precisely one day after, I started getting loooong load times at game start, only after my rig was rebooted. I've never seen this before. It took 6 min. to load DCS with no switches used on .exe. It happened 3 times. So... since there are no improvement in the only bird I fly, the Hornet, more problems compiled on top of that. (not the performance though, my rig is hauling ass on SteamVR)... time to bail out for some time, until ED figures out a better scheme. Oh, it probably be a good time to re-image my rig to a pristine Windows install from 2 months ago.

Hey, by all means it needs to go, hehe but no safety? 1 sec. perhaps? I can see how a selected Amraam (stores) has no time or need to communicate with radar and snatch an L&S track beforehand or LHAQ/HAQC locking on a maneuvering target at a close distance (aspect changing rapidly) but wait... we need to download. The heater? go and kill right now! Fine with me.

Just click on any/all threads above and below and the clear picture will emerge. If I were you, I'd try to get massively de-optimized, lol. After the next update is 'released', I'll wait before downloading, get some feedback and recon... if it's worth updating, I will.

So, would visual mode require the same delay?

Here's a short clip. You can see it doesn't take radical maneuvering to throw the ATFLIR off: Now, another short clip. The hot vehicles are quite visible now:

Learn something new every day. Never realized it takes that long.

I usually keep mine unplugged (power) and everything else connected before booting up my rig. For some reason, occasionally I would get '7-14' when booted up. Unplugging and re-plugging would wake it up every time. It happened regardless of how I set the startup in WMR. I'm actually able to use my rig's USB 'c' port directly instead of going through hub, which was necessary on my old setup. So far, I didn't have to replace the cable but I did get a scare once after I dropped the set. I had to unplug the cable from the set, then REALLY make sure it's plugged in properly. The connector could be finnicky.

I think cutting this delay in half would be a sufficient 'butterfinger' prevention feature. How about 9X.. this sucker could be even more dangerous if you have it following your HMD and fumbling around hotas. In either case Master Arm is our friend.

Thanks, done. @RealDCSpilot Looking forward to it.

Since I don't know how to change the title of this thread, to '... OpenVR' instead of OpenXR, perhaps a mod could do it.

OK, agreed. I didn't spend too much time selecting the proper nomenclature out of this chaos. I was still a bit 'Steamed' about the way the update was done. I've never used OpenComposite, never downloaded it. I never felt the need to do that. Yes, I was actually running SteamVR with OpenVR. I did install MS OpenXR Tools. Reprojection was disabled (I've never used it at any time) Res. at 100%. After the latest patch, I did try the switch with DCS.exe shortcut... well, actually I put the --force_OpenXR part outside of the quote mark. The way you wrote it, it should've probably be within... Anyways, the DCS loaded up, the hanger screen showed up and disappeared. That was it for me. I didn't feel like running through trial and error type of routine... I needed to smoke some Flankers and I did, eventually

I started getting occasional micro stutters on Open XR (No tool kit). Uninstalled OpenXR and fired up SteamVR (re-installed). Not a single stutter over any area in Syria. I'm running at 150% G2 res., no AA, AFx16, everything maxed. No tinkering, no spreadsheets or graphs. Immediate smoothness and speed. FPS is roughly the same as in OpenXR (50 ~ 90). I realize I'm an oddball here but until my rig runs OpenXR without hiccup and weeks of tinkering to achieve the same smoothness I get now right of the bat... I'm on Steam (offline). I just hope that OpenXR doesn't get 'mandated', at least until fully ready.

First, on the positive note: The IR image of stationary and moving vehicles shows hot spots right at the start of mission w/o any edits in ME. Now, the ability of ATFLIR to maintain the 'scene' stabilized position doesn't work very well. Even a mild turn that masks the spot momentarily causes the pod to drift off and it keeps drifting off. Not every time but it happens a lot. Litening is steady in any mode. So... Litening goes back in my inventory.

I just realized... 'Mixed Reality' - a new name for this time in history... ps, my next callsign is 'Mr OT' or worse.

Sure, who knows what else effects missile behavior. I've done a few different setups: coaltitude, lookup, lookdown, against a division in trail, line abreast. To my surprise the Amraams performed quite well. Out of all the missiles fired 3 were defeated by Flanker's extreme maneuvering at low altitudes but they were heading for the right targets. The Hornet's radar is a different story but that's a separate discussion.

I did a quick test in the latest OB, using the Hornet in a head-on setup aganst 2 Flankers, flying in right echelon. On the first hop I used the pinky switch to cycle the bandits. On the second engagement I used RAID to sort them out and designate. I did few more setups at different aspects and altitudes. So far it all worked fine. It's was all in SP though. https://youtu.be/UKN4GMk-BCw

Hmm, your post is right below mine so I assume you referring to me. If that's the case then NO. I like google and ms to collect my data, not some suckerberg.

Yes, yes, that's what that oldcrusty meant... thanks. That's his tiny contribution to this entire mess. The bottom line is: this cluster.... type of an update is needed on occasions to wake up complacent people like myself and make them dig in some more and learn new things...